WRF 4.3.3 error “EXIT CODE: 134” when using BEP/BEM+LCZ

fanhao

New member
Dear WRF Team:

I am using WRF 4.3.3 with BEP/BEM+LCZ schemes. The preprocessing steps (geogrid.exe, ungrib.exe, metgrid.exe, and real.exe) all ran successfully without any errors. However, an error occurred when executing wrf.exe:


===================================================================================

= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES

= EXIT CODE: 134

= CLEANING UP REMAINING PROCESSES

= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES

===================================================================================

YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Aborted (signal 6)

This typically refers to a problem with your application.

Please see the FAQ page for debugging suggestions


In fact, I also used the Chinese urban canopy dataset developed by Professor Ning Zhang from Nanjing University, which I named UCPs_60 and placed in the static data folder. I added this dataset to GEOGRID.TBL and called it in namelist.wps as well. I wonder if the problem is related to this.
I have also provided two namelist files and the rsl.error.0000 log file. Could you please give me some troubleshooting suggestions?

Yours sincerely,
Fan Hao
 

Attachments

Hi Fan, It's difficult to determine whether the new canopy dataset is causing the issues. To test this, will you run a test without using the new canopy dataset - if it runs okay without that, then we know it's the data. Otherwise, we will need to dig a bit deeper.

When you run WRF, please also set "debug_level = 0." This parameter has been taken out of the default namelist.input file for the past several versions because it rarely provides any useful information and it causes the rsl* files to be enormous and too junky to read. When the test fails, please package all of the rsl* files into a single *.tar or zipped file and attach that, as well.

I notice you're using a version of WRF that is pretty old/outdated. Is there a reason you need to use V4.3.3? If not, try using the latest version (v4.7.1) to see if code modifications and bug fixes since then may have corrected your issue.
 
Dear Kwerner:
I commented out the debug_level line, commented out all lines related to UCPs_60 in GEOGRID.TBL, and removed references to UCPs_60 in namelist.wps. Then I re-ran the WPS and WRF simulations, but the same error still occurred. I have packed all the rsl log files.


I use WRF 4.3.3 because this is the standard version adopted by our research team, and it has worked without issues in other similar studies.


Could you please help me analyze the possible causes of this problem?

Yours sincerely,
Fan Hao
 

Attachments

Back
Top