Now I have one N-Body Simulation task in progress.

It shows 99.525 completed, with 1 day:00:03:46 elapsed and 00:06:53 remaining. However, there has been no progress on it for several hours and CoreTemp shows 46 degrees F, indicating no crunching is going on. If I let it run, there's no telling how long it will take to finish and my other projects will be stopped and languishing.

So should I abort it?

Earlier today the computer completed one N-Body simulation task and one Separation task without issue.

S. Gaber

Restart the BOINC client (or simply your PC), than it should continue from the last checkpoint.

---

Restart the BOINC client (or simply your PC), than it should continue from the last checkpoint.

I restarted the computer as you suggested. Lo and behold, the task finished within the hour.

I tried that in the past. But this time it worked.

The machine is now running two MW Separation tasks.

Thanks a heap.

S. Gaber

Nbody I've found is rather temperamental and rather viciously territorial. Anecdotal, but every time I've run Nbody, tasks from other projects would start to fail and other processes on the computer (favorite targets include any sort of monitoring program although BOINC itself has been victim at least once) would mysteriously terminate with no error message or warning. It doesnt happen immediately, but if left to its devices something will break.

IMO, if you want to just set and forget and not worry about any issues I would stick with Separation. Use Nbody (or both; cap Nbody to a lower number of threads and let Separation run on the rest) if you're checking up on the machine regularly, so when it does decide to cause issues it's corrected in a more timely manner.