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

Re: 20040126:BGSU Data Feed

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: 20040126:BGSU Data Feed
  • Date: Wed, 28 Jan 2004 12:30:57 -0700 (MST)
Patrick,

You can eliminate the request for UNIDATA as it consists of

HDS, IDS|DDPLUS, and UNIWISC, so it is redundant.

Requests all look in order, leads me to suspect some sort of packet
shaping/sniffing/throttling on port 388...

Cheers,

Jeff
---------------------------------------------------------------------
Jeff Weber                                    address@hidden        :
Unidata Program Center                        PH:303-497-8676        :
University Corp for Atmospheric Research      3300 Mitchell Ln       :
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000  :
---------------------------------------------------------------------

On Wed, 28 Jan 2004, Patrick L. Francis wrote:

>  >I suspect that they are all on the same request line:
>
> >request IDS|DDPLUS|UNIWISC|HDS  ohio state...blah
> >
> >If I am correct in this assumption please re-do into seperate request
> >lines:
>
> currently my setup is this:
>
> request UNIDATA ".*" twister.sbs.ohio-state.edu PRIMARY
> request HDS ".*" twister.sbs.ohio-state.edu PRIMARY
> request IDS|DDPLUS ".*" twister.sbs.ohio-state.edu PRIMARY
> request UNIWISC ".*" twister.sbs.ohio-state.edu PRIMARY
>
>
> checking on the other requests..
>
>