Posts by wjm

1) Message boards : Application Code Discussion : N-Body Simulation Problem (Message 71434) Posted 8 Dec 2021 by wjm Post: My system shows only the N-Body running when it locks up with 0% CPU. Once an N-Body terminates normally, the computer is happy to simultaneously run 4 Separation programs that are single CPU apps. BOINC seems to be smart enough to not run any other application while N-Body is running. At least in my limited experience. Is there some way to tell MW to never send me the N-Body to run? Otherwise I seem only to be able to block MW altogether. (Never mind - I found the Preference for that) Thanks.
2) Message boards : Application Code Discussion : N-Body Simulation Problem (Message 71432) Posted 8 Dec 2021 by wjm Post: My apologies for somehow posting this thread twice. I cannot figure out how to delete the other version of the post, but if some moderator can, please do so.
3) Message boards : Application Code Discussion : N-Body Simulation Problem (Message 71431) Posted 8 Dec 2021 by wjm Post: There's some problem with this application, so I've suspended all instances of it. I'm running BIONC on an old HP Win10 Pro with an Intel Core I5. Generally nothing else is running on that computer other than a very little background syncing of data with other computers. It seems to run N-Body properly with the CPU at 100%. But later when I look the utilization will be down near 0% and it stays there. If I suspend it and restart it, it will go back to 100% for long periods. No other BOINC project does this, and neither do other MilkyWay@Home applications. The only solution seems to be to abort all instances of the N-Body. FWIW. wjm