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

20040603: setup of bigbird and Level II data (cont.)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20040603: setup of bigbird and Level II data (cont.)
  • Date: Thu, 03 Jun 2004 13:30:21 -0600
>From: Unidata Support <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200405311647.i4VGlNtK006820 GEMPAK gpnexr2

Hi Gerry,

Chiz and I talked about the NEXRAD Level II and III setup on bigbird
earlier today.  We decided that it was better to have things setup so
that you don't have to modify $GEMTBL/config/datatype.tbl each time you
install a new GEMPAK distribution.  Instead, I changed where both the
Level II and Level III files are being stored on bigbird.

Previously, I had things setup to FILE into directories that follow:

/data/ldm/gempak/nexrad/craft/ccyymmdd/...
/data/ldm/gempak/nexrad/NIDS/ccyymmdd/...

Things are now setup as:

/data/ldm/gempak/nexrad/craft_all/ccyymmdd/...
/data/ldm/gempak/nexrad/NIDS_all/ccyymmdd/...

and

/data/ldm/gempak/nexrad/craft -> /data/ldm/gempak/nexrad/craft_all/ccyymmdd
/data/ldm/gempak/nexrad/NIDS -> /data/ldm/gempak/nexrad/NIDS_all/ccyymmdd

The links are (re)created once per hour by a CShell script run out
of cron:

#
# Create link to current CRAFT and NIDS dierctories
#
06 * * * *   util/idd_link.csh craft
07 * * * *   util/idd_link.csh NIDS

The downside to this configuration is that two pqact.conf files in
~ldm/etc need to be maintained:

pqact.gempak_craft
pqact.gempak_nexrad

The maintenance involves having things filed to:

/data/ldm/gempak/nexrad/craft_all/ccyymmdd
/data/ldm/gempak/nexrad/NIDS_all/ccyymmdd

Since GEMPAK comes with a script that creates pqact.conf files for the
various data types, and since the intention is for the user that
installs a new GEMPAK distribution to recreate the pqact.conf files, we
felt that it was better to rename the configuration files that get
local modifications and also to change the pqact entries in ldmd.conf.

The NEXRAD and CRAFT actions in ldmd.conf are now:

exec    "pqact -f NNEXRAD|WSI|FNEXRAD etc/pqact.gempak_nexrad.tamu"
exec    "pqact -f CRAFT -p BZIP2/K[A-D] etc/pqact.gempak_craft.tamu"
exec    "pqact -f CRAFT -p BZIP2/K[E-K] etc/pqact.gempak_craft.tamu"
exec    "pqact -f CRAFT -p BZIP2/K[L-R] etc/pqact.gempak_craft.tamu"
exec    "pqact -f CRAFT -p BZIP2/K[S-Z] etc/pqact.gempak_craft.tamu"

and the matching configuration files are:

~ldm/etc/pqact.gempak_nexrad.tamu
~ldm/etc/pqact.gempak_craft.tamu

I hope that this makes sense to you.  If not, please let me know and
I will take another run at explaining it.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.