Very Short WU - 52 seconds long


Advanced search

Message boards : Number crunching : Very Short WU - 52 seconds long
Message board moderation

To post messages, you must log in.

AuthorMessage
Luke
Volunteer developer
Avatar

Send message
Joined: 31 Dec 06
Posts: 2546
Credit: 817,560
RAC: 0
New Zealand
Message 717305 - Posted: 23 Feb 2008, 7:36:59 UTC

I just received a WU:
22fe07af.16547.6616.16.7.0

Estimated completion was 15 hours, then claims it is done 52.52 seconds later, I am currently waiting on 0.09 credit for it. Then got bombarded with 7 snappy two hour WU's and one 13 hour one. Confusing.

What went wrong?

Thanks,
Luke
- Luke.
ID: 717305 · Report as offensive
Alinator
Volunteer tester

Send message
Joined: 19 Apr 05
Posts: 4178
Credit: 4,647,982
RAC: 0
United States
Message 717311 - Posted: 23 Feb 2008, 7:56:39 UTC

That one was a Dash 9 (aka a 'noisey' Workunit).

Execution was terminated early because more 'signals' were found than is allowed to be stored in the output file. The typical reason for them is man made RF interference contaminating the data.

HTH,

Alinator
ID: 717311 · Report as offensive
Odysseus
Volunteer tester
Avatar

Send message
Joined: 26 Jul 99
Posts: 1808
Credit: 6,701,347
RAC: 6
Canada
Message 717626 - Posted: 24 Feb 2008, 2:23:19 UTC

Note that you still get credit roughly proportional to the time spent on a “-9 overflow”; BOINC doesn’t treat it as an error. It’s only a cause for concern if your quorum partners don’t get similar results.

ID: 717626 · Report as offensive

Message boards : Number crunching : Very Short WU - 52 seconds long


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.