[Support #DYC-541261]: Parsing models (Eta/NAM) for ldm distribution

> Steve,
> 
> What are you using to parse the Eta/NAM files into components for LDM
> distribution?  Is the code available?  While we're hoping to see the
> AWIP32 and AWIP12 grids become available, for the SCOOP project, we need
> to be able to distribute these products to our modelers now.  We're
> already doing it via LDM but since we're not parsing to components
> (sending the whole NAM hourly file) I suspect we're seeing some lost
> data due to filesize.
> 
> At the same time... most of our users really need only the subset of 10m
> winds and surface pressure for their model init's.  If we can reduce
> what we're sending, we're ahead of the  game.
> 
> If you can point me in the right direction, I'd appreciate it.
> 
> Thanks, Gerry
> --
> Gerry Creager -- address@hidden
> Texas Mesonet -- AATLT, Texas A&M University
> Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.862.3983
> Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843
> 


Gerry,

The long and sort of it:

No, the code wasn't available as a distribution since the CONDUIT host
that I created the code for didn't have any compilers of its own, so I
never had to make a distribution for general building. Rather, I just
built the code under AIX here as needed.

I did some porting to the current LDM that is available, and have
posted the distribution now as:

ftp://ftp.unidata.ucar.edu/pub/gribinsert/gribinsert-1.1.tar.gz

The tar file can be downloaded and unpacked into the LDMHOME (generally
~ldm) directory where you have downloaded and built LDM (and must have
created the appropriate runtime/ links to runtime/include, runtime/bin,
runtime/lib, runtime/src (if you haven't done this already per the LDM
installation instructions).

after unpacking, cd to gribinsert-1.1 and build with:
make all install

If successful, it will install gribinsert into ~ldm/runtime/bin, and
copy some grib tables into ~ldm/etc.

The program is run like:

gribinsert -f EXP gribfile

(assuming you want to insert the data into your ldm.pq (otherwise
override that using -q).

The file will place each grib message within the grib file into the
queue as a separate LDM product using the file name and a seuence
number for each grib product. Additionally, it attempts to add a
descriptive name for the product enclosed by "!" characters, eg the LDM
product header will be"

filename !descriptive name! seqno

It will also create a .status.filename file with an inventory of all
the grib products within the file (unless you specify "-S" on the
command line of gribinsert).

Steve Chiswell
Unidata User Support


Ticket Details
===================
Ticket ID: DYC-541261
Department: Support CONDUIT
Priority: Normal
Status: Closed