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

Re: CONDUIT feed changes

Steve,

After the 12 UTC run on Wednesday August 9 should work for me.

One question.. I'm still splitting my request lines for CONDUIT into
5 separate ones as:

request                 CONDUIT "[05]$"         tgsv32.nws.noaa.gov
request                 CONDUIT "[16]$"         tgsv32.nws.noaa.gov
request                 CONDUIT "[27]$"         tgsv32.nws.noaa.gov
request                 CONDUIT "[38]$"         tgsv32.nws.noaa.gov             
request                 CONDUIT "[49]$"         tgsv32.nws.noaa.gov

Do I still need to be doing this, and should I similarly split
the ncepldm requests?  

Thanks,

Pete

In a previous message to me, you wrote: 

 >
 >David and Pete,
 >
 >I need to coordinate a change in your LDM request lines so that we
 >can implement the extended forecast output for the GFS0.5 degree and add
 >GRIB2 RUC files (which provide additional hourly forecast hours).
 >
 >I would like to enact the change after the 12Z 0.5 degree GFS run has
 >propagated
 > (eg after 1700Z) and would like to know if you can  implement the LDM
 >restart on Wednesday Aug 9.
 >
 >The change required will be:
 >
 >Current request line to tgsv32:
 >request     CONDUIT     ".*"     tgsv32.nws.noaa.gov
 >
 >New request lines:
 >request     CONDUIT     "ST.opnl"     tgsv32.nws.noaa.gov
 >request     CONDUIT     "nccf.*prod/(gfs.*pgrb2|ruc2a.*grib2)"      ncepldm.w
  >oc.noaa.gov
 >
 >The effect of the restriction of the tgsv32 to just the ST.opnl will
 >remove the feed of the ST.opnt  0.5 degree products. All other products
 >from TGSV32 are ST.opnl. I will
 >coordinate with NCEP/NWS afterwards to actually remove the 0.5 degree
 >products from being inserted on TGSV32. 
 >
 >The request line for ncepldm will receive the GRIB2 format 0.5 degree
 >gfs files and the grib2 ruc2a files.
 >
 >We are not removing the 1 degree GFS files which was a primary user
 >concern voiced, nor are we removing the GRIB1 RUC files, so users do not
 >have to worry about changing their processing of those products. The
 >GFS0.5 degree products will have a different naming convention that
 >users will have to adapt their pqact actions for. The additional
 >forecast hours in RUC GRIB2 should be a carrot for GRIB2.
 >
 >The additional data volume will be 32 additional GFS 0.5 degree files @
 >39MB per file ~= 1.25 GB per run (~5GB additional data per day), and
 >253MB per synoptic RUC run max ~= 5.5 GB GB/day additional RUC GRIB2
 >data.
 >
 >Please let me know if you can implement this change and any concerns on
 >timing
 >or data relay.
 >
 >Steve Chiswell
 >Unidata User Support
 >
 >-- 
 >Steve Chiswell <address@hidden>
 >Unidata


--
+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+
^ Pete Pokrandt                    V 1447  AOSS Bldg  1225 W Dayton St^
^ Systems Programmer               V Madison,         WI     53706    ^
^                                  V      address@hidden       ^
^ Dept of Atmos & Oceanic Sciences V (608) 262-3086 (Phone/voicemail) ^
^ University of Wisconsin-Madison  V       262-0166 (Fax)             ^
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+