Forum > Discussion Forum
When corrupted results get validated...
Raistmer:
--- Quote from: Miep on 07 Jan 2011, 05:30:16 am ---also quite a few very different counts between x32f and 6.09 - how often should that happen?! I'll better stop looking through inconclusives now...
--- End quote ---
Hehe :)
Usually we all stop to looking for inconclusives right after app release.... And maybe it's very bad practice :)
Raistmer:
And more seriously - we have some fancy statistic from SETI servers but few very important pieces are missed completely.
For example, counters that describe inconclusives and invalids rates per host per app version.
If we would have such we could do app "profiling" on quite different level of quality.
Miep:
--- Quote from: Richard Haselgrove on 07 Jan 2011, 05:49:34 am ---Joe Segur posted a list in number crunching - I've linked from the new thread. I think all your Fermis are already known, though 6.02 is a new (or newly identified) problem.
Edit - the app details for http://setiathome.berkeley.edu/host_app_versions.php?hostid=5508489 indicate it's actually running stock v6.03. Do I vaguely remember that Eric forgot to bump the internal version number on that build, just as stock v6.10 Fermi reports v6.09 in stderr_txt? In any event, although the host clearly has problems, it isn't a mis-use of anonymous platform that's causing it.
--- End quote ---
Yes, thank Richard, saw your reply there, that's when I amended my post here.
'That build' has a problem then - there were quite a few CPU to GPU inconclusives over multiple hosts showing up with 6.02 on CPU - crosschecking
ok, difficult to say what it's valid against, with results being purged so quickly atm, but hosts with this build have difficulties against 6.09 and x32f - I've seen valids against V12 :P
Also valids against 6.09 ::). should have opend a new thread...
Richard Haselgrove:
Isn't that what we're already talking about in http://lunatics.kwsn.net/gpu-crunching/08jn10ad-4151-19449-3-10-56-test-case.0.html ? (development area link, not available to all)
Miep:
If that's stock 6.03 with dodgy stderr showing wrong version number... maybe?
most of inconclusives are GPU -9 and some diverging signal reports plus a few where signal reported match, so something the validator checks that isn't in stderr?
alltogether lots of inconclusives from that corner :(
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version