Dear Yingli,<br>The same error I got, while running 4DVAR with version 3.4 two weeks back,  I could overcome the problem by using 6hourly boundary files instead of 3houly.  Probably in the WRFDA3.4 not accepting 3hourly boundary files when hourly observations are supplied for 6hour interval. I think your error will be resolved,  if try using 6houlry GFS files in WPS and WRF and change option in 4DVAR namelist.input from &quot;interval_seconds=10800&quot; to  &quot;interval_seconds=21600&quot;   (Or) supply  hourly observations  for 3hourly by changing 4DVAR namelist.input &quot;time_window_min=&quot;2000-03-01_18:00:00.0000&quot;,

time_window_max =&quot;2000-03-01_21:00:00.0000&quot;

<br><br><br>with regards,<br>V.Yesubabu,<br>CES Group,<br>CDAC,Pune. <br>
<br><br><div class="gmail_quote">On 18 May 2012 23:30,  <span dir="ltr">&lt;<a href="mailto:wrf-users-request@ucar.edu" target="_blank">wrf-users-request@ucar.edu</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Send Wrf-users mailing list submissions to<br>
        <a href="mailto:wrf-users@ucar.edu">wrf-users@ucar.edu</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
        <a href="http://mailman.ucar.edu/mailman/listinfo/wrf-users" target="_blank">http://mailman.ucar.edu/mailman/listinfo/wrf-users</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
        <a href="mailto:wrf-users-request@ucar.edu">wrf-users-request@ucar.edu</a><br>
<br>
You can reach the person managing the list at<br>
        <a href="mailto:wrf-users-owner@ucar.edu">wrf-users-owner@ucar.edu</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of Wrf-users digest...&quot;<br>
<br>
<br>
Today&#39;s Topics:<br>
<br>
   1. 4dvar error for V3.4 (yingli zhu)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 18 May 2012 10:27:01 -0400<br>
From: yingli zhu &lt;<a href="mailto:yingli@mail.usf.edu">yingli@mail.usf.edu</a>&gt;<br>
Subject: [Wrf-users] 4dvar error for V3.4<br>
To: wrfhelp Help &lt;<a href="mailto:wrfhelp@ucar.edu">wrfhelp@ucar.edu</a>&gt;<br>
Cc: <a href="mailto:wrf-users@ucar.edu">wrf-users@ucar.edu</a><br>
Message-ID: &lt;<a href="mailto:BBED383E-5F0E-4281-8D32-DBBEEB2BF04D@mail.usf.edu">BBED383E-5F0E-4281-8D32-DBBEEB2BF04D@mail.usf.edu</a>&gt;<br>
Content-Type: text/plain; charset=&quot;us-ascii&quot;<br>
<br>
Hi,<br>
I try to run 4dvar of version 3.4 and get this error:  &quot;lateral boundary update is not allowed&quot;<br>
For the version 3.3, it works, but when I transferred to v3.4, this occurred.<br>
Any suggestion?<br>
Attached is the namelist.input and error message.<br>
Yingli<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: rsl.out.0000<br>
Type: application/octet-stream<br>
Size: 13600 bytes<br>
Desc: not available<br>
Url : <a href="http://mailman.ucar.edu/pipermail/wrf-users/attachments/20120518/a99be560/attachment-0002.obj" target="_blank">http://mailman.ucar.edu/pipermail/wrf-users/attachments/20120518/a99be560/attachment-0002.obj</a><br>


-------------- next part --------------<br>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: namelist.input<br>
Type: application/octet-stream<br>
Size: 2042 bytes<br>
Desc: not available<br>
Url : <a href="http://mailman.ucar.edu/pipermail/wrf-users/attachments/20120518/a99be560/attachment-0003.obj" target="_blank">http://mailman.ucar.edu/pipermail/wrf-users/attachments/20120518/a99be560/attachment-0003.obj</a><br>


<br>
------------------------------<br>
<br>
_______________________________________________<br>
Wrf-users mailing list<br>
<a href="mailto:Wrf-users@ucar.edu">Wrf-users@ucar.edu</a><br>
<a href="http://mailman.ucar.edu/mailman/listinfo/wrf-users" target="_blank">http://mailman.ucar.edu/mailman/listinfo/wrf-users</a><br>
<br>
<br>
End of Wrf-users Digest, Vol 93, Issue 9<br>
****************************************<br>
</blockquote></div><br>