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

20000922: LWTOA3 image data missing from Unidata-Wisconsin datastream (cont.)



>From: Thomas Don Aratari <address@hidden>
>Organization: University of Michigan
>Keywords: 200009210254.e8L2sbb18779 Unidata-Wisconsin ldm-mcidas pnga2area 

Tom,

>The files are still called AREA1### not AREA0###
>
>the onesky.engin.umich.edu machine gets fed from yin.engin.umich.edu (our
>main machine)

OK.

>I did the notifyme on yin.engin and i saw both types coming thru.

This makes sense since onesky is seeing all products.
>
>Here's my pqact.conf entry: (from onesky.engin.umich.edu)

>MCIDAS  ^pnga2area Q1 (..) (....) (.*) (.*) (.*) (........) (....)
>        PIPE    -close /sky1/local/ldm-mcidas-7.6.4/bin/pnga2area
>        -a /usr/local/ldm/data/mcidas/SATANNOT
>        -b /usr/local/ldm/data/mcidas/SATBAND
>        -l /logs/mcidas.log -v
>        -d /usr/local/ldm/data/mcidas -r \1,\2

There are two things to change here:

o put a tab between '-close' and '/sky1/local/ldm-mcidas-7.6.4/bin/pnga2area'
o change and the second selection parentheses on the header line

I recommend you change your entry to:

MCIDAS  ^pnga2area Q1 (..) (.*) (.*) (.*) (.*) (........) (....)
        PIPE    -close
        /sky1/local/ldm-mcidas-7.6.4/bin/pnga2area
        -a /usr/local/ldm/data/mcidas/SATANNOT
        -b /usr/local/ldm/data/mcidas/SATBAND
        -l /logs/mcidas.log -v
        -d /usr/local/ldm/data/mcidas -r \1,\2

The BIG culprit is the second selection parenthsis.  The default AREA file
numbers for the CIMSS products are 4 digits long, and three digits long
for the "normal" GOES images. This can be seen from the headers contained
in the notifyme listing from onesky:


Since these AREA numbers are not constrained
to be any particular length, it is best to use the '(.*)' selector.

>I tried having that script use the AREA115? and AREA114? but the output is
>all black on the .GIF after i run the xsat program...

I suspect that xsat can't handle the CIMSS products, but I have no way
of knowing.  Have you tried running it by hand and see if there area
any error messages.

notifyme -vxl- -f MCIDAS -o 3600 -h onesky.engin.umich.edu
Sep 21 22:00:50 notifyme[22115]: Starting Up: onesky.engin.umich.edu: 
20000921210050.247 TS_ENDT {{MCIDAS,  ".*"}}
NOTIFYME(onesky.engin.umich.edu) returns OK
Sep 21 22:00:54 notifyme[22115]: NOTIFYME(onesky.engin.umich.edu): OK
Sep 21 22:00:54 notifyme[22115]: d6ceaabbd7c8568d384dd79b3490a3ed     9782 2
0000921210606.778  MCIDAS 000  pnga2area Q1 U3 202 GRAPHICS UNKBAND 5km 
20000921 2059
Sep 21 22:00:54 notifyme[22115]: 1db66532d041a451784b92074061fadf   133016 2
0000921211028.991  MCIDAS 000  pnga2area Q1 U1 192 GOES-9_IMG UNKBAND 20km 
20000921 1800
Sep 21 22:00:55 notifyme[22115]: d87536de1c13ddd7039e32ac610ef78c    87565 2
0000921211511.793  MCIDAS 000  pnga2area Q0 CA 1100 GOES-10_SND UNKBAND 14km 
20000921 2000
Sep 21 22:00:55 notifyme[22115]: 65d4a9ba0a4da18a20433b84b018e2c9   160135 2
0000921211634.061  MCIDAS 000  pnga2area Q1 UB 173 GOES-10_IMG 6.8um 8km 
20000921 2100
Sep 21 22:00:55 notifyme[22115]: 0d6764fb1aaf4bee024009a5456f178b   989282 2
0000921211720.883  MCIDAS 000  pnga2area Q1 U5 131 GOES-10_IMG 10.7um 4km 
20000921 2100
Sep 21 22:00:55 notifyme[22115]: b2f14025c753b36b0d1f1a9a26dcb263  1693926 2
0000921211712.645  MCIDAS 000  pnga2area Q1 U9 121 GOES-10_IMG 0.65um 4km 
20000921 2100
Sep 21 22:00:56 notifyme[22115]: e85ff8028d9232a37e6bfee3418c0c80    60430 2
0000921211809.942  MCIDAS 000  pnga2area Q0 CD 1130 GOES-10_SND UNKBAND 14km 
20000921 2000
Sep 21 22:00:56 notifyme[22115]: 266e0e79acf863cd9ec780d582541f2f    60858 2
0000921213109.253  MCIDAS 000  pnga2area Q0 CB 1110 GOES-10_SND UNKBAND 14km 
20000921 2000

The headers in this list are:

pnga2area Q1 U3 202  GRAPHICS    UNKBAND 5km  20000921 2059
pnga2area Q1 U1 192  GOES-9_IMG  UNKBAND 20km 20000921 1800
pnga2area Q0 CA 1100 GOES-10_SND UNKBAND 14km 20000921 2000
pnga2area Q1 UB 173  GOES-10_IMG 6.8um   8km  20000921 2100
pnga2area Q1 U5 131  GOES-10_IMG 10.7um  4km  20000921 2100
pnga2area Q1 U9 121  GOES-10_IMG 0.65um  4km  20000921 2100
pnga2area Q0 CD 1130 GOES-10_SND UNKBAND 14km 20000921 2000
pnga2area Q0 CB 1110 GOES-10_SND UNKBAND 14km 20000921 2000
          ^  ^  ^    ^           ^       ^    ^        ^
          |  |  |    |           |       |    |        |__ Time [HHMM]
          |  |  |    |           |       |    |________ Date [CCYYMMDD]
          |  |  |    |           |       |____ resolution
          |  |  |    |           |_______ band (wavelength)
          |  |  |    |___________ SATellite
          |  |  |___ default AREA file number
          |  |__ McIDAS routing table product code
          |_ time indicator [Q0..Q4]

The CIMSS products are broadcast under the 'Q0' time indicator, and the
"normal" GOES images are broadcast under the 'Q1' time indicator.

>Any more ideas ? :)

I a confident that as soon as you change your pqact.conf entry and send
a HUP to pqact, you will once again be decoding the images you want.

Tom

>From address@hidden Fri Sep 22 17:07:35 2000
>Subject: Re: 20000922: LWTOA3 image data missing from Unidata-Wisconsin 
>datastream (cont.) 

Tom

Yes! its working.. I'm getting the GOES images now, and xsat is pumping
the IR/SAT images out..

thanks for all your help! .. and sorry that i missed the email a ways back
about the McIDAS change :)

Thanks again

Tom

--------------------------------------------------------------
Thomas Aratari                  address@hidden
UofM ITD Contract Services      Unix System Administration
Pager: 670-3861                 E-Page: address@hidden
AOSS Building - LDM/Sys Admin           (734) 764-4584
Medical Science Building II - Sys Admin (734) 763-5558

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.