overshoot coupling time error while running CAM6 simulation

[arti-14]

Hi,
I am running the CAM using the F2000_climo compset for the duration 2011-05-09, 21 UTC to 2011-05-15, 21 UTC. I changed the user_nl_cam to change the namelist. The model build has been successful. But when I run the model, I am getting an error 'overshoot coupling time on 2011-05-11'. I have attached the log files for reference.

Thank you for your help in advance.

Best Regards,
Arti Jadav

 

[nusbaume]

Hi Arti,

This appears to be a land-ice/CISM error, so I am moving this thread over to the land ice forum in case someone there with more knowledge on that particular component can answer your question.

Hope that helps, and have a great day!

Jesse

 

[sacks]

It sounds like you are starting the model mid-day, rather than at the day boundary (i.e., 0Z). This is currently problematic with compsets that include CISM (the land ice model). If you don't care about land ice (Greenland) diagnostics, I recommend changing your compset to use SGLC in place of CISM2%NOEVOLVE. Specifically: In the version of the model I'm looking at, I see F2000climo defined as: 2000_CAM60_CLM50%SP_CICE%PRES_DOCN%DOM_MOSART_CISM2%NOEVOLVE_SWAV. Assuming that is how it is defined in your code version, too, you can use the modified
2000_CAM60_CLM50%SP_CICE%PRES_DOCN%DOM_MOSART_SGLC_SWAV instead (via --compset 2000_CAM60_CLM50%SP_CICE%PRES_DOCN%DOM_MOSART_SGLC_SWAV at create_newcase time). The resulting run will differ slightly over Greenland, but not hugely so.

 

[Francesca Bruno]

Hi, Arti Jadav. I met the same problem. Have you already solved it?

 

[katec]

Hi everybody,

I just wanted to add a comment here as a note in case anybody runs across this conversation after hitting this error. There are two issues (generally) that cause this error to happen. One is what Bill mentioned above, CISM does not like to restart at times that are not 00000 (not date boundaries). If this is causing your error, then you can either find a restart that is on a date boundary (time: 00000) or create a case that does not use CISM as Bill describes.

The other reason this error occurs is often when a user is trying to start a new hybrid or branch run but "CONTINUE_RUN" is still set to "TRUE". When this happens, CISM ignores the refdate start date and restarts fully from the restart file, and this often causes the time calculation to be out of line.

Whenever you are starting a new run of any type (Branch or Hybrid), the "CONTINUE_RUN" xml variable MUST BE set to "FALSE" or weird things can happen.

Thanks!
Kate