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

[IDD #UUK-983031]: help needed

Hi Heath,

re: what is your objective for the RUC2 grids
> Yes we want to file each individually

OK.  There are MANY ways to process the data; the following
example is one to do this for the RUC2 grids in the CONDUIT
data feed:

Create the following entries in the ~ldm/etc/pqact.conf file:

#
# RUC2 grids
#
# hybrid
CONDUIT 
^data/nccf/com/ruc/prod/ruc2a.(........)/ruc2.t(..)z.bgrb20.*ncep/(.*)/#000
        FILE    -close
        
data/conduit/RUC2/CONUS_20km/hybrid/RUC2_CONUS_20km_hybrid_\1_\200_\3.grib2
#
# surface
CONDUIT ^data/nccf/com/ruc/prod/ruc2a.(........)/ruc2.t(..)z.sgrb20.*/(.*)/#000
        FILE    -close
        
data/conduit/RUC2/CONUS_20km/surface/RUC2_CONUS_20km_surface_\1_\200_\3.grib2
#
# pressure
CONDUIT ^data/nccf/com/ruc/prod/ruc2a.(........)/ruc2.t(..)z.pgrb20.*/(.*)/#000
        FILE    -close
        
data/conduit/RUC2/CONUS_20km/pressure/RUC2_CONUS_20km_pressure_\1_\200_\3.grib2

Important notes:

1) various of the white space characters in these _example_ actions are tabs, 
not
   spaces.  Here is a marked up version of the first entry above that shows 
which
   white space characters are actually tabs:

CONDUIT<tab>^data/nccf/com/ruc/prod/ruc2a.(........)/ruc2.t(..)z.sgrb20.*/(.*)/#000
<tab>FILE<tab>-close
<tab>data/conduit/RUC2/CONUS_20km/surface/RUC2_CONUS_20km_surface_\1_\200_\3.grib2

2) these actions will separate grids of different types (hybrid, surface, 
pressure)
   into different directory structures.  This may or may not be what you/your 
user
   wants.

3) it is the user's responsibility (or your's) to setup crontab-initiated 
scouring
   of data that is received.

   You can use the LDM 'scour' utility to scour keeping full day sets.

4) in looking at the ~ldm/etc/ldmd.conf file that you sent, I do _not_ see
   that you are attempting to do anything with the data you are receiving.

   What I mean is that your ldmd.conf file shows that you are not EXECing pqact
   at all.  The default 'pqact' invocation is commented out:

#EXEC   "pqact"

This entry ** when uncommented ** will result in an instance of 'pqact' running
at LDM startup.  That instance of 'pqact' will use as its pattern-action file
~ldm/etc/pqact.conf to process data.  My example actions above when correctly
put into your pqact.conf file (i.e., with no typos, etc.) will be used to
process the CONDUIT data.

5) whenever a change(s) is made to the ~ldm/etc/ldmd.conf file, the LDM must be
   stopped and restarted for the change(s) to take effect:

   <as 'ldm'>
   ldmadmin restart

Question:

- how have you been processing the KLIX NEXRAD2 data you are requesting
  from idd.cise-nsf.gov?

  It looks like all you are doing/can do with the data is relay it to another
  machine. 
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: UUK-983031
Department: Support IDD
Priority: Normal
Status: Closed