Message boards :
Number crunching :
Funny WU
Message board moderation
Author | Message |
---|---|
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Check this WU it seems that no-one can make sense of it.... http://setiathome.berkeley.edu/workunit.php?wuid=1196302413 |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
It's a perfectly normal MAX_TRIPLETS_ABOVE_THRESHOLD (Exit status -12) Check this WU it seems that no-one can make sense of it.... And there's a button (above right when posting) to make urls clickable. |
Mike Send message Joined: 17 Feb 01 Posts: 34253 Credit: 79,922,639 RAC: 80 |
Thats a normal work unit with to much triplets. All cuda hosts failed while the CPU hosts didn`t. With each crime and every kindness we birth our future. |
Josef W. Segur Send message Joined: 30 Oct 99 Posts: 4504 Credit: 1,414,761 RAC: 0 |
Thats a normal work unit with to much triplets. It's the "cudaAcc_find_triplets doesn't support more than MAX_TRIPLETS_ABOVE_THRESHOLD numBinsAboveThreshold in find_triplets_kernel" version of the -12 error. The analysis requires keeping track of which bins are above threshold, and for CUDA there's limited storage considering that many arrays are being analyzed in parallel. Anyhow, just because there are more bins above threshold than normal does not mean that the particular spacings between those bins will be correct for detecting a Triplet event. When we make the transition to SETI@home v7 those errors will no longer happen. Jason coded the new CUDA apps to send those rare cases back to be rechecked on the CPU. But meanwhile those -12 errors are a fact of life for stock CUDA SETI@home Enhanced applications. Joe |
©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.