What I have heard is that the transition on NOAAPort will be much like the
transition from the ETA to the NAM. The grids, model number, content, etc
would stay the same. We just know that when it happens, the output will be
from the RAP, not the RUC. Nothing in the grid will tell us.
One thing I did hear is that the low resolution 80km RUC grids will go
away. There will be no 80km RAP equivalent. Other than that, everything
else should be transparent.
Can someone confirm this?
Dan Vietor.
On Tue, Apr 24, 2012 at 12:35 PM, Unidata User Support <
support@xxxxxxxxxxxxxxxx> wrote:
>
> Users of CONDUIT and NGRID datastream model products:
>
> If the current schedule remains unchanged, RUC2 grids will be replaced
> by RAP (aka RR - Rapid Refresh) grids in the IDD CONDUIT and NGRID
> datastreams next Tuesday, May 1 or the following Tuesday, May 8 (ref:
> http://rapidrefresh.noaa.gov/).
>
> Unidata has been assured that the goal of the RUC2 -> RAP transition is
> to have little to no impact on end-users. This will be accomplished,
> in part, by keeping the model id and areal coverage the same in
> replacement RAP products as they are current RUC2 products. We believe
> that a completely transparent transition will be the case for NOAAPort
> SBN-delivered/IDD-relayed NGRID products. However, the impact of the
> transition on CONDUIT grids may or may not require end-user modifications
> to LDM pattern-action file entries.
>
> The following is representative INFO output from the LDM 'notifyme'
> utility captured during RUC2 -> RAP transition testing conducted by
> Unidata and NOAA:
>
> Feb 28 18:04:19 notifyme[2201] INFO: 21645 20120228180356.764 CONDUIT
> 000 data/nccf/com/rap/para/rap.20120228/rap.t12z.awp252pgrbf00.grib2
> !grib2/ncep/RUC2/#000/201202281200F000/HGHT/1000 hPa PRES! 000000
>
> Note that the LDM/IDD Product ID contains somewhat contradictory
> information:
>
> First part of the Product ID represents the name of the disk file
> that the product would have on the IDD toplevel nodes at NOAA/WOC:
>
> data/nccf/com/rap/para/rap.20120228/rap.t12z.awp252pgrbf00.grib2
>
> The second part of the Product ID is created by the LDM queue insertion
> process that cracks the GRIB2 message to get PDS values which are then
> interpreted for Product ID information:
>
> !grib2/ncep/RUC2/#000/201202281200F000/HGHT/1000 hPa PRES!
>
> The third and last part is a sequence number.
>
> 000000
>
> The small, contradictory difference in RAP Product IDs is the appearance
> of 'rap' in the file name portion and 'RUC2' in the "cracked" portion.
> The continued appearance of RUC2 in the second portion of the Product ID
> is a result of the model id being kept the same in RAP products as it
> has been in RUC2 products.
>
> If CONDUIT datastream users' pattern-action file patterns use information
> from the first or first AND second portion of the Product ID, changes
> will need to be made. If users' pattern-action file patterns only use
> information from the second portion of the Product ID, no change should
> be required.
>
> The following is a comparison of two 'notifyme'-listed Product IDs that
> hopefully illustrates the effect of RUC2 -> RAP transition:
>
> Existing CONDUIT RUC2 product:
>
> Feb 28 16:56:31 notifyme[2201] INFO: 22807 20120228165614.508 CONDUIT
> 024 data/nccf/com/ruc/prod/ruc2a.20120228/ruc2.t16z.sgrb20f09.grib2
> !grib2/ncep/RUC2/#000/201202281600F009/CAPE/255-0 hPa PDLY! 000024
>
> New CONDUIT RAP product:
>
> Feb 28 18:04:19 notifyme[2201] INFO: 21645 20120228180356.764 CONDUIT
> 000 data/nccf/com/rap/para/rap.20120228/rap.t12z.awp252pgrbf00.grib2
> !grib2/ncep/RUC2/#000/201202281200F000/HGHT/1000 hPa PRES! 000000
>
> NB: these listings are NOT for the same product/type of product
>
> The following is a simple example of the kind of change that one could
> make to an existing pattern-action file pattern to accommodate the RUC2 ->
> RAP transition:
>
> Existing entry for RUC2 hybrid grids:
>
> CONDUIT ^data/nccf/com/ruc/prod/ruc2a.(........)/ruc2.t(..)z.bgrb20.*#000
> FILE
>
>
> data/pub/native/grid/NCEP/RUC2/CONUS_20km/hybrid/RUC2_CONUS_20km_hybrid_\1_\200.grib2
>
> One way to accomodate the RUC2 -> RAP transition is to simply replicate
> the entry changing 'ruc' and 'ruc2' to 'rap':
>
> # This entry will continue to match RUC2 products
> CONDUIT ^data/nccf/com/ruc/prod/ruc2a.(........)/ruc2.t(..)z.bgrb20.*#000
> FILE
>
>
> data/pub/native/grid/NCEP/RUC2/CONUS_20km/hybrid/RUC2_CONUS_20km_hybrid_\1_\200.grib2
>
> # This one will match RAP products
> CONDUIT ^data/nccf/com/rap/prod/rapa.(........)/rap.t(..)z.bgrb20.*#000
> FILE
>
>
> data/pub/native/grid/NCEP/RUC2/CONUS_20km/hybrid/RUC2_CONUS_20km_hybrid_\1_\200.grib2
>
>
> There are, of course, a number of different ways to accomodate the
> change in Product IDs. The best approach to use will depend on your
> particular circumstance.
>
> Please send any/all questions about the upcoming RUC2 -> RAP transition
> to Unidata CONDUIT Support <support-conduit@xxxxxxxxxxxxxxxx>.
>
> Cheers,
>
> Tom Yoksas
> --
> ********************************************************************** <
> Unidata User Support UCAR Unidata Program <
> (303)497-8643 P.O. Box 3000 <
> support@xxxxxxxxxxxxxxxx Boulder, CO 80307 <
> ---------------------------------------------------------------------- <
> Unidata Web Support http://www.unidata.ucar.edu/support <
> ********************************************************************** <
>
> _______________________________________________
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
>
--
*Dan Vietor*
*Senior Systems Engineer*
Contractor, LS Technologies
Aviation Weather Center
Kansas City, MO
816.584.7211
