Message boards :
Number crunching :
Lots of "Completed, validation inconclusive" errors
Message board moderation
Author | Message |
---|---|
Send message Joined: 2 Jan 08 Posts: 17 Credit: 2,608,409 RAC: 0 |
I seem to be getting a succession of "Completed, validation inconclusive" results. Task Work unit Computer Sent Time reported or deadline Status Run time CPU time Credit Application 399362675 308407768 462901 9 Feb 2013 | 21:42:33 UTC 10 Feb 2013 | 1:19:10 UTC Completed, validation inconclusive 962.17 164.17 pending MilkyWay@Home v1.02 (opencl_nvidia) 399362671 308311940 462901 9 Feb 2013 | 21:42:33 UTC 10 Feb 2013 | 1:19:10 UTC Completed, validation inconclusive 956.65 171.08 pending MilkyWay@Home v1.02 (opencl_nvidia) 399148819 308257986 462901 9 Feb 2013 | 14:37:56 UTC 9 Feb 2013 | 21:42:33 UTC Completed, validation inconclusive 956.90 167.38 pending MilkyWay@Home v1.02 (opencl_nvidia) 399803703 291524669 462901 10 Feb 2013 | 12:36:32 UTC 18 Feb 2013 | 3:52:29 UTC Completed, validation inconclusive 659,757.00 1,561,110.00 pending MilkyWay@Home N-Body Simulation v1.06 (opencl_nvidia) 399803697 303617765 462901 10 Feb 2013 | 12:36:32 UTC 18 Feb 2013 | 3:53:39 UTC Completed, validation inconclusive 88.47 88.47 pending MilkyWay@Home N-Body Simulation v1.06 (opencl_nvidia) 399803696 297188080 462901 10 Feb 2013 | 12:36:32 UTC 18 Feb 2013 | 3:53:39 UTC Completed, validation inconclusive 15.13 14.08 pending MilkyWay@Home N-Body Simulation v1.06 (opencl_nvidia) The ones taking 900 seconds are tolerable, but the one that claims to have taken 18 DAYS of CPU time is VERY annoying. Is it just me, or a general problem? |
Send message Joined: 8 May 09 Posts: 3321 Credit: 520,544,701 RAC: 27,959 |
I seem to be getting a succession of "Completed, validation inconclusive" results. There is already a whole thread on the n-body workunit problems. YES they are working on it. |
Send message Joined: 19 Jul 10 Posts: 595 Credit: 18,964,932 RAC: 5,531 |
"Completed, validation inconclusive" is not an error, it simply means that (at least) one more result is needed for validation. |
Send message Joined: 4 Sep 12 Posts: 219 Credit: 456,474 RAC: 0 |
"Completed, validation inconclusive" is not an error, it simply means that (at least) one more result is needed for validation. And for some reason, this project decided to do them consecutively, rather than concurrently. |
Send message Joined: 19 Jul 10 Posts: 595 Credit: 18,964,932 RAC: 5,531 |
"Completed, validation inconclusive" is not an error, it simply means that (at least) one more result is needed for validation. Because most tasks do not need more than one result. Almost all of my _0 tasks pass the validation without a wingman. |
Send message Joined: 2 Jan 08 Posts: 17 Credit: 2,608,409 RAC: 0 |
Thank you for the explanations and I see there has been discussion about long N-Body packets elsewhere. I am now watching work unit 291524669 every day. The most recent attempt has timed out and it has now been farmed out to a slightly slower machine than the last one. So far this work unit has used up some 46 days of processor time. Previously, I would have whinged about this. With hindsight I see the benefit of distributed processing: having a few PCs ut on the internet tied up with such a work unit is far better than an entire processor of a research team being tied up for 46 days. Anyway, I do hope this packet finally gets validated. At my average of 775 credits per run time hour, it is worth between 140k and 244k credits. At my average of 5,800 credits per CPU hour, this work unit is worth 2.5 million credits. :-D I know that if I get nothing for what was 18 days of CPU time over 7.6 elapsed days, I won't be happy! I wonder if it is worth extending the deadline by another week or two for these long N-Body packets so they can be validated? Please. |
Send message Joined: 2 Jan 08 Posts: 17 Credit: 2,608,409 RAC: 0 |
This work unit I completed successfully a month ago is still "Completed, validation inconclusive". The most recent attempt by another wingman did indeed run out of time and it has been issued yet again, this time to a slower machine so it will also probably run out of time. Extending the deadline for the MilkyWay@Home N-Body Simulation v1.06 jobs might actually see these being completed, instead of wastefully started, re-started and re-started. They need to be permitted to use something like 21 days. |
Send message Joined: 22 Apr 11 Posts: 64 Credit: 899,745,181 RAC: 13,711 |
I have almost 459 and climbing PENDING tasks... Seems the last few days they have been building up. http://milkyway.cs.rpi.edu/milkyway/results.php?userid=159224&offset=0&show_names=0&state=2&appid= Seen this before... about 10% error rate.. Hope it gets fixed. 8-) |
©2024 Astroinformatics Group