I have started:

de_nbody_02_28_orphan_real_0
ps_nbody_02_28_orphan_real_0


de_nbody_02_28_orphan_real_1
ps_nbody_02_28_orphan_real_1

de_nbody_02_28_orphan_real_2
ps_nbody_02_28_orphan_real_2

OK, btw what's different about these WUs/simulations to others?

And nbody means CPU WUs only?

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

MilkyWay@Home runs 2 applications:

Separation tries to pull out structures called "stellar streams" from a background (see astrophysics section of the website) by running a complicated probability calculation. Separation is an older project and has since acquired a GPU version to supplement the CPU calculations.

N-body is tasked with the problem of replicating the creation of stellar streams from collisions in an arbitrary Galactic gravitational potential (basically a measure of how strong the gravity of the Milky Way is at any point and space, and in principle, time as well). What you guys are doing is running a single n-body simulation and telling us what the likelihood of your simulation fitting the observed data. In principle, this will eventually tell us where dark matter is in the Milky Way system. This is a newer application and only runs on CPUs at present, although this has potential to change in the near future.

I hope this helps!

Jake

Please mark assignments for N-body as burdening N-1 (and possibly N-2, or even N*3/4) CPU cores. Now it turns out the situation in which the equipment (4CPU + HT = 8CPU) is not fully loaded, that is not correct :(

MilkyWay@Home runs 2 applications:

Separation tries to pull out structures called "stellar streams" from a background (see astrophysics section of the website) by running a complicated probability calculation. Separation is an older project and has since acquired a GPU version to supplement the CPU calculations.

N-body is tasked with the problem of replicating the creation of stellar streams from collisions in an arbitrary Galactic gravitational potential (basically a measure of how strong the gravity of the Milky Way is at any point and space, and in principle, time as well). What you guys are doing is running a single n-body simulation and telling us what the likelihood of your simulation fitting the observed data. In principle, this will eventually tell us where dark matter is in the Milky Way system. This is a newer application and only runs on CPUs at present, although this has potential to change in the near future.

I hope this helps!

Jake

Yea it does, thx :)

What's the difference between de & ps, & real 0-2?

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

p.s:

(4CPU + HT = 8CPU) is not fully loaded, that is not correct :(

Loading kept within 60-70%, so the mind just to make corrections N*3/4 (for N-body) that would provide full system load.

This problem I have seen in other multi-core systems with the first appearance of multi-threaded applications in MilkyWay@Home. Waiting for corrections load CPU, or complete transfer of such applications on the GPU.