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

Re: NCEP TIGGE parameters

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: NCEP TIGGE parameters
  • Date: Wed, 11 Oct 2006 12:45:47 -0600
Doug,

I verified that tigge-ldm.ecmwf.int is currently feeding from both
idd.unidata.ucar.edu and atm.geo.nsf.gov....
http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT
+tigge-ldm.ecmwf.int
They should change to idd.cise-nsf.gov from the atm name when convenient
though since the idd name will always remain while individual machines
change roles.

Steve Chiswell
Unidata User Support


On Wed, 2006-10-11 at 11:39 -0600, Doug Schuster wrote:
> Steve,
> 
> Can ECMWF access these parameters off CONDUIT without any additional
> permission?
> 
> I sent them a copy of my ldmd.conf that uses:
> 
> REQUEST CONDUIT "data/nccf/com/gens/.*" idd.unidata.ucar.edu PRIMARY
> REQUEST CONDUIT "TIGGE.*"       idd.unidata.ucar.edu PRIMARY
> REQUEST CONDUIT "^.status\.*data/nccf/com/gens/.*"  
> idd.unidata.ucar.edu PRIMARY
> REQUEST CONDUIT "^.status.*TIGGE.*" idd.unidata.ucar.edu PRIMARY
> REQUEST CONDUIT "data/nccf/com/gens/.*" atm.geo.nsf.gov ALTERNATE
> REQUEST CONDUIT "TIGGE.*"       atm.geo.nsf.gov ALTERNATE
> REQUEST CONDUIT "^.status.*TIGGE.*" atm.geo.nsf.gov ALTERNATE
> REQUEST CONDUIT "^.status\.*data/nccf/com/gens/.*" atm.geo.nsf.gov  
> ALTERNATE
> 
> Doug
> 
> 
-- 
Steve Chiswell <address@hidden>
Unidata