Posts by Koen

1) Message boards : Number crunching : Giving Zero Credit for Work Completed (Message 80689) Posted 28 Sep 2016 by Koen Post: These might be a result of the database and filesystem issues we had recently. It's stable now at the moment particularly without the load coming from Charity Engine. Please let us know if these errors continue for the rb_ jobs. These jobs are standard jobs that should not fail (they should have a high success rate). I had a closer look at this. It seems like all these workunits are marked as 'Canceled' on the workunit-details-page. Might be the smoking gun in solving this problem...
2) Message boards : Number crunching : Low credit from mini version vs prior (Message 55285) Posted 25 Aug 2008 by Koen Post: The way the credit system works, if one host is consistently getting significantly less then claimed credit, there must be hosts elsewhere that are getting consistently more then claim. Has anyone spotted any hosts getting more then their claims for task crunched by mini? Perhaps duos and Quads? Yes I have, on my Intel(R) Pentium(R) D CPU 3.20GHz (PIV 940D,dual core, @ 3.3 GHz). My Genuine Intel(R) CPU T2400 @ 1.83GHz gets roughly what it claims. My 3 Intel(R) Core(TM)2 Duo CPU's E4500 @ 2.20GHz get significantly less credit. My Pentium D is the only one that has 2MB L2 cache per core (the other cpu's only have 1MB L2 per core). I wonder if this has anything to do with it.
3) Message boards : Number crunching : Tasks end prematurely. (Message 55266) Posted 24 Aug 2008 by Koen Post: It happens when the task has run for more than half your target CPU-time. On restart this task ends and reports only 1 decoy, as seen in task details ( Example), but receives what seems to be the right amount of credits. My guess: At restart Rosetta Mini (only occurs on Mini-tasks) reports the exact runtime to Boinc but only 1 decoy. If this runtime is past half way your target time, Boinc decides there isn't enough time to complete another decoy. If needed I can try to describe this a little better, my English is a bit rusty... Koen
4) Message boards : Rosetta@home Science : Prototype of Rosetta "game" (Message 45304) Posted 23 Aug 2007 by Koen Post: OK, I believe it's fixed now. Totally quit out of your browser and/or clear your cache and/or reboot if you're still having trouble. Does that fix the problem for everyone who tried Java 6 under Windows and got the red X? Best, Ian PS Much thanks for helping track down this bug! I never would have caught it on my own... Problem fixed! Well done! Glad I could 'help'. Koen
5) Message boards : Rosetta@home Science : Prototype of Rosetta "game" (Message 45127) Posted 18 Aug 2007 by Koen Post: Worked fine with Java 5 Update 4 (+ Firefox). Had to update Java today to version 6 Update 2 and all I get to see now is that darn red X. (On the game-screen it said: "If you're having trouble loading the game, update Java to the latest version". Oops :)) Regret the X in the box does not activate for me either. I am using Microsoft Internet Explorer 7.0 and Java 6 Update 2, which I think are the latest in the UK. Is the game working with these versions anywhere else?
6) Message boards : Number crunching : Miscellaneous Work Unit Errors (Message 11490) Posted 28 Feb 2006 by Koen Post: Don't know if it has anything to do with it but I noticed that the RAM footprint of the rosetta-app. sometimes rises to as high as 130MB when processing HBLR_1.0-workunits.Do I remember correctly that this also caused problems a couple of months ago? Looking at the errors my fellow-crunchers experienced I noticed that a lot of those errors occur on the above mentioned HBLR_1.0-workunits.So I thought this was worth mentioning.If not, please allow my appologies for wasting your time. K.
7) Message boards : Number crunching : Report Maximum CPU Time Exceeded WU HERE (Message 10590) Posted 9 Feb 2006 by Koen Post: Got one more: WU5802261
8) Message boards : Number crunching : Report Maximum CPU Time Exceeded WU HERE (Message 10059) Posted 27 Jan 2006 by Koen Post: Got one too: WU 5705193 Last time I checked the WU was at 97,5% K.