Wrf model executing error

[Amrutha]

While executing real. exe and wrf. exe shows error. How to solve.

 

[kwerner]

Without any additional information, it's difficult to help with this. If an error occurs with real.exe, then wrf.exe will also give an error. Can you run real.exe again and then package the error/out logs (e.g., rsl.error.* and rsl.out.*) into a single *.tar or zipped file and attach that? Please also attach your namelist.input file. Thanks.

 

[Amrutha]

I am simulating just example data (Katrina hurricane). I attached the rsl.error.* and rsl.out.0000 and namelist.input. Can you please go through this?

 

[Amrutha]

./real.exe successfully executed. then when i execute ./wrf.exe this happening.

 

[kwerner]

Hi,
Thanks for sharing that. Can you try using ra_sw_physics = 1 and see if that works better? Typically we recommend that if ra_lw_physics = 1, then ra_sw_physics should, as well.

 

[Amrutha]

I tried this also.. But same error happened which I already mentioned.. Can you please solve this. I want help.

 

[kwerner]

In the directory where you're running this case (either in wrf/run or wrf/test/em_real), are there files that exist "CAMtr_volume_mixing_ratio.* ? If so, can you issue the following command and then attach the cam.txt file?

ls -ls CAMtr_volume_mixing_ratio* >& cam.txt

 

[Amrutha]

I used the above code. I attached the namelist, rsl.out and rsl.error files. Can you please go through.

 

[kwerner]

There is now a new error, related to one of your namelist settings:

  ------ ERROR while reading namelist physics ------
Maybe here?:      bldt                                = 0,
Maybe here?:      use_ozone                           = .true.,
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:   11575
ERRORS while reading one or more namelists from namelist.input.

The namelist parameter "use_ozone" does not exist in the WRF code. Maybe it did many years ago, but it hasn't been in the code since at least V4.0. Try removing that line and running it again. If you continue to get new errors not related to the original error regarding CAMtr_volume_mixing_ratio, please start a new thread on the forum - that way we can keep threads specific to each error. Thanks!