Hat tip for the hint to revisit the project news website. This allowed to recalibrate and update the charts % and start basing this off accumulated CPU time. Fast forward the number previously shown in there was 18.41%. It also allowed to slightly tweak the 'calculated end date bringing it closer to what the planner said, anticipating growth of volunteered CPU time.

Also tonight or tomorrow the project will have 10 million results accumulated. The average run times due increasing device power has been dropping down to 5.5 hours, so maybe we'll see a resizing of the jobs in the near future, WCG aiming for a ~7 hour project mean in most cases where it's possible.

cheers & thanks

Congrats on both reaching that & also 20% completion. As this project touches close to home for me (son of a friend with thankfully a happy ending) I try to keep an eye on the forums even if I can't devote a whole lot of CPU time at the moment. Although, with the 3 projects wrapping up over/within the next couple of months that will change for the better soon I hope.

Let's hope that our small contributions will make a difference in conquering this killer.



Is there any particular reason for the 7 hour sized work units instead of 6 hour (or 4)? It is much easier to do the mental gyrations necessary to figure out how many more work units are needed to reach a certain goal (badge related or not) when they can be evenly divided into a 24 hour period. Just curious...

That makes sense, thanks.

just a guess but i am guessing they are shooting for something like ~25 work units per week per computer(processer) but thats just a guess. I am just asumeimg that they have a goal of x jobs per week and it just avarages down to ~25 per week per machine

also if projects are the same time then it is easy for a person to swap from RICE to AIDS to HFCC and have the machine know about how much work to grab