Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Retired Forums Forum: UD Windows Agent Support [Read Only] Thread: workunits negative |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 3
|
Author |
|
workel
Cruncher Joined: Jan 22, 2006 Post Count: 11 Status: Offline |
hey,
just got a question I have since several weeks... how does a workunits result could become negative, so there has to be send out a 4th workunit of more to recompute the workunit in a right way... is it because you shut down your PC while the UDclient wasn't closed first... is it because you took out the power supply of your laptop so the agent is paused immediately... is it because... maybe if we know how a bad crunch can appear, we could maybe avoid such bad computations! greets workel |
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
suppose you mean a result that reports an "error" or "invalid"? Multiple causes, you mention a few, can turn your WU into GOOH, including hickups during transmission, when the checksum does not match the completed WU transmitted (very unlikely). Hardbooting your PC/Laptop definitely falls in the cagetory of hi potential disaster. If you can plan it, best is to properly close BOINC or UD agent, check if any remaining processes can be seen in Taskmanager, then proceed to close.
----------------------------------------I must say, with UD & BOINC i rarely had issue long as i properly closed thru the windows closing procedure. Both programs safe the WU every somany seconds / minutes, and pick up from there when restarting....you might observe the counter skipping back 7 to 10 minutes (even half an hour in UD). I'm sure the FAQ's give some advise for either BOINC or UD how to best go about it....in my specific case, empiricals taught me what to do and not, broadly described above. ciao
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All! |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Interrupting the client shouldn't damage the work unit. Still, you should shut down your PC properly to avoid file corruption.
The main causes of work unit loss are: Work units that are simply never returned. Work units that are aborted by the user (these are sent straight back marked as "error"). Overclocked computers miscalculating the result (this is probably the most common and easily avoidable error). Memory or hard drive errors. You will probably know about it if you have a failing HDD, but memory errors can be more subtle. |
||
|
|