It looks like credit = runtime / 432.
This means that faster machine will get less credit than slower machine for the same amount of work.
Even more, the run time is wrong. It counts run time from last checkpoint only. In reality first 8 tasks on my screenshot ran for about 56 hours, but this computer wasn't powered on continuosly.

Hi! When granted credit is proportional to amount of calculations, for each computer granted credit = run_time / k. But k are different for different computers. :)

Hi! When granted credit is proportional to amount of calculations, for each computer granted credit = run_time / k. But k are different for different computers. :)

The runtime resets if the task is paused, PC shut down etc

Velmi zajímavá strategie přidělění kreditu za výpočet Spectra of Latin squares 3.03
Kredit je přidělěn za čas od posledního restartu PC a ne za celou dobu výpočtu která trvala rozhodně déle!
Než provedete nápravu, jsem nucen vynechat Váš projek ze své oblasi zájmu.
Děkuji za pochopení a žádám o nápravu odeslaných a doručených výsledků!


Very interesting strategy of credit allocation for calculation of Spectra of Latin squares 3.03
Credit is allocated for the time since the last PC restart and not for the entire calculation time which took definitely longer!
Until you make a correction, I am forced to leave your project out of my area of ​​interest.
Thank you for your understanding and I request a correction of the sent and delivered results!

Hi! When granted credit is proportional to amount of calculations, for each computer granted credit = run_time / k. But k are different for different computers. :)

This is extremely unfair to EVERYONE who returns valid tasks......

If you want to keep the current volunteers and attract new volunteers, I highly recommend you change this way of awarding credit.

So an OLDER, less powerful computer will receive MORE CREDIT than a very MODERN, and MORE POWERFUL computer will receive LESS CREDIT FOR THE SAME AMOUNT OF WORK.

Also, if the computer/BOINC exit BEFORE the task completes the time and credit received will be LESS than if they let it run without interruptions.

This is coming from a 25 year veteran of SETI/BOINC.

---

In your 25 years have you come up with something better?

Yes it can suck. But its used as its the easiest option when run times are not consistent.

Hi! :) It's a usual BOINC credit system that has been supplememnted in recent years with additional internal statistics that smooth out deviations.