With all of Rosetta's problems, my laptop had about 40 three-hour wu's completed.

Since the lappy is slow AMD, and not Rosetta friendly, I "detached" from Rosetta and added other projects.

I "thought" i checked to see if the wu's were uploading to Rosie first, but apparently I didn't.

Assuming i goofed in detaching before the wu's uploaded, is there any way to get back the results of ~120 hours of crunching?

If in fact (only my "assumption" at this point in time) BOINC Manager does delete any completed wu's which are pending upload when a project is detached, would it not be a good idea to issue a warning dialog box to this effect?

If you detach before reporting you work it will be lost.
____________
BOINC WIKI

BOINCing since 2002/12/8

When I mouse over a version 5.8.15 boinc manager button, without clicking, I get a small pop-up message explaining what will happen. The Detach button's message warns that 'Tasks in progress will be lost. Use Update first to report any completed tasks.'.

The only way to get lost or crashed workunits back is to restore a backup of the contents of the boinc folder. CPDN members are advised to make regular backups because the workunits are so long that almost anything could go wrong before the end. But for projects with much shorter WUs (ie all other projects) it isn't usually considered worth the hassle as after a restore you have to crunch again from the backup point.

Scheduled backups made with boinc running generally speaking can't be successfully restored.

If anyone does need a boinc folder backup & restore method, the CPDN READMEs are the place to look:

http://www.climateprediction.net/board/index.php

Little pop-up messages when hovering are useless for fast navigators. Radical steps as detaching when there is still work to upload and report, and i agree with the OP, should be with a blunt screen warning to say that all and everything is lost when executed, not just a 'you are about to detach'. Even better would be if the logic were in place to send and report work automatically when this radical step is taken.

Discussing backups may be in the mind of CPDN participants which run jobs of many hundreds or several thousand hours, but if attached to a project that runs jobs for 4-6 hours it is not IMHO.

____________
Coelum Non Animum Mutant, Qui Trans Mare Currunt

A few crunchers seem to understand the word Abort as it is used by NASA or ESA for a countdown to launch that is temporarily suspended but will be recontinued when for example the wind direction changes.

And if you reset the table for a meal you just do the job again. The crockery and cutlery don't mysteriously disappear for ever.

So the finality of the effect of both the Abort and Reset Project buttons can be misunderstood. Jorden, would it be a good idea for you to add these two buttons to the same Trac ticket?

Thanks.