Howdy.

I just ran 26 N-Body tasks and 50% got the stated error; didn't matter if it was a single or multi thread.

Here is a for instance:

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=705830538

Any idea if it's hardware or a WU flaw?

Thanks!

8-)

"Validation inconclusive" is nothing to worry about. It just means you are waiting for another cruncher to return results for you get credit.

"Validation inconclusive" is nothing to worry about. It just means you are waiting for another cruncher to return results for you get credit.

I would think they would get placed in the Validation Pending category if that was the case. I just came across this myself running Modified Fit tasks.

I see Validation Inconclusive and the first thing to cross my mind is I think its a error and all my computer time has been wasted. The project team might want to put things in the correct categories to keep people from jumping to conclusions and just giving up on the project. I have seen it happen for less reason than this.

"Validation inconclusive" is nothing to worry about. It just means you are waiting for another cruncher to return results for you get credit.

I would think they would get placed in the Validation Pending category if that was the case. I just came across this myself running Modified Fit tasks.

I see Validation Inconclusive and the first thing to cross my mind is I think its a error and all my computer time has been wasted. The project team might want to put things in the correct categories to keep people from jumping to conclusions and just giving up on the project. I have seen it happen for less reason than this.

I suspect that is a BOINC issue not a Milkway-specific issue as I've seen this happen on multiple projects. Might want to post this on their forums.

http://boinc.berkeley.edu/dev/forum_forum.php?id=10

---

"Validation inconclusive" is nothing to worry about. It just means you are waiting for another cruncher to return results for you get credit.

I would think they would get placed in the Validation Pending category if that was the case. I just came across this myself running Modified Fit tasks.

I see Validation Inconclusive and the first thing to cross my mind is I think its a error and all my computer time has been wasted. The project team might want to put things in the correct categories to keep people from jumping to conclusions and just giving up on the project. I have seen it happen for less reason than this.

That's because you don't know the WHOLE story yet...my understanding of the whole story, at least the parts I know, are that each workunit is run thru a program to determine what the acceptable range should be for the unit to be 'valid'. A unit that is marked as 'validation inconclusive' is outside this projected range, which doesn't mean the unit is necessarily bad, it just means they expected one thing and got something else instead. You are now waiting on your wingman to prove which is right or more correct, to see if you get credit for the unit or not. It seems MOST of the time credit is granted, but I am guessing not always.

Lots of projects do this to prevent cheating and to pre-screen the returned units for validity. Boinc is about Science, most projects base their work on the units we crunch, having them be as accurate as possible is preferable. BUT they understand that your pc's run different hardware, software, even versions of software, speeds etc then my pc's do, and almost everyone elses, this throws a variability into the results that must be taken into account.