It looks like the star file was misspecified for the *22_3s_free_1/2 and *22_3s_edge_1/2 searches. I've made a new fixed star file for *22_3s_free_3 and *22_3s_edge_3 searches, and shut down the old ones. Let me know how these are working.
____________
/ 
Reply
Quote
...I've made a new fixed star file for *22_3s_free_3 and *22_3s_edge_3 searches...Let me know how these are working.
I've run through only about 30 of these these, but, so far, so good. Previously, my error rate had been about 10%.
____________
/ Reply
Quote
A Follow-up...
After two hours of the version '3' , I have seen *zero* errors on them.
Still having a few errors on the version '1' and '2' WUs as those batches run their course.
It looks like the problem is solved.
Thx.
/ Reply
Quote
...so far, so good.
Or, maybe not so much... This result, 319700259, shows a failure similar to the earlier runs. :-(
____________
/ Reply
Quote
...so far, so good.
Or, maybe not so much... This result, 319700259, shows a failure similar to the earlier runs. :-(
Looks like the job completed successfully but for some reason the client marked it as a failure (it does have the output for the likelihood at the end). I wonder if this is due to the fact that one of the stream only likelihoods ended up being NAN.
I hope the errors like this are at least less frequent...
____________
/ Reply
Quote
Had some errors overnight like this :
http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=319788399
____________
DSKAG Austria Research Team: http://www.research.dskag.at
/ Reply
Quote
For edge_1 and edge_3 and free_1 and free_3 still many errors (while computing) and even more validate error for same, however wingman seems to run them fine and get validated.
I have the newest driver 1.4.1741 with HD5870 and BOINC 7.0.28 on Win7 x64.
____________
Greetings from,
TJ
/ Reply
Quote
Could it be a graphics driver problem?
I run Albert@home once a while as well and they did okay since yesterday as there are many validate errors too with ati as I saw with wingman. Nvidia seems to be okay.
____________
Greetings from,
TJ
/ Reply
Quote
And I have seen a number of errors on the version '3' WUs overnight as well.
These seem to have an #IND in the result as:
<stream_only_likelihood> -3.638176510600306 -10.877692835483177 -1.#IND00000000000 </stream_only_likelihood>
/ Reply
Quote
Travis said:
I hope the errors like this are at least less frequent...
A rough calculation with my host's results shows an error rate of about 2%-3% over the last 4 hours, or so. So, they do seem to be less frequent (for me).
____________
/ Reply
Quote
I hope the errors like this are at least less frequent...
Yes, errors are less frequent compared 22_3s_free_1 and 22_3s_edge_1 searches, today I had just 3 bad *free_3* WUs. So that's way better than those 11 edge/free_1 from yesterday.
What I have noticed is we have a lot of WUs which need 3 results before they be validated. Here some examples: 253847186, 253944881, 254009156, 253771061, 253995223, 253888155. That's just from 1 page of my results, which still contains many "completed, validation inconclusive", some of which will very probably join this club.
____________
.
/ Reply
Quote
I hope the errors like this are at least less frequent...
Yes, errors are less frequent compared 22_3s_free_1 and 22_3s_edge_1 searches, today I had just 3 bad *free_3* WUs. So that's way better than those 11 edge/free_1 from yesterday.
What I have noticed is we have a lot of WUs which need 3 results before they be validated. Here some examples: 253847186, 253944881, 254009156, 253771061, 253995223, 253888155. That's just from 1 page of my results, which still contains many "completed, validation inconclusive", some of which will very probably join this club.
I've upped the quorums for some workunits a little bit because I was noticing we were getting some weird results validated. So there's no problem there, just a little bit extra validation on our end.
____________
/ Reply
Quote