the case:
yesterday when i left my office my workunit hadsm3fub_0205_005913780_0 had finished about 66 to 67%. Modeldate was around: 1830/1835 proposed ending should be 2050 on timeline.
Duuring the night i´ve got a visual-fortran runtime error.
Restarting the model this morning, my workunit shows me 17th January 2051, still about 67% and timestep 2200 of 259000.
What has happend there? My workunit jumped out of proposed timeline.
Is my work unit destrucetd yet or is it a normal behaviour.

I hope anybody can declare what has happened.

Greetings from center of europe.

P.S.: another older workunit on my pc went through timeline and model-work-percentage more even.

---

The 2050 displayed on the graphics is incorrect, it should read 2065. There are three phases, each of 259280 timesteps, so you observed the transition from phase 2 to phase 3.

For some general background information about the different types of models, see the \'README - running the model\', first two posts in the \'information\' section. The link to the readmes is in my signature.

Do you have the screensaver turned on? It may help to turn off the screensaver (use the \'show graphics\' button instead)

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

The 2050 displayed on the graphics is incorrect, it should read 2065. There are three phases, each of 259280 timesteps, so you observed the transition from phase 2 to phase 3.

For some general background information about the different types of models, see the \'README - running the model\', first two posts in the \'information\' section. The link to the readmes is in my signature.

Do you have the screensaver turned on? It may help to turn off the screensaver (use the \'show graphics\' button instead)

Thx for this extensive information.
It heled me to understand a little bit more.

I dont´t run BOINC in screensaver-mode only as background-application with using \'show graphics\' to view graphics)

Your answr calmed me down, because i have lost som units in the past which where not repairable because of fortran-error.

---