Pages: [1]
BigEfromLC
BAM!ID: 4116
Joined: 2006-08-16
Posts: 1
Credits: 0
World-rank: 0

2006-08-16 19:56:17

If this is not the correct place for this question, let me know and I will move it.

In the past few days, I have had several SETI runs terminated very early with the following result coding:

Work Unit Info
True angle range: 0.393911
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

True angle range figure changes.

What does this mean? Is this a "Divide by zero" kind of thing?
Looking for intelligent life in Lake City Florida (with little success so far!)
Son Goku 3SSJ
 
Forum moderator - Translator
BAM!ID: 8
Joined: 2006-01-11
Posts: 182
Credits: 2,572,985
World-rank: 120,807

2006-08-16 21:11:54
last modified: 2006-08-16 21:13:53

If this is not the correct place for this question, let me know and I will move it.

In the past few days, I have had several SETI runs terminated very early with the following result coding:

Work Unit Info
True angle range: 0.393911
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

True angle range figure changes.

What does this mean? Is this a "Divide by zero" kind of thing?

No this is not a "Divide by zero" kind of thing

This error means that the found signals exceed the maximum signals reported threshold for that Work Unit (usually this threshold is 30 signals). This error is not serious and happens often when there was much radio interference while the Work unit was taken.

***EDIT***
Renamed & moved your topicto the projects forum, because it concerns a particular project and not BOINC itself.
part of
Wenn jeder an sich denkt, wird an alle gedacht!
Dotsch
Tester
BAM!ID: 833
Joined: 2006-05-27
Posts: 74
Credits: 3,239,543
World-rank: 104,763

2006-08-19 21:43:48

This error means that the found signals exceed the maximum signals reported threshold for that Work Unit (usually this threshold is 30 signals). This error is not serious and happens often when there was much radio interference while the Work unit was taken.

If it appers sometimes, it would be a noicy signal, and is OK.
But if you get this error on every result, it could also be a problem with the software (porting problems for example) or with the hardware.
Pages: [1]

Index :: The Projects :: SETI@Home Results error coding help needed
Reason: