6 of the EMD_NEW_100K units - 3 of the "de" and 3 "ps" .. all failed.

Steve has written:

I just uploaded two searches, de_plum_slice_EMD_NEW_100K and ps_plum_slice_EMD_NEW_100K. Hopefully these will run smoothly but let me know if anyone has any problems.

Dear Steve,

well, as You see, they run pretty smuuuuthly. :)))

Now seriously: It has been three days. Please, tell us about some progress, we deserve it. :)
I have 3 small questions:

1) Can You estimate when they are fixed or deleted?

2) Because they replicate over and over when error, can You please set lower limit of their MAX.replication rate? ... So the last one of them will have their LAST TRY error out sooner ? :)

3) Tel us what to do with them. Compute untill they all error out their last try? Or shall we kill them on sight? ... shall we wait and compute something else for the time being untill fixed?

4) Can You please create new set of WUs that will work - to compute between the returning error-ones (there is already not enough work for all) ??
I have suggestion - as a professional programmer/developer: Now that You know for sure what is wrong with them(NEW) from all the posts, I would recommend: to compare the config of the "output generator" of the old ones and config of new ones, make it perfectly similar (search for hidden whitespace also! no extra tab or space should be there around the Line 37, just for sure ) - so it would be really the same format/syntax as the old ones,
thus would run OK like the old WUs.

Steve, could You try it, please? We need some new work for CPU (only NBody is really for CPU - the separation is done 800 times faster on GPUs... so better may it run on them).

Thanx a lot for all answers to come, Steve.

*Namaste*
Filip

Why not to use, just for now, the old format of the output histograms ?

After Restarting NBody-Server after last stop on beginning of month 6, I get many WU's.
First 3 Day's all work well.
On Third day, all WU's ending with calculation errors, I think ERR-NR15
After 4. day NBody Server where stopped and nobody gets new WU's
Now no WU's and no running NBody-Server is the Staus of today.
Over 6 weeks and no proper working NBody WOW!?

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
process exited with code 15 (0xf, -241)
</message>
<stderr_txt>
<search_application> milkyway_nbody 0.88 Linux x86_64 double  OpenMP, Crlibm </search_application>
Using OpenMP 7 max threads on a system with 4 processors
Error reading histogram line 37: massPerParticle = 0.000100
18:53:54 (5221): called boinc_finish

</stderr_txt>

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=253993090

2.5% by 2.5% :)

When the outstanding n-Body work units finally get down to zero, is there to be another series ?

The count is now at 2.