Page 1 of 1

Stats false on web

Posted: Fri Apr 30, 2021 4:46 am
by PhilTheNet
The page https://client.foldingathome.org/ shows a completely wrong point total: 6,888,188 whereas the total is now 15,028,132
When I click on Stats the link is
https://stats.foldingathome.org/donor/PhilTheNet
which gives an empty page
whereas the link
https://stats.foldingathome.org/donor/239973
gives the right results
(same problem on all my Ubuntu OSX Windows machines)

Any ideas?

Re: Stats false on web

Posted: Fri Apr 30, 2021 6:34 am
by PaulTV
Hi,

Maybe it's passkey related. When you look at https://apps.foldingathome.org/bonus?user=PhilTheNet, you see one entry, with 736 WUs returned. Your stats page shows 1837 units though. Could it be that you haven't set the (same) passkey everywhere? My guess would be that WUs returned with a username but without passkey aren't listed on the bonus status page, meaning about 1100 were returned by clients that don't have the passkey set.

Paul

Re: Stats false on web

Posted: Fri Apr 30, 2021 7:39 am
by PhilTheNet
Indeed if I delete the passkey on a computer it gives the right total, the one that corresponds to the username

It is strange that the statistics do not link username and passkey....

Thks

Re: Stats false on web

Posted: Fri Apr 30, 2021 8:00 am
by gunnarre
The statistics site is being reworked at the moment. You might want to submit an issue here: https://github.com/FoldingCommunity/fah ... end/issues

Re: Stats false on web

Posted: Fri Apr 30, 2021 8:19 am
by PaulTV
You're probably already aware, but still: you'll only get quick return bonus (read: much more points) if you've set the passkey (and return more than 10 WUs, with 80% success rate, which you've exceeded by far).

With regards to the stats... The web control client most likely asks for the current points of the username/passkey combination. The API returns the total for the username with any or no passkey, if the passkey isn't given. The fact that the web control client doesn't give the proper link to the stats page is a known issue, already reported on github.