Hi All,<br><br>I checked the code. The subroutine to adapt time steps is no longer called for NESTED domains unless at a boundary update time, so it is not able to adapt the time step to hit the output time, except for the outer domain.<br>
<br>Here is the 3.1.1 code in solve_em.F when it worked:<br><br> ! Adaptive time step: Added by T. Hutchinson, WSI 3/5/07<br> ! In this call, we do the time-step adaptation and set time-dependent lateral<br> ! boundary condition nudging weights.<br>
!<br> IF (config_flags%use_adaptive_time_step) THEN<br> CALL adapt_timestep(grid, config_flags)<br> adapt_step_flag = .TRUE.<br> ELSE<br> adapt_step_flag = .FALSE.<br> ENDIF<br>
! End of adaptive time step modifications<br><br>And here is the equivalent code in 3.2.1:<br><br> ! Adaptive time step: Added by T. Hutchinson, WSI 3/5/07<br> ! In this call, we do the time-step adaptation and set time-dependent lateral<br>
! boundary condition nudging weights.<br> !<br> IF ( (config_flags%use_adaptive_time_step) .and. &<br> ( (.not. grid%nested) .or. &<br> ( (grid%nested) .and. (abs(grid%dtbc) < 0.0001) ) ) )THEN<br>
CALL adapt_timestep(grid, config_flags)<br> adapt_step_flag = .TRUE.<br> ELSE<br> adapt_step_flag = .FALSE.<br> ENDIF<br> ! End of adaptive time step modifications<br><br>The variable dtbc is descripbed as: "TIME SINCE BOUNDARY READ." Since I don't know the purpose of the changes, I won't suggest changing 3.2.1 to look like 3.1.1<br>
<br>I also looked at the code related to the configuration variable "adjust_output_times". To me it looks like the output string for the file name is changed when this is "true" but not the timestep or anything else.<br>
<br>Kevin Nuss<br><br><br><div class="gmail_quote">On Mon, Jun 28, 2010 at 3:05 PM, Zulauf, Michael <span dir="ltr"><<a href="mailto:Michael.Zulauf@iberdrolausa.com">Michael.Zulauf@iberdrolausa.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">FYI, I've seen this exact issue with 3.2 also (and _only_ 3.2). I've<br>
had a couple emails with wrfhelp (the last being about a month ago), but<br>
haven't heard back as to whether they were able to reproduce or<br>
otherwise shed some light on this issue. I expect they're busy. But<br>
I'll ping them again here. ;-)<br>
<br>
I've been planning to try a different set of compilers, and see if that<br>
makes any difference. But I've been busy too.<br>
<br>
So, no help, but at least you're not alone.<br>
<br>
Mike<br>
<div><div></div><div class="h5"><br>
<br>
-----Original Message-----<br>
Date: Fri, 25 Jun 2010 11:17:35 -0700<br>
From: Rahul Mahajan <<a href="mailto:rahulm@atmos.uw.edu">rahulm@atmos.uw.edu</a>><br>
Subject: Re: [Wrf-users] Adaptive Time-step output times<br>
mismatch/incorrect<br>
To: David Ovens <<a href="mailto:ovens@atmos.washington.edu">ovens@atmos.washington.edu</a>><br>
Cc: <a href="mailto:wrf-users@ucar.edu">wrf-users@ucar.edu</a><br>
Message-ID:<br>
<<a href="mailto:AANLkTikc8pDwNWZhHCtmbP0LrJ6m8Sy0chrsCp7pzqGC@mail.gmail.com">AANLkTikc8pDwNWZhHCtmbP0LrJ6m8Sy0chrsCp7pzqGC@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
David,<br>
It does look like the way you say. So, I suppose the issue is someplace<br>
else.<br>
<br>
Thanks,<br>
Rahul.<br>
<br>
On Fri, Jun 25, 2010 at 11:09 AM, David Ovens<br>
<<a href="mailto:ovens@atmos.washington.edu">ovens@atmos.washington.edu</a>>wrote:<br>
<br>
> 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 =<br>
clock%clockint%CurrTime<br>
> alarm%alarmint%RingTimeSet = .FALSE. !it is a one<br>
time<br>
> 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>
</div></div>*****************************<br>
<br>
<br>
<br>
<br>
This message is intended for the exclusive attention of the address(es) indicated. Any information contained herein is strictly confidential and privileged, especially as regards person data,<br>
which must not be disclosed. If you are the intended recipient and have received it by mistake or learn about it in any other way, please notify us by return e-mail and delete this message from<br>
your computer system. Any unauthorized use, reproduction, alteration, filing or sending of this message and/or any attached files to third parties may lead to legal proceedings being taken. Any<br>
opinion expressed herein is solely that of the author(s) and does not necessarily represent the opinion of Iberdrola. The sender does not guarantee the integrity, speed or safety of this<br>
message, not accept responsibility for any possible damage arising from the interception, incorporation of virus or any other manipulation carried out by third parties.<br>
<div><div></div><div class="h5"><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>
</div></div></blockquote></div><br>