<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 92.4pt 1.0in 92.4pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:2041272587;
mso-list-type:hybrid;
mso-list-template-ids:-1753176122 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoPlainText>John,<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I figured that the vertical interpolation would best be
handled outside of MET, so that is what I plan to do. I will assign the
OBS to the valid layer in the model.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>With that, I hinted at my WRF configuration. I’m
running with the Noah LSM with soil layers of 0-10, 10-40, 40-100, and 100-200
cm. Given those layers, how should I go about assigning the OBS to the
model layer in the ascii2nc process? <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Here’s what in the WRF GRIB-1 file:<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>lc2:/usr/people/casejl/tmp/seus_2008062103/control >
wgrib WRFPRS00.tm00.d01 | grep SOILW<o:p></o:p></p>
<p class=MsoPlainText>86:13184188:d=08062103:SOILW:kpds5=144:kpds6=112:kpds7=10:TR=0:P1=0:P2=0:TimeU=1:0-10
cm down:anl:NAve=0<o:p></o:p></p>
<p class=MsoPlainText>88:13482750:d=08062103:SOILW:kpds5=144:kpds6=112:kpds7=2600:TR=0:P1=0:P2=0:TimeU=1:10-40
cm down:anl:NAve=0<o:p></o:p></p>
<p class=MsoPlainText>90:13781312:d=08062103:SOILW:kpds5=144:kpds6=112:kpds7=10340:TR=0:P1=0:P2=0:TimeU=1:40-100
cm down:anl:NAve=0<o:p></o:p></p>
<p class=MsoPlainText>92:14079874:d=08062103:SOILW:kpds5=144:kpds6=112:kpds7=25800:TR=0:P1=0:P2=0:TimeU=1:100-200
cm down:anl:NAve=0<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>lc2:/usr/people/casejl/tmp/seus_2008062103/control >
wgrib WRFPRS00.tm00.d01 | grep TSOIL<o:p></o:p></p>
<p class=MsoPlainText>85:13005070:d=08062103:TSOIL:kpds5=85:kpds6=112:kpds7=10:TR=0:P1=0:P2=0:TimeU=1:0-10
cm down:anl:NAve=0<o:p></o:p></p>
<p class=MsoPlainText>87:13303632:d=08062103:TSOIL:kpds5=85:kpds6=112:kpds7=2600:TR=0:P1=0:P2=0:TimeU=1:10-40
cm down:anl:NAve=0<o:p></o:p></p>
<p class=MsoPlainText>89:13602194:d=08062103:TSOIL:kpds5=85:kpds6=112:kpds7=10340:TR=0:P1=0:P2=0:TimeU=1:40-100
cm down:anl:NAve=0<o:p></o:p></p>
<p class=MsoPlainText>91:13900756:d=08062103:TSOIL:kpds5=85:kpds6=112:kpds7=25800:TR=0:P1=0:P2=0:TimeU=1:100-200
cm down:anl:NAve=0<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Thanks much!<br>
Jonathan<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> -----Original Message-----<o:p></o:p></p>
<p class=MsoPlainText>> From: John Halley Gotway
[mailto:johnhg@rap.ucar.edu]<o:p></o:p></p>
<p class=MsoPlainText>> Sent: Friday, May 08, 2009 12:16 PM<o:p></o:p></p>
<p class=MsoPlainText>> To: Case, Jonathan (MSFC-VP61)[Other]<o:p></o:p></p>
<p class=MsoPlainText>> Cc: met_help<o:p></o:p></p>
<p class=MsoPlainText>> Subject: Re: soil verification in point_stat<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> Jonathan,<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> As a short answer I'd say, yes, you could probably
use Point-Stat to verify<o:p></o:p></p>
<p class=MsoPlainText>> soil moisture and temperature observations from WRF.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> ...BUT... I don't think you'll be able to do any
vertical interpolation<o:p></o:p></p>
<p class=MsoPlainText>> without some code changes. Right now,
Point-Stat is only set up to do<o:p></o:p></p>
<p class=MsoPlainText>> vertical interpolation for pressure levels... and
that's<o:p></o:p></p>
<p class=MsoPlainText>> done linear in the log of pressure.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> Here's what I'd recommend...<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> (1) Take a look at the soil moisture and temperature
fields you have from<o:p></o:p></p>
<p class=MsoPlainText>> WRF. Depending on which "surface
scheme" (I think that's right) you're<o:p></o:p></p>
<p class=MsoPlainText>> using, the soil moisture fields may be at a single<o:p></o:p></p>
<p class=MsoPlainText>> levels or a layer of levels. If it's in
layers, you probably wouldn't want<o:p></o:p></p>
<p class=MsoPlainText>> to interpolate in the vertical. You'd just
like to match the observation<o:p></o:p></p>
<p class=MsoPlainText>> to the forecast value for the layer in which the<o:p></o:p></p>
<p class=MsoPlainText>> observation falls. If it's single levels, you
may want to consider<o:p></o:p></p>
<p class=MsoPlainText>> interpolating.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> (2) Take a look at the observation levels. Are
they all at some set of<o:p></o:p></p>
<p class=MsoPlainText>> "standard" depths or do the depths vary
greatly?<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> Here's one approach that may be pretty easy:<o:p></o:p></p>
<p class=MsoPlainText>> - Assuming that your forecasts are in single levels.<o:p></o:p></p>
<p class=MsoPlainText>> - Assuming that your observations are at some set of
"standard" depths.<o:p></o:p></p>
<p class=MsoPlainText>> - When you pre-process the observations to prepare
them for ASCII2NC, just<o:p></o:p></p>
<p class=MsoPlainText>> round the level value for the observation to the
nearest depth you have in<o:p></o:p></p>
<p class=MsoPlainText>> your model output.<o:p></o:p></p>
<p class=MsoPlainText>> - Then run Point-Stat to verify at each of your
model depths (i.e. no<o:p></o:p></p>
<p class=MsoPlainText>> vertical interpolation).<o:p></o:p></p>
<p class=MsoPlainText>> - You could even dump out the matched pair (MPR)
line type for all of the<o:p></o:p></p>
<p class=MsoPlainText>> levels and use the Stat-Analysis tool to aggregate
across levels<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> I've never done this before, but you could
*probably* do that approach with<o:p></o:p></p>
<p class=MsoPlainText>> no code changes. However, if you'd like to do
more sophisticated vertical<o:p></o:p></p>
<p class=MsoPlainText>> interpolation, I may be able to point you in the<o:p></o:p></p>
<p class=MsoPlainText>> right direction as for what code to modify.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> Hope that helps.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> John<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> Case, Jonathan (MSFC-VP61)[Other] wrote:<o:p></o:p></p>
<p class=MsoPlainText>> > Thank you John!<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > I have another question for you regarding
point_stat.<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > I would like to use observations from SCAN
(Soil Climate Analysis<o:p></o:p></p>
<p class=MsoPlainText>> Network) to verify soil moisture and temperature
observations in the WRF<o:p></o:p></p>
<p class=MsoPlainText>> model. Is there a way we could use point_stat
for processing/interpolating<o:p></o:p></p>
<p class=MsoPlainText>> data for soil verification? I don't have the
exact specs yet on the<o:p></o:p></p>
<p class=MsoPlainText>> observations, but it would probably require a
vertical interpolation or<o:p></o:p></p>
<p class=MsoPlainText>> nearest-neighbor assignment of a soil layer to the
sensor obs depth. I<o:p></o:p></p>
<p class=MsoPlainText>> figure that if could use ascii2nc to pre-process the
data into a netcdf<o:p></o:p></p>
<p class=MsoPlainText>> file with the same variable naming convention as the
WRF GRIB output, then<o:p></o:p></p>
<p class=MsoPlainText>> I might be able to pull it off.<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > Thanks in advance,<o:p></o:p></p>
<p class=MsoPlainText>> > Jonathan<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> >> -----Original Message-----<o:p></o:p></p>
<p class=MsoPlainText>> >> From: John Halley Gotway
[mailto:johnhg@rap.ucar.edu]<o:p></o:p></p>
<p class=MsoPlainText>> >> Sent: Friday, May 08, 2009 8:47 AM<o:p></o:p></p>
<p class=MsoPlainText>> >> To: Case, Jonathan (MSFC-VP61)[Other];
met_help<o:p></o:p></p>
<p class=MsoPlainText>> >> Subject: Re: formatted output in
mode_analysis<o:p></o:p></p>
<p class=MsoPlainText>> >><o:p></o:p></p>
<p class=MsoPlainText>> >> Jonathan,<o:p></o:p></p>
<p class=MsoPlainText>> >><o:p></o:p></p>
<p class=MsoPlainText>> >> Take a look in
METv2.0/lib/vx_analysis_util/mode_job.cc. In lines 458<o:p></o:p></p>
<p class=MsoPlainText>> >> to 485, change all instances of
"%.2f" to "%.3f". That should increase<o:p></o:p></p>
<p class=MsoPlainText>> >> your precision by 1.<o:p></o:p></p>
<p class=MsoPlainText>> >><o:p></o:p></p>
<p class=MsoPlainText>> >> Thanks,<o:p></o:p></p>
<p class=MsoPlainText>> >> John<o:p></o:p></p>
<p class=MsoPlainText>> >><o:p></o:p></p>
<p class=MsoPlainText>> >> Case, Jonathan (MSFC-VP61)[Other] wrote:<o:p></o:p></p>
<p class=MsoPlainText>> >>> John,<o:p></o:p></p>
<p class=MsoPlainText>> >>><o:p></o:p></p>
<p class=MsoPlainText>> >>> I would like to output an addition
decimal place in the mode_analysis<o:p></o:p></p>
<p class=MsoPlainText>> >> -summary output to have 3 decimal places.<o:p></o:p></p>
<p class=MsoPlainText>> >>> What line(s)/file(s) should I modify in
order to get 1 more decimal<o:p></o:p></p>
<p class=MsoPlainText>> >> point precision?<o:p></o:p></p>
<p class=MsoPlainText>> >>> Thanks much!<o:p></o:p></p>
<p class=MsoPlainText>> >>> Jonathan<o:p></o:p></p>
<p class=MsoPlainText>> >>><o:p></o:p></p>
<p class=MsoPlainText>> >>>
***********************************************************<o:p></o:p></p>
<p class=MsoPlainText>> >>> Jonathan Case, ENSCO, Inc.<o:p></o:p></p>
<p class=MsoPlainText>> >>> Aerospace Sciences & Engineering
Division<o:p></o:p></p>
<p class=MsoPlainText>> >>> Short-term Prediction Research and
Transition Center<o:p></o:p></p>
<p class=MsoPlainText>> >>> 320 Sparkman Drive, Room 3062<o:p></o:p></p>
<p class=MsoPlainText>> >>> Huntsville, AL 35805-1912<o:p></o:p></p>
<p class=MsoPlainText>> >>> Voice: (256) 961-7504 Fax:
(256) 961-7788<o:p></o:p></p>
<p class=MsoPlainText>> >>> Emails: Jonathan.Case-1@nasa.gov<o:p></o:p></p>
<p class=MsoPlainText>> >>>
case.jonathan@ensco.com<o:p></o:p></p>
<p class=MsoPlainText>> >>>
***********************************************************<o:p></o:p></p>
<p class=MsoPlainText>> >>><o:p></o:p></p>
<p class=MsoPlainText>> >>><o:p></o:p></p>
</div>
</body>
</html>