Hello all,
I just wanted to let you know that new runs for the newest version of the MilkyWay@home Nbody program have just been released. The names of these new runs are:
-de_nbody_04_23_2019_v176_40k__data__1
-de_nbody_04_23_2019_v176_40k__data__2
-de_nbody_04_23_2019_v176_40k__data__3
I apologize for any inconveniences over the last few days. If you have any issues with these runs, please let me know on this thread and I will try to sort them out as quickly as I can.
Just so you know, some of the changes we made for this nbody version take runs that would've taken extremely long times to compute and return success immediately. As such, credit for nbody may be a little strange until the server recognizes the new average runtime. Also note that there is no longer support for multi-threaded.
Again, thank you all for your continued support.
-Eric Mendelsohn

Just checked my machines and see all of the my nbody tasks are failing with computation errors. I looked and can see the executable in the project folder so appears to be an issue on the server side.

The tasks are "de_nbody_4_16_2017_v174_20k__sim..." and are associate with the app "milkyway_nbody_1.76_x86_64-pc-linux-gnu"

Don't know enough to say these are new or just new to me.

Ron

I am also getting large numbers of failures with the 1.76 work. They run for a few seconds at most then error out.

Checking my error list the phrase "too many errors may have a bug" comes up repeatedly.

Application
Milkyway@home N-Body Simulation 1.76
Name
de_nbody_4_16_2017_v174_20k__sim_ex_1_1555431910_15537
State
Computation error
Received
Wed 24 Apr 2019 16:00:56 AEST
Report deadline
Mon 06 May 2019 16:00:55 AEST
Estimated computation size
31,856 GFLOPs
CPU time
00:00:00
Elapsed time
00:00:05
Executable
milkyway_nbody_1.76_x86_64-pc-linux-gnu

Application
Milkyway@home N-Body Simulation 1.76
Name
de_nbody_4_16_2017_v174_20k__sim_ex_1_1555431910_354929
State
Computation error
Received
04/24/19 07:45:42
Report deadline
05/06/19 07:45:41
Estimated computation size
48029 GFLOPs
CPU time
00:00:00
Elapsed time
00:00:09
Executable
milkyway_nbody_1.76_x86_64-pc-linux-gnu

Just a thought, but if you guys could stop sending out these units till they're sorted, that would be great.

I’ve stopped all new MilkyWay work until this is sorted. Waste of my machine.

We can cancel all of these workunits and abort them on the server side. I'll do that now. The only ones that should be erroring are those which haven't cleared the work queue yet.

Sorry about that.

Best,

Jake

Well I’ll be. Restarted and lo and behold …

Milkyway@Home 1.76 Milkyway@home N-Body Simulation de_nbody_04_23_2019_v176_40k__data__1_1555431910_414159_0 00:22:17 (00:21:37) 4/24/2019 1:21:01 PM 4/24/2019 1:28:56 PM 97.008 Reported: OK 11.52 MB 15.33 MB

5 others and a bunch currently running.

Glad I could help!

Best,
Jake

How does a person opt OUT of the N-body work? There used to be a way to do this in Preferences, but I can no longer find that option.

We recently moved MilkyWay@home onto a new server, so it might just be that the preferences were not transferred over correctly. I'll try to figure out how to get that fixed.
-Eric

How does a person opt OUT of the N-body work?

Just de-select "Use CPU". It is the only CPU project they have now.

How does a person opt OUT of the N-body work?

Just de-select "Use CPU". It is the only CPU project they have now.

No, "Milkyway@home Separation" has CPU apps as well, see applications page.

---

Eric, could you drop in on the thread regarding inability to get work from the server when requested for fast hosts. The consensus is that the server "feeder" mechanism isn't set up correctly. One of the Einstein scientists offered some insight on the issue that Einstein experienced and remedied with correct configuration. The thread is here:
https://boinc.berkeley.edu/forum_thread.php?id=12918#91262

---

No, "Milkyway@home Separation" has CPU apps as well, see applications page.

You are right. I just attached a new BOINC instance, selected CPU only, and got both N-Body and Separation. It appears that something got lost in the transition.

On the other hand, what happens when you select both CPU and GPU? (That is, do you get only the GPU Separations then?)
I will try that later.

On the other hand, what happens when you select both CPU and GPU? (That is, do you get only the GPU Separations then?)

Than you get Separation for GPU and Separation and n-Body mix for the CPU.

---

Do you remember what the option for opting out of N-body units was called? Was it "Run test applications?"? I'm still looking into the website code to resolve this.
-Eric

Eric,
It was just one of the options offered under the user's project preferences. Perhaps Travis knows?

Do you remember what the option for opting out of N-body units was called? Was it "Run test applications?"? I'm still looking into the website code to resolve this.
-Eric

Do you remember what the option for opting out of N-body units was called? Was it "Run test applications?"? I'm still looking into the website code to resolve this.
-Eric

No, it was something like:

Run only the selected applications:   Milkyway@home Separation: yes/no
                                      Milkyway@home N-Body Simulation: yes/no

If no work for selected applications is available, accept work from other applications?: yes/no

---