[Wrf-users] Adaptive Time-step output times mismatch/incorrect

Fri Jun 25 12:17:35 MDT 2010

David,
It does look like the way you say. So, I suppose the issue is someplace
else.

Thanks,
Rahul.

On Fri, Jun 25, 2010 at 11:09 AM, David Ovens <ovens at atmos.washington.edu>wrote:

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