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

[IDD #INB-206452]: Trying to configure LDM software



Hi Andrés,

re:
> Hi, my name is Andrés, student from Universidad Simón Bolívar of Venezuela.
> I already made the steps for the installation of the ldm software (and
> others programs such gempak) and now I go by the configuration steps, I
> trying to configure the LDM  to obtain this two feedtypes : NGRID and NMC2.
> But i dont know  ceirtanly how to configure the system to obtain only this
> feedtypes, i am a little lost and confused with this. Maybe you can help me
> telling me how must look my ldmd.conf file and what other things must be to
> do specifically to this two feedtypes,

OK.  First, please be aware that the NGRID and CONDUIT (aka NMC2) feeds contain
the majority of the data flowing in the IDD.  Given the volume of the data,
you may need to split your data request into several requests.

Until we determine how good/fast your Internet connection is, let's start
by requesting all of the data in each feed.  To do this, add the following
two lines to your ~ldm/etc/ldmd.conf file:

request NGRID ".*" idd.cise-nsf.gov
request CONDUIT ".*" idd.cise-nsf.gov

I fully expect that your Internet connection is not fast enough to get all of
the CONDUIT data on a single request.  I also expect that you are mainly
interested in the global model data available in CONDUIT, not the data that
is focused over the US.  Because of these two assumptions on my part, you
might want to try requesting just the global model output from CONDUIT
and splitting the request 5 ways:

request NGRID ".*" idd.cise-nsf.gov
request CONDUIT "MT.gfs_CY.*[05]$" idd.cise-nsf.gov PRIMARY
request CONDUIT "MT.gfs_CY.*[16]$" idd.cise-nsf.gov PRIMARY
request CONDUIT "MT.gfs_CY.*[27]$" idd.cise-nsf.gov PRIMARY
request CONDUIT "MT.gfs_CY.*[38]$" idd.cise-nsf.gov PRIMARY
request CONDUIT "MT.gfs_CY.*[49]$" idd.cise-nsf.gov PRIMARY

After we get an idea of how good (or bad) your Internet connection is,
we may want to adjust your request lines.

Second item:  since you will be requesting a lot of data, I want to
make sure that your LDM queue is large enough.  I recommend that
you set your LDM queue size to at least 2 GB.  This is done by
modifying the $pq_size variable in ~ldm/etc/ldmadmin-pl.conf:

$pq_size = "2G";

After making a change in ~ldm/etc/ldmadmin-pl.conf, you will need
to delete and remake your LDM queue:

<as 'ldm'>
cd ~ldm
ldmadmin stop        <- just in case your LDM is running
ldmadmin delqueue
ldmadmin mkqueue -f  <- the '-f' (for 'fast') assumes you have enough disk for 
the queue
ldmadmin start       <- to start the LDM

Now, assuming that you have correctly setup /etc/syslog.conf for LDM logging, 
you
should see a 'Starting up' message in ~ldm/logs/ldmd.log.  If your LDM does not
start, you should see an error message in ~ldm/logs/ldmd.log that tells you
where in ~ldm/etc/ldmd.conf there is an error (and errors are typically typos).

> the two upstream sites that were given to us are follows:
> 
> idd.cise-nsf.gov
> idd.unidata.ucar.edu (backup)
> 
> If something else is needed, i will send you in another email.

OK.

> I would appreciate much your help. Thanks for your help
> (Sorry my english)

No worries.  Please let us know if the above helped.

> Andrés Vidal


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: INB-206452
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.