Hey All,

I just released a new version of Nbody. This updates fixes some library issues we were having. Also, it adds a center of mass and center of momentum correction to the initialization (the added computation time is very negligible). We did this because we found that different seeds would produce a small random initial center of mass position and velocity. While it was not a large difference, we wanted it to be nonexistent.

I will be putting up some runs shortly.

As always, thank you all!
Sidd

Seems the RUN TIME ESTIMATES are WAY OFF!

On my 8 core PC I have one that is STILL running with just slightly over 16 hours (Multiply by 8 CORES = 128+ HOURS CPU TIME) currently at about 84.65% completed.

1.56 MilkyWay@Home N-Body Simulation (mt)
ps_nbody_3_8_16_orphansim_v156_3_1453826702_1075098_0
16:06:55 (117:34:50) 84.650%

The Original Run times estimates were about 20 minutes.

---

System--Kindle Fire HD 7..Dual ARMv7 1200MHz cpus, Android 3.0.8, supposedly

After running Milky Way for several days with no issues (2200 credits), suddenly...

Message from Server: Your app_info.xml file doesn't have a useful version of MilkyWay@Home N-body Simulation

This may be related to the new N-body version....

New to Milky Way and Android, but approaching 700,000 credits on Mapping Cancer Markers and Rosetta on Dell/HP desktops running Linux.

[Edit] "may be related to the new N-body version...' ...or not..fiddled with things for a few minutes, and new tasks are again running (7 hours estimated)--will check this evening.

S.