in case we lose power or have to turn off the pc for awhile?


just wondering.

> in case we lose power or have to turn off the pc for awhile?
>
>
> just wondering.
>
Absolutely. It stores intermediate information to the hard drive every 144 timesteps (3 model days).

good to know. probably won't lose more then 15 minutes worth of cpu time in case of an outage then.




join USA. click sig for info. expanding into all BOINC projects
<a href="http://usa.duane-n-lisa.net"><img src="http://usa.duane-n-lisa.net/signature.php?id=1918"></a>

I think the setting "write to hard disk" is the check point, I'm not totally sure. Got my set to default, which is 60 seconds any way.

&gt; I think the setting "write to hard disk" is the check point, I'm not totally
&gt; sure. Got my set to default, which is 60 seconds any way.
&gt;
Might be that too. But checking on my system, there is writing to the hard drive every 3 model days at 0030 UTC as in the old client.

&gt; &gt; I think the setting "write to hard disk" is the check point, I'm not
&gt; totally
&gt; &gt; sure. Got my set to default, which is 60 seconds any way.
&gt; &gt;
&gt; Might be that too. But checking on my system, there is writing to the hard
&gt; drive every 3 model days at 0030 UTC as in the old client.
&gt;
&gt;
The "write to hard disk" setting is the minimum time between checkpoints. The project does not have to checkpoint that frequently. If a project wanted to checkpoint every 30 seconds with that setting at 60 it would wait until 60 seconds before checkpointing. A project that wants to checkpoint every 90 seconds will do so providing the setting is less than 90 seconds.
<br>John Keck
BOINCing since 2002/12/08

This model checkpoints itself every 144 timesteps, which is roughly every 15 minutes on a typical PC (say a P4/1.6Ghz). Of course for you guys running at 2 seconds per timestep it's more like every 5 minutes! Since it's "built in" to the model it doesn't respond to BOINC checkpoint settings or requests, it's just coded at 144 I do a "boinc_checkpoint_completed()" so boinc knows about it. If you stop the run one timestep after a multiple of 144 you can be sure that it is there (BOINC CPU time goes back to the time at the last 144 anyway).