David,<div>It does look like the way you say. So, I suppose the issue is someplace else.</div><div><br></div><div>Thanks,</div><div>Rahul.<br><br><div class="gmail_quote">On Fri, Jun 25, 2010 at 11:09 AM, David Ovens <span dir="ltr"><<a href="mailto:ovens@atmos.washington.edu">ovens@atmos.washington.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Rahul,<br>
<br>
I am not sure if this bug is the same that I found earlier in 3.2,<br>
since I noticed an output bug with a time_step of 216 seconds and<br>
adaptive time stepping was turned off. But, take a look at your<br>
external/esmf_time_f90/ESMF_Clock.F90 around line 1024. It should<br>
look like this:<br>
<br>
IF ( ( .NOT. ( pred1 ) ) .AND. &<br>
( ( pred2 ) .OR. ( pred3 ) ) ) THEN<br>
alarm%alarmint%Ringing = .TRUE.<br>
! alarm%alarmint%PrevRingTime = clock%clockint%CurrTime<br>
alarm%alarmint%RingTimeSet = .FALSE. !it is a one time alarm, it rang, now let it resort to interval<br>
#if 1<br>
! logic above is sufficient to set the PrevRingTime, it is now.<br>
IF ( positive_timestep ) THEN<br>
<br>
I hope that does it for you.<br>
<br>
David<br>
--<br>
David Ovens e-mail: <a href="mailto:ovens@atmos.washington.edu">ovens@atmos.washington.edu</a><br>
Research Meteorologist phone: (206) 685-8108<br>
Dept of Atm. Sciences plan: Real-time MM5 forecasting for the<br>
Box 351640 Pacific Northwest<br>
University of Washington <a href="http://www.atmos.washington.edu/mm5rt" target="_blank">http://www.atmos.washington.edu/mm5rt</a><br>
Seattle, WA 98195 Weather Graphics and Loops<br>
<a href="http://www.atmos.washington.edu/~ovens/loops" target="_blank">http://www.atmos.washington.edu/~ovens/loops</a><br>
<div><div></div><div class="h5"><br>
<br>
On Fri, Jun 25, 2010 at 10:53:29AM -0700, Rahul Mahajan wrote:<br>
> Hi,<br>
> I am using the adaptive time-stepping options in WRFV3.2.<br>
><br>
> I have set the following options in namelist.input that control the dump to<br>
> the wrfout_d0X files<br>
><br>
> step_to_output_time = .true.<br>
> adjust_output_times = .true.<br>
><br>
> According to the documentation, if the above options are used, the output<br>
> times in the wrfout_d0X files for the nests should match the<br>
> history_interval times. However, they dont. Is there a fix that makes sure<br>
> that the output times in the nest be at the requested times? The parent<br>
> domain always outputs at the specified history interval.<br>
><br>
> Here is an example: Say I want to output ever 10 mins, then the output times<br>
> in the parent and the nest are:<br>
> ncdump -v Times wrfout_d01<br>
> Times =<br>
> "2008-08-10_00:00:00",<br>
> "2008-08-10_00:10:00",<br>
> "2008-08-10_00:20:00",<br>
> "2008-08-10_00:30:00",<br>
> "2008-08-10_00:40:00",<br>
> "2008-08-10_00:50:00",<br>
> "2008-08-10_01:00:00",<br>
> "2008-08-10_01:10:00",<br>
> "2008-08-10_01:20:00",<br>
> "2008-08-10_01:30:00",<br>
> "2008-08-10_01:40:00",<br>
> "2008-08-10_01:50:00",<br>
> "2008-08-10_02:00:00",<br>
> "2008-08-10_02:10:00",<br>
> "2008-08-10_02:20:00",<br>
> "2008-08-10_02:30:00",<br>
> "2008-08-10_02:40:00",<br>
> "2008-08-10_02:50:00",<br>
> "2008-08-10_03:00:00",<br>
> "2008-08-10_03:10:00",<br>
> "2008-08-10_03:20:00",<br>
> "2008-08-10_03:30:00",<br>
> "2008-08-10_03:40:00",<br>
> "2008-08-10_03:50:00",<br>
> "2008-08-10_04:00:00",<br>
> "2008-08-10_04:10:00",<br>
> "2008-08-10_04:20:00",<br>
> "2008-08-10_04:30:00",<br>
> "2008-08-10_04:40:00",<br>
> "2008-08-10_04:50:00",<br>
> "2008-08-10_05:00:00",<br>
> "2008-08-10_05:10:00",<br>
> "2008-08-10_05:20:00",<br>
> "2008-08-10_05:30:00",<br>
> "2008-08-10_05:40:00",<br>
> "2008-08-10_05:50:00",<br>
> "2008-08-10_06:00:00" ;<br>
> }<br>
><br>
> ncdump -v Times wrfout_d02<br>
> Times =<br>
> "2008-08-10_00:00:00",<br>
> "2008-08-10_00:10:00",<br>
> "2008-08-10_00:20:16",<br>
> "2008-08-10_00:30:16",<br>
> "2008-08-10_00:40:38",<br>
> "2008-08-10_00:50:45",<br>
> "2008-08-10_01:01:07",<br>
> "2008-08-10_01:11:31",<br>
> "2008-08-10_01:21:35",<br>
> "2008-08-10_01:31:37",<br>
> "2008-08-10_01:41:54",<br>
> "2008-08-10_01:52:14",<br>
> "2008-08-10_02:02:15",<br>
> "2008-08-10_02:12:29",<br>
> "2008-08-10_02:22:37",<br>
> "2008-08-10_02:33:02",<br>
> "2008-08-10_02:43:23",<br>
> "2008-08-10_02:53:23",<br>
> "2008-08-10_03:03:23",<br>
> "2008-08-10_03:13:32",<br>
> "2008-08-10_03:23:32",<br>
> "2008-08-10_03:33:32",<br>
> "2008-08-10_03:43:32",<br>
> "2008-08-10_03:53:32",<br>
> "2008-08-10_04:03:32",<br>
> "2008-08-10_04:13:44",<br>
> "2008-08-10_04:23:58",<br>
> "2008-08-10_04:34:22",<br>
> "2008-08-10_04:44:24",<br>
> "2008-08-10_04:54:39",<br>
> "2008-08-10_05:04:55",<br>
> "2008-08-10_05:15:05",<br>
> "2008-08-10_05:25:18",<br>
> "2008-08-10_05:35:25",<br>
> "2008-08-10_05:45:35",<br>
> "2008-08-10_05:55:50" ;<br>
> }<br>
><br>
> As you can see, the output times in the nest quickly gets out of sync and<br>
> is no longer at the requested interval or at the requested times.<br>
> Furthermore, the end time in the nest is not even outputted to file. (This<br>
> can be a critical issue if the history_interval is large and the nest does<br>
> not reach the end time exactly)<br>
><br>
> If the frames_per_outfile is set to 1 for all domains, the final time file<br>
> for domain 2 is not even created.<br>
><br>
> Any help in this matter will be greatly appreciated.<br>
<br>
</div></div>> _______________________________________________<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>
</blockquote></div><br></div>