Geoff
Actually, I've been getting both the bgrb and pgrb files, and,
together, we can run WPS. We are also performing hourly assimilation
and cycling after the init, but that's another process.
For the record, we're also looking at using the ESRL RAP, which is
also not available by LDM.
One of my reasons for requesting the data via LDM is in order to
automate the process. When the last needed files arrive via LDM, I can
use PQACT actions to trigger our workflow scripts, rather than
depending on a cron job that might be mangled if the model run's late.
For our project, automation and reliable data are both going to be
requirements. I'm sure I can find another way to improve the
automation... this is one of the easier and more reliable methods.
I do appreciate your pointers earlier to the data via NOMADS. We've
been using that on a regular basis since then!
Regards, Gerry
CIMMS/NSSL FRDD
On Thu, Sep 13, 2012 at 11:54 AM, Geoff DiMego <geoff.dimego@xxxxxxxx> wrote:
> Greg et al.
>
> While I understand the desire for native model output and I wish we could
> get all of it out to everyone, I don't believe you can initialize a WRF run
> using WPS with it. If there was a complete WRF restart or init file's worth
> of native you could probably bypass WPS (like is done in data assimilation
> cycling), but I don't think that is what Gerry or others want to or are
> capable of doing.
>
>
> On 9/11/2012 4:33 PM, Greg Thompson wrote:
>>
>>
>> Agreed here on 13km RAP model - native vertical coordinate with
>> hydrometeors - all things as close to native as possible rather than
>> interpolated either to pressure or eliminating the critical 3D variables.
>>
>> --Greg Thompson, NCAR-RAL
>>
>>
>> On Sep 11, 2012, at 2:29 PM, Gerry Creager wrote:
>>
>>> Becky
>>>
>>> Thanks for getting back to me. We are interested in the 12 km NAM and 13
>>> km (130 grid) RAP data. If that's possible, it'd be a help. When I first
>>> asked on the LDM list, there was at least one other researcher interested in
>>> higher resolution NAM and RAP. Somehow, I don't think I'd be the only user.
>>>
>>> Appreciate the help, and I fully understand about the delays for new
>>> systems and schedules.
>>>
>>> Regards,
>>> Gerry
>>>
>>> On Tue, Sep 11, 2012 at 3:16 PM, Rebecca Cosgrove
>>> <rebecca.cosgrove@xxxxxxxx> wrote:
>>> Gerry,
>>> I apologize for my delayed response.
>>> Right now we've got a limit on adding new data to CONDUIT until we
>>> upgrade our system here at NCEP. We're in the process of that upgrade right
>>> now. I'll submit your request for additional NAM 12km fields to the User
>>> Committee meeting on the 17th for consideration after the upgrade. If
>>> others in the group would like to see this data, I encourage you to chime in
>>> and voice your desire for this as well.
>>>
>>> For the RAP, we do have 20km and 40km grids for the CONUS available in
>>> CONDUIT. Is there additional RAP data you are interested in?
>>>
>>> Becky Cosgrove
>>> NCEP Central Operations
>>>
>>>> CONDUIT folk
>>>>
>>>> We're working on a project and I'd configured a CONDUIT feed to acquire
>>>> NAM 218 data. My plan was to kick off processing using a PQACT action when
>>>> the last of the needed data arrived. Problem: We get the surface fields,
>>>> which is not sufficient to initialize WRF. Of course, I can go download the
>>>> data from NCEP (in fact, that's what we're now doing) but I'm wondering: Am
>>>> I the only one looking for these data? Is there sufficient bandwidth to
>>>> allow carrying the full NAM 12 km dataset? What's the chances of getting
>>>> NAM
>>>> (and, for that matter, RAP) added?
>>>>
>>>> Thanks, Gerry
>>>> OU/CIMMS/NSSL
>>>>
>>>> _______________________________________________
>>>> conduit mailing list
>>>>
>>>> conduit@xxxxxxxxxxxxxxxx
>>>>
>>>> For list information or to unsubscribe, visit:
>>>> http://www.unidata.ucar.edu/mailing_lists/
>>>
>>>
>>> _______________________________________________
>>> conduit mailing list
>>> conduit@xxxxxxxxxxxxxxxx
>>> For list information or to unsubscribe, visit:
>>> http://www.unidata.ucar.edu/mailing_lists/
>>
>>
>> _______________________________________________
>> conduit mailing list
>> conduit@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe, visit:
>> http://www.unidata.ucar.edu/mailing_lists/
>>
>>
>
> --
> Geoff DiMego, Chief Mesoscale Modeling Branch
> Environmental Modeling Center, NCEP, NWS/NOAA/DOC
> NOAA Center for Weather and Climate Prediction
> 5830 University Research Court (W/NP22) Room 2131
> College Park, MD 20740 Tel/Fax 301-683-3764
>
>
