Looking at this list, i find a lot of participants having a RAC from months ago. The list has not been updated

---

The list is kept up to date with each individual's current figures.

The problem is that the "current figure" only changes when the user in question is actively processing new work - and there hasn't been a lot of that recently. Hopefully, that will change soon.

The problem is that the "current figure" only changes when the user in question is actively processing new work

Is that what happens with most projects with the server code Richard? So a user who stops crunching with a very high average credit can remain near the top of the lists till eventually those with newer and faster computers can depose them?

Edit: Just thinking that if so, then a request for a change in the server code over at git-hub might be in order?

Is that what happens with most projects with the server code Richard?

Yes. I have a current RAC of 874.09 at SETI@home - which stopped issuing new work in the Spring of 2020.

Ironically, this project was an outlier until last year. It used a special, bespoke, credit handling system, which did keep the figures updated during a work drought. - but that system was desperately inefficient, and placed a heavy load on the project's servers. It was replaced (with a few bugs, which we've now ironed out) with a new bespoke system which brought us closer to the standard BOINC framework.

But that framework has an unspoken assumption that no BOINC project ever runs out of work or closes down ...

Edit - SETI RAC table

I could be wrong but I have a feeling this RAC situation was made worse by a credit glitch not to long ago that gave people way more points than what they should have received. The guy at the top of the list, parsnip soup in a clay bowl, has a few computers but nowhere what would be needed to earn an RAC of 4,082,186. To make matters worse he's a team hopper. Sometimes he's on my team, TeAm AnandTech, other times he's on Team Ukraine.
https://www.primegrid.com/show_user.php?userid=1364357
He's currently on Team Ukraine doing the "Einstein" Anniversary Challenge on PrimeGrid.
He likes to change his name somewhat as well.

You can see him here: https://statsgr.id/challenge.php?challenge_id=2024_2

And his computers are hidden, too - so we have no idea what operating system he's running, and hence what task types he's likely to have processed.

But you're right - there was a credit glitch last summer. The earliest IFS runs for Linux weren't fully credited in real time, under the old system. When the new system was activated for the first time, everyone's RAC was calculated as if the work had all been processed on a single recent day. That made for a huge spike in RAC. He may have decided to retire from this project and rest on his laurels at that point ...

Just thinking that if so, then a request for a change in the server code over at git-hub might be in order?

The server packet includes a script that updates RAC from inactive users/hosts/teams following the same method that is used when an active user/host/team reports work.
Project admins just need to run it periodically.
The suggestion is once a day.

The server packet includes a script that updates RAC from inactive users/hosts/teams following the same method that is used when an active user/host/team reports work.
Project admins just need to run it periodically.
The suggestion is once a day.

Thanks. I admit to being even more ignorant about the server side of things than I am about the client and manager code. Even there, how things change when I compile it myself following the same procedure often baffle me. I have yet to try building my own client and or manager under Windows. - Linux keeps me busy enough on that score!

Not a script (sorry) but a C++ program:
https://github.com/BOINC/boinc/blob/master/sched/update_stats.cpp

And here is how to use it:
https://boinc.berkeley.edu/trac/wiki/ProjectTasks

It'd be nice to see a correction applied here.