[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
1999129: 19990129: mesoeta grids on noaaport

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: 1999129: 19990129: mesoeta grids on noaaport
Date: Fri, 29 Jan 1999 14:34:30 -0700
Dave,
>     Actually there are some differences. From the
>list you sent it appears you are getting the
>ensemble forecasts on grid 2, but getting
>0-168 mrf on grid 3 and 180- on grid 2.


Dave, this is the same set of drfmr.*.2 grids you are getting.
They are not the full ensemble grids that are mentioned earlier
on the www page, just those with the C001 fields which you had
asked a while ago about how to strip off that extension.

The files have the "ens" name in the .2 grids for 0-168 hours
(this is just the name as sent by OSO). I always thought the OSO
ftp server was wierd for not putting the .2 on the 180-384 files.

I pipe all the MRF drfmr files (grids 2 and 3) to dcgrib with
a template YYMMDDHH_mrf_grid@@@.gem, so I do get 2 files here-
grid #2 and grid #3.


As for the ensembles that are mentioned on the www page, these are
what are found at:
ftp://140.90.6.103/ncepb/ens/ens.990129/
These are all grid #2. I pipe these to a different dcgrib action
with a template YYMMDDHH_ens_grid@@@.gem.

Here are the rough GEMPAK file sizes:
 124190208 Jan 29 02:17 99012900_mrf_grid002.gem
 363185152 Jan 29 02:00 99012900_mrf_grid003.gem

 148893184 Jan 28 11:45 99012800_ens_grid002.gem

Steve Chiswell

>From: "David J. Knight" <address@hidden>
>Organization: .
>Keywords: 199901292110.OAA08304

>
>Chiz,
>     Actually there are some differences. From the
>list you sent it appears you are getting the
>ensemble forecasts on grid 2, but getting
>0-168 mrf on grid 3 and 180- on grid 2.
>I assume your dcgrib makes two grid files
>for the "normal" mrf.
>
>Here is what I get...
>
>   ftp -v 140.90.6.103 <<EOF > ftp_mrf.out
>   binary
>   prompt
>   cd ncepb/mrf/mrf.$yr$mn$dy
>   lcd $INPUT
>   get drfmr.T00Z.PGrbF00.2 drfmr.T00Z.PGrbF00
>   get drfmr.T00Z.PGrbF12.2 drfmr.T00Z.PGrbF12
>   get drfmr.T00Z.PGrbF24.2 drfmr.T00Z.PGrbF24
>   get drfmr.T00Z.PGrbF36.2 drfmr.T00Z.PGrbF36
>   get drfmr.T00Z.PGrbF48.2 drfmr.T00Z.PGrbF48
>   get drfmr.T00Z.PGrbF60.2 drfmr.T00Z.PGrbF60
>   get drfmr.T00Z.PGrbF72.2 drfmr.T00Z.PGrbF72
>   get drfmr.T00Z.PGrbF84.2 drfmr.T00Z.PGrbF84
>   get drfmr.T00Z.PGrbF96.2 drfmr.T00Z.PGrbF96
>   get drfmr.T00Z.PGrbF108.2 drfmr.T00Z.PGrbF108
>   get drfmr.T00Z.PGrbF120.2 drfmr.T00Z.PGrbF120
>   get drfmr.T00Z.PGrbF132.2 drfmr.T00Z.PGrbF132
>   get drfmr.T00Z.PGrbF144.2 drfmr.T00Z.PGrbF144
>   get drfmr.T00Z.PGrbF156.2 drfmr.T00Z.PGrbF156
>   get drfmr.T00Z.PGrbF168.2 drfmr.T00Z.PGrbF168
>   get drfmr.T00Z.PGrbF180
>   get drfmr.T00Z.PGrbF192
>   get drfmr.T00Z.PGrbF204
>   get drfmr.T00Z.PGrbF216
>   get drfmr.T00Z.PGrbF228
>   get drfmr.T00Z.PGrbF240
>   bye
>
>I *think* you have to explicitly specify .2 to get
>grid 2 for the earlier times. The nice things about
>this is then all grids can be put into the same gempak file.
>
>Or maybe I just didn't understand what you said.
>For example, perhaps the grids in the ens directory
>are the same as the grids I get from the mrf directory...
>
>I'll run the traceroutes and send them in seperate email.
>
>Thanks
>David
>
>> 
>> 
>> Dave,
>> 
>> Actually, we have the grid 2 0-384 hours (I strip off
>> those C001 extensions out of those mrf.2 files). 
>> I need to update that www page to reflect that.
>> 
>> Here are the mrf sets today:
>> 
>> /public/ncepb/mrf/ens.990129/
>> drfmr.T00Z.PGrbF00.2    
>> drfmr.T00Z.PGrbF12.2    
>> drfmr.T00Z.PGrbF24.2 
>> drfmr.T00Z.PGrbF36.2 
>> drfmr.T00Z.PGrbF48.2 
>> drfmr.T00Z.PGrbF60.2  
>> drfmr.T00Z.PGrbF72.2   
>> drfmr.T00Z.PGrbF84.2 
>> drfmr.T00Z.PGrbF96.2  
>> drfmr.T00Z.PGrbF108.2   
>> drfmr.T00Z.PGrbF120.2   
>> drfmr.T00Z.PGrbF132.2   
>> drfmr.T00Z.PGrbF144.2   
>> drfmr.T00Z.PGrbF156.2  
>> drfmr.T00Z.PGrbF168.2 
>> 
>> /public/ncepb/mrf/mrf.990129/
>> drfmr.T00Z.PGrbF00
>> drfmr.T00Z.PGrbF12
>> drfmr.T00Z.PGrbF24
>> drfmr.T00Z.PGrbF36
>> drfmr.T00Z.PGrbF48
>> drfmr.T00Z.PGrbF60
>> drfmr.T00Z.PGrbF72
>> drfmr.T00Z.PGrbF84
>> drfmr.T00Z.PGrbF96
>> drfmr.T00Z.PGrbF108
>> drfmr.T00Z.PGrbF120
>> drfmr.T00Z.PGrbF132
>> drfmr.T00Z.PGrbF144
>> drfmr.T00Z.PGrbF156
>> drfmr.T00Z.PGrbF168
>> drfmr.T00Z.PGrbF180
>> drfmr.T00Z.PGrbF192
>> drfmr.T00Z.PGrbF204
>> drfmr.T00Z.PGrbF216
>> drfmr.T00Z.PGrbF228
>> drfmr.T00Z.PGrbF240
>> drfmr.T00Z.PGrbF252
>> drfmr.T00Z.PGrbF264
>> drfmr.T00Z.PGrbF276
>> drfmr.T00Z.PGrbF288
>> drfmr.T00Z.PGrbF300
>> drfmr.T00Z.PGrbF312
>> drfmr.T00Z.PGrbF324
>> drfmr.T00Z.PGrbF336
>> drfmr.T00Z.PGrbF348
>> drfmr.T00Z.PGrbF360
>> drfmr.T00Z.PGrbF372
>> drfmr.T00Z.PGrbF384
>> 
>> 
>> In the second data set, its grid 3 through 168, and grid 2 thereafter.
>> I just pipe all these to dcgrib and use the "@@@" template I put in to
>> let dcgrib sort our which is grid2 and which is grid3.
>> 
>> 
>> Can you try some traceroute for me:
>> nora.gsfc.nasa.gov
>> profhorn.meteor.wisc.edu
>> data3.atmos.uiuc.edu
>> navier.meteo.psu.edu
>> 
>> Thanks,
>> 
>> Chiz
>> 
>> >From: "David J. Knight" <address@hidden>
>> >Organization: .
>> >Keywords: 199901292041.NAA07537
>> 
>> >
>> >Chiz,
>> >Thanks for getting back so quick, and for pointing out that
>> >link. Looks like none of the noaaport grids give me what
>> >I used to get from NCM, or what I was until recently getting
>> >from our local NWS office. I checked the CONDUIT page
>> >and it seems to have what I want from the mesoeta.
>> >Unfortunately the CONDUIT stream does not appear to reproduce
>> >what I currently ftp from NCEP (I get MRF grid 2 0-240 hour (I
>> >like to keep all the times in one grid file, and grid 2 is
>> >adequate resolution for global datasets). I can send
>> >you the grid names if you like.
>> >Looks like I'll need to get some of our model grids from
>> >noaaport, some direct ftp from ncep (unless they are
>> >willing to add the rest of the mrf grid 2 files), some 
>> >from ncep/goddard/conduit feed (or i could go back to ftping
>> >the mesoeta instead).  Decisions decisions, I was hoping
>> >to simplify things not complicate them...
>> >
>> >OK. Please sign us up for the CONDUIT feed. We may need
>> >a little help putting together a filter that will grab just
>> >what we need (probabaly start with mesoeta, then maybe
>> >MRF ensemble, and if the 0-168 MRF becomes available
>> >on grid 2 we'll get that as well.) I'm not sure if we have
>> >the bandwidth right now to carry the whole NMC2 feed
>> >(the networking group is performing upgrades that aren't
>> >working properly yet...)
>> >
>> >Thanks
>> >David
>> >> 
>> >> 
>> >> David,
>> >> 
>> >> You are correct. 
>> >> 
>> >> Dan put together a www page with the inventory of NOAAport grids at:
>> >> http://weather.unisys.com/noaaport/grib_inventory.html
>> >> 
>> >> I can dump out the inventory of 212 and 215 from noaaport vs NCEP
>> >> for a product by product comparison of whats common and what
>> >> is unique.
>> >> 
>> >> Steve Chiswell
>> >> Unidata User Support
>> >> 
>> >> >From: "David J. Knight" <address@hidden>
>> >> >Organization: .
>> >> >Keywords: 199901291937.MAA05742
>> >> 
>> >> >Hi,
>> >> >     Ive started taking a closer look at the mesoeta grids
>> >> >on noaa port.
>> >> >
>> >> >I'm matching
>> >> >#
>> >> ># mesoETA grid212 (R) 40km CONUS Lambert
>> >> >#
>> >> >HRS     ^Y.R... KWBE ([0-3][0-9])([0-2][0-9]).*/mETA
>> >> >
>> >> >and
>> >> >
>> >> >#
>> >> ># ETA grid215 (U) 20km CONUS Lambert
>> >> >#
>> >> >HRS     ^[YZ].U... KWB. ([0-3][0-9])([0-2][0-9]).*/mETA
>> >> >
>> >> >and sending both through dcgrib.
>> >> >
>> >> >It appears that the "R" grid has constant pressure data, but
>> >> >only at 6 hour intervals, and only to 30 hours.
>> >> >
>> >> >The U grids have 3 hour forecasts, but, most of the fields
>> >> >are surface, or near surface grids. The only pressure level
>> >> >data appears to be vorticity.
>> >> >
>> >> >I haven't been able to find documentation on what *should* be
>> >> >available in these grids.
>> >> >
>> >> >Can you tell me if what I'm getting is all there is in these grids?
>> >> >
>> >> >If so, perhaps not would be a good time to consider joining
>> >> >the CONDIUT project and start getting the mesoeta grids directly
>> >> >from NCEP again.
>> >> >
>> >> >Thanks
>> >> >
>> >> >David Knight
>> >> >Department of Earth and Atmospheric Sciences   Tel: (518)-442-4204
>> >> >SUNYA   ES-228                                 Fax: (518)-442-4494
>> >> >Albany, NY  12222                              Email: knight@atmos.alban
> y.e
>> > du
>> >> >
>> >> 
>> >> *************************************************************************
> ***
>> >> Unidata User Support                                    UCAR Unidata Prog
> ram
>> >> (303)497-8644                                                  P.O. Box 3
> 000
>> >> address@hidden                                   Boulder, CO 80
> 307
>> >> -------------------------------------------------------------------------
> ---
>> >> Unidata WWW Service                        http://www.unidata.ucar.edu/  
>    
>> >> *************************************************************************
> ***
>> >> 
>> >
>> 
>> ****************************************************************************
>> Unidata User Support                                    UCAR Unidata Program
>> (303)497-8644                                                  P.O. Box 3000
>> address@hidden                                   Boulder, CO 80307
>> ----------------------------------------------------------------------------
>> Unidata WWW Service                        http://www.unidata.ucar.edu/     
>> ****************************************************************************
>> 
>
Prev by Date: Re: 19990129: mesoeta grids on noaaport - traceroutes
Next by Date: Re: WSI data latency problem
Previous by thread: Re: 19990129: mesoeta grids on noaaport - traceroutes
Next by thread: Re: WSI data latency problem
Index(es):
- Date
- Thread