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

19990105: ldm & Gempak question

Mark,

I provided an update to areaInfo back in July when the
GOES-10 switch was made so that the program would
recognize the new satellite:
see...
http://www.unidata.ucar.edu/glimpse/gembud-list/1209
http://www.unidata.ucar.edu/glimpse/gembud-list/1213

I have reposted the source for building areaInfo under
~gbuddy/nawips-5.4/patches/areainfo.tar.Z

The Linux binary through patch8 is at:
~gbuddy/nawips-5.4/binary/linux/gempak5.4_pl8_linux.tar.gz

Regarding WSI data reception, that data is sent directly from
WSI, and therefore, if you change your LDM host, you must
inform WSI so that they can send it to your new machine.
Also, be sure your ldmd.conf file has the appropriate
accept entry for receiving the data from WSI:
accept  WSI     .*      ^[a-z].*\.uni\.wsicorp\.com$


Steve Chiswell
Unidata User Support


>From: Mark Tucker <address@hidden>
>Organization: .
>Keywords: 199901051459.HAA29432

>
>We do not appear to be receiving any nids data.  Both the entries for
>gempak and for mcidas ingestion of the products do not produce any output.
>I've included the entries from pqact.conf.  I haven't made any changes to
>these entries since we switched servers but we have never received nids
>data since the switch.  The gempak entry is just a pipe to a file so I'm
>wondering if there has been a change in the headers for these recently.
>
>From our pqact.conf:
>================================================================ 
>
>WSI 
>^NEX/(...)/(.*)/..([0-9][0-9])([0-1][0-9])([0-3][0-9])([0-2][0-9])([0-6][0-9])
>        FILE
>        -close /usr/local/ldm/data/gempak/rawnids/\2/\6/\3\4\5\6\7.\1.wsi
>---snip---
>
>WSI
>^NEX/(...)/(BREF1)/..([0-9][0-9])([0-1][0-9])([0-3][0-9])([0-2][0-9])([0-6][0-
> 9])
>        PIPE    -close
>        nids2area -d /usr/local/ldm/data/mcidas/xdata 9001 \1 DIALPROD=R1
>\3%j \6\700 DEV
>=CCN
>
>WSI
>^NEX/(...)/(BREF2)/..([0-9][0-9])([0-1][0-9])([0-3][0-9])([0-2][0-9])([0-6][0-
> 9])
>        PIPE    -close
        nids2area -d /usr/local/ldm/data/mcidas/xdata 9002 \1 DIALPROD=R2
>\3%j \6\700 DEV
>=CCN
>
>WSI
>^NEX/(...)/(BREF3)/..([0-9][0-9])([0-1][0-9])([0-3][0-9])([0-2][0-9])([0-6][0-
> 9])
>        PIPE    -close
>        nids2area -d /usr/local/ldm/data/mcidas/xdata 9003 \1 DIALPROD=R3
>\3%j \6\700 DEV
>=CCN
>
>===========================================================================
>
>On another Garp/Gempak related item, we seem to be having trouble
>processing satellite data from the Mcidas AREA files for the GOES-10
>satellite.  What appears to be happening is that the script file,
>/usr/local/gempak/bin/scripts/nsat_links, runs $GEMEXE/areaInfo on the
>AREA files which returns "g10im" instead of GOES-10.  The links are
>created in the 4km and 8km directory under g10im but list as UNK instead
>of VIS, IR or WV as typically happens with the GOES-8 data.  I've checked
>all the gempak and garp configuration files that I know could affect this
>but have not been able to correct the situation.  
>
>I also have changed the passwords to our systems because a minor security
>problem we had here.  I will call with the passwords later today or you
>may call me at 802-626-6375.
>
>
>
>Mark Tucker
>Information Technology
>Lyndon State College
>address@hidden
>
>