Invalid results after aborted transfer
28 Mar 2006 8:40:48 UTC
Topic 190978
(moderation:
When the servers went down yesterday, two results were just up to be sent. The client stated "network timeout", and to avoid useless retries, I aborted those transfers. This morning, when servers were back up, I uploaded all results, including the two aborted ones from last night.
Unfortunately, I found these two results to be "invalid", although they already had been calculated well.
http://einsteinathome.org/task/22908443
http://einsteinathome.org/task/22887844
The stderr.txt says:
/stderr_txt>
r1_1037.0__151_S4R2a_2_0
-115
user requested transfer abort
r1_1037.0__151_S4R2a_2_0
-115
And the validate state says "Invalid".
Why is that? Aborted transfers could just be sent again and be accepted as valid if they are.
--lox
Invalid results after aborted transfer
)
When you abort anything in BOINC, it means it's aborting the whole unit. Even in the transfer tab of Boinc Manager. It's deleting the whole result from your computer.
BOINC, if left alone, will try to upload results until it can make contact with the server. Check the Help on BM on this: Pressing F1 in BM shows this screen.
Transfers: Aborted by user: Result has been aborted and will be reported to the project server as a computational error.