LAR_Systems

Just as a follow up, some changes have been made to how the charts are implemented for when you toggle them on and off. The F@H "slot id" id dynamically assigned and the client when you tried only supported up to the number 8... issue is F@H if you add and remove devices in the same session can increment the number to be larger than 8 and then you don't get chart even if there is only one device folding. So little re-work on the code and now to account for this it can dynamically create charts up to 32 slot IDs for those that end up with the high IDs from trying stuff in the client or i

The people reporting numbers in the 2 Mil range are currently running on target, looks like PPD reward / WUs have changed over the past two weeks for the card which happens when projects that reward heavy are replaced by something else.

Hi, There are multiple 1070s and other GPUs with duplicate records because they will be slight variations on the model as identified by F@H client (and shown under the card name) so the records are kept separate as the different revisions, mobile units etc. behave differently with different firmware/hardware. In terms of the ranks, they are based on real-time data that is collected form users using the extension and are averaged across different work units and projects which have different PPD rewards that can and do change. As for you card reporting low P

Power outage for the API server today... good times. Back up now.

I'm hoping you will find it back online now. Looks like something changed on server/browser communication, made a couple changes and loos like its running for me. You might need to clear browser caches to see it go right away. Cheers,

You were right to call it out, the publishing service was stuck. Thanks for letting me know.

I saw this, the issue is the project throws a 404 on their API, like they were handing out work units but did not add it to the project list, so I can't get the ID, to store the data correctly, once F@H ads it' to the DB for the API, my end will pick it up and associate all the back data. It's why their project description window does not load as well.

I actually really like this solution.

I just dropped a 2950TR on SI and a RTX 3090 will run on Prime for a couple days. Hope this makes a dent.

The real reason new hires wait weeks to get their email and shared network drive

Afraid not... means I can't do development on the folding DB / Web client, need my systems running for testing and some of the uptime tests I have setup. Have the python terminal based client prototype running, but needs work.

I have 25 threads running on the Marathon project. We will see how badly the folding DB suffers as it's that server doing the lifting

To add too this, users that lower power settings for their card to save money folding. The Facepalm of people I see trying to fold using old mining rigs on 1X risers. Combine these with any of the above and brutal PPD.

They botched the rollout... it broke the APIs of the web clinets and other integrations... they need to account for the legacy systems then try again would be my guess.

Points scores etc. all come out of the F@H core client I have no say in their calculation, reward etc. I capture samples of the data reported by F@H during folds to be averaged and they fluctuate up and down while folding, they are never 100% consistent, you can see that in the charting view in the client. This means you can not really look at how your card is folding right now on a specific Work Unit PRCG and have it be 100% match of the average for the project/gpu as each WU PRCG will fold differently day to day or within the folds inside the work unit, which is w