Posts by Michael E.@ team Carl Sagan

1) Message boards : Number crunching : Error While Computing after brief processing with Orbit Fitting work units (Message 77092) Posted 2 days ago by Michael E.@ team Carl Sagan Post: Thank you @eiernacken1983 and @xii5ku. It seems the bad tasks are less of a problem now. I can live with a 10% or less error rate, so I enabled the Orbit tasks.
2) Message boards : Number crunching : Error While Computing after brief processing with Orbit Fitting work units (Message 77006) Posted 20 days ago by Michael E.@ team Carl Sagan Post: I am getting an Error While Computing when trying to process work units with Orbit Fitting, such as 943173290. They process only for a few seconds. This seems to be a new error to me. It might be specific to my environment. The normal work units without the Orbit Fitting option seem to run fine. I am using 2 CPUs per work unit. I turned off Orbit Fitting in my Project > Account > MilkyWay@Home preferences for now.
3) Message boards : News : New N-Body Runs (Message 76281) Posted 19 Jul 2023 by Michael E.@ team Carl Sagan Post: When a task has used more than a few days of Elapsed time, it is correct to abort it? No. If the task is however not using any CPU time, than you need to restart it. This might happen if you don't let BOINC use 100% of CPU time (not CPUs), if this happens to you sometimes, leave CPUs at your 42%, but set CPU time to 100%, nBody doesn't like anything below. Thank you @Link! Would have never known that. Yes, I set the CPU % of time to 100. I just downloaded a few more n-body tasks.
4) Message boards : News : New N-Body Runs (Message 76272) Posted 17 Jul 2023 by Michael E.@ team Carl Sagan Post: I do not use a config file and enabled N-body in Milkyway Preferences. I limit CPU use to 2 cores (such as 42% of the CPUs in a 6 core system) and measure temperature using Mooo System Monitor. So the Milkyway tasks use 2 CPUs. Some N-body tasks take less than an hour, while others a few hours. When a task has used more than a few days of Elapsed time, it is correct to abort it? FYI: I have a Windows OS and an Intel Core 5 CPU 9th gen. about 6 years old. I check the task manager for CPU use. Any tips or suggestions?
5) Message boards : News : Nbody release v1.74 (Message 68165) Posted 17 Feb 2019 by Michael E.@ team Carl Sagan Post: I just started using N-body work units again after a few years. A work unit that originally said it would complete in 18 hours on a 2-CPU system (50% of 4 CPUs) has taken almost three days so far and is about half finished (Host name: DESKTOP-QKT2DLD has BOINC Versiom 7.14.2). I suspect at least one or both CPU threads are stalled maybe waiting for a join based on very low CPU usage. I just turned off N-body apps in Milkyway Preferences temporarily because one system is a laptop and I prefer shorter work units. That laptop only allows one CPU (25% or 4 CPUs) so I was not expecting it to get N-body work units assigned! If I can help, please send me a private note. I am familiar with parallel processing and native code app performance analysis, so I am curious what is happening. Michael E.