[thredds] 20100517: impending change in IDD NEXRAD3 datastream

• To: ldm-users@xxxxxxxxxxxxxxxx, gembud@xxxxxxxxxxxxxxxx, mcidas-x@xxxxxxxxxxxxxxxx, thredds@xxxxxxxxxxxxxxxx
• Subject: [thredds] 20100517: impending change in IDD NEXRAD3 datastream
• From: Unidata User Support <support@xxxxxxxxxxxxxxxx>
• Date: Mon, 17 May 2010 17:06:53 -0600

All,

The NWS will be conducting a test of the backup AWIPS NCF (NOAAPort) this
Wednesday, May 19.  If this test goes like the past few, there _will_
be problems with GRIB2 messages sent in the nwstg2 channel, and the
contents of that channel get relayed in the IDD NGRID datafeed.  During the
last test of the backup NCF, run-together GRIB2 messages would cause
data ingestion to die on systems running the UPC NOAAPort ingest software.

Steve Chiswell (DOE/Savannah River National Laboratory) has implemented
code modifications and GRIB2 table updates to the UPC NOAAPort
ingest package that should prevent the data ingest problems seen previously.
Administrators of systems that feed NOAAPort data into the IDD have been
asked to upgrade to the new code on or about 0Z on Wednesday, May 19
(18 MDT Tuesday).

As a by-product of the ingest code update, the NEXRAD Level III and TDWR
Digital Precipitation Array (DPA) products (SDUS8) are being moved
from distribution in HDS to NEXRAD3.  If you are currently processing
the DPA products, you will need to make a change in LDM pattern-action
file processing.  You should implement this change _before_ 15Z on
Wednesday, May 19!

The following are examples of 'pqact' pattern-action file entries
that will process DPA products in the same way that other NEXRAD
Level III and TDWR products are processed:

GEMPAK

#################################################################################
#
# NEXRAD specific pqact processing
#
# Feedtypes included in these actions are:
#
#       NEXRAD, WSI
#
#################################################################################
#
# Use this action to file everything
NEXRAD  ^SDUS[23578]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...)
        FILE    -overwrite      -close
        data/gempak/nexrad/NIDS/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3


McIDAS

#########################################################################
#
# NEXRAD3 (NOAAPORT NEXRAD Level III products) section using pqact's FILE
#        action
#
# NOTEs:
#        - stop and restart the LDM to activate
#
#########################################################################

# All NEXRAD Level III products
#        SDUS53      KDVN  20          22          15           /p N0R  DVN
NEXRAD3 ^SDUS[23578]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...)
        FILE    -close
        
data/mcidas/images/NIDS/(\1:yyyy)(\1:mm)\1/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3


THREDDS

#
# level3 radar from NEXRAD feedtype
#
NNEXRAD ^SDUS[23578]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...)
        FILE    -close
        
data/pub/native/radar/level3/\4/\5/(\1:yyyy)(\1:mm)\1/Level3_\5_\4_(\1:yyyy)(\1:mm)\1_\2\3.nids


NB:  After making changes to LDM pattern-action files, you should test
to see if the changes have any simple errors using the LDM utility 'ldmadmin':

<as 'ldm'>
-- make change(s) to one or more 'pqact' pattern-action files

ldmadmin pqactcheck

-- if there are no errors indicated, then tell the LDM to start using the
   newly changed action(s)

ldmadmin pqactHUP


Please send any questions/comments/concerns about the datastream change to
support-idd@xxxxxxxxxxxxxxxx

Cheers,

Tom Yoksas
Unidata User Support
--
********************************************************************** <
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  <
********************************************************************** <