20050201: Unidata McIDAS-XCD Trouble (cont.)

>From: "James T. Brown" <address@hidden>
>Organization: MSU
>Keywords: 200501201933.j0KJXOv2020815 McIDAS-XCD ADDE

Hi Jim,

re: previous slow response

>Not a problem.   Thanks to all your help, everything seems to be
>running pretty well.

>I didn't notice the extra "ingetext" process.   For example, when
>I had the following entries in my "pqact.conf" file:
>
>WMO     ^([^HIJOLMPSYZ]|S[^D]) 
>        PIPE    xcd_run DDS
>
>HRS     ^.*    
>        PIPE    xcd_run HRS
>
>#IDS|DDPLUS      ^.*    
>#        PIPE    xcd_run DDS
>
>
>I noticed the following processes running:
>
>accas{ldm} 36:% ps -ef | grep xcd
>     ldm 17817 17814  0 15:43:12 ?        0:00 startxcd.k
>     ldm 17855 17817  0 15:43:13 ?        0:00 startxcd.k
>     ldm 24208 10846  0 15:53:06 pts/1    0:00 grep xcd
>
>
>accas{ldm} 37:% ps -ef | grep inge
>     ldm 17825 17816  0 15:43:12 ?        0:00 ingetext.k DDS
>     ldm 17852 17827  1 15:43:13 ?        0:11 ingebin.k HRS
>     ldm 17860 17825  1 15:43:13 ?        0:10 ingetext.k DDS
>     ldm 17827 17816  0 15:43:12 ?        0:00 ingebin.k HRS
>     ldm 25015 10846  0 15:53:24 pts/1    0:00 grep inge

>However, when I change the "pqact.conf" file to the following:
>
>WMO     ^([^HIJOLMPSYZ]|S[^D]) 
>        PIPE    xcd_run DDS
>
>HRS     ^.*    
>        PIPE    xcd_run HRS
>
>IDS|DDPLUS      ^.*    
>        PIPE    xcd_run DDS
>
>The following list of processes appear:
>
>accas{ldm} 45:% ps -ef | grep xcd
>     ldm 29858 29855  0 15:54:55 ?        0:00 startxcd.k
>     ldm 29897 29858  0 15:54:56 ?        0:00 startxcd.k
>     ldm   715 10846  0 15:55:05 pts/1    0:00 grep xcd
>
>accas{ldm} 46:% ps -ef | grep inge
>     ldm 29890 29865  0 15:54:56 ?        0:00 ingebin.k HRS
>     ldm 29865 29857  0 15:54:55 ?        0:00 ingebin.k HRS
>     ldm 29891 29863  2 15:54:56 ?        0:01 ingetext.k DDS
>     ldm 29863 29857  0 15:54:55 ?        0:00 ingetext.k DDS
>     ldm  1575 10846  0 15:55:18 pts/1    0:00 grep inge

Hmm...  I was expecting that you would see two pairs of 'ingetext.k DDS'
invocations.  I am pleasantly relieved that you only saw one!

>The "pqing" to my NOAAPORT is enabled, but never seen the extra processes.

If it isn't there, there is no need to worry :-)

>A bit strange.  However, since it doesn't make sense to have the
>extra "IDS|DDPLUS" entry, I have simply removed it.

Good.  This is tidier anyway.

>I will worry about the changing the HRS entry when I enable the
>grid decoders.

OK.

re: FNEXRAD feed

>Great.  I already have an entry to capture some of the FNEXRAD
>products in my "pqact.conf" file, but do not believe I am currently
>setup/authorized to receive such products.   Do I have to contact
>my primary data source or can I simply add a REQUEST entry to my
>"ldmd.conf" file.   Here are my current REQUEST entries:
>
>request UNIDATA|FSL     ".*" f5.aos.wisc.edu PRIMARY
>#request UNIDATA|FSL    ".*" flood.atmos.uiuc.edu ALTERNATE
>request NLDN    ".*" striker2.atmos.albany.edu PRIMARY
>request CONDUIT "/MT.ruc_CY" f5.aos.wisc.edu

The easy way to test to see if you are already allowed to receive
data is to use the LDM notifyme utility.  For instance, if you
want to receive FNEXRAD data from f5.aos.wisc.edu, you could use:

notifyme -vxl- -f FNEXRAD -h f5.aos.wisc.edu -o 3600

If you are allowed by f5.aos.wisc.edu, you should see the products it
has received in the past hour (3600 seconds) in the FNEXRAD feed.  If
you are not allowed, you will be informed that you aren't.

re: NOAAPORT

>Thanks for the information on the NOAAPORT change.  I will have to
>pass this information on to Jeff Andresen.   I was a little worried
>that the upgrade/replacement was going to cost a lot more than the
>estimates you provided.  I am sure that Jeff will be a bit relieved.

Please remember that the costs I sent along are for hardware.  What
your NOAAPORT vendor may charge to upgrade your system is an entirely
different matter.

>Please (or have someone from Unidata) let me know what I need to
>do to enable access to the FNEXRAD feed.

First, check to see if either UW or UI have allows for FNEXRAD data
for you.  If they don't, you will need to send an email to the LDM
contact at the site(s) you want to feed from requesting that they
add an allow for the FNEXRAD data for your LDM machine.

The LDM contact email addresses for UW and UI are:

UW - Pete Pokrandt <address@hidden>
UI - David Wojtowicz <address@hidden>

>Since I am getting NNEXRAD
>via NOAAPORT, I don't think I need to bother getting a duplicate of
>that product via IDD,

Exactly.

>but the FNEXRAD products would be nice (especially
>the composites images - again, we would like to capture/store products
>of the NEXRCOMP group if possible).

Yup, you need FNEXRAD since the radar composites are included in it.
If you want to take a look at what is available, "point" (DATALOC ADD NEXRCOMP)
at one of the cooperating community servers and take a look.  This is
easily done through the MCGUI by:

- click on the client routing table configuration button (the button just
  to the right of the button with the red Z)

- click on the IMAGE tab

- click on the downarrow for NEXRCOMP and select one of the servers in the
  list

After pointing at one of the available servers, you should be able
to look at the various composites that are available.

Cheers,

Tom
--
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.