Hi all, This is a follow up on a problem mentioned in one of the technical topics ( Payu potentially miscalculating a leap year ) I am having trouble trying to run one particular year in ACCESS-ESM1.5. I have completed 299 years of a simulation, and it just won’t run for the 300th year. I tried star…

Hello, I tried one suggestion from @tiloz , which was successful and my model has now crossed the 400th year and is at 404th year right now. Below is the suggestion that worked: (thanks a lot @tiloz ) I set up a new run, a copy of the existing one, but taking the last restart from the current run…

From @holger : Looking into the configuration, the model crashes in the year 400. The crash comes from OASIS, with the error message oasis_advance_run at 31536000 31536000 ERROR: t_surf oasis_advance_run ERROR model time beyond namcouple maxtime 31536000 31536000 oasis_advance_…

I’m still working on it. It seems as if MOM knows the year is 400, at least from the file time_stamp.out.

Made any progress with this @holger ? Is there anything we can do to assist?

[image] HIMADRI_SAINI: So now, I have new output and restart folders as output/restart001,002…, but the model year continues as 400,401 etc. In case it is useful in the future, you can tell payu what number to start the run from. In your case adding a restart option to your config.yaml file …

Thanks. I will keep this in mind.

I had another thought: ACCESS-OM2 had issues with MOM5 using a gregorian calendar, but actually implementing proleptic_gregorian Incorrect calendar in MOM output opened 03:28AM - 22 Oct 18 UTC (UTC) closed 01:23A…

Hi, A quick note to report that I am still running into this problem in a different simulation. I have reached year 400 (a difficult leap / non-leap year to get right apparently), and the model hangs. I’m going to bypass it for now by “jumping” the calendar to year 2400, to make it easier to keep t…

Hi @HIMADRI_SAINI , thanks for bringing this up in the working group meeting. I’d be interested in looking into this error and trying to reproduce it. Would you still have the configurations and restart files for the years just prior to the crash?

Hi @spencerwong . Sorry, I have been looking into my simulations and found that the last restart I have in that simulation is the 395th year. I guess I deleted the next 4 years while transferring or archiving my data. What I can do is run my simulation for the next 5 years, and if/when it gets stuck …

Payu: Model exited with error code 1; aborting. Stuck at a leap year

Earth System Earth System Model

Topic		Replies	Views
Payu potentially miscalculating a leap year Technical payu , access-esm	9	427	15 March 2024
Restart problem (atmosphere) Earth System help , payu , restart , access-esm	22	793	24 March 2025
Payu issues for ACCESS-ESM1.5 on vk83 Earth System Model help , payu , technical	3	138	5 September 2024
Tips, tricks, and troubleshooting for new ACCESS-ESM 1.5 user Earth System help , payu , access-esm	12	498	5 August 2024
MOM6 Calendar Error (Potentially Payu related?) Technical cosima , payu	14	610	25 May 2023

Payu: Model exited with error code 1; aborting. Stuck at a leap year

Related topics