Minirosetta v1.40 bug thread

Message boards : Number crunching : Minirosetta v1.40 bug thread

To post messages, you must log in.

Previous · 1 . . . 12 · 13 · 14 · 15

AuthorMessage
Alec Rosa

Send message
Joined: 11 Nov 08
Posts: 18
Credit: 2,635
RAC: 0
Message 57633 - Posted: 5 Dec 2008, 20:06:43 UTC

I don't care anymore! Version 1.45 works! (For now anyway.)
Yay.
ID: 57633 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
bluelady9

Send message
Joined: 7 Nov 08
Posts: 1
Credit: 10,331
RAC: 0
Message 57637 - Posted: 5 Dec 2008, 22:56:27 UTC

Hi
I am getting this message constantly on the rosetta project currently running:
restarting task cc_3_5_nocst4_homo_bench_foldst_chunk_general_t368_olange__IGNORE_THE_REST_1NADA_4_5376_10_0_usingminirosettaversion140

over and over again, I have over 60 of these messages one after the other in the messages window. What's going on? Should I just reset the whole thing? I'd appreciate any help with this. Thank you.
ID: 57637 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mike Tyka

Send message
Joined: 20 Oct 05
Posts: 96
Credit: 2,190
RAC: 0
Message 57642 - Posted: 6 Dec 2008, 2:19:05 UTC - in response to Message 57633.  

I don't care anymore! Version 1.45 works! (For now anyway.)
Yay.


Well awesome! That's what we like to hear :) Keep us posted if you see any issues.
I know there are still issues with 1.45 do with the graphics which we'll address in future updates, but they are cosmetic and the errors concerning lockfiles, validator errors etc etc etc had priority. Stability first.

Thanks for crunching!

Mike

http://beautifulproteins.blogspot.com/
http://www.miketyka.com/
ID: 57642 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile rochester new york
Avatar

Send message
Joined: 2 Jul 06
Posts: 2838
Credit: 2,020,043
RAC: 0
Message 57660 - Posted: 6 Dec 2008, 20:21:01 UTC

ID: 57660 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5528
Credit: 5,543,488
RAC: 1,208
Message 57661 - Posted: 6 Dec 2008, 20:51:20 UTC - in response to Message 57660.  

https://boinc.bakerlab.org/rosetta/results.php?hostid=267483&offset=20


more detached clients? have you closed boinc mgr and restarted it or your system since this started? only other thing i would suggest is to NOT accept any new work and then reset the project after all the current work has finished and reported.
ID: 57661 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile gabberattack (johnny, eriq, segfault, r2k4, bully, sifon)

Send message
Joined: 27 Sep 05
Posts: 12
Credit: 5,984,531
RAC: 533
Message 57666 - Posted: 7 Dec 2008, 5:37:55 UTC
Last modified: 7 Dec 2008, 5:38:14 UTC

iMac Intel Core2Duo 1,86 GHz, OSX 10.5.5, BOINC 5.10.45, CPU use limited to 75%.

This WU https://boinc.bakerlab.org/rosetta/result.php?resultid=211924207 and this one https://boinc.bakerlab.org/rosetta/result.php?resultid=211927271 are running for 18 and 25 hours already using Minirosetta 1.40. Should I reset the project or let it run ? Progress is frozen at 99.079% and 99.353%, remaining time shows on both WU 9 minutes 56 seconds.
ID: 57666 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile robertmiles

Send message
Joined: 16 Jun 08
Posts: 1193
Credit: 13,206,567
RAC: 721
Message 57669 - Posted: 7 Dec 2008, 8:56:57 UTC - in response to Message 57666.  

iMac Intel Core2Duo 1,86 GHz, OSX 10.5.5, BOINC 5.10.45, CPU use limited to 75%.

This WU https://boinc.bakerlab.org/rosetta/result.php?resultid=211924207 and this one https://boinc.bakerlab.org/rosetta/result.php?resultid=211927271 are running for 18 and 25 hours already using Minirosetta 1.40. Should I reset the project or let it run ? Progress is frozen at 99.079% and 99.353%, remaining time shows on both WU 9 minutes 56 seconds.


That type of apparantly frozen progress is typical when you get a minirosetta workunit that takes significantly more CPU time than predicted. I got one with a predicted time of 6 CPU hours; it actually took 19.5. What predicted length of workunits have you asked for, or have you left it as the default? If I remember correctly, the default has recently been raised to 6 CPU hours. I'd let it run a few more hours before doing anything.

ID: 57669 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5528
Credit: 5,543,488
RAC: 1,208
Message 57671 - Posted: 7 Dec 2008, 9:22:12 UTC
Last modified: 7 Dec 2008, 9:29:05 UTC

https://boinc.bakerlab.org/rosetta/result.php?resultid=211774333
1scjB_BOINC_ABRELAX_SPLIT_CONTROL_NOHATR_IGNORE_THE_REST-S25-9-S3-3--1scjB-_4846_1647_0
Outcome Client error
Client state Compute error
Exit status -1073741819 (0xc0000005)
CPU time 14839.63

this ran 4 out of 6 hrs and crashed. no credit. that suck big time.
I noticed this task has not been reassigned to anyone.

---------

same with this older task
ran for a good length of time and then crashed

https://boinc.bakerlab.org/rosetta/result.php?resultid=211601090
h014__BOINC_ABRELAX_RANGE_yebf_IGNORE_THE_REST-S25-10-S3-3--h014_-_4675_302_0
Outcome Client error
Client state Compute error
Exit status -1073741819 (0xc0000005)
CPU time 17704.41

--------

older still with same error code
https://boinc.bakerlab.org/rosetta/result.php?resultid=211595747
1louA_BOINC_ABRELAX_SPLIT_SPLIT2_NOHATR_IGNORE_THE_REST-S25-9-S3-3--1louA-_4845_1323_0
Outcome Client error
Client state Compute error
Exit status -1073741819 (0xc0000005)
CPU time 3769.953
ID: 57671 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5528
Credit: 5,543,488
RAC: 1,208
Message 57676 - Posted: 7 Dec 2008, 13:01:22 UTC

Task ID 211937560
Name cc_0_8_nocst4_homo_bench_foldcst_chunk_general_t362__olange_IGNORE_THE_REST_2GF6A_2_5176_11_0

this shows in the boinc manager as waiting to run while there is 1 rosetta and 1 einstein already running. the cpu time is running and when clicking on the graphics the graphics sequence is also running.

how is this possible? I have only 2 cores. (note as i am writing this note, it has switched to running and the einstein task has gone to waiting)
ID: 57676 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile gabberattack (johnny, eriq, segfault, r2k4, bully, sifon)

Send message
Joined: 27 Sep 05
Posts: 12
Credit: 5,984,531
RAC: 533
Message 57679 - Posted: 7 Dec 2008, 14:49:40 UTC - in response to Message 57669.  

iMac Intel Core2Duo 1,86 GHz, OSX 10.5.5, BOINC 5.10.45, CPU use limited to 75%.

This WU https://boinc.bakerlab.org/rosetta/result.php?resultid=211924207 and this one https://boinc.bakerlab.org/rosetta/result.php?resultid=211927271 are running for 18 and 25 hours already using Minirosetta 1.40. Should I reset the project or let it run ? Progress is frozen at 99.079% and 99.353%, remaining time shows on both WU 9 minutes 56 seconds.


That type of apparantly frozen progress is typical when you get a minirosetta workunit that takes significantly more CPU time than predicted. I got one with a predicted time of 6 CPU hours; it actually took 19.5. What predicted length of workunits have you asked for, or have you left it as the default? If I remember correctly, the default has recently been raised to 6 CPU hours. I'd let it run a few more hours before doing anything.



Update: - now the WUs show 22 and 29,5 hours, progress is at 99.245 and 99.441 respectively, so it is progressing but very very slowly. Remaining time still shows 9:56 and 9:57 to completion, iMac seems to be instable a bit, sometimes does not respond for couple seconds, but I let it run and see how far can that get. I had not selected any predicted time or any graphics CPU time - so it should be at the lowest numbers (3 hours, 10% graphics).
ID: 57679 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile robertmiles

Send message
Joined: 16 Jun 08
Posts: 1193
Credit: 13,206,567
RAC: 721
Message 57692 - Posted: 8 Dec 2008, 0:54:33 UTC - in response to Message 57676.  

Task ID 211937560
Name cc_0_8_nocst4_homo_bench_foldcst_chunk_general_t362__olange_IGNORE_THE_REST_2GF6A_2_5176_11_0

this shows in the boinc manager as waiting to run while there is 1 rosetta and 1 einstein already running. the cpu time is running and when clicking on the graphics the graphics sequence is also running.

how is this possible? I have only 2 cores. (note as i am writing this note, it has switched to running and the einstein task has gone to waiting)


Minirosetta 1.40 sometimes fails to suspend when it comes time for it to yield a timeslice to some other project, and then ends up sharing that CPU core with the other project during the next timeslice and only getting half of the CPU time it thinks it is getting. Expect the einstein workunit to have only gotten half the CPU time it thinks it got during that timeslice also. You can hope to get some minirosetta 1.45 workunits soon, which are more likely to be problem-free.
ID: 57692 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile robertmiles

Send message
Joined: 16 Jun 08
Posts: 1193
Credit: 13,206,567
RAC: 721
Message 57693 - Posted: 8 Dec 2008, 1:19:52 UTC - in response to Message 57679.  

iMac Intel Core2Duo 1,86 GHz, OSX 10.5.5, BOINC 5.10.45, CPU use limited to 75%.

This WU https://boinc.bakerlab.org/rosetta/result.php?resultid=211924207 and this one https://boinc.bakerlab.org/rosetta/result.php?resultid=211927271 are running for 18 and 25 hours already using Minirosetta 1.40. Should I reset the project or let it run ? Progress is frozen at 99.079% and 99.353%, remaining time shows on both WU 9 minutes 56 seconds.


That type of apparantly frozen progress is typical when you get a minirosetta workunit that takes significantly more CPU time than predicted. I got one with a predicted time of 6 CPU hours; it actually took 19.5. What predicted length of workunits have you asked for, or have you left it as the default? If I remember correctly, the default has recently been raised to 6 CPU hours. I'd let it run a few more hours before doing anything.



Update: - now the WUs show 22 and 29,5 hours, progress is at 99.245 and 99.441 respectively, so it is progressing but very very slowly. Remaining time still shows 9:56 and 9:57 to completion, iMac seems to be instable a bit, sometimes does not respond for couple seconds, but I let it run and see how far can that get. I had not selected any predicted time or any graphics CPU time - so it should be at the lowest numbers (3 hours, 10% graphics).


Since you have not selected any predicted time, it should the the default instead. You still have the option of selecting 3 hours instead, if that is what you prefer.

I'd let the workunits run for about 5 times the selection of the predicted time when you got those workunits, to see if the automatic cutoff of workunits that take too long is able to work for those workunits. For you, that should be about 30 hours CPU time, but even more wall clock time. I'd then abort them, after making sure that I had reported which workunits this happened to.

Under Vista SP1, I had enough free disk space that I was able to improve performance by telling BOINC that it could use more disk space and a higher percentage of the swap space. I have no idea whether that will work under iMac also. Months ago, I was able to improve performance to adding more RAM memory to my computer, but I'm now at the limit this model of computer can handle. Also, note that on machines with a 32-bit operating system, such as most of those sold with less that 4 GB of RAM memory already installed, 4 GB or less is the limit of what you can use even if more is installed; you need to switch to a 64-bit operating system to get beyond that limit. Most computers sold these days have the capability to switch to a 64-bit operating system, but do not come with one already.
ID: 57693 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile gabberattack (johnny, eriq, segfault, r2k4, bully, sifon)

Send message
Joined: 27 Sep 05
Posts: 12
Credit: 5,984,531
RAC: 533
Message 57694 - Posted: 8 Dec 2008, 2:23:15 UTC - in response to Message 57693.  

iMac Intel Core2Duo 1,86 GHz, OSX 10.5.5, BOINC 5.10.45, CPU use limited to 75%.

This WU https://boinc.bakerlab.org/rosetta/result.php?resultid=211924207 and this one https://boinc.bakerlab.org/rosetta/result.php?resultid=211927271 are running for 18 and 25 hours already using Minirosetta 1.40. Should I reset the project or let it run ? Progress is frozen at 99.079% and 99.353%, remaining time shows on both WU 9 minutes 56 seconds.


That type of apparantly frozen progress is typical when you get a minirosetta workunit that takes significantly more CPU time than predicted. I got one with a predicted time of 6 CPU hours; it actually took 19.5. What predicted length of workunits have you asked for, or have you left it as the default? If I remember correctly, the default has recently been raised to 6 CPU hours. I'd let it run a few more hours before doing anything.



Update: - now the WUs show 22 and 29,5 hours, progress is at 99.245 and 99.441 respectively, so it is progressing but very very slowly. Remaining time still shows 9:56 and 9:57 to completion, iMac seems to be instable a bit, sometimes does not respond for couple seconds, but I let it run and see how far can that get. I had not selected any predicted time or any graphics CPU time - so it should be at the lowest numbers (3 hours, 10% graphics).


Since you have not selected any predicted time, it should the the default instead. You still have the option of selecting 3 hours instead, if that is what you prefer.

I'd let the workunits run for about 5 times the selection of the predicted time when you got those workunits, to see if the automatic cutoff of workunits that take too long is able to work for those workunits. For you, that should be about 30 hours CPU time, but even more wall clock time. I'd then abort them, after making sure that I had reported which workunits this happened to.

Under Vista SP1, I had enough free disk space that I was able to improve performance by telling BOINC that it could use more disk space and a higher percentage of the swap space. I have no idea whether that will work under iMac also. Months ago, I was able to improve performance to adding more RAM memory to my computer, but I'm now at the limit this model of computer can handle. Also, note that on machines with a 32-bit operating system, such as most of those sold with less that 4 GB of RAM memory already installed, 4 GB or less is the limit of what you can use even if more is installed; you need to switch to a 64-bit operating system to get beyond that limit. Most computers sold these days have the capability to switch to a 64-bit operating system, but do not come with one already.


OK, so both tasks finished successfully - 25 hrs and 33 hrs. I changed CPU load to 100% to speed up the process. Manager is asking 438 and 332 credits, they are pending so far. I will allow more swap space and see if it helps. I have 1 GB now, but I'll change to 2 GB, because I see MiniRosetta is using 865 MB virtual memory for each WU, so it is almost 2GB together. Thanks for help, I appreciate a lot.
ID: 57694 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile gabberattack (johnny, eriq, segfault, r2k4, bully, sifon)

Send message
Joined: 27 Sep 05
Posts: 12
Credit: 5,984,531
RAC: 533
Message 57695 - Posted: 8 Dec 2008, 4:00:50 UTC - in response to Message 57694.  

iMac Intel Core2Duo 1,86 GHz, OSX 10.5.5, BOINC 5.10.45, CPU use limited to 75%.

This WU https://boinc.bakerlab.org/rosetta/result.php?resultid=211924207 and this one https://boinc.bakerlab.org/rosetta/result.php?resultid=211927271 are running for 18 and 25 hours already using Minirosetta 1.40. Should I reset the project or let it run ? Progress is frozen at 99.079% and 99.353%, remaining time shows on both WU 9 minutes 56 seconds.


That type of apparantly frozen progress is typical when you get a minirosetta workunit that takes significantly more CPU time than predicted. I got one with a predicted time of 6 CPU hours; it actually took 19.5. What predicted length of workunits have you asked for, or have you left it as the default? If I remember correctly, the default has recently been raised to 6 CPU hours. I'd let it run a few more hours before doing anything.



Update: - now the WUs show 22 and 29,5 hours, progress is at 99.245 and 99.441 respectively, so it is progressing but very very slowly. Remaining time still shows 9:56 and 9:57 to completion, iMac seems to be instable a bit, sometimes does not respond for couple seconds, but I let it run and see how far can that get. I had not selected any predicted time or any graphics CPU time - so it should be at the lowest numbers (3 hours, 10% graphics).


Since you have not selected any predicted time, it should the the default instead. You still have the option of selecting 3 hours instead, if that is what you prefer.

I'd let the workunits run for about 5 times the selection of the predicted time when you got those workunits, to see if the automatic cutoff of workunits that take too long is able to work for those workunits. For you, that should be about 30 hours CPU time, but even more wall clock time. I'd then abort them, after making sure that I had reported which workunits this happened to.

Under Vista SP1, I had enough free disk space that I was able to improve performance by telling BOINC that it could use more disk space and a higher percentage of the swap space. I have no idea whether that will work under iMac also. Months ago, I was able to improve performance to adding more RAM memory to my computer, but I'm now at the limit this model of computer can handle. Also, note that on machines with a 32-bit operating system, such as most of those sold with less that 4 GB of RAM memory already installed, 4 GB or less is the limit of what you can use even if more is installed; you need to switch to a 64-bit operating system to get beyond that limit. Most computers sold these days have the capability to switch to a 64-bit operating system, but do not come with one already.


OK, so both tasks finished successfully - 25 hrs and 33 hrs. I changed CPU load to 100% to speed up the process. Manager is asking 438 and 332 credits, they are pending so far. I will allow more swap space and see if it helps. I have 1 GB now, but I'll change to 2 GB, because I see MiniRosetta is using 865 MB virtual memory for each WU, so it is almost 2GB together. Thanks for help, I appreciate a lot.

OK, both WUs got granted credit - first one 26.66, second one 10.43 - the time was not worth the credit - next time I will abort if any WU goes over 5 hours.
ID: 57695 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile robertmiles

Send message
Joined: 16 Jun 08
Posts: 1193
Credit: 13,206,567
RAC: 721
Message 57698 - Posted: 8 Dec 2008, 4:48:06 UTC - in response to Message 57694.  

Under Vista SP1, I had enough free disk space that I was able to improve performance by telling BOINC that it could use more disk space and a higher percentage of the swap space. I have no idea whether that will work under iMac also. Months ago, I was able to improve performance to adding more RAM memory to my computer, but I'm now at the limit this model of computer can handle. Also, note that on machines with a 32-bit operating system, such as most of those sold with less that 4 GB of RAM memory already installed, 4 GB or less is the limit of what you can use even if more is installed; you need to switch to a 64-bit operating system to get beyond that limit. Most computers sold these days have the capability to switch to a 64-bit operating system, but do not come with one already.


OK, so both tasks finished successfully - 25 hrs and 33 hrs. I changed CPU load to 100% to speed up the process. Manager is asking 438 and 332 credits, they are pending so far. I will allow more swap space and see if it helps. I have 1 GB now, but I'll change to 2 GB, because I see MiniRosetta is using 865 MB virtual memory for each WU, so it is almost 2GB together. Thanks for help, I appreciate a lot.


If that helps, but not enough, you may also want to try something more than 2 GB multiplied by number of BOINC projects you are participating in for the swap space but not the RAM memory, like I did, in case BOINC is dividing the available swap space equally among the projects before deciding how much to allocate to each workunit.
ID: 57698 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5528
Credit: 5,543,488
RAC: 1,208
Message 57711 - Posted: 8 Dec 2008, 20:57:11 UTC
Last modified: 8 Dec 2008, 21:02:46 UTC

https://boinc.bakerlab.org/rosetta/result.php?resultid=212000802
cc_2_2_nocst4_homo_bench_foldcst_chunk_general_t332__olange_IGNORE_THE_REST_1ZJRA_12_5312_16_0

died after 3000+ secs and was sent out again.


also earlier this one died at 14839 seconds
https://boinc.bakerlab.org/rosetta/result.php?resultid=211774333
1scjB_BOINC_ABRELAX_SPLIT_CONTROL_NOHATR_IGNORE_THE_REST-S25-9-S3-3--1scjB-_4846_1647_0

also sent out to a another person.

can someone tell me if these errors are a result of the task not liking my OC speed or what? funny thing is that 5 tasks were completed ok in between these errors. something odd is going on.
ID: 57711 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile gabberattack (johnny, eriq, segfault, r2k4, bully, sifon)

Send message
Joined: 27 Sep 05
Posts: 12
Credit: 5,984,531
RAC: 533
Message 57724 - Posted: 9 Dec 2008, 0:51:34 UTC - in response to Message 57698.  

Under Vista SP1, I had enough free disk space that I was able to improve performance by telling BOINC that it could use more disk space and a higher percentage of the swap space. I have no idea whether that will work under iMac also. Months ago, I was able to improve performance to adding more RAM memory to my computer, but I'm now at the limit this model of computer can handle. Also, note that on machines with a 32-bit operating system, such as most of those sold with less that 4 GB of RAM memory already installed, 4 GB or less is the limit of what you can use even if more is installed; you need to switch to a 64-bit operating system to get beyond that limit. Most computers sold these days have the capability to switch to a 64-bit operating system, but do not come with one already.


OK, so both tasks finished successfully - 25 hrs and 33 hrs. I changed CPU load to 100% to speed up the process. Manager is asking 438 and 332 credits, they are pending so far. I will allow more swap space and see if it helps. I have 1 GB now, but I'll change to 2 GB, because I see MiniRosetta is using 865 MB virtual memory for each WU, so it is almost 2GB together. Thanks for help, I appreciate a lot.


If that helps, but not enough, you may also want to try something more than 2 GB multiplied by number of BOINC projects you are participating in for the swap space but not the RAM memory, like I did, in case BOINC is dividing the available swap space equally among the projects before deciding how much to allocate to each workunit.


I have just Rosetta on my iMac. I set the disk space to 4 GB anyway. So far no strange WUs and all new WUs use Minirosetta 1.45 so I hope this should not be a problem anymore. Thanks for help.

ID: 57724 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Reaper

Send message
Joined: 12 Feb 06
Posts: 6
Credit: 364,880
RAC: 0
Message 57777 - Posted: 10 Dec 2008, 16:40:06 UTC

This one has been running for days and resetting every few minutes.
It is currently at 99.280% complete after just over 23 hours of CPU time.

I had restarted the system on the 7th and another project ran on it until 7:37AM on the 8th. I believe the progress was already at or near 99plus percent complete then as well.
While typing this up I noticed that the latest reset, reduced CPU time to less than 23 hours. I am aborting since I don't seem to be making any progress.
Sorry I didn't notice this sooner.

12/8/2008 7:37:24 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/8/2008 7:53:47 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/8/2008 8:10:54 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/8/2008 8:28:24 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140


... time passes with resets like below
12/10/2008 4:30:21 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/10/2008 4:46:42 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/10/2008 5:03:52 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/10/2008 5:34:01 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/10/2008 5:50:25 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/10/2008 6:07:49 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/10/2008 6:24:11 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/10/2008 6:52:30 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/10/2008 7:08:48 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/10/2008 7:25:21 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/10/2008 7:41:57 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140
12/10/2008 7:57:46 AM|rosetta@home|Restarting task cc_0_6_nocst4_homo_bench_foldcst_chunk_general_t317__olange_IGNORE_THE_REST_2ESBA_10_5137_6_0 using minirosetta version 140


ID: 57777 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Previous · 1 . . . 12 · 13 · 14 · 15

Message boards : Number crunching : Minirosetta v1.40 bug thread



©2022 University of Washington
https://www.bakerlab.org