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

[McIDAS #ECE-924432]: Creating and populating a local ADDE server

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 #ECE-924432]: Creating and populating a local ADDE server
  • Date: Tue, 30 Apr 2013 10:36:22 -0600
Hi Kevin,

Well, what I was seeing was making no sense to me... for instance,
I was seeing ~ldm/logs/ldm-mcidas.log entries that indicated
that the ldm-mcidas 'pnga2area' decoder was running even though
the ~ldm/etc/pqact.conf_mcidasB pattern-action file clearly indicated
that the UNIWISC products should be processed (filed) by ~ldm/util/ldmfile.sh.
That was getting VERY frustrating indeed, because I could simply not figure
out what was going on.

I finally resorted to doing a clean build of ldm-6.11.4 after making
sure that the environment defined in ~ldm/etc/.cshrc was correct AND
was in scope before doing the new build/re-install.

After the rebuild/reinstall, I started the LDM and everything came
up working as it should (meaning that XCD is running nicely, and
all images are being processed through ~ldm/util/ldmfile.sh).  I thought
about this for a couple of minutes and then a light bulb went on:  the
LDM administrative script ~ldm/bin/ldmadmin has the variable 'ldmhome'
that gets set when the package is built/installed.  This variable
obviously had been set to a value that was not correct given the
regularized LDM build that I _thought_ I had done... I never rebuilt
the LDM until a few minutes ago.  So, the problem all along was in
my not performing a clean rebuild of the LDM when I went about
regularizing the LDM installation; my bad!

As I end this note, I believe that everything is working as it should
(but I will do a bit more snooping to make sure).  Since satellite
imagery is now being processed, the ADDE dataset definitions that
I implemented when configuring the 'mcidas' account will now find
the imagery data.  You should, therefore, be able to view the imagery
from derecho in your IDV as soon as you set the Server: value in
the Data Choosers -> Sat & Radar -> Images GUI.

I'll write more if anything comes to mind...

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