What does the server state really mean in CPDN? If you look at the list of results from the View link in your account page, you see one of the columns is server status.

I have read the explain, and I understand what this column means on other BOINC projects, but those projects don\'t trickle. Why do some of my ongoing results show \"over\" and others show \"in progress\" under this status?

Is it to do with how recently that result has trickled? I can\'t spot a pattern at all.

River~~

I have the same question too.
One of my results (1347636) shows the \"over\" state, but this result is still crunching, trickling and getting credits.

CPDN is kind of different as of \"state\".
Server will accept further trickles and even final upload - even after WU is beyond deadline.
If you are doing regular backups and - for example - experience a power failure with model crash, you can revert to backup and continue your model.
This is to enable participant to finish the whole model.

In that perspective, I think, it does make more sense.

---

<i>phpBB forum for CPDN, all are </i><a href="http://www.climateprediction.net/board">invited</a>

Hi, Honza !

I aggree with you, that the CPDN behavoir is ok, but I wondered about the over state on a work unit, that hasn\'t reached dead line.

I only want to be sure not to crunch for the paper-basket.

Regards, Frank

...I only want to be sure not to crunch for the paper-basket...

Hi Frank: There is no problem with the \"over\" status, I see it often and the wu still accepts the next trickle. I am sure you do not need to worry about the waste paper basket.

Hi Honza: agreed, but as a hacker myself, when I see more than one outcome from what looks lie the same situation I immediately get curious - what does this difference mean, or if it is meaningless, how does it arise?

I am not worried, just curious

River~~

Perhaps a simple fix like: when newer trickle arrives, put to state from \"over\" to \"In Progress\" again. This may propitiate people\'s curiosity and make it more consistent with the actual situation of individual model progress.

Lookin at my results page, server status ain\'t no right.

---

<i>phpBB forum for CPDN, all are </i><a href="http://www.climateprediction.net/board">invited</a>

Perhaps a simple fix like: when newer trickle arrives, put to state from \"over\" to \"In Progress\" again. This may propitiate people\'s curiosity and make it more consistent with the actual situation of individual model progress.

but what I am curious about is exactly what it is that is making it go to \'over\' in the first place? It does not seem to do it to all results, only to some; and it happens well before the deadline so it aint that.

Is there some kind of time-out that happens between trickles, or what?

Personally I am happy to leave the code as it is, I am saying it is the explanation that is buggy not the code, as users don\'t know what the various values mean. And some hackerish users, like me, want to know as much as we can about such things...

Is there some kind of time-out that happens between trickles, or what?

There is a 2-weeks time-out to the active machine count/status.
The policy on re-sending inactive model, I assume, depends on the current needs of the project (e.g. when Sulphur cycle models are needed, Slab model will not be re-send when they error-out or become inactive).

---

<i>phpBB forum for CPDN, all are </i><a href="http://www.climateprediction.net/board">invited</a>

There is a 2-weeks time-out to the active machine count/status.

In which case I agree with you, it would be friendly to reset it to \'in progress\' every time a new trickle comes in. This would also prevent the project from re-issuing a wu if in fact work had been restarted, so would save wasted crunching as well as user\'s curiosity.

The policy on re-sending inactive model, I assume, depends on the current needs of the project (e.g. when Sulphur cycle models are needed, Slab model will not be re-send when they error-out or become inactive).

In practice, I have twice had recycled WU that were aborted by previous user (shown as client error and code 197 if I remember rightly) but have personally never seen a recycled WU that had simply timed out. Doesn\'t mean they don\'t exist of course!

Thanks for your responses Honza.

River~~

Is there some kind of time-out that happens between trickles, or what?

There is a 2-weeks time-out to the active machine count/status...

Looking again at my results, the time out still does not explain this result, sent to me less than 14 days ago on the 6th, trickled twice since, and yet shown as \'over\'

I am still curious why this result is over, when other trickling results are not. I wonder what makes the difference?

There\'s a problem somewhere in the current version of the BOINC server code that sometimes causes it to set the wrong result state, but tracking it down is proving to be elusive. If you hunt around there are quite a few results that failed very quickly that have been marked as sucessfully completed!

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Please see Carl\'s post on why this has happened.

---

And all this time I thought it was the opposite of under ...

---