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

hi ,I have problems running ./real.exe.

Erickana

New member
嗨,我在运行 ./real.exe 时遇到问题。
错误如下:
尾部:rsl.out.0000
taskid: 0 主机名: cnode5300
module_io_quilt_old。F 2931 吨
--------------致命的 ---------------
从文件 <STDIN> 行:5817 调用 FATAL
域 2 的父 ID 无效
-------------------------------------------
在节点 0(通信 0 中的排名 0)上中止 (1):调用 MPI_Abort(MPI_COMM_WORLD, 1) 的应用程序 - 进程 0

我将附加 namelist.input 和 namelist.wps 文件
 

Attachments

  • namelist.wps
    786 bytes · Views: 1
  • namelist.input
    1.3 KB · Views: 2
嗨,我在运行 ./real.exe 时遇到问题。
错误如下:
尾部:rsl.out.0000
taskid: 0 主机名: cnode5300
module_io_quilt_old。F 2931 吨
--------------致命的 ---------------
从文件 <STDIN> 行:5817 调用 FATAL
域 2 的父 ID 无效
-------------------------------------------
在节点 0(通信 0 中的排名 0)上中止 (1):调用 MPI_Abort(MPI_COMM_WORLD, 1) 的应用程序 - 进程 0

我将附加 namelist.input 和 namelist.wps 文件
few things i see

domain 1 needs to be 100x100 grid points minimum as per the best practices page"

I would also look to make sure everything matches the sample namelists that are in the test case folder

as for wps

does it make all the files?
 
Your namelist.input looks fine. Can you upload your rsl files that contain the error message for me to take a look?
 
Thank you for your prompt response. Please find attached the requested rsl files for your reference. Let me know if you need any further information .
 

Attachments

  • rsl.error.0000
    345 bytes · Views: 3
REAL crashed at the time when it tried to process data at 2015-02-05_12:00:00. Please try:

(1) run REAL over the period from 2015-01-01_06:00:00 to2015-02-05_06:00:00. If it works fine, we can confirm that REAL works as expected.

(2) double check me_em data at 2015-02-05_12:00:00 to make sure it is correct

Please keep me posted about the results of (1) and (2).
 
REAL crashed at the time when it tried to process data at 2015-02-05_12:00:00. Please try:

(1) run REAL over the period from 2015-01-01_06:00:00 to2015-02-05_06:00:00. If it works fine, we can confirm that REAL works as expected.

(2) double check me_em data at 2015-02-05_12:00:00 to make sure it is correct

Please keep me posted about the results of (1) and (2).
I don't quite understand your reply. Could you please tell me in more detail what I need to do?
 
I meant that you can do a quick test to run REAL program over the period of 2015-01-01_06:00:00 to2015-02-05_06:00:00, which is right before your previous run failed. This will tell us whether there is any issue in REAL. If this test can be done successuly, we will know for sure that the data at 2015-02-05_12:00:00 could be wrong.
 
Top