Through some strange setting of preferences (don\'t bother looking, i\'ve restored them), I have received a 2nd CP work unit.

Currently my 1st WU is only 10% completed and is preempted while SETI crunches for awhile.

I also have 6 SETI WU\'s in the queue.

I have no problem holding this CP WU until it can start processing at the end of September but, wouldn\'t it be nice if I could select that extra WU for return to CP for reassignment to someone who could start crunching it sooner.

This could also be made part of the reset and/or detatch function to return unprocessed WU\'s to the appropriate project for reassignment.

-P

The challenge for the BOINC development team was to design something that could be run on the on the computer of our hypothetical technologically challenged Aunt Maud or Uncle Henry with no intervention. Most of us on these message boards don't come into that category, and find very disconcerting the way that the BOINC client does things with no apparent explanation and limited ways for us to control it :-)

So far as this particular case is concerned, I wouldn't worry. The number of possible parameter permutations in the model is very large, and there is not normally any particular priority order in which they are given out. So it should not matter that the WU is sitting in your machine for a while.

I agree, though, that it would be useful to be able to ditch WUs from the cache and tell the server that we have done so. At the moment the only way I know is to reset the project, which will kill any WU currently being processed, which is not what we want to do on these occasions. The issue doesn't arise with SETI, because of their short deadlines, but it is different for CPDN.