New credit system being inconsistently applied?
Message boards : Number crunching : New credit system being inconsistently applied?
Author | Message | |
---|---|---|
Hello, I'm so thirlled we've moved to the server assigned credits and understand that'll be tweaked here and there for a bit.
|
||
ID: 5276 | Rating: 0 | rate: / | ||
From what I've seen
most
tasks I received after some point on August 3rd have all been granted the fixed credit. The only one so far that gave me the old credit was a task that was reissued because the first host never returned it.
|
||
ID: 5277 | Rating: 0 | rate: / | ||
Yeah, some of my units are being applied iwth the new system. In fact, I have one computer where most everything has been on the new system. But some of my other systems are getting a mix of new and old scoring systems for work untis being returned even within the last couple of hours. Should I abort all unfinished work units and fetch all new ones? Anyone else seeing this issue? I've got at least three machines (10 cores) affected by this. Three of the other machines seem to be faring better. |
||
ID: 5278 | Rating: 0 | rate: / | ||
AFAIK the method of granting credits is determined with the creation of the WU, unless someone with the projects writes an extra script to fiddle with the database afterwards. Those with the old credits are probably old WUs, perhaps resends or just some who still linger on the machines.
|
||
ID: 5280 | Rating: 0 | rate: / | ||
Yes, that's correct workunits previous to 1k1j will get variable credit, and all workinits after that will get fixed credits |
||
ID: 5287 | Rating: 0 | rate: / | ||
Yeah, some of my units are being applied iwth the new system. In fact, I have one computer where most everything has been on the new system. But some of my other systems are getting a mix of new and old scoring systems for work untis being returned even within the last couple of hours. Should I abort all unfinished work units and fetch all new ones? Anyone else seeing this issue? I've got at least three machines (10 cores) affected by this. Three of the other machines seem to be faring better. It is not an issue! If you abort...someone else would just get them and have to cover your butt. Just do the work for crying out loud. We all will finish them up in time. Try to remember why we are really doing this. ____________ Recognized by the Carnegie Institute of Science . Washington D.C. |
||
ID: 5290 | Rating: 0 | rate: / | ||
Well, of course I"m not going to do it now that they've clarified the odl score is for particular batches of work units. You could imagine a situation where the old scores are being used on units issued before a certain time and if they were reissued now they would get scored under the new system, at which point it would make sense to abort and then anyone who got those would get credited under the new system. Since the server is continuing to assign old credit values for older BATCHES of work units then yes, it would be rude to abort them now and I won't do that. That's why I was seeking clarification. Everyone relax. |
||
ID: 5294 | Rating: 0 | rate: / | ||
Well, of course I"m not going to do it now that they've clarified the odl score is for particular batches of work units. You could imagine a situation where the old scores are being used on units issued before a certain time and if they were reissued now they would get scored under the new system, at which point it would make sense to abort and then anyone who got those would get credited under the new system. Since the server is continuing to assign old credit values for older BATCHES of work units then yes, it would be rude to abort them now and I won't do that. That's why I was seeking clarification. Everyone relax. ~smiles~ ____________ Recognized by the Carnegie Institute of Science . Washington D.C. |
||
ID: 5295 | Rating: 0 | rate: / | ||
Since the server is continuing to assign old credit values for older BATCHES of work units then yes, it would be rude to abort them now and I won't do that. You won't be smiling at me Heidi..... I aborted them....., But mainly because it looked like my farm was going to be down for nearly a week (budgetary restraints) and most of them were too near to the deadline - I run a fairly long cache. Sorry Captain!!! :( |
||
ID: 5298 | Rating: 0 | rate: / | ||
Currently there seems to be one series of results that has way too high credits,
|
||
ID: 5739 | Rating: 0 | rate: / | ||
Currently there seems to be one series of results that has way too high credits, Lately there have been credits way too low. something like : claimed=10 granted=34 |
||
ID: 5746 | Rating: 0 | rate: / | ||
Currently there seems to be one series of results that has way too high credits, Oh, then the higher grant is planned - I assumed that 10/34 was normal. |
||
ID: 5750 | Rating: 0 | rate: / | ||
Currently there seems to be one series of results that has way too high credits, Never assume anything. I just prefer it to be higher. |
||
ID: 5762 | Rating: 0 | rate: / | ||
I had one task that took 11 minutes to crunch. 2 credits claimed/100 granted. There was only one like that in the few dozen I reviewed.
|
||
ID: 5789 | Rating: 0 | rate: / | ||
I had one task that took 11 minutes to crunch. ... They sure had a warning with "Code101" in them, I have seen a few of those too. I guess this catches a condition that should not occur in a regular result, similar to those at SETI where terrestrial signals polluted the Arecibo data. I reported it in a separate thread, those sure need a special treatment in the science database. |
||
ID: 5796 | Rating: 0 | rate: / | ||
Hi,
|
||
ID: 5834 | Rating: 0 | rate: / | ||
Hi,
|
||
ID: 5840 | Rating: 0 | rate: / | ||
Sorry about that, they were possibly part of the incomplete workunits |
||
ID: 5862 | Rating: 0 | rate: / | ||
We had some problems with workinits in the past days, and since the credit is very democratic it assigns the average of what all the volunteers in the past 3 hours were asking for the same type of workunit, that's why it varies from time to time |
||
ID: 5863 | Rating: 0 | rate: / | ||
Message boards : Number crunching : New credit system being inconsistently applied?
Database Error: The MySQL server is running with the --read-only option so it cannot execute this statement
array(3) { [0]=> array(7) { ["file"]=> string(47) "/boinc/projects/docking/html_v2/inc/db_conn.inc" ["line"]=> int(97) ["function"]=> string(8) "do_query" ["class"]=> string(6) "DbConn" ["object"]=> object(DbConn)#24 (2) { ["db_conn"]=> resource(108) of type (mysql link persistent) ["db_name"]=> string(7) "docking" } ["type"]=> string(2) "->" ["args"]=> array(1) { [0]=> &string(51) "update DBNAME.thread set views=views+1 where id=455" } } [1]=> array(7) { ["file"]=> string(48) "/boinc/projects/docking/html_v2/inc/forum_db.inc" ["line"]=> int(60) ["function"]=> string(6) "update" ["class"]=> string(6) "DbConn" ["object"]=> object(DbConn)#24 (2) { ["db_conn"]=> resource(108) of type (mysql link persistent) ["db_name"]=> string(7) "docking" } ["type"]=> string(2) "->" ["args"]=> array(3) { [0]=> object(BoincThread)#3 (16) { ["id"]=> string(3) "455" ["forum"]=> string(1) "2" ["owner"]=> string(4) "9657" ["status"]=> string(1) "0" ["title"]=> string(47) "New credit system being inconsistently applied?" ["timestamp"]=> string(10) "1269635587" ["views"]=> string(3) "502" ["replies"]=> string(2) "18" ["activity"]=> string(22) "1.7335989005138001e-75" ["sufferers"]=> string(1) "0" ["score"]=> string(1) "0" ["votes"]=> string(1) "0" ["create_time"]=> string(10) "1249423133" ["hidden"]=> string(1) "0" ["sticky"]=> string(1) "0" ["locked"]=> string(1) "0" } [1]=> &string(6) "thread" [2]=> &string(13) "views=views+1" } } [2]=> array(7) { ["file"]=> string(63) "/boinc/projects/docking/html_v2/user/community/forum/thread.php" ["line"]=> int(184) ["function"]=> string(6) "update" ["class"]=> string(11) "BoincThread" ["object"]=> object(BoincThread)#3 (16) { ["id"]=> string(3) "455" ["forum"]=> string(1) "2" ["owner"]=> string(4) "9657" ["status"]=> string(1) "0" ["title"]=> string(47) "New credit system being inconsistently applied?" ["timestamp"]=> string(10) "1269635587" ["views"]=> string(3) "502" ["replies"]=> string(2) "18" ["activity"]=> string(22) "1.7335989005138001e-75" ["sufferers"]=> string(1) "0" ["score"]=> string(1) "0" ["votes"]=> string(1) "0" ["create_time"]=> string(10) "1249423133" ["hidden"]=> string(1) "0" ["sticky"]=> string(1) "0" ["locked"]=> string(1) "0" } ["type"]=> string(2) "->" ["args"]=> array(1) { [0]=> &string(13) "views=views+1" } } }query: update docking.thread set views=views+1 where id=455