Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

Cesm.exe fail when executing the time ../bld/cesm.exe

jgx

jiagongxu
New Member
Hi,
While running the clm5.0.35 The model setup and built has been successful. When I executing the time ../bld/cesm.exe in the run directory, it shows the 'ERROR: ERROR in histFileMod.F90 at line 681' and ' Abort(1001) on node 0 (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1001) - process 0'.
I am trying to run the I2000Clm50SpGs compset with 1x1_vancouverCAN resolution. I have compiled the Netcdf fortran with intel compiler.
I have attached the lnd.log file for the case.

ERROR: ERROR in histFileMod.F90 at line 681
Image PC Routine Line Source
cesm.exe 00000000010ADC77 Unknown Unknown Unknown
cesm.exe 0000000000D5261D shr_abort_mod_mp_ 114 shr_abort_mod.F90
cesm.exe 000000000050F71B abortutils_mp_end 50 abortutils.F90
cesm.exe 0000000000579BE5 histfilemod_mp_ht 681 histFileMod.F90
cesm.exe 0000000000578A2F histfilemod_mp_hi 487 histFileMod.F90
cesm.exe 0000000000520BFC clm_initializemod 577 clm_initializeMod.F90
cesm.exe 0000000000509818 lnd_comp_mct_mp_l 233 lnd_comp_mct.F90
cesm.exe 0000000000438983 component_mod_mp_ 267 component_mod.F90
cesm.exe 00000000004276D4 cime_comp_mod_mp_ 1181 cime_comp_mod.F90
cesm.exe 0000000000435A1C MAIN__ 92 cime_driver.F90
cesm.exe 00000000004182E2 Unknown Unknown Unknown
libc-2.31.so 000014B6F6187083 __libc_start_main Unknown Unknown
cesm.exe 00000000004181EE Unknown Unknown Unknown
Abort(1001) on node 0 (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1001) - process 0
 

Attachments

  • lnd.log.txt
    74.8 KB · Views: 5

oleson

Keith Oleson
CSEG and Liaisons
Staff member
The land log file says you are running release-clm5.0.03, not release-clm5.0.35, is that correct?
I see this in your lnd log file:

htapes_fieldlist ERROR: DECL in fincl( 1 ) for history tape
1 not found
ENDRUN:
ERROR: ERROR in histFileMod.F90 at line 681

It looks like you are requesting DECL in your history output? I don't see that variable being available in either release-clm5.0.03 or release-clm5.0.35.
 

jgx

jiagongxu
New Member
The land log file says you are running release-clm5.0.03, not release-clm5.0.35, is that correct?
I see this in your lnd log file:

htapes_fieldlist ERROR: DECL in fincl( 1 ) for history tape
1 not found
ENDRUN:
ERROR: ERROR in histFileMod.F90 at line 681

It looks like you are requesting DECL in your history output? I don't see that variable being available in either release-clm5.0.03 or release-clm5.0.35.
Sorry, I'm running clm5.0.03 and I accidentally typed the wrong version number
 

jgx

jiagongxu
New Member
The land log file says you are running release-clm5.0.03, not release-clm5.0.35, is that correct?
I see this in your lnd log file:

htapes_fieldlist ERROR: DECL in fincl( 1 ) for history tape
1 not found
ENDRUN:
ERROR: ERROR in histFileMod.F90 at line 681

It looks like you are requesting DECL in your history output? I don't see that variable being available in either release-clm5.0.03 or release-clm5.0.35.
This is my first time to run CLM, and I'm not quite sure what DECL is. Could you please tell me? Thank you very much.
 

jgx

jiagongxu
New Member
The land log file says you are running release-clm5.0.03, not release-clm5.0.35, is that correct?
I see this in your lnd log file:

htapes_fieldlist ERROR: DECL in fincl( 1 ) for history tape
1 not found
ENDRUN:
ERROR: ERROR in histFileMod.F90 at line 681

It looks like you are requesting DECL in your history output? I don't see that variable being available in either release-clm5.0.03 or release-clm5.0.35.
Thank you very much for your advice. The error caused by variable DECL does not exist. After modifying the use_nl_clm file, this case can be run successfully
 
Top