startup run: Internal sea-ice clock not in sync with Sync Clock

[Zhu Zhu]

Hello all,

I am porting CESM2.2.0 to a new machine. I've successfully run F2000climo compset. But got errors below when turning to B1850 compset:

cice ymd= 101 cice tod= -84600
sync ymd= 101 sync tod= 1800
ERROR: ice_run_mct:: Internal sea-ice clock not in sync with Sync Clock
cice ymd= 101 cice tod= -84600
sync ymd= 101 sync tod= 1800
ERROR: ice_run_mct:: Internal sea-ice clock not in sync with Sync Clock
cice ymd= 101 cice tod= -84600
sync ymd= 101 sync tod= 1800
ERROR: ice_run_mct:: Internal sea-ice clock not in sync with Sync Clock
cice ymd= 101 cice tod= -84600
sync ymd= 101 sync tod= 1800
ERROR: ice_run_mct:: Internal sea-ice clock not in sync with Sync Clock
ERROR: ice_run_mct:: Internal sea-ice clock not in sync with Sync Clock
Image PC Routine Line Source
cesm.exe 000000000303BFC7 tracebackqq_ Unknown Unknown
cesm.exe 0000000002C51F0E Unknown Unknown Unknown
cesm.exe 00000000015DDB1E Unknown Unknown Unknown
cesm.exe 000000000043AE1E Unknown Unknown Unknown
cesm.exe 000000000041DD5E Unknown Unknown Unknown
cesm.exe 000000000043AAAD Unknown Unknown Unknown
cesm.exe 000000000041BD22 Unknown Unknown Unknown
libc-2.28.so 000015283D10F7B3 __libc_start_main Unknown Unknown
cesm.exe 000000000041BC2E Unknown Unknown Unknown
Abort(1001) on node 97 (rank 97 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1001) - process 97
Sun Nov 10 21:32:33 CST 2024 -- CSM EXECUTION HAS FINISHED

log file is attached bellow. I have searched this error, but previous posts of similar problems were restart running. This is a default startup running, and I don't know what's went wrong. Any suggestions would be helpful. Thanks very much!

 

[dbailey]

This sounds like you are reading an ice restart that does not match the RUN_REFDATE. Is this truly a startup run? A hybrid?

 

[Zhu Zhu]

This sounds like you are reading an ice restart that does not match the RUN_REFDATE. Is this truly a startup run? A hybrid?

Hi dbailey,

Thank you for reminding me. This is truly a startup run. But I set RUN_STARTDATE by "./xmlchange --file env_run.xml --id RUN_STARTDATE --val '0000-01-01' ". After I remove this setting, it runs well. The default RUN_STARTDATE is 0001-01-01. So the RUN_STARTDATE can't be changed in startup run?

Best,
Zhu

 

[slevis]

I think that you can change it, but I suspect that RUN-STARTDATE's year needs to be greater than zero.

 

[Zhu Zhu]

I think that you can change it, but I suspect that RUN-STARTDATE's year needs to be greater than zero.

Yes, RUN-STARTDATE's year needs to be greater than zero. Thanks for your reply.