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

[CONDUIT #MUM-195000]: Re: [conduit] 20150113: 2nd/final notice of impending change to CONDUIT GFS Product IDs

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.

  • Subject: [CONDUIT #MUM-195000]: Re: [conduit] 20150113: 2nd/final notice of impending change to CONDUIT GFS Product IDs
  • Date: Tue, 13 Jan 2015 14:11:40 -0700
Hi Pete,

re:
> Will the path leading up to the file name stay the same? i.e. the
> 
> data/nccf/com/gfs/prod/gfs.2015010512/
> 
> part?

Everything we've heard from NCEP suggests that the only change is to
the portion of the Product ID that contains the 'pgrb' clause.  The
thing that is unknown to us is whether or not the 2.5 deg fields will
be available for all time steps, or if they will continue to just
be for time steps >= 204 hours.

re:
> I've got that coded into my pqact lines too. For example,
> 
> CONDUIT
> data/nccf/com/gfs/prod/gfs.20([0-9][0-9])([0-9][0-9])([0-9][0-9])../gfs.t(..)z.pgrbf([0-9][0-9]).grib2\
> !grib2.*
> FILE    /data/grib2/gblav.\1\2\3\4_F0\5

I believe that you will only need to focus on the 
'gfs.t(..)z.pgrbf([0-9][0-9]).grib2'
portion of your extended regular expression.

NB:

- make a backup copy of your pattern-action file(s) before making any
  changes

- replicate the action(s) in each pattern-action file and make changes in
  the replicated action(s)

By the way, we have been testing LDM delivery of the 0.25 deg GFS global fields.
This test allows us to see what the new Product IDs should look like.  Here
is one example:

Jan 05 18:48:54 notifyme[20541] INFO:   398190 20150105164856.825 CONDUIT 358  
data/nccf/com/gfs/para/gfs.2015010512/gfs.t12z.pgrb2.0p25.f240 
!grib2/ncep/GFS/#000/201501051200F240/UREL/-2 K*m**2*kg-1*s-1 POTV! 000358

This example (extracted out of a 1.4 GB log of test CONDUIT relay) suggests 
that the
portion of the Product ID that you are asking about above will not change.  We 
will
know for sure tomorrow :-)

While we have your attention focused on CONDUIT...

Questions:

- what is your position on replacing the 0.5 deg GFS in the currently 
constituted
  CONDUIT datastream with the 0.25 deg GFS?

- will your IDD relay machine be able to handle the 0.25 deg GFS data?

  Our experience is that the 0.25 deg GFS volume is on the order of 20 GB
  for each run.

  What is the current size of your relay machine's LDM queue, and can it
  be increased?

re:
> Thanks!

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: MUM-195000
Department: Support CONDUIT
Priority: Normal
Status: Closed