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

[Datastream #CEH-596523]: Re: 20060227: Changes on unidata2 this week.

Hi Jerry,

I ws out of the office yesterday, hence this tardy reply...

First, an FYI:

We are transitioning to a new inquiry tracking system, and it will help us
greatly if emails could be sent to topic-based addresses.  For instance,
your email would have received quicker attention if it had been addressed
to 'address@hidden' (To: not CC:).  We just published
an CommunitE-letter article on this transition:

  Help Us Help You!
  http://www.unidata.ucar.edu/newsletter/2006feb/06febel.html#Article3

This article has a link to a web page that lists the various topic-specific
email addresses that we currently support:

  http://www.unidata.ucar.edu/support/topics.html


re:
> I got tied up with some problems with Meteosat, so I didn't finish this
> today,

No worries.

> but still plan to have it running next week.

Sounds good.

> Right now I am requesting the data, and have a pqact entry, but maybe
> you can answer what I'm sure is a simple question.
> 
> The name that the AREA composite is inserted with is:
> USAP.AMRC.Composite.infrared.YYYYMMdd.h(h)
> 
> For example the 3 UTC AREA composite is named
> USAP.AMRC.Composite.infrared.20060302.3
> 
> and the 12 UTC is named
> USAP.AMRC.Composite.infrared.20060302.12

It would be better/simpler if Matthew regularized his headers to always use two
digits for the hour of the product.

> Unfortunately there is also a jpg and png file inserted.  They are named
> as follows (using the 3 UTC example)
> 
> USAP.AMRC.Composite.infrared.20060302.3.jpg
> USAP.AMRC.Composite.infrared.20060302.03.png

Yup, I see them.

> What is the best way to request/process only the AREA file.  Probably an
> easy question, but I'm not a regular expression expert.

The best way is to be very explicit in the pattern you use to request the
data.  Currently, you are using:

request EXP     "USAP.AMRC.Composite.infrared.*"        ice.ssec.wisc.edu       
PRIMARY

This pattern is actually a bit problematic in that the '.*' at the end is
not needed AND can cause the regular expression parser to work harder
than needed.  An appropriate revision to this pattern that eliminates the
extra parsing would be:

request EXP     "USAP.AMRC.Composite.infrared"        ice.ssec.wisc.edu       
PRIMARY

One revision to the pattern that only requests the imagery in AREA file format
while at the same time being more explicit would be:

request EXP     
"^USAP\.AMRC\.Composite\.infrared\.........\.([0-9]|[0-2][0-9])$"        
ice.ssec.wisc.edu       PRIMARY

This pattern is more explicit in that it:

- identifies periods explicitly
- takes into account that the date is 8 and only 9 digits long
- specifies the set of times that are allowed: 0-9, 10-29 (OK, so 25-29 are not 
valid :-)
- explicitly ends after the time

Given the naming scheme that is being used in the Antarctic-IDD, the pattern 
could be shortened
to:

request EXP     "infrared\.........\.([0-9]|[0-2][0-9])$"        
ice.ssec.wisc.edu       PRIMARY

Finally the best way to check to make sure that the pattern being used is valid 
is to use
the LDM utility 'notifyme':

<as 'ldm' on unidata2.ssec.wisc.edu>
notifyme -vxl- -f EXP -o 10000 -p "infrared\.........\.([0-9]|[0-2][0-9])$"

For the 15Z hour this returned the following on unidata2:

Mar 03 19:36:21 notifyme[24526] NOTE: Starting Up: localhost: 
20060303164941.596 TS_ENDT {{EXP,  "infrared\.........\.([0-9]|[0-2][0-9])$"}}
Mar 03 19:36:21 notifyme[24526] NOTE: LDM-5 desired product-class: 
20060303164941.596 TS_ENDT {{EXP, "infrared\.........\.([0-9]|[0-2][0-9])$"}}
Mar 03 19:36:21 DEBUG: NOTIFYME(localhost) returns OK
Mar 03 19:36:21 notifyme[24526] NOTE: NOTIFYME(localhost): OK
Mar 03 19:36:25 notifyme[24526] INFO: 5e6dcd4c0fbd7eda7a44eb0bbd467898  4195904 
20060303174525.385  EXP 000  USAP.AMRC.Composite.infrared.20060303.15

> Thanks much.

No worries.

Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: CEH-596523
Department: Support Datastream
Priority: Normal
Status: Closed