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

HUJI SBM

S

Sanjeev Singh

New member
I encounter following error during HUJI SBM fast mp 30
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 6206
module_mp_FAST_SBM_INIT: error opening hujisbm_DATA on unit,model stop 21
 
Last edited:
Can you please attach your namelist.input file, as well as the full out/error log(s). If you have multiple rsl* files, please package them into a single *.tar or zipped file and attach that. Thanks!
 
Thanks for entertaining my issues. I have attached my namelist and rsl files. For your convenience i have re-run with only one core to get single rsl file for error and out. Also to mention that I am using WRF 4.5
 

Attachments

  • namelist.input
    4 KB · Views: 1
  • rsl.error.0000
    6 KB · Views: 1
  • rsl.out.0000
    6.2 KB · Views: 1
Last edited:
Thanks for taking a look. If you haven't already, can you try downloading the SBM_input_33.tgz file and unpacking it in your running directory so from test/em_real (or run/ - depending on where you're running wrf), you have the directory SBM_input_33?

If you still get the same error, from your running directory, will you issue
Code: 
ls -ls >& ls.txt

and attach that ls.txt file so I can take a look at what files you have available? Thanks!
 
kwerner said:
Thanks for taking a look. If you haven't already, can you try downloading the SBM_input_33.tgz file and unpacking it in your running directory so from test/em_real (or run/ - depending on where you're running wrf), you have the directory SBM_input_33?

If you still get the same error, from your running directory, will you issue
Code: 
ls -ls >& ls.txt

and attach that ls.txt file so I can take a look at what files you have available? Thanks!
Click to expand...
i have already downloaded SBM_input_33 in early phase only. As per your direction i have attached ls.txt
 

Attachments

  • ls.txt
    8.2 KB · Views: 2
I apologize for asking you for one more thing to do. Can you go into the SBM_input_33/ directory and issue

Code: 
ls -ls >& ls_33.txt

and then attach the ls_33.txt? I expect everything to be in there, as is necessary, but I just want to make sure there isn't anything missing. Thanks!
 
Hi,
Apologies again for the delay. I've been trying to understand what could be happening here because the error message you're getting can only indicate a file is missing, or it's not able to read it, or something like that. However, based on the text files you've sent, it seems that you do have everything there, and they are all the right sizes.

Can you package up the following and share it with me? This packaged file will be too large to attach, so take a look at the home page of this forum for instructions on sharing large files.

- wrfbdy_d01
- wrfinput_d0*
- wrflowinp_d0*
 
Thank you so much for sending those. Using your files and your namelist, I'm able to run without any problems. I looked a little closer at the listing of files in your running directory, and the only thing that *may* be the issue is that your "scattering_tables_2layer_high_quad_1dT_1%fw_110"
directory is much smaller than mine, which leads me to wonder if you're missing something. Can you try removing that directory from your running directory, then grab this file and unpacking it in your running directory, then try again. Go ahead and use however many processors you need to - using only 1 processor will take a really long time to run this, if it's actually able to at all.

If it still fails, since I'm unable to repeat the issue, the only other thing I can suggest is to try building WRF again, using a clean version of the code (download or use 'git clone' to get one that's pristine), and building it again. You'd then need to make sure to download the scattering_tables_2layer_high_quad_1dT_1%fw_110 and SBM_input_33 directories again, as well.
 
My problem is still not fixed i re-downloaded the required files as per your instruction in a freshly installed WRF. I ran the WRF with 64 cores. But still the problem persists. I am using WRF v4.5. I dont think i have any issue with whatever we discussed because i already did it before submitting this problem to this forum. i guess this issue may be because of my CPU architecture or may be WRF version
 
You must log in or register to reply here.
Top