<html><head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">Dear all, <br>
<br>
thank you for your useful comments! My problem is now solved by using
the DX and DY values calculated by metgrid in the namelist.input. <br>
<br>
It would be a good idea to update the manual on this point.<br>
<br>
<blockquote style="border: 0px none;"
cite="mid:50265F0A-C6EA-491E-B81F-B4DE5AD52684@gmail.com" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:jatin.kala.jk@gmail.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Jatin Kala</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">14. November 2013
21:56</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div>Do an ncdump -h of any
met_em file, and you should get the dx and dy in m which u can specify
in namelist.input. We had the same problem when uding rotated lat-lon
grid<br><br>Sent from my iPhone<br><br></div></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:rxschuster@gmail.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Robert Schuster</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">14. November 2013
18:26</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div>Dear WRF users,<br><br>I
have the same problem as already described below. I configured WRF<br>with
a regional "lat-lon" domain. My grid spacing is 0.081 degrees in<br>each
direction. The WPS tools accept dx and dy in degrees (as described<br>in
the user guide), but real.exe complains about a mismatch between the<br>dx/dy
from namilist.input and the values stored by metgrid in the<br>met_em....nc
files.<br><br>How to solve this problem? Is a solution to place the
metgrid calculated<br>dx/dy in meters in namelist.input? Is it better to
store dx/dy in the<br>metgrid produced files in degrees (for example by
editing the attributes<br>with ncatted)? Are there any side effects of
these solutions?<br><br>Best Regards,<br>Robert Schuster<br><br>Output
from real.exe (Version 3.5.1):<br>dx and dy from file 9005.376 9005.376<br>dx
and dy from namelist 8.1000000E-02 8.1000000E-02<br>--------------
FATAL CALLED ---------------<br>FATAL CALLED FROM FILE: <stdin>
LINE: 531<br>DX and DY do not match comparing namelist to the input file<br>-------------------------------------------<br><br></div></div>
</blockquote>
</body></html>