Getting errors for the 1.90 applications for missing parameters.

<core_client_version>8.3.0</core_client_version>
<![CDATA[
<message>
process exited with code 13 (0xd, -243)</message>
<stderr_txt>
<search_application> milkyway_nbody 1.90 Linux x86_64 double  OpenMP, Crlibm </search_application>
Using OpenMP 1 max threads on a system with 32 processors
Running MilkyWay@home Nbody v1.90
Optimal Softening Length = 0.010487539811713 kpc
Error evaluating NBodyCtx: [string "-- /* Copyright (c) 2016 - 2018 Siddhartha ..."]:108: 
  Unknown named argument 'PMCorrect'
  Unknown named argument 'PMSigma'
  Unknown named argument 'usePropMot'
  3 bad named arguments found 
Failed to read input parameters file
2025-06-27 05:19:47 (346627): called boinc_finish(13)

</stderr_txt>
]]>

I'm still getting errors and invalids... as well as some Valid's also.
You seem to be on the right track but I think you need to make more changes.

As far as I can see, all the WUs, that errored out for you, were created before Kevin's latest message. it will take some time, before those are out from the system, I'm not sure if Kevin was able to increase the limit for new results or only new WUs.

Seems like I might have changed the wrong thing?
I changed what I think should be the right setting now to 100MB.
Again, let me know if the issue persists.

Somewhat annoying...

https://milkyway.cs.rpi.edu/milkyway/result.php?resultid=1015374201

Well, this WU was created before the change (well, at least before Kevin's message), not sure if the change applies to new results or just new WUs.

Got another created after Kevin's message
https://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=1003011105

Ooops! Sorry! I forgot that I did abort literally all of those in an effort to get Orbit Fitting to not give me single tasks when I have x4 CPUs in my app_config.xml file.

Don't use app_config.xml anymore for setting the number of threads per WU, use MilkyWay@home preferences instead, than you will get what you want.

All that's left of my app_config.xml is this (to get better run time estimates):

<app_config>
 <app>
  <name>milkyway_nbody</name>
  <fraction_done_exact/>
 </app>
 <app>
  <name>milkyway_nbody_orbit_fitting</name>
  <fraction_done_exact/>
 </app>
</app_config>

The same applies to me. I have nearly 2,200 errors.

Nearly all of your errors are Aborted by user, 203 (0x000000CB) EXIT_ABORTED_VIA_GUI. Users aborting 2000 WUs is not an issue we are talking here about.

Still seeing the errors. I have very low caches on each host but the older resends are still coming through with the misconfiguration. It will probably take a fairly long while to clear all the bad work with 8 possible resends for each task.

I've not checked every failed Orbit task, but the large number I did check were all from the 03_29_2024 data feed and all seemed to have task names without "orbit_fitting" -- oops! :-)

The same seems to be the case for the 04_03_2024 data set... However, I am still processing retries for earlier, valid, tasks

Cheers - Al.

[Edited to fix a date typo (I often mess up U.S.-style dates...)]

[Edited again to note that I still get some older, viable, tasks...]

Hello everyone,

One common concern has been the need for better communication. Despite my efforts to preemptively share updates, it appears more is needed. I would like to improve in this area. I'm considering regular updates (weekly, bi-weekly, or monthly) and would appreciate your thoughts on this. Please share your ideas in the comments on how I could improve communication.

Once again, I apologize for the recent issues with MilkyWay@home and am very thankful for your patience.

Best regards,
Kevin