Farpung, the client setting will multiply the set days with the number of cores that BOINC is allowed to use. 3.8 days will thus result in ~15 core days of work.

with rice, will always be 7 hrs, reguardless of cpu, more cpu=more positions completed=more points.

Thanks for the info Sek. I normally do not cache WUs, but I am so close to my first-ever blue badge I did not want to miss by a few WUs. I created a little spreadsheet to compute how many days and results have left to go (7 calendar days). I had planned to decrease the cache daily until I hit my mark. I did not want to go over by much either since I have other badges to chase. I did not know that aborted results would not be re-issued, so I'll be extra careful.

The only variable I hadn't been able to factor in accurately in the past was the hours waiting to be credited. Now that I have been caching, my completed jobs are validated immediately so I am assuming that everything gets picked up when the stats are updated.

Your chart that predicts the completion dates of the active projects has been most helpful to me to strategically select which projects to run. If there was anyway to hone that projection for this project to get the number of days left or total number of available WUs I wouldn't be so anxious (or perhaps greedy).

There's 2 parts to user aborted in the specific RICE project case:

1 - if at point of abort there are the minimum seeds, no reissue.
2 - if at point of abort there is a need to re-issue it only goes to the fast returners. Locks the > 4 day cachers out. I'll take them.

The techs emphasized "we like to have them", again me underlining what the title of the thread expresses. Cutting it short here, max the available results for the last minute boarders including the bigger bufferers... badges are a mission too... to show you were there ;>)

There's currently over 16,377 places - as it's in Sekerob's signature (as well as in the FAQ's)