i'd like to report a serious bug with some strand of N-body simulation tasks:
some of them, namely all with "chisq_alt_" in their name show computation time estimate of over 800 hours, and get to about 10% after running 3 days straight, verification then shows as inconclusive on the website
here is example of 1 task
MilkyWay@Home N-Body Simulation 1.08
de_nbody_10k_chisq_alt_40913_1366886102_673146
computation size 624753000 GFLOP’s
it's estimated computation time was 799 hours, it seemed to be not progressing at all
i think there may be a bug related to that task series.
To milkyWay@Home team: please consider this as a bug report and please investigate the cause of this

Thanks in advance

i'd like to report a serious bug with some strand of N-body simulation tasks:
some of them, namely all with "chisq_alt_" in their name show computation time estimate of over 800 hours, and get to about 10% after running 3 days straight, verification then shows as inconclusive on the website
here is example of 1 task
MilkyWay@Home N-Body Simulation 1.08
de_nbody_10k_chisq_alt_40913_1366886102_673146
computation size 624753000 GFLOP’s
it's estimated computation time was 799 hours, it seemed to be not progressing at all
i think there may be a bug related to that task series.
To milkyWay@Home team: please consider this as a bug report and please investigate the cause of this

Thanks in advance

Next time you get one let it run for a couple of minutes then suspend MW for a slow count of 5 then restart it and see if the processing picks back up. SOMETIMES Boinc forgets what it is doing and stops using the gpu and instead tries to use the cpu to crunch with, the suspend/resume method sometimes brings it back to reality and the gpu kicks back in again.

Next time you get one let it run for a couple of minutes then suspend MW for a slow count of 5 then restart it and see if the processing picks back up. SOMETIMES Boinc forgets what it is doing and stops using the gpu and instead tries to use the cpu to crunch with, the suspend/resume method sometimes brings it back to reality and the gpu kicks back in again.

Thanks for the reply.
I will be sure to try the described method