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

CESM2 executes and stops in within 2 minutes INTEL

acgvar

Alvin C.G. Varquez
Member
I encountered a strange error when porting to supercomputer (Intel compilers Intel-mpi) with no clear indication as what could be the problem.

The CaseStatus file reveals:
---------------------------------------------------
2019-11-13 08:19:25: case.run starting
---------------------------------------------------
2019-11-13 08:19:30: model execution starting
---------------------------------------------------
2019-11-13 08:20:49: model execution success
---------------------------------------------------
2019-11-13 08:20:49: case.run error
ERROR: Model did not complete - see /scratch/user/b.day1.0/run/cpl.log.191113-081925
---------------------------------------------------

Inside cpl.log.191113-081925, the error is unclear and ends with:
:
:
:
tfreeze_option is mushy

(seq_mct_drv) : Initialize each component: atm, lnd, rof, ocn, ice, glc, wav, esp
(component_init_cc:mct) : Initialize component atm
(component_init_cc:mct) : Initialize component lnd
(component_init_cc:mct) : Initialize component rof
(component_init_cc:mct) : Initialize component ocn
 

Attachments

  • cpl.log.191113-081925.txt
    41 KB · Views: 19

acgvar

Alvin C.G. Varquez
Member
This issue above was brought about by inconsistency in bathymetry input. It was solved for intel, intel-mpi compilers by appending the following to FFLAGS
-convert big_endian

An issue comes up next which shows:
forrtl: severe (36): attempt to access non-existent record, unit 99, file /CESM/inputdata/ocn/pop/gx1v7/grid/horiz_grid_20010402.ieeer8
 

liyongkang

liyongkang
New Member
This issue above was brought about by inconsistency in bathymetry input. It was solved for intel, intel-mpi compilers by appending the following to FFLAGS
-convert big_endian

An issue comes up next which shows:
forrtl: severe (36): attempt to access non-existent record, unit 99, file /CESM/inputdata/ocn/pop/gx1v7/grid/horiz_grid_20010402.ieeer8
Hello, I had the same issue that "tfreeze_option is mushy", Can you describe the solution in detail? Thanks~
 
Top