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

20041130: CONDUIT model name changes effect on end user 12Z GFS/ETA processing

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: 20041130: CONDUIT model name changes effect on end user 12Z GFS/ETA processing
  • Date: Tue, 30 Nov 2004 17:39:04 -0700
>From: =?ISO-8859-1?Q?Christian_Pag=E9?= <address@hidden>
>Organization: UQAM
>Keywords: 200411302007.iAUK7FlI010437

Hi Christian,

re: notice of CONDUIT header changes with model rename
>Is this needed to regular IDD data?

No.

>Also, I want to be able to receive CONDUIT data.

OK.  We will initiate the process of setting you up to feed CONDUIT
from either the University of Illinois or the University of
Wisoconsin and get back to you when this they are ready.

Given some of the seemingly volume related problems you have had
ingesting data in the not too distant past, have you considered
how the addition of CONDUIT ingestion will impact your network?
The full CONDUIT datastream averages over 1 GB/hour and has peaks
that can approach 2 GB/hour.

>Christian Pagé
>http://meteocentre.com/    http://meteoalerte.com/
>
>Etudiant au Doctorat en Sciences de l'environnement UQAM
>+1 514 987 3000 ext. 2376

Cheers,

Tom
--
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.