Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

WRF completes successfully but not going out to end time specifications

J

jamesrup

New member
Hi all,

I'm having a strange problem. It's strange because I'm not getting an error: I achieve the highly sought-after "SUCCESS COMPLETE WRF"

What's strange is that it only integrates forward out to 3 hours model time, regardless of what I set in the namelist. I'm attaching both namelist.input and namelist.output. The values in namelist.output seem to confirm that my specifications for a 24-hour run are successfully being read in and applied, and yet it completes at 3 hours every time.

I'm using WRF latest version, and ideal. The test_convrad case, slightly modified. Let me know if you need to see anything else. FWIW, I'm not having this problem on a different computer. That may not help. :)

Ideas??

Thanks!
James
 

Attachments

  • namelist.output.txt
    85.3 KB · Views: 1
  • namelist.input.txt
    4.7 KB · Views: 2
James,

This seems not a model issue. Did you check whether you have enough storage space for the case?

Since you set
frames_per_outfile = 1000,

I suppose you only have a single wrfout file generated. How many times of data do you have in that file? If the rsl file indicates that the case is run successfully but you only have 3 hours of data saved in wrfout, it indicates that either the space is not enough or something is wrong with your netCDF lib.

If the storage space is not an issue, I would suggest you reinstall netCDF and WRF, then try again.
 
Hi Ming,

Thanks a lot for your reply. I'm doing this on Derecho scratch, so there's definitely no space limitation. I can try doing single time step files. But just out of curiosity, if it were a space limitation issue, wouldn't that crash the model?

Since I get the message "SUCCESS COMPLETE WRF" it makes me think the maximum time step is somehow not being set properly.

I will also test a previous version of WRF and/or try recompiling as you suggest to see if that fixes it.
 
James,

Can you point me to the working directory where you run the case?

Also, would you please turn off the adaptive time step option, then rerun this case? Please let me know whether you still have the issue.

Thanks.
 
Ming,

I'm surprised to say that turning off adaptive time stepping worked! Is that a bug?

The directory I've been running it is /glade/derecho/scratch/ruppert/wrf-ideal/smalldom

Cheers,
James
 
I was able to reproduce this bug on a different computer, suggesting it is indeed a bug. Just submitted that on the WRF github.

Thanks for the suggestion, Ming!

James
 
James,
This is definitely a bug. Thanks for reporting this. We will look into this issue and get back to you if we find a solution.
Ming
 
You must log in or register to reply here.
Top