Hey everyone,

We are really close to releasing a new version of NBody. Hopefully, after the next two sets of optimizations, we'll have all the bugs in the newer version fixed. So for the time being, here are the new runs:
-de_nbody_05_30_2020_v176_40k__data__1
-de_nbody_05_30_2020_v176_40k__data__2
-de_nbody_05_30_2020_v176_40k__data__3

Thank you all for your continued support,

-Eric

Hello :)

I don't know, is there something wrong - just 2 seconds calculation times?

- - - - -

de_nbody_05_30_2020_v176_40k__data__2_1588605902_203704_0
<core_client_version>7.16.5</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkyway_nbody 1.76 Windows x86_64 double OpenMP, Crlibm </search_application>
Using OpenMP 4 max threads on a system with 4 processors
Number of particles in bins is very small compared to total. (0 << 1). Skipping distance calculation
Number of particles in bins is very small compared to total. (0 << 1). Skipping distance calculation
<search_likelihood>-9999999.900000000400000</search_likelihood>
<search_likelihood_EMD>-0.000000000000000</search_likelihood_EMD>
<search_likelihood_Mass>-0.000000000000000</search_likelihood_Mass>
<search_likelihood_Beta>-0.000000000000000</search_likelihood_Beta>
17:26:23 (2144): called boinc_finish(0)

</stderr_txt>
]]>

- - - - -

de_nbody_05_30_2020_v176_40k__data__2_1588605902_193201_1
<core_client_version>7.16.5</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkyway_nbody 1.76 Windows x86_64 double OpenMP, Crlibm </search_application>
Using OpenMP 4 max threads on a system with 4 processors
Number of particles in bins is very small compared to total. (0 << 1). Skipping distance calculation
Number of particles in bins is very small compared to total. (0 << 1). Skipping distance calculation
<search_likelihood>-9999999.900000000400000</search_likelihood>
<search_likelihood_EMD>-0.000000000000000</search_likelihood_EMD>
<search_likelihood_Mass>-0.000000000000000</search_likelihood_Mass>
<search_likelihood_Beta>-0.000000000000000</search_likelihood_Beta>
17:50:12 (5320): called boinc_finish(0)

</stderr_txt>
]]>

- - - - -

Thanks :)

---

Hello :)

I don't know, is there something wrong - just 2 seconds calculation times?

- - - - -

de_nbody_05_30_2020_v176_40k__data__2_1588605902_203704_0
<core_client_version>7.16.5</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkyway_nbody 1.76 Windows x86_64 double OpenMP, Crlibm </search_application>
Using OpenMP 4 max threads on a system with 4 processors
Number of particles in bins is very small compared to total. (0 << 1). Skipping distance calculation
Number of particles in bins is very small compared to total. (0 << 1). Skipping distance calculation
<search_likelihood>-9999999.900000000400000</search_likelihood>
<search_likelihood_EMD>-0.000000000000000</search_likelihood_EMD>
<search_likelihood_Mass>-0.000000000000000</search_likelihood_Mass>
<search_likelihood_Beta>-0.000000000000000</search_likelihood_Beta>
17:26:23 (2144): called boinc_finish(0)

</stderr_txt>
]]>

- - - - -

de_nbody_05_30_2020_v176_40k__data__2_1588605902_193201_1
<core_client_version>7.16.5</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkyway_nbody 1.76 Windows x86_64 double OpenMP, Crlibm </search_application>
Using OpenMP 4 max threads on a system with 4 processors
Number of particles in bins is very small compared to total. (0 << 1). Skipping distance calculation
Number of particles in bins is very small compared to total. (0 << 1). Skipping distance calculation
<search_likelihood>-9999999.900000000400000</search_likelihood>
<search_likelihood_EMD>-0.000000000000000</search_likelihood_EMD>
<search_likelihood_Mass>-0.000000000000000</search_likelihood_Mass>
<search_likelihood_Beta>-0.000000000000000</search_likelihood_Beta>
17:50:12 (5320): called boinc_finish(0)

</stderr_txt>
]]>

- - - - -

Thanks :)

I thought there was a problem but just turned out to be new installation routine for me .... ***Anyhow*** AMD marketing parody: its obvious they're firebugs lol

Don't worry. We have a check to see if a run would require over 1.5 million time steps. If it does, it sets the number of time steps to 4, and then runs it. It ends super quickly, and that error you see is just the code complaining that there are not enough particles in the histogram to calculate a likelihood, so it spits out the worst case. This is to make sure you guys do not spend months on one simulation.

However, there was something wrong with the data in the run, so we will be replacing them shortly.

-Eric