[Wrf-users] Wrf-users Digest, Vol 73, Issue 4

V.YesuBabu yesubabu2006 at gmail.com
Tue Sep 7 21:51:21 MDT 2010


Dear Will
The Same Problem I got 6 months back. It depends on your time step(delta T)
 and input boundary files interval .I mean you input gfs files interval is
21600(6hours) then  time step for domain(delta T) should be divisible by
your delta T without remainder then it won't give error
like this .

On 7 September 2010 23:30, <wrf-users-request at ucar.edu> wrote:

> Send Wrf-users mailing list submissions to
>        wrf-users at ucar.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://mailman.ucar.edu/mailman/listinfo/wrf-users
> or, via email, send a message with subject or body 'help' to
>        wrf-users-request at ucar.edu
>
> You can reach the person managing the list at
>        wrf-users-owner at ucar.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wrf-users digest..."
>
>
> Today's Topics:
>
>   1. fdda time problem in WRF V3.2 (Will Thurston)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 4 Sep 2010 15:25:21 +1000
> From: Will Thurston <willthurston at gmail.com>
> Subject: [Wrf-users] fdda time problem in WRF V3.2
> To: wrf-users at ucar.edu
> Message-ID:
>        <AANLkTikXKf3WTTTDxDRConYZzXuCo1_dAvsrmKtiy9g_ at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> I'm running a nested (4 domain) simulation using fdda at 6 hourly
> intervals with WRF V3.2 (having downloaded the fixed reg_parse.c and
> recompiled). The simulation runs fine until 6 hours of model time,
> when it crashes.
>
> >From looking at rsl.out.0000 the nudging happens correctly on the
> three innermost domains, but fails on d01, because multiples of the
> timestep on this domain don't coincide exactly with 6h, whereas they
> do on the other domains (timesteps of 81s, 27s, 9s, 3s). The exact
> error given is:
>
>  Time in file: 2010-08-04_06:00:00
>  Time on domain: 2010-08-04_06:00:27
>  **WARNING** Time in input file not equal to time on domain **WARNING**
>  **WARNING** Trying next time in file wrffdda_d01 ...
>  Time in file: 2010-08-04_12:00:00
>  Time on domain: 2010-08-04_06:00:27
>  **WARNING** Time in input file not equal to time on domain **WARNING**
>  **WARNING** Trying next time in file wrffdda_d01 ...
>  Time in file: 2010-08-04_18:00:00
>  Time on domain: 2010-08-04_06:00:27
>  **WARNING** Time in input file not equal to time on domain **WARNING**
>  **WARNING** Trying next time in file wrffdda_d01 ...
>  Time in file: 2010-08-05_00:00:00
>  Time on domain: 2010-08-04_06:00:27
>  **WARNING** Time in input file not equal to time on domain **WARNING**
>  **WARNING** Trying next time in file wrffdda_d01 ...
>  Time in file: 2010-08-05_06:00:00
>  Time on domain: 2010-08-04_06:00:27
>  **WARNING** Time in input file not equal to time on domain **WARNING**
>  **WARNING** Trying next time in file wrffdda_d01 ...
>  Time in file: 2010-08-05_12:00:00
>  Time on domain: 2010-08-04_06:00:27
>  **WARNING** Time in input file not equal to time on domain **WARNING**
>  **WARNING** Trying next time in file wrffdda_d01 ...
>  Time in file: 2010-08-05_18:00:00
>  Time on domain: 2010-08-04_06:00:27
>  **WARNING** Time in input file not equal to time on domain **WARNING**
>  **WARNING** Trying next time in file wrffdda_d01 ...
>  Time in file: 2010-08-06_00:00:00
>  Time on domain: 2010-08-04_06:00:27
>  **WARNING** Time in input file not equal to time on domain **WARNING**
>  **WARNING** Trying next time in file wrffdda_d01 ...
>  Time in file: 2010-08-06_06:00:00
>  Time on domain: 2010-08-04_06:00:27
>  **WARNING** Time in input file not equal to time on domain **WARNING**
>  **WARNING** Trying next time in file wrffdda_d01 ...
>  Time in file: 2010-08-06_12:00:00
>  Time on domain: 2010-08-04_06:00:27
>  **WARNING** Time in input file not equal to time on domain **WARNING**
>  **WARNING** Trying next time in file wrffdda_d01 ...
>  Time in file: 2010-08-06_18:00:00
>  Time on domain: 2010-08-04_06:00:27
>  **WARNING** Time in input file not equal to time on domain **WARNING**
>  **WARNING** Trying next time in file wrffdda_d01 ...
>           2 input_wrf: wrf_get_next_time current_date: 2010-08-06_18:00:00
> Sta
>  tus =           -4
>  -------------- FATAL CALLED ---------------
>  FATAL CALLED FROM FILE:  <stdin>  LINE:     715
>  ... Could not find matching time in input file wrffdda_d01
>  -------------------------------------------
>
> Is there a way to fix this, other than selecting a timestep that ensures
> the fdda times are an integer multiple of the timestep? I have tried
> this run with
> WRF 3.1.1 previously and didn't have any problems with the nudging.
>
> Thanks,
> Will.
>
>
> ------------------------------
>
> _______________________________________________
> Wrf-users mailing list
> Wrf-users at ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/wrf-users
>
>
> End of Wrf-users Digest, Vol 73, Issue 4
> ****************************************
>



-- 
**************************************
V  Yesubabu,
Project Engineer,CAS-SECG,C-DAC,
Main Building,Pune University,
Ganeshkhind,Pune-411007.
Phone :020-25704226
yesubabu2006 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/wrf-users/attachments/20100908/5017ea7f/attachment.html 


More information about the Wrf-users mailing list