Error running ndown : "Found *date*_06:00 before I found *date*_00:00"

[Arty]

Hello,

I got previous data from a 33 vert. levels simulation accross South Pacific I want to use for a downscaling simulation over a smaller area. I'm aware of UPP possibilities and I intend to try it next, but I would like to make it work with ndown.

I passed the real.exe step and got all required files (including specific ndown files) cheating a little bit : I got 33-levels wrfouts* but 50-levels met_em --> that's the only way I managed to run real.exe / else I got "Not enough levels to reach p_top (5000)" error when setting 33 levels. I was said it shouldn't be problematic, but it might anyway (now or later), so it seems legit to inform you.
So, when I run my test configuration (see attached file for namelist) for 5 days, it crashes immediately and I get this in rsl.error.0000 :

-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 366
Found 2005-02-02_06:00:00 before I found 2005-02-02_00:00:00.
-------------------------------------------

I checked (the best I could) all paths in the PBS script to exclude this possibilty : seems OK. Anyway, this doesn't seem like a file location problem, as one file is found, but not the previous one. I also checked that I have all met_em* and other files for each required 6-hours timesteps : I do ; only wrfout* used as input for downscalig are recorded as daily files.

I'm kind of stuck here so if anyone have an idea how to solve this problem, it'd be great.

Also : could someone tell me where should I look about this line :

FATAL CALLED FROM FILE: <stdin> LINE: 366

There must be something intersting to understand the error, but I don't know where to look (except the LINE number).

Thank you.

 

[kwerner]

Hi,
A couple of questions:
1) Are you getting this error when you run ndown.exe? Can you detail the steps you took and which files you have before/after each step?
2) When you say you obtained previous data, do you mean you have wrfout* files from a previous run? Do you still have the wrfbdy_d01 file for the parent domain?
3) Can you attach the full output/error file (e.g., rsl.error.0000)?
Thanks!

 

[Arty]

Hi,
A couple of questions:
1) Are you getting this error when you run ndown.exe? Can you detail the steps you took and which files you have before/after each step?
2) When you say you obtained previous data, do you mean you have wrfout* files from a previous run? Do you still have the wrfbdy_d01 file for the parent domain?
3) Can you attach the full output/error file (e.g., rsl.error.0000)?
Thanks!

Hello kwerner

1) Yes (see Help & tips using ndown for config details)

2) Yes, wrfout* I'm willing to use as input come from previous PhD work
And no : I recreated wrfbdy from a new config which d01 is exactly the same as my wrfout* and forced by CFSR --> because I've been told I only need few timesteps (via real.exe) to initiate ndown/wrf.exe.

3) I didn't save it and I circumvented the problem (and got new errors... so much fun xD) :
I just changed my namelist to start simulation on the 3rd of February instead of 2nd. First timestep is always 06:00 and not 00:00 hence I was missing the 00:00 timestep for the 2nd of February and simulation crashes.

This case can be closed. Thanks for your answer anyway, it's very conforting not feeling alone in all this.

 

[kwerner]

Thank you for updating the post with the problem and solution. It may help another user in the future! Glad you got it figured out.

 

[Kongs]

Hello kwerner

1) Yes (see Help & tips using ndown for config details)

2) Yes, wrfout* I'm willing to use as input come from previous PhD work
And no : I recreated wrfbdy from a new config which d01 is exactly the same as my wrfout* and forced by CFSR --> because I've been told I only need few timesteps (via real.exe) to initiate ndown/wrf.exe.

3) I didn't save it and I circumvented the problem (and got new errors... so much fun xD) :
I just changed my namelist to start simulation on the 3rd of February instead of 2nd. First timestep is always 06:00 and not 00:00 hence I was missing the 00:00 timestep for the 2nd of February and simulation crashes.

This case can be closed. Thanks for your answer anyway, it's very conforting not feeling alone in all this.

Hello, I have also encountered this problem with you. May I know how to solve it?

 

[Arty]

Hello, I have also encountered this problem with you. May I know how to solve it?

I had input files which started at different times between wrfinput (created by WPS/REAL) starting at 00:00 and wrfout (input for ndown.exe) starting at 06:00. I was missing a timestep so I just did post-schedule my ndown-run start-time to the next day (I could have post-scheduled from just 1 timestep).
Does this help ?

 

[Kongs]

我的输入文件在 wrfinput（由 WPS/REAL 创建）从 00:00 开始和 wrfout（ndown.exe 的输入）从 06:00 开始之间的不同时间开始。我错过了一个时间步，所以我只是将我的 ndown-run 开始时间后安排到第二天（我可以只从 1 个时间步开始后安排）。
这有帮助吗？

Thank you very much for your reply. My input file time is consistent with the wrfout time, but this error still occurs. I will try again. Thank you

 

[george_victor]

Hi! @Kongs, in case you haven't solved the issue yet; the issue is probably because the model is expecting inputs at a certain time interval (interval_seconds in namelist.input), but the wrfout_d0*_<date> file that you use is having a different data/time interval. This mis match results in the error. Changing "interval_seconds" in namelist.input would therefore solve the concern.

For example: interval_seconds=3600 (1 hour)... but your model wrfout_d*_<date> file have data every 3hours, then this error will pop up.

In case there is another reason like @Arty pointed out, please share with us.