This result
has found 30 signals.
WU true angle range is : 0.377523

Flopcounter: 47662394873873.266000

Spike count: 15
Pulse count: 1
Triplet count: 14
Gaussian count: 0
called boinc_finish

</stderr_txt>

Flopcounter: 46196446787078.453000

Spike count: 15
Pulse count: 1
Triplet count: 14
Gaussian count: 0
called boinc_finish

</stderr_txt>

---

iirc the maximum is 30. So 30 get reported 31 don't.

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

I have seen -9 overflow with 30 pulses or spikes, should have saved them.
I take it, you're right on this one, 31 is a true result overflow
Anyway I'm ofc glad it's OK :)
From time to time, I have to see some valid results
;^) . . .

[ADDED]

A real -9

WU true angle range is : 0.378217
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

Flopcounter: 39606771957846.133000

Spike count: 29
Pulse count: 1
Triplet count: 0
Gaussian count: 0
called boinc_finish

---

iirc the maximum is 30. So 30 get reported 31 don't.

But IIRC the app stops processing and errors out if it reaches 30. Could someone more knowledgeable comment, please?

---

iirc the maximum is 30. So 30 get reported 31 don't.

But IIRC the app stops processing and errors out if it reaches 30. Could someone more knowledgeable comment, please?

quoting Joe:

result_overflow is triggered by the 31st found signal

that knowledgable enough for you?

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

Added in the above mentioned post!

How about this
WU?

Have never seen this before, I mean why has it normally ended?!?
It's nice getting credits for this Result, but what is the result?

WU true angle range is : 0.378217

Flopcounter: 47581855434324.695000

Spike count: 5
Pulse count: 2
Triplet count: 0
Gaussian count: 1
called boinc_finish

</stderr_txt>

---

I have seen -9 overflow with 30 pulses or spikes...

Probably the 31st one doesn't get reported in the log, so 30 events reported without overflow => 30 found; 30 events reported with overflow => 31 found but only 30 shown.

Gruß,
Gundolf

At least it is an explanation, I sort of stumbled upon these results............
And I'm far from an expert.... ;-)

@ Miep and Gundolf Jahn, Ok you are both right.

---

Ahmmm sorry to disagree.
I had some units with 31 pulses reported.
More than 1.

---

With each crime and every kindness we birth our future.

IIRC the overflow is hit if the 30 results are found before a certain amount of the WU is done.

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

Ahmmm sorry to disagree.
I had some units with 31 pulses reported.
More than 1.

That's right. The 31st signal does trigger overflow, but if it's a Pulse, Gaussian, or Triplet it also gets reported. If it's a Spike (or Autocorr for S@H v7) the quit logic is ahead of the report logic.

                                                                Joe

Thanks for the correct answer Joe, I did remember 200 series or 8000 or 9000 series
producing (false) -9 , as my 9800GTX+ did, as result of heat.
It gave 31 pulses, most of the time.

---

Well ehh, spikes!
Never try to do a few things, all at once!

---

And to make sure this will be clear I've found a example of 31 signals are reported, as joe explained. ;-)

v_BaseLineSmooth (no other)
v_vGetPowerSpectrumUnrolled 0.00009 0.00000
sse3_ChirpData_ak 0.00969 0.00000
v_vTranspose4 0.00138 0.00000
AK SSE folding 0.00149 0.00000
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

Flopcounter: 20978111668909.398000

Spike count: 2
Pulse count: 28
Triplet count: 1
Gaussian count: 0
called boinc_finish

</stderr_txt>
]]>

Two stock crunched workunit.

---