Credit adjustment

Hi!

What people are experiencing here wrt credits is a combination of many things.

1 the average credit was reduced by 25% for S5R4 compared to S5R3 as announced.
2 the claimed credit is currently independent of the granted credit, and found to be much lower atm.
3 the workunits generated at first by the S5R4 workunit generator all at the upper end of the runtime variation for a given frequency band. They should average out over time, but at the beginning we got all "bad" ones.

I intend to fix 2 in the next few days, it's an unwanted side-effect of our efforts to fix the "duration correction factor". I hope to be able to fix 3 in a longer term in the workunit generator. For now I bumped up the credit (for newly generated workunits) manually by 15% (>= 13.9%) based on the following database queries (we gave 28% more credit than SETI at the end of S5R3):

mysql> select avg(granted_credit/cpu_time) from result where name like '%S5R3%' and granted_credit>0 and cpu_time>1000;
+------------------------------+
| avg(granted_credit/cpu_time) |
+------------------------------+
|           0.0095896610820667 | 
+------------------------------+
1 row in set (1.36 sec)

mysql> select avg(granted_credit/cpu_time) from result where name like '%S5R4%' and granted_credit>0 and cpu_time>1000;
+------------------------------+
| avg(granted_credit/cpu_time) |
+------------------------------+
| 0.0061389230693111 |
+------------------------------+
1 row in set (1.42 sec)

mysql> select 0.0061 / 0.0095;
+-----------------+
| 0.0061 / 0.0095 |
+-----------------+
| 0.642105 |
+-----------------+
1 row in set (0.00 sec)

mysql> select 1/1.28;
+--------+
| 1/1.28 |
+--------+
| 0.7812 |
+--------+
1 row in set (0.00 sec)

mysql> select 0.7812 - 0.642105;
+-------------------+
| 0.7812 - 0.642105 |
+-------------------+
| 0.139095 |
+-------------------+
1 row in set (0.00 sec)

We'll keep watching these numbers and adjust credits as needed.

BM