We have stopped generating the next work units for this beta test. We will be letting the ones in progress finish normally. We are working on sending the results back to the researchers for them to investigate.

As for the double cpu time, the next version of beta will have a fix for that. Also, it did not affect the results from this beta test which is great. This means that we have lots of data to send back. We are still in alpha with the next version of the code, but we hope to have another round of beta in the future. I would probably guess the next round won't happen this week though, but again don't hold me to that guess as it is my opinion only :)

Thank you again for everyone who has contributed towards this beta test. We have worked out LOTS of bugs in both application as well as the backend systems that will be used in production.

Thanks,
-Uplinger

Go team, GOOOOOO !!!

CJSL

Crunching for a better world...

I got a resend where the initial cruncher aborted the task after 19,000 steps.
He was not granted for the 1st trickle and a pity for him, after the next trickle (at 20%),
his task would have been awarded cause server abort:

[01:43:08] INFO: Checkpointed. Progress 13000 of 100000 steps complete CPU time 6650.524000
[23:37:26] INFO: received message from server to exit after next major checkpoint.
[23:37:26] INFO: Checkpointed. Progress 14000 of 100000 steps complete CPU time 7157.544000
The task must have been waiting in memory for at least almost 1 day.

My resend-task got a similar server abort message at step 31,000:

[02:56:14] INFO: Sending trickle message to server.
[02:56:14] INFO: Starting intermediate upload, index = 3
[02:56:14] INFO: Checkpointed. Progress 30000 of 100000 steps complete CPU time 34642.181520
[03:15:29] INFO: received message from server to exit after next major checkpoint.
[03:15:29] INFO: Checkpointed. Progress 31000 of 100000 steps complete CPU time 35794.860584
[03:34:44] INFO: Checkpointed. Progress 32000 of 100000 steps complete CPU time 36946.824286
[03:54:07] INFO: Checkpointed. Progress 33000 of 100000 steps complete CPU time 38106.638900
[04:13:19] INFO: Checkpointed. Progress 34000 of 100000 steps complete CPU time 39256.788567
[04:32:37] INFO: Checkpointed. Progress 35000 of 100000 steps complete CPU time 40412.162218
[04:51:53] INFO: Checkpointed. Progress 36000 of 100000 steps complete CPU time 41564.830671
[05:11:16] INFO: Checkpointed. Progress 37000 of 100000 steps complete CPU time 42725.470416
[05:30:40] INFO: Checkpointed. Progress 38000 of 100000 steps complete CPU time 43887.315943
[05:50:00] INFO: Checkpointed. Progress 39000 of 100000 steps complete CPU time 45046.087991
[06:09:19] INFO: Exit:<current_step>40000</current_step> <total_steps>100000</total_steps>
06:09:19 (14211): called boinc_finish(0)

The result is purged from the database, but from this lines

[05:50:00] INFO: Checkpointed. Progress 39000 of 100000 steps complete CPU time 45046.087991
[06:09:19] INFO: Exit:<current_step>40000</current_step> <total_steps>100000</total_steps>

The total cpu time from the returned task after 40% was done, is 45046.087991 seconds
is 12 hours and 31 minutes + 19 minutes from step 39,000 to 40,000.