Message boards :
Number crunching :
Triple validated
Message board moderation
Author | Message |
---|---|
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
http://setiathome.berkeley.edu/workunit.php?wuid=1960925997 This is not the only WU that has been validated 3 times (or twice, depending on how you look at it) on this computer. Is this happening because of the reworking on the servers? SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
Cosmic_Ocean Send message Joined: 23 Dec 00 Posts: 3027 Credit: 13,516,867 RAC: 13 |
I think that just happens naturally. If there are, for example, up to 30 results reported by the first two iterations, and somewhere a few places beyond the decimal in enough of the values doesn't quite agree, it will be "inconclusive" and need a third iteration. Third iteration returns back roughly the same result, then all three are deemed "weakly similar" and "close enough," so all three get credit. Richard and/or Josef have explained this one really well multiple times in the past, but that's my rough explanation for it. Linux laptop: record uptime: 1511d 20h 19m (ended due to the power brick giving-up) |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
Thanks, I think you are correct. I just forget a lot of what is posted here. As I like to say, I have forgotten more than most people will ever know. SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
Cosmic_Ocean Send message Joined: 23 Dec 00 Posts: 3027 Credit: 13,516,867 RAC: 13 |
It seems to mostly happen in situations where there are different crunching platforms involved.. CUDA/nvidia vs. OpenCL/ATI vs. CPU. The two GPU types have different limitations on how precise the digits beyond the decimal go when they do their floating point math. Purely mathematically, if you take pi for example, 3.141593 is not the same as 3.1415926. The validator sees that those two reported results do not exactly match, so a third iteration goes out. That one returns 3.1415927, and the validator sees that between the three of them, there's only a difference of 0.000001 or less, so it decides they are close enough and all three must be right. Beyond that, I don't know the exact specific thresholds that make the decision on the rounding errors, but if a _2 task gets validated against _0 and _1, then that almost always means there was a difference in rounding between the first two and the third one agreed with the consensus. Linux laptop: record uptime: 1511d 20h 19m (ended due to the power brick giving-up) |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
Beyond that, I don't know the exact specific thresholds that make the decision on the rounding errors, but if a _2 task gets validated against _0 and _1, then that almost always means there was a difference in rounding between the first two and the third one agreed with the consensus. Certainly seems to be what happened here. Thanks again. SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
©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.