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

[Datastream #NUL-612145]: NAM Model TIN 11-16

Hi Kevin,

re:
> Tom, here is some more info about the grids I was interested in from the
> people at NCEP. Looks like they become operational around September 20.
> Innermost nests on CONDUIT is what the Cape is interested in, I think.

This is very interesting and timely... we have been working with the folks
at the WOC on adding fire weather grids to CONDUIT.  The experiments conducted
have been on one of the three toplevel CONDUIT machines that the WOC operates
in Silver Springs, after it was pulled from "operational" duties.  The
parallel NAM fire weather products will increase the volume in CONDUIT by
an average of 800 MB/hour.  Good thing that they are available for insertion
into the feed at different times than the current data peaks (which are 
dominated
by GFS and ensemble fields).

We just had a conference call with our contact at the WOC regarding the
fire weather test results, and she happened to mention her wondering if
users were going to be interested in the inner nests for the various products.
Your note indicates that folks you are working with are.  Also, since
you included a note from him, I can mention that Justin Cooke was the
technical contact we were working with for the tests of CONDUIT additions.

Must be something in the air that gets folks thinking about the same issues
at the same time :-)

> -------- Original Message --------
> Subject:     Re: Fwd: TIN 11-16 Models
> Date:     Tue, 30 Aug 2011 08:16:18 -0400
> From:     Geoff DiMego <address@hidden>
> To:     Kevin Baggett <address@hidden>
> CC:     Justin Cooke, NCEP Support <address@hidden>
> References:
> <20110829200019.11046.468848664.swift@nco_helpdesk01.ncep.noaa.gov>
> <20110829202002.11057.695082961.swift@nco_helpdesk01.ncep.noaa.gov>
> 
> 
> Kevin;
> The new NAM nests (to become operational 20 September we hope) will
> eventually be on NOMADS in all their full glory (next quarter sometime)
> and our innermost nest - the Fire Weather / IMET Support (FWIS) runs,
> are going on CONDUIT also in all their full glory.  You can request thru
> UniData for the nests to go there too and I hope you will ^_^
> 
> Bandwidth on NOAAPORT and AWIPS SBN is limited (evfen after the
> enhancement) so we haven't come close to delivering the NAM nests to
> users in all their full glory.  We do have a plan: NOAAPORT users will
> have access to NAM nests via the so-called NAM-DNG (Downscaled Numerical
> Guidance) gridded product.  These are now 12km NAM grids downscaled to
> the NDFD grids (5km over CONUS, 5.9km over Alaska, 2.5km over Hawaii and
> 2.5km over Puerto Rico.  When the new NAM becomes operational, these DNG
> grids will come from the NAM nests and will have had to undergo very
> little downscaling - there should be a TIN on that already out there.
> In addition, we are adding a 2.5km DNG for CONUS and a 3km DNG for
> Alaska.  All of these DNG contain only a dozen or so sensible weather
> fields but this time around we are adding simulated radar reflectivity.
> 
> -------- Original Message --------
> Subject:     Re: [DATAFLOW #MTT-54665-913] TIN 11-16 Models
> Date:     Mon, 29 Aug 2011 16:22:04 -0400
> From:     Justin Cooke, NCEP Support <address@hidden>
> Reply-To:     Justin Cooke, NCEP Support <address@hidden>
> To:     address@hidden
> References:
> <20110829200019.11046.468848664.swift@nco_helpdesk01.ncep.noaa.gov>
> 
> 
> Hi again Kevin,
> 
> I've confirmed that there are no plans to have these grids added. I've
> passed along your interest to the Environmental Modeling Center as they
> would make the request to have these data added, but getting anything
> added to the SBN/NOAAPort takes quite a bit of time.
> 
> Justin Cooke
> NCEP Central Operations
> 
> On Mon, 29 Aug 2011 16:00:19 -0400, "Justin Cooke, NCEP Support"
> <address@hidden> wrote:
> > Hello Kevin,
> >
> > These data are only available on the NCEP FTP site. To my knowledge
> there are currently no plans to add them to NOAAPort, I'll ask around to
> confirm.
> >
> > Justin Cooke
> > NCEP Central Operatio
> 
> Unidata Datastream Support wrote:
> > Hi Kevin,
> >
> > re:
> >
> >> Thanks for the info.
> >>
> >
> > No worries.
> >
> > re:
> >
> >> I am not sure what the Product ID's should look like - these are grids
> >> that someone at the Cape requested. They are a NAM nested grid 84,
> >> NAM_NEST84 and NMM nested grid 89, NMM_NEST89??
> >>
> >
> > I would look for grids with Product IDs that contain NMM_89 as a first
> > step.
> >
> > re:
> >
> >> With regard to how I'm looking for the grids: I took the sample files
> >> that I downloaded from the para FTP site, ran a script to extract the
> >> navigation, put the nav values into the
> >> /home/mcidas/data/grib2NavLookup.txt file, then passed them through
> >> -XCD.
> >>
> >
> > Interesting, I wouldn't have thought of doing that!
> >
> > re:
> >
> >> Via LDM, using HDS/HRS/NGRID and a ^.* to look for everything, I
> >> have not seen similar grids float across in 24 hours,
> >>
> >
> > Are you looking for these from your local NOAAPort ingester, or
> > are you look for these in the IDD feeds?  The reason I ask is that
> > by looking at the full IDD HDS|NGRID feeds, you would see something
> > _if_ what you are looking for is really there.  Looking at your own
> > NOAAPort ingester should be equivalent _unless_ it is having some
> > problems (which I am not suggesting, by the way).
> >
> > re:
> >
> >> even though I can
> >> see these files have been updated on the parallel run site. Our contact
> >> at the Cape seemed certain that these files should be coming across
> >> NOAAPORT. I don't understand why they are showing up in the parallel
> >> directory and not in NOAAPORT.
> >>
> >
> > Again, I have been told many, many times that the contents of the NOAAPort
> > SBN are determined by operational needs as determined by the NWS.  If the
> > NWS has determined that parallel runs of the NAM are important for 
> > operations,
> > it would seem to me that they would cease being parallel runs and join
> > the operational status.  I could, of course, be wrong in this, but the
> > fact that you haven't seen what you are looking for suggests that my view
> > is correct.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: NUL-612145
Department: Support Datastream
Priority: Normal
Status: Closed