Inconclusive, but why?
Message boards :
Number crunching :
Inconclusive, but why?
Message board moderation
| Author | Message |
|---|---|
alan  Send message Joined: 18 Feb 00 Posts: 131 Credit: 401,606 RAC: 0 
|
ID: 1288756 ·  |
Richard Haselgrove  Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874
 |
Why is this set of results inconclusive? How do you know? Did you manage to capture both the uploaded data files? As we've said before, there's a heck of a lot more to validation than the raw signal counts - powers, frequencies, timings, threshholds.... ID: 1288769 · |
|
alan Send message Joined: 18 Feb 00 Posts: 131 Credit: 401,606 RAC: 0
|
Obviously not. So there is more to the results than what is made available in the task file, then? That's all you needed to say. I've got a larger number of inconclusives than I've ever seen before, five out of my seven pendings, all with different wingmen. I wondered if there was a common factor, other than me. ID: 1288791 · |
|
Josef W. Segur Send message Joined: 30 Oct 99 Posts: 4504 Credit: 1,414,761 RAC: 0 
|
Obviously not. So there is more to the results than what is made available in the task file, then? That's all you needed to say. Three of those five inconclusives in your pending list do show enough information in the stderr section to make a judgement. When a GPU overflows on a WU where your CPU didn't it's almost certain your result is right and the wingmate's wrong. Joe ID: 1288824 · |
©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.