Forum > GPU crunching

x38g reports

<< < (32/58) > >>

Josef W. Segur:
Not unexpected, http://setiathome.berkeley.edu/workunit.php?wuid=766762437 which we looked at pretty closely ended with all 5 getting credit. The stock CUDA 6.08 got canonical so was strongly similar to CRUNCH3R's 6.01 CUDA for 64 bit Linux.
                                                            Joe

Jason G:
Thanks for keeping track of that one.   Yep looks like we need to at least take a look at the gaussians then.  I'm not happy with the outwardly clean looking 6.03 run being marginalised.  While we can discount the legacy Cuda builds' accuracy for a mixed bag of reasons (& the spikes in 6.03 for that matter), and the x38g one for stability & the unexplored gaussfit code, it's going to be the marginal cases that'll show us where to look.   They are going to get stranger I suppose.

Jason

Slavac:
X39e's up and running on two 560ti's.  We'll see how she does.

_heinz:
Hi Jason,
I get one -9 resultoverflow resultid=1981104197
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

I thought this is solved ?

Claggy:

--- Quote from: _heinz on 06 Jul 2011, 04:55:14 am ---Hi Jason,
I get one -9 resultoverflow resultid=1981104197
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

I thought this is solved ?

--- End quote ---
That's quite Normal, as long as your wingman finds too many signals too,

You were probably thinking of error that happens when there are too many triplets,

Claggy

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version