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

Re: LDM status update (fwd)

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: Re: LDM status update (fwd)
  • Date: Tue, 26 Sep 2000 08:33:36 -0600 (MDT)

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Mon, 25 Sep 2000 18:23:16 -0600 (MDT)
From: Tim Alberta <address@hidden>
To: Karl Hanzel <address@hidden>
     JimC <address@hidden>, address@hidden,
     BernardB <address@hidden>, BobW <address@hidden>
Subject: Re: LDM status update

Karl,

See if you can find Tom McDermott's address (something brockport) then ask
him for his mvarea.pl.  

Tim


On Mon, 25 Sep 2000, Karl Hanzel wrote:

> Tim & all -
> 
> Rob Kambic of Unidata was over earlier today to help me try and
> troubleshoot things.  We also conferenced-in Jim Cowie via phone.
> 
> Rob's pretty confident (right?) that the problem is with the
> /pub/ldm/bin2/mvarea1.pl perl script... possibly in the way it's
> invoking the binary /pub/ldm/bin/pnga2area, or possibly this binary is
> not in-sync/compatible with current (new??) file formats or sum-such.
> 
> I'm trying to debug the script with the tools PERL provides, but not
> having much success.  I really think this is something for Tim to look
> into... i could invest more time & energy, and still come up empty-
> handed because i just don't know all of the inner-workings of the system
> as a whole.
> 
> 
> In the meantime, it sounds like the Dstreme folks have a viable
> work-around in place (right?).
> 
> 
> *----->
> 
> 
>