Reading about doubled credit i took a look into my account and found this:

3358630 1620482 5172 20 Dec 2020, 16:08:42 UTC 20 Dec 2020, 19:47:19 UTC Fertig und Bestätigt 5,302.74 5,175.34 4,326,400.00 Machine Learning Dataset Generator (GPU) v9.75 (cuda10200)
windows_x86_64

Can i have more of these wu's please?

lol.....I would like some of those, maybe one for each of the false validations I was getting.

Uuuhhhhhhh.....

facepams

My goof. Should be fixed now.

Honestly I've been so distracted with work, the holidays, and trying to write up a paper, I got lazy with this last change. After running the project for 5 months I got complacent and tried to do this one simple change without really testing it ahead of time. It's now bitten us twice, once with validation, once with credit calculation for continuation WUs based on the doubling. Most of this is caused by validation, assimilator, and new work logic that was built when we had one WU type, and one dataset, and has now grown to be very complicated and should be re-architected behind the scenes. Maybe that'll be another over-the-holidays project.

Thanks for reporting.
[/i]

No need to hurry, i can live with that kind of error! No priority one issue.
I wish you merry christmas!

Have those WUs actually been reverted to the original base credit or has the initial overestimated credit been finally assigned? Not much a credit hunter myself, but doesn't seem to have any relevance at all for comparison among users, if millions of credits were assigned for single faulty WU, while others have spent x times more CPU and GPU hours were simply overtaken within a few hours due to some misconfiguration. Defintely skewed the RAC and leaderboard calculations. What do credits actually measure then or represent if they don't accurately gauge one's computing effort anymore? Just my two cents... Thanks for your quick fix though!

For ds4 rollout I'd like to see beta-testing of the new app first.

Have those WUs actually been reverted to the original base credit or has the initial overestimated credit been finally assigned? Not much a credit hunter myself, but doesn't seem to have any relevance at all for comparison among users, if millions of credits were assigned for single faulty WU, while others have spent x times more CPU and GPU hours were simply overtaken within a few hours due to some misconfiguration. Defintely skewed the RAC and leaderboard calculations. What do credits actually measure then or represent if they don't accurately gauge one's computing effort anymore? Just my two cents... Thanks for your quick fix though!

For ds4 rollout I'd like to see beta-testing of the new app first.

no the problem is not solved