[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

19990923: McIDAS: Route Table and Missing Data Products?

>From: Michael Keables <address@hidden>
>Organization: DU
>Keywords: 199909231536.JAA06546 McIDAS-X RedHat 6.0 Linux


>McIDAS is loaded on the Dells and ready for use (as soon as we get the NFS
>problem worked out. We're getting a "Program Not Registered" message from
>the RPC call when trying to mount /data/ldm. Suggestions?)

I will ask our system administrator about this tomorrow if he is in.

>I just looked at the Routing Table on cyclone and the following data
>products are still not listed: MA (Surface MD), NF (Global Init. Grid), NG
>(Early Domestic Prod), all of the NIDS products, and RM and RS (mand and
>sig UA).

These were the non-image products that were deleted from the Unidata-Wisconsin
datastream on July 1.  The MA, RM, and RS (surface, mandatory upper air,
and significant level upper air) products are replaced by surface
and upper air MD files decoded by XCD.  You should SUSpend or delete
these products from the McIDAS routing table to remind yourself that
the entries will no longer update.

The NG and NF products were also removed from the Unidata-Wisconsin
datastream on July 1.  The information that they had was a small fraction
of what is now available from the XCD GRID decoder.  If you need to
recreate the NG and NF products (to make the actions in the Fkey and
MCGUI interfaces work), you should investigate using the 7.60 routine
UWGRID.  A shell script named uwgrid.sh, installed in the ~mcidas/workdata
directory, can be run from cron (after you edit uwgrid.sh and set McIDAS
environment variables to match your setup) to recreate the NG and NF
products.  Route PostProcessing can also be done if the NG and NF entries
in the routing table are active.  One caution, however:  I have noted
that there do not seem to be any global AVN grids on any of the McIDAS
systems that I have access to.  I am assuming that something changed
of late that may require a code change in the XCD GRID decoder.  The
really bad part about this is I don't have time right at the moment
to give this the attention that it deserves.

>I did a notifyme to be sure the IDD and HRS data are flowing (they are),  
>checked to be sure that startxcd is running (it is), and viewed the Decoder
>Status display via STAT in McIDAS (it shows DDS and HRS ingestors are
>active and list the sao, rab, syn, shp, f14, pir, ter, grib, and mdr
>decoders with the most recent time stamp.) I assume this means the data are 
>being ingested and decoded, but the products aren't showing up on the
>Routing Table.

Right.  The XCD decoded products do not show up in the routing table.
The routing table pertained to Unidata-Wisconsin products only.  The
image PostProcesses still work since there is still imagery being
sent in the UW stream.

>I had thought that releasing the suspended products would take care of
>this but it didn't.



I think that the explanation above will explain what is going on.  If
not let me know and I can provide a (few) more details.

>Thanks in advance.



>From address@hidden  Thu Sep 23 19:03:03 1999

I forgot to include in the previous message that you do not getting NIDS
products unless you subscribe to WSI for them.  If you have done this, it
means that the NIDS products are not being turned into McIDAS image
files (AREAs).  In fact, McIDAS now handles NIDS products in their
native format (both for WSI sent and those few unencrpyted ones in the
NOAAPORT datastream).  At some point in the future (at least a year off
and maybe more), the NWS will be broadcasting all of the NIDS products
in NOAAPORT.  At that point you will have access to more radar data
than you may want.

Sorry I forgot to include a comment about the NIDS products in my
previous email.


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.