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

[IDD #PSZ-278843]: [ldm-users] UNIWISC via conduit.unidata.ucar.edu

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: [IDD #PSZ-278843]: [ldm-users] UNIWISC via conduit.unidata.ucar.edu
  • Date: Thu, 12 Dec 2019 11:23:21 -0700
Hi again Victor,

re:  My sincere apologies! I was not aware that this was still on the down-low

No worries.  I am just worried that we will see other sites trying to feed
UNIWISC from conduit.unidata.ucar.edu, and they will be unsuccessful due
to firewall rules, and that, in turn, would likely lead to support inquiries
that I will have to answer and explain about the test.

re:
> Thanks for checking into this. 

No worries.

Just so you know, the products were still being generated and received by your
machine:

atlas.niu.edu UNIWISC volume:
https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?UNIWISC+atlas.niu.edu

but the Product IDs were slightly different from what they were before the
McIDAS upgrade.  This resulted in your LDM pattern-action file actions that
process the data not matching the new Product IDs.

I traced the problem down to file that associates a label (e.g., G16 IMG) with
satellite source numbers in the McIDAS distribution having changed from the
older McIDAS installation (v2018) and the one I upgraded to yesterday (v2019).
To "fix" the problem, I copied the file from the previous distribution to the
~ldm/mcidas/data directory and modified the invocation of the routine that uses
the file in the scripts that are creating UNIWISC content.  As soon as I had 
edited
all of the scripts, the LDM/IDD Product IDs for the products returned to what
they had been, so existing LDM pattern-action file actions should once again
work as written.  Please check your machine to verify that this is, in fact,
the case.


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: PSZ-278843
Department: Support IDD
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly 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.