The error in running WRF-CROCO

coupling (ocean-wave-atm)
1

Hello，When I run the WRF-CROCO coupling model, the following error occurs. The error shows that namelist is not read, but I am not sure how this error occurs. How can I solve this problem? Do you have any suggestions?

(oasis_abort) ABORT: CALLING ABORT FROM OASIS LAYER NO
W (oasis_abort) ABORT: See the log files in the run dire
ctoryAbort(1) on node 0 (rank 0 in comm 480): application ca
lled MPI_Abort(comm=0x84000004, 1) - process 0

The error in croco.log:
GET_INITIAL - unable to find variable: hbl
in input NetCDF file: ./croco_ini.nc ==> Initialized to zero state.
>> CAUTION in case of #define EXACT_RESTART <<
If it is the case
- OK if it is a ‘cold start’ i.e coming from a 3rd-party initial file
- otherwise if it is a ‘hot start’ i.e from a restart file produced by this code:
=> problem: run is not restartable
=> check your initial file

out_run.txt
gribmap.txt
nout.000000.txt
croco.log
debug.01.000000.txt
rsl.out.0000.txt
rsl.error.0000.txt
C:\fakepath\namelist.input.txt

Here are my other files.
debug.02.000003.txt
job_cpl02_exp1_20130101_20130101.sh
myenv_mypath.sh
myjob.sh
mynamelist.sh

=================================================================
AND when I run the program on my personal computer instead of a cluster, I encounter this error. I’ve tried increasing the stack size with ‘ulimit -s unlimited,’ but it doesn’t seem to be taking effect.
out_run.txt

And the “wrfout” file has appeared
image description

2

The message in croco.log is not your issue (it is normal). I have checked the different logs your provided but could not find the error, yet. Can you provide the debug.02.00000 file? as well as your job output (e.g. job_…oXXXXXX)? Can you also provide your mynamelist.sh and myjob.sh files?

3

Ok, I’ll add those files in the comments.

4

Hello, I have added some files to the original post.

5

May I ask for your email, please? I often have to wait a considerable amount of time to receive feedback when asking questions here.