Inconclusive, but why? |
![]() |
| log in |
Message boards : Number crunching : Inconclusive, but why?
| Author | Message |
|---|---|
|
Why is this set of results inconclusive? | |
| ID: 1288756 · | |
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 · | |
|
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. | |
| ID: 1288791 · | |
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 · | |
Message boards : Number crunching : Inconclusive, but why?
| Copyright © 2013 University of California |