[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
20040818: 20040813: ETA initialization data LDM
- Subject: 20040818: 20040813: ETA initialization data LDM
- Date: Fri, 20 Aug 2004 11:20:09 -0600
David,
Since you are interested in only a small subset of the CONDUIT feed,
I'll have you feed it from atm.geo.nsf.gov at this time.
If later you want to increase the amount of data, I'll likely
try to have you feed from Penn St. or another 2nd tier site.
To get the awipd3 grids, you can create a request line as follows:
request CONDUIT "MT.eta.*awip3d" atm.geo.nsf.gov
For your pqact.conf, you can use:
CONDUIT MT.eta_CY.(..)/RD.(........)/PT.grid_DF.gr1/fh.00(..)_tl.press_gr.awip3d
FILE data/conduit/eta/\2\1/eta.t\1z.awip3d\3.tm00
The conduit files have the tgftp.nws.noaa.gov directory naming. So,
if you want that naming convention, your pqact action would be more simple.
Steve CHiswell
Unidata User Support
>From: David Fitzgerald <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200408181735.i7IHZQaW022490
>Chiz,
>
>Setting us up with a CONDUIT feed for awip3d data would be great!
>
>Thanks!!
>
>-----Original Message-----
>From: Unidata Support [mailto:address@hidden]
>Sent: Wednesday, August 18, 2004 12:42 PM
>To: David Fitzgerald
>Cc: Unidata Support (address@hidden)
>Subject: 20040813: ETA initialization data LDM
>
>
>David,
>
>The ETA212 grid data on NOAAPORT is only a subset of the data
>availble on the FTP server. You likely need the full fields for
>initializing a model since those files have more levels and parameters.
>
>The CONDUIT IDD feed contains the FTP server files and do have the
>FTP server names:
>http://my.unidata.ucar.edu/content/data/conduit/ldm_idd/index.html
>
>If you want to explore adding the awip3d (eta212 pressure grid) files
>from CONDUIT, we can set uou up with an upstream.
>
>Steve Chiswell
>Unidata User Support
>
>
>
>
>
>
>
>>From: David Fitzgerald <address@hidden>
>>Organization: UCAR/Unidata
>>Keywords: 200408131530.i7DFUkaW025486
>
>>This message is in MIME format. Since your mail reader does not understand
>>this format, some or all of this message may not be legible.
>>
>>------_=_NextPart_001_01C4814A.4B6D8C10
>>Content-Type: text/plain
>>
>>Hi,
>>
>>
>>
>>We are running the WRF model here, using ETA initialization data to kick
>off
>>our model run. We have been pulling the ETA data from an NCEP ftp site,
>but
>>lately we have been having trouble getting all the data we need from the
>ftp
>>site. The data we ftp is in grib format, with filenames of
>>eta.t12z.awip3d00.tm00, eta.t12z.awip3d03.tm00 etc. out to 48 hours.
>>
>>
>>
>>Since we get the ETA model in grib format through the LDM anyway, is there
>a
>>way for us to pull out this ETA initialization data from the LDM stream and
>>store it with filenames like we get from NCEP? That way we wouldn't have
>to
>>depend on ftp'ing the data from NCEP. What would a pqact.conf entry look
>>like to do this?
>>
>>
>>
>>Thanks!!
>>
>>
>>
>>Dave
>>
>>
>>
>>*********************************************
>>
>>David Fitzgerald
>>
>>Distributed System Specialist II
>>
>>Millersville University
>>
>>Millersville PA 17551
>>
>>Phone: 717-871-2394
>>
>>Fax: 717-871-4725
>>
>>E-mail: address@hidden
>><mailto:address@hidden>
>>
>>
>>
>>
>>------_=_NextPart_001_01C4814A.4B6D8C10
>>Content-Type: text/html
>>
>><html>
>>
>><head>
>><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
>>
>>
>><meta name=Generator content="Microsoft Word 10 (filtered)">
>>
>><style>
>><!--
>> /* Style Definitions */
>> p.MsoNormal, li.MsoNormal, div.MsoNormal
>> {margin:0in;
>> margin-bottom:.0001pt;
>> font-size:12.0pt;
>> font-family:"Times New Roman";}
>>a:link, span.MsoHyperlink
>> {color:blue;
>> text-decoration:underline;}
>>a:visited, span.MsoHyperlinkFollowed
>> {color:purple;
>> text-decoration:underline;}
>>span.EmailStyle17
>> {font-family:Arial;
>> color:windowtext;}
>>@page Section1
>> {size:8.5in 11.0in;
>> margin:1.0in 1.25in 1.0in 1.25in;}
>>div.Section1
>> {page:Section1;}
>>-->
>></style>
>>
>></head>
>>
>><body lang=EN-US link=blue vlink=purple>
>>
>><div class=Section1>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'>Hi,</span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'> </span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'>We are running the WRF model here, using ETA
>initialization
>>data to kick off our model run. We have been pulling the ETA data
>from a
>> n
>>NCEP ftp site, but lately we have been having trouble getting all the data
>we
>>need from the ftp site. The data we ftp is in grib format, with
>filename
>> s
>>of eta.t12z.awip3d00.tm00, eta.t12z.awip3d03.tm00 etc. out to 48
>hours.</span>
>> </font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'> </span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'>Since we get the ETA model in grib format through the
>LDM a
>> nyway,
>>is there a way for us to pull out this ETA initialization data from the LDM
>>stream and store it with filenames like we get from NCEP? That way we
>wo
>> uldn't
>>have to depend on ftp'ing the data from NCEP. What would a pqact.conf
>>entry look like to do this?</span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'> </span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'>Thanks!!</span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'> </span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'>Dave </span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'> &n
>bsp
>> ; </span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'>*********************************************</span></fo
>nt>
>> </p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>> font-family:Arial'>David Fitzgerald</span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'>Distributed System Specialist II</span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>> font-family:Arial'>Millersville</span></font><font size=2
>face=Arial><span
>> style='font-size:10.0pt;font-family:Arial'> </span></font><font size=2
>> face=Arial><span
>style='font-size:10.0pt;font-family:Arial'>University</span
>> ></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'>Millersville PA 17551</span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'>Phone: 717-871-2394</span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'>Fax: 717-871-4725</span></font></p>
>>
>><p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
>>font-family:Arial'>E-mail: <a
>href="mailto:address@hidden";>
>> address@hidden</a></span></font></p>
>>
>><p class=MsoNormal><font size=3 face="Times New Roman"><span
>style='font-size:
>>12.0pt'> </span></font></p>
>>
>></div>
>>
>></body>
>>
>></html>
>>
>>------_=_NextPart_001_01C4814A.4B6D8C10--
>>
>--
>****************************************************************************
><
>Unidata User Support UCAR Unidata Program
><
>(303)497-8643 P.O. Box 3000
><
>address@hidden Boulder, CO 80307
><
>----------------------------------------------------------------------------
><
>Unidata WWW Service http://my.unidata.ucar.edu/content/support
><
>----------------------------------------------------------------------------
><
>NOTE: All email exchanges with Unidata User Support are recorded in the
>Unidata inquiry tracking system and then made publically 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 publically 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.
