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

19990404: chinook request from aldehyde.sprl.umich.edu

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: 19990404: chinook request from aldehyde.sprl.umich.edu
  • Date: Tue, 04 May 1999 12:56:09 -0600
>From: Unidata User Support
>Organization: Unidata
>Keywords: IDD request

Clint,

First to business.  It seems that your machine, chinook, is requesting
the 'FSL' feed from aldehyde.sprl.umich.edu.  Here is the information
we are seeing in our FOS routing chart
(from: http://www.unidata.ucar.edu/projects/idd/status/idd/fosTopo.html):

chinook.unl.edu EXP|FAA604|DIFAX|WSI|NLDN|NMC|FSL|WMO|0xbffc0000

This appears to be incorrect on two counts:  The FSL wind profiler data
is in the FSL2 feed (you are requesting FSL), and the last item in the
list looks mighty weird to me.  Can you check on what data you are
requesting from aldehyde and update your pattern if it is incorrect and
stop/restart your LDM?  Thanks.

Tom