Message boards : BOINC client : ? detaching from project / are wu's pending upload "lost"
Message board moderation
Author | Message |
---|---|
Send message Joined: 9 Sep 07 Posts: 15 |
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? |
![]() Send message Joined: 29 Aug 05 Posts: 304 ![]() |
|
![]() Send message Joined: 13 Aug 06 Posts: 778 ![]() |
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 |
![]() Send message Joined: 29 Aug 05 Posts: 15588 ![]() |
Even better would be if the logic were in place to send and report work automatically when this radical step is taken. A bit difficult if the project in question is off line... So then what happens, no detach until the work is uploaded & reported? I do like the better warning about the consequences of a detach though and will contact David on that. |
![]() Send message Joined: 29 Aug 05 Posts: 15588 ![]() |
Or better yet, I made a Trac ticket. Changes in the example text are welcome. :-) |
![]() ![]() Send message Joined: 30 Oct 05 Posts: 1239 ![]() |
Or better yet, I made a Trac ticket. Changes in the example text are welcome. :-) I'm not motivated to install an old version just to find out... But didn't there used to be a warning in the dialog box that a detach/reset would result in the loss of all work. Or am I just thinking there was because every time I've said something about it on the forums I've put a warning in my post. Kathryn :o) |
![]() Send message Joined: 29 Aug 05 Posts: 15588 ![]() |
I think there was only a warning on one of the Help sites that you got through from BOINC Manager's Help menu. And then you had to read the warning correctly as well. And find it first. ;-) Oooh, just look at the description for Detach on Manager Advanced: "Detach: Your computer will stop working for the project." Is that all? ;-) (And edited that page ;-)) |
![]() Send message Joined: 13 Aug 06 Posts: 778 ![]() |
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? |
![]() Send message Joined: 29 Aug 05 Posts: 15588 ![]() |
I'll add them. |
![]() Send message Joined: 13 Aug 06 Posts: 778 ![]() |
Thanks. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.