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

gen_be error 127

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

Doofus

New member
Hi WRF forum,

Does anyone know how to fix the gen_be error 127?
I thought this meant that the wrf files NUM_LEVEL and gen_be_wrapper are not the same. This is what I have:

1) ./gen_be_wrapper.ksh:
...
---------------------------------------------------------------
Run Stage 4: Calculate horizontal covariances (regional lengthscales).
---------------------------------------------------------------
Beginning CPU time: Tue Feb 26 15:48:46 MST 2019
Ending CPU time: Tue Feb 26 15:53:42 MST 2019
Stage gen_be_diags failed with error 127

2) ncdump -h wrfout_d01_2006-08-02_00\:00\:00 | grep "bottom_top"
bottom_top = 39 ;

3) in gen_be_wrapper.ksh:
export NUM_LEVELS=39

I thought this would fix the issue, but it doesn't. I have also tried NUM_LEVELS = 40 and 38 just in case.

Anyone have any ideas?

Thank you!
 
Just in case someone comes across this, this is my gen_be_diags.log output:

FIO-F-217/unformatted read/unit=23/attempt to read past end of file.
File name = gen_be_stage2.dat unformatted, sequential access record = 1
In source file da_gen_be.f, at line number 2780


If that helps anything.
 
Hi,
As you requested, we have moved this topic to the appropriate location. If this happens in the future, you should have the option to do this, yourself. At the bottom of the forum topic, you'll see an icon that looks like a tool/hammer (see attached screen shot). If you click on that, then you can click 'Move topic' to move the entire topic to a new location. After that, click on the drop-down box and choose the location to which you'd like to move it.
 

Attachments

  • Screen Shot 2019-03-04 at 8.43.59 AM.png
    Screen Shot 2019-03-04 at 8.43.59 AM.png
    63.5 KB · Views: 3,674
Thank you for moving this to the right location.
Is there anyone here who knows what this problem may be or how to fix it?
 
Top