hi,
not receiving any work units from N-Body. Separation were last units received.
how do I get the n-body units?

You have to change your Preferances at the site to accept n-bodys for processing. It's under projects tab..

hi,
not receiving any work units from N-Body. Separation were last units received.
how do I get the n-body units?

You have to change your Preferances at the site to accept n-bodys for processing. It's under projects tab..

You have to select cpu versus ATI gpu or Nvidia gpu yes

Resource share ---
Use CPU
Use ATI GPU
Use NVIDIA GPU
Is it OK for MilkyWay@home and your team (if any) to email you?
Emails will be sent from milkyway@cs.rpi.edu; make sure your spam filter accepts this address.
Should MilkyWay@home show your computers on its web site?
Default computer location ---
Maximum CPU % for graphics
0...100 20
Run only the selected applications Milkyway@home N-Body Simulation: yes
If no work for selected applications is available, accept work from other applications? no

Edit preferences

I meant Preferances.
Sorry.

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?

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?

Yes, let them run. I have had a number of those increase in time remaing! But they will eventually sort themselves out. I have also seen tasks that start at high values of time left, say 35 hours or so, will click off 3 or 4 minutes/3 second update, as they get closer to finishing. Kinda wierd, but it works out ok in the end. Good Luck!

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.

---

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.

I see in the download dir of Milkyway both mt and non-mt versions of n-Body application, for Linux and Windows. Maybe since separation is gone it would be possible to make it possible to choose, which of those we want to run since you have both anyway. Yes, I know it's possible to run the mt app on a single core via app_info.xml, but this would be more convenient for most users and maybe a real ST app could be even a bit faster than MT app forced to run on a single core (though this is just a speculation). Or is there some way to get the non-mt app which I am not aware of?

---

Download the non-MT app and use it in a anonymous platform via an app_info.xml.

---