[wrfems] Using SPoRT SSTs and LIS together

Case, Jonathan (MSFC-ZP11)[ENSCO INC] jonathan.case-1 at nasa.gov
Tue Feb 14 10:39:49 MST 2012

A follow up on using both SPoRT SSTs and LIS together:

Be sure to specify RTG SSTs as a backup option for SST because the SPoRT SSTs are not produced over land like the RTG.
Also, Bob should have a built-in backup capability for LSM fields.

So in your conf/ems_auto/ems_autorun.conf, specify:
SFC = sstsport,ssthr
                LSM = lis,namptile

Jonathan @ NASA SPoRT

From: wrfems-bounces at comet.ucar.edu [mailto:wrfems-bounces at comet.ucar.edu] On Behalf Of Case, Jonathan (MSFC-ZP11)[ENSCO INC]
Sent: Tuesday, February 14, 2012 11:33 AM
To: Steve Keighton; WRF EMS Users
Subject: Re: [wrfems] Qstns about using RUC13 for initialization and SPoRT LIS for Lands Surface

Hi Steve,

Being in Blacksburg, VA, the current SPoRT LIS domain should more than accommodate your local model domain.
I attached a file showing the current coverage area of the SPoRT LIS land surface data for initializing the WRF EMS.

A couple requirements for using SPoRT LIS:

1.       As you alluded to, your model domain must fall within the extent of the LIS data (in the file attached).

2.       You MUST use the Noah land surface model option in the WRF EMS (i.e. SF_SURFACE_PHYSICS = 2 in conf/ems_run/run_physics.conf).   The SPoRT/LIS runs with the operational 4-layer Noah land surface model, so you need to use the same land surface model to initialize with the high-res LIS data.

There could also be an issue with using the RUC data in the initial conditions along with the LIS data.  I can work with you to make the minor changes needed to make this happen if you have your heart set on RUC ICs.  It involves removing the LSM lines in the Vtable.RUCH (depending on which EMS version you are running).

Feel free to contact me with any assistance you need.

Good luck!
Jonathan @ NASA SPoRT

From: wrfems-bounces at comet.ucar.edu [mailto:wrfems-bounces at comet.ucar.edu] On Behalf Of Steve Keighton
Sent: Tuesday, February 14, 2012 10:38 AM
To: WRF EMS Users
Subject: [wrfems] Qstns about using RUC13 for initialization and SPoRT LIS for Lands Surface

List, I'm in the category of just knowing enough to be dangerous with playing around with WRF configurations, so have what may be a couple of simple questions:

1) I've been hearing for some time (just dragging my feet to do anything about it) that folks are getting some good success initializing with the RUC13.  What is the preferred option for this: ruc13ha (hybrid vert coord analysis only), ruc13hf (hybrid fcst files), or ruc13pa (press coord analysis only).  I'm initializing a new run every 3 hrs, but since the RUC is hourly I figure I do not need the forecast data set, but not sure which of the two analysis options would be best.  Related to this is the appropriate command line in ems_autorun.conf file. We're currently initializing with a LAPS hotstart, and using NAM12 boundary conditions, so the line is DSETS = laps%tile12. Can I simply change that to ruc13ha%tile12 if I still want to use the NAM for BC?

2) I'm already using the SPoRT SST as my primary choice for sea sfc temps, but also want to use the SPoRT LIS for land surface initialization vs. the NAM12.  At one point I tried simply replacing LSM = tile12 with LSM = lis, but got errors and WRF never ran so went back to tile12.  Could this be because the SPoRT LIS has a limited domain and our WRF domain goes too far north?  Can anyone point me to details on what the SPoRT LIS domain is (unless it does cover the CONUS, in which case my error must be for another reason).


[cid:image001.jpg at 01CCEB0D.5ABB5370]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.comet.ucar.edu/pipermail/wrfems/attachments/20120214/276df42d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 16833 bytes
Desc: image001.jpg
URL: <https://mailman.comet.ucar.edu/pipermail/wrfems/attachments/20120214/276df42d/attachment-0001.jpg>

More information about the wrfems mailing list