I am unable to join my Team Boinc@Australia. When clicking join this team I receive the following error:

Deprecated: Creation of dynamic property BoincTeam::$refcnt is deprecated in /home/boinc/boinc/milkyway/html/user/team_search.php on line 67.

Can anybody help me identifying where the problem lies. ?

Is there a source code available for the orbit fitting version of the nbody tasks? I would like to try it out on some ARM devices like Raspberry Pi 5 or something similar :)

Currently there are only "Milkyway@home N-Body Simulation with Orbit Fitting tasks" available, which is basically a newer version of the N-Body application. Simply enable both, they use about same amount of memory and same amount of threads, so you shouldn't run into any issues, you might however need to update your app_config.xml if that's what you are using to limit the number of cores per task.

I hope they bring back the regular N-Body Simulation tasks, I'm almost to a milestone and would hate to miss it.

About 70% of my results look like this:

run time | CPU time | credits
223.89   | 1,807.51 | 28.25

But the other 30% look like this:

run time | CPU time | credits
224.09   | 1,863.43 | 1.41

Why are there so many results with such low credits?
This happens on 2 different PCs.

I am unable to get any Milkyway project tasks when using single core CPU computers from The Science Cloud.

Please fix the blockage.

Kevin Roux wrote:

Working on
- Will look into getting number of CPUs used as an option in Preferences

When looking into it, perhaps you can also check if it's possible to send the single thread application in case someone chooses to run Milkyway on a single core. I have not tested it, but probably it will run faster than the MT application forced to run on a single core. At least in theory it should. I mean, you compiled a single core version, it's there, there's just no way to get it automatically from the server. Or maybe a selection between the ST app and the MT app could be a simple way to get at least some options in case making it possible to select any number of cores needs too much time.

i assume there are still no plans as of today to support the Apple silicon arm architecture ?

And what does "OCS" mean in the job name?

@Kevin: will the new N-Body Simulation with Orbit Fitting replace the old N-Body Simulation? As far as I see in the results it's calculating <search_likelihood>, <search_likelihood_EMD>, <search_likelihood_Mass> and <search_likelihood_Beta> like the old app did and adds on top of that <search_likelihood_BetaAvg>, <search_likelihood_VelAvg> and <search_likelihood_Dist>. So the old app does not seem necessary unless it's working on completely different data.

Hello everyone,

I am working on getting a new version of our code up on the server.
This new version will allow us to fit orbits on top of the other parameters we have already been fitting.
There seems to be a slight issue right now with downloading the new version and I am working on fixing the issue.

Thank you,
Kevin