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

20041018: request for model data



>From: Clint Rowe <address@hidden>
>Organization: University of Nebraska Geosciences
>Keywords: 200410181536.i9IFaCUE028035 LDM IDD

Mynul and Clint,

re:
>In my log files, meteor has a lone request line and cyclone is only
>requesting NNEXRAD and FNEXRAD.  You might want to change meteor
>to something like "ANY-(NNEXRAD|FNEXRAD)" (again, w/o quotes).  I
>don't know if this is allowed syntax, I've only seen a single
>feedtype after the "-" before.  I'll copy this to support for them
>to chime in.

OK, I'm chiming in. The correct syntax to remove feeds or a
list of feeds would be:

request ANY-NNEXRAD-FNEXRAD     <pattern>       <upstream_feed_host>

I strongly recommend on this approach, however, given its potential
for unintended consequences.  For instance, if you using papagayo
as your upstream feed host, and if papagayo is getting all data available
in the IDD (and this is close to being true), then a request like:

request ANY-NNEXRAD-FNEXRAD     ".*"    papagayo.unl.edu

wil result in you getting a LOT of data (e.g., all CONDUIT, all NIMAGE,
etc.).  Given that St. Cloud State's appetite for data has always been
more subdued than some of the larger IDD sites, it would be much better
if you requested exactly the feeds that you want to receive.  Here is
a workable example:

request UNIDATA ".*"    papagayo.unl.edu

The pseudo stream UNIDATA is the combination of IDS|DDPLUS, HDS, and
UNIWISC.  Since St. Cloud is getting some NNEXRAD and FNEXRAD data,
you could expand this to:

request FNEXRAD|NNEXRAD|UNIDATA ".*"    papagayo.unl.edu

or you could split the single request into multiple requests like:

request FNEXRAD|NNEXRAD ".*"    papagayo.unl.edu
request UNIDATA ".*"    papagayo.unl.edu

One would opt to split up the feed requests if/when the network bandwidth
into his/her site is limited in some way.

Cheers,

Tom

>Sorry for the delay, it's been really busy here and I was out of
>town for a while and your email got buried by incoming mail.
>
>It's already set at my end, all you need to do is request the HDS
>feed.  Since I don't know what you have in your ldnd.conf now I 
>can't be any more explicit than that right now.  You should be able to
>add "|HDS" to your current request line (without the quotes).
>In my log files, meteor has a lone request line and cyclone is only
>requesting NNEXRAD and FNEXRAD.  You might want to change meteor
>to something like "ANY-(NNEXRAD|FNEXRAD)" (again, w/o quotes).  I 
>don't know if this is allowed syntax, I've only seen a single 
>feedtype after the "-" before.  I'll copy this to support for them
>to chime in.
>
>Also, I have three machines listed for you in my ldmd.conf *waldo,
>cyclone, meteor).  Looking at my log files, I see active requests 
>from only cyclone and meteor -- is waldo gone?  Can I remove it?
>
>Clint
>
>
>On Thu, 2004-10-07 at 09:06, mynul khan wrote:
>> Hi Clint,
>> We have decided to recieve model data on 'meteor'. I
>> understand that to recieve such new type of data would
>> require to modify ldmd.conf file. I am not sure how to
>> make those  modifications. Is it possible you can
>> guide me with that if I send you the file?
>> As always I very much appreciate your help.
>> -Mynul
>> St Cloud, MN
>> 
>> 
>>              
>> __________________________________
>> Do you Yahoo!?
>> Read only the mail you want - Yahoo! Mail SpamGuard.
>> http://promotions.yahoo.com/new_mail
>-- 
>====================================================================
>Clinton M. Rowe
>Associate Professor
>Meteorology/Climatology Program                  phone:(402)472-1946
>Department of Geosciences                          fax:(402)472-4917
>University of Nebraska-Lincoln                        address@hidden
>
--
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.


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.