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

[McIDAS #XGD-732939]: McIdas and LDM

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: [McIDAS #XGD-732939]: McIdas and LDM
  • Date: Mon, 19 Mar 2007 05:01:42 -0600
Hi Ben,

I guess my comments will continue to straggle in as I take fresh looks at
the setup on climate-db...

This morning I noticed that your ~ldm/etc/pqact.conf file did not have an
action that would process the NNEXRAD data that was being requested from
webcat. I added the action at the bottom of the file.

After successfully FILEing the NNEXRAD data, I added a crontab entry to
scour the data to leave 64 images online.  The scouring script for the
NNEXRAD images runs every three hours like the scouring script for the
UNIWISC images.  I also adjusted the ADDE dataset definition parameters
for the NNEXRAD images in ~mcidas/workdata/NNEXRAD.CFG.  Your McIDAS
setup can now access the NNEXRAD images.

Speaking of UNIWISC images, I saw that you were requesting both the UNIDATA
and UNIWISC feeds.  Since UNIDATA contains UNIWISC (UNIDATA is a compound
feed type that includes WMO and UNIWISC), I deleted the separate request
for UNIDATA from your ~ldm/etc/ldmd.conf.

I further see that you are not requesting the FNEXRAD feed from webcat,
and that webcat is likely not requesting this feed of NNEXRAD composites
from any upstream (although I seem to remember setting this up at one
time on webcat).  You may want to investigate ingesting the FNEXRAD feed
as the NEXRAD composites are very useful products.

One last thing for this email: I note that logging to ~ldm/logs/ldmd.log
is not working.  A quick look at /etc/syslog.conf shows that the setup
for logging does not follow the instructions listed in the Unidata LDM
web pages.  In order to fix this, I would need 'root' access on your machine.

I have to get ready for a meeting now...  I will take a new look at the setup
on unidata-db this evening.

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: XGD-732939
Department: Support McIDAS
Priority: Normal
Status: Closed