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

Re: CONDUIT at NOC

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: CONDUIT at NOC
  • Date: Wed, 05 Apr 2006 21:41:46 -0400
Thanks Steve. We are still waiting on a new account to set this up on and then we can figure out access to UNIDATA and start some tests. One thing that was pointed out to me yesterday, the file names at the NOC will be different than what they are on the NWS servers. They will be the same as they are on FTPPRD. Will this cause the CONDUIT folks any difficulties? 

Brent

Steve Chiswell wrote:


Brent and Paula,

I have ported the gribinsert code to the current LDM distribution
(tgsv32 is running an old LDM-6.0.10 version compiled for AIX here
since it didn't have compilers).

I ported the code to eliminate the use of the fortran routines,
and placed the distribution tarfile as:

ftp://ftp.unidata.ucar.edu/pub/gribinsert/gribinsert-1.1.tar.gz

The tarfile can be downloaded into the LDMHOME directory (typically
~ldm), and unpacked with "gunzip -c gribinsert.tar.gz | tar xvf - ".
This will create a gribinsert-1.1 directory.

your ~ldm/ directory would then contain the ldm-6.4.5 (for instance)
directory, the gribinsert-1.1 directory, and the runtime/ links
that you create when you install the LDM. If you haven't done this
for the LDM, you will nbeed to do this to build gribinsert:

in LDMHOME.....
ln -s ldm-6.4.5 runtime
ln -s runtime/src src
ln -s runtime/include include
ln -s runtime/bin bin
ln -s runtime/lib lib

then build and install gribinsert with:
cd gribinsert-1.1
make all install

If sucessful, you will install gribinsert into runtime/bin,
and some grib2 tables into LDMHOME/etc.

That should get us to the point where we were with tgsv32.

If you have trouble building gribinsert, let me know as I had to
build this locally and send for Allan (Francis Yang) to install in the
past, so I didn't have a distribution tar file set up previously.

Thanks!

Steve

On Wed, 2006-03-29 at 05:52, Brent A. Gordon wrote:

Steve,

Here is the uname -a info:

Linux diskserver 2.6.15-rev3 #1 SMP PREEMPT Wed Mar 22 03:16:44 EST
2006 i686 GNU/Linux

It has cc and gcc on it, but not fortran.  Will we need more more than
that for gribinsert?

Brent
Steve Chiswell wrote: 
Brent,

I will have to create a gribinsert installation since its not part of
the standard LDM tar file. The TGSV32 system didn't have a compiler
environment so I had to create a binary rather than build by source
installation. Sounds like the NOC will not have that problem?

Do you know what OS the NOC system will be?

Thanks,

Steve

On Tue, 2006-03-28 at 05:44, Brent A. Gordon wrote:

Steve,

Yesterday I finally received permission the install LDM on our systems
at the NOC.  We are working towards that now and will install the most
recent and stable version of LDM to do this.  At this point we need to
know what we need to do to service CONDUIT.  Is it as simple as
running gribinsert?

Paula will be the one leading up this install, so please keep here on
your response.

Brent