[TIGGE #GAX-848665]: ncep TIGGE pqact.conf on motherlode

Doug,

I looked at your pqact and it appears that your second CONDUIT entry
for TMPK @ 300 will conflict with your 4th entry which
matches PRES|TMPK|HGHT @ .*.

Your 7th entry for TMPK|CINS|SWEM @ 0 will also have a TMPK conflict
with the 4th entry.

Your 1st entry which includes HGHT @ .* will conclict with the 4th entry
as above also.

These are all under the TIGGE specific entries. Having multiple FILE -overwrite
actions trying to hit the same file could be quite problematic, since pqact 
will 
continue processing through the pqact.conf file even after a first match. Would
you double check your intended processing with those actions?

I definitely want to keep a CONDUIT specific directory tree on motherlode that 
matches the NCEP 
directory name so that the receipt can be compared vs the inventory. Filing the 
data separately 
for TIGGE may be possible but will have to check on space availability. I don't 
think that there 
is enough space for 5 days presently. It may be possible to cross link the 
actual data file name to
your specific file name convention. 


Steve Chiswell
Unidata User Support

 Steve,
> 
> Would it be possible to run our NCEP specific pqact.conf on
> motherlode to save TIGGE NCEP data?
> I realize you're grabbing the complete GENS forecast files in native
> NCEP structure,
> but it would be much easier for us to use if NCEP's data is saved in
> the same structure
> as we save it on ultrazone for TIGGE.  As NCEP is unable to provide
> resend capability of
> any kind, we could potentially use data saved on motherlode as a
> backup to ultrazone, assuming all fields
> are consistently received as has been stated.  If this is possible,
> could you keep ~5 days worth on motherlode's disk?
> 
> Thanks,
> Doug
> 
> 
> 


Ticket Details
===================
Ticket ID: GAX-848665
Department: Support IDD TIGGE
Priority: Normal
Status: Closed