This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Doug, I started up a pqact process on motherlode this morning to match your specific CONDUIT file entries on ultrazone in pqactkwbcbin.conf. I will set up scouring of old days accordingly this afternoon. The data tree is rooted on motherlode from: /data/ldm/pub/native/tigge/ Since motherlode is not housed up at the mesa, it should not be affected by the mesa lab's power shutdowns. The idd.unidata.ucar.edu cluster keeps about 3 hours of data in the queue for your recovery when you come back up- we don't have any other backfilling service. Steve Chiswell Unidata User Support > The daily volume of NCEP data that we capture totals 5.6 GB. Could > you keep the current and prior day available on a motherlode > disk in our TIGGE directory/file structure (max 11.2 GB)? I'll copy > these files onto the MSS daily, and use the MSS to retrieve any > fields that are missing on > ultrazone. This would be extremely helpful for the assuring a > complete archive in cases of sporadic missing > fields on ultrazone, or downtime for ultrazone. > > I've attached the updated NCEP TIGGE pqact.conf. > > Doug > > > > On Feb 22, 2007, at 12:58 PM, Unidata IDD TIGGE Support wrote: > > > 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 > > > > > Ticket Details =================== Ticket ID: GAX-848665 Department: Support IDD TIGGE Priority: High Status: Closed