Posts by Gavin Shaw

1) Message boards : Number crunching : Problems with Minirosetta Version 1.64/1.65 (Message 61027) Posted 5 May 2009 by Gavin Shaw Post: Crashed unit using MiniRosetta 1.65. Docking_benchmark_natives__1FBI.mppk.pdb.gzdock_score12_hi.xml_11809_52_1 Boinc error message: Unrecoverable error for result Docking_benchmark_natives__1FBI.mppk.pdb.gzdock_score12_hi.xml_11809_52_1 ( - exit code -1073741819 (0xc0000005))
2) Message boards : Number crunching : Problems with Minirosetta v1.54 (Message 60817) Posted 25 Apr 2009 by Gavin Shaw Post: And another big upload. Task 246174559 run for 4 hours with 82 decoys. File upload size was 8.9MB. Took a while to upload. Hate to see what it would have been if there were 99 decoys...
3) Message boards : Number crunching : Problems with Minirosetta v1.54 (Message 60660) Posted 15 Apr 2009 by Gavin Shaw Post: Had another big one overnight. Task 243710356 was another 6.8MB upload, again with 99 decoys. Of course I have now seen a post about some problem with units, but it didn't help as the unit had already crunched :)
4) Message boards : Number crunching : Problems with Minirosetta v1.54 (Message 60638) Posted 14 Apr 2009 by Gavin Shaw Post: While not exactly a bug, this morning I had a rather large upload file... Task 243404526 had a 6.8MB file to upload. The task only run for about 50 minutes and my preference is set to 4 hours. It did 99 decoys from 99 attempts. Thought admin might want to know...
5) Message boards : Number crunching : Problems with Minirosetta v1.54 (Message 59228) Posted 1 Feb 2009 by Gavin Shaw Post: Got this one a day or so ago. Not sure if it is a failure/error. 224812655
6) Message boards : Number crunching : Discussion on increasing the default run time (Message 56946) Posted 15 Nov 2008 by Gavin Shaw Post: Though the watchdog doesn't seem to kick in until about 3.5x the desired time has elapsed. Perhaps it is giving the unit some time to finish off before booting it?
7) Message boards : Number crunching : Discussion on increasing the default run time (Message 56942) Posted 15 Nov 2008 by Gavin Shaw Post: This obviously will only affect people with default run times or people who have set their run time to be less than 6 hours. Perhaps I'm just thick or slow (it is the weekend where I am), but how does changing the min time to 3hr and the default to 6hr affect me when I have my run time set to 4hr? It is still greater than the min time so nothing should change right?
8) Message boards : Number crunching : Minirosetta v1.40 bug thread (Message 56922) Posted 14 Nov 2008 by Gavin Shaw Post: Had one unit go funny. Long Unit My preference is set to 4 hours and this one went way longer than that and didn't finish? When I last looked it was still on the first model/decoy. I also notice that it was a resend as well.
9) Message boards : Number crunching : minirosetta v1.15 bug thread (Message 52763) Posted 28 Apr 2008 by Gavin Shaw Post: Ran a second Rosetta Mini unit. It dies after about 7 hours (target runtime is 8 hours). Boinc output has the following: 28/04/2008 4:51:14 AM\|rosetta@home\|Computation for task 1cei__BOINC_ABINITIO_IGNORE_THE_REST-S25-13-S3-11--1cei_-_3105_1_0 finished 28/04/2008 4:51:14 AM\|rosetta@home\|Output file 1cei__BOINC_ABINITIO_IGNORE_THE_REST-S25-13-S3-11--1cei_-_3105_1_0_0 for task 1cei__BOINC_ABINITIO_IGNORE_THE_REST-S25-13-S3-11--1cei_-_3105_1_0 absent Task 158649586 Looks like a similar error to my previous.
10) Message boards : Number crunching : minirosetta v1.15 bug thread (Message 52744) Posted 26 Apr 2008 by Gavin Shaw Post: Okay. Run my first Roseeta Mini unit over night while I was asleep. Woke up and found it had a compute error. From the message log in Boinc this was given as the reason: 27/04/2008 7:51:52 AM\|rosetta@home\|Output file 1c8cA_BOINC_ABINITIO_IGNORE_THE_REST-S25-9-S3-3--1c8cA-_3092_209_0_0 for task 1c8cA_BOINC_ABINITIO_IGNORE_THE_REST-S25-9-S3-3--1c8cA-_3092_209_0 absent Have reported it back and received no credits (not that I expected otherwise) and it is task 158393978 In short the first lines say the following: Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x005BD4A8 write attempt to address 0x00000008 Engaging BOINC Windows Runtime Debugger... Memory addressing problem? Hope this helps...