The minirosetta application has been updated to 3.50. This version includes improvements to the score function and protocols amended for distributed computing which include docking and optimized forward folding.

With this update, we may no longer support 32-bit Mac OSX platforms due to compiler issues with Rosetta. However, we will try our best to resolve these issues, if possible.

Please post problems related to this update here.

A unit now takes much longer for not a proportionate credit. May take over 20 hours each as opposed to 3 hours or even less time. I liked the previous units better.

Looks like the credit given for these longer 24 hour+ units is given in proportion. However, a heads up before sending them out would have been helpful. Just to alert us that these are expected to take much longer to complete.

Hi Miklos,M,

I believe the normal way of working is for Rosetta to keep calculating new decoys until you have reached your preferred run time and then stop at the next completed decoy. In cases where the final decoy is taking an extremely long time to complete, the watchdog should step in and terminate the task.

A 20 hour task based on a 3 hour preferred run time sounds very strange.

Can you post a link to the results page for the affected task(s) (or just the task ID)? That will help the project scientists to investigate the problem.

The minirosetta application has been updated to 3.50. This version includes improvements to the score function and protocols amended for distributed computing which include docking and optimized forward folding.

With this update, we may no longer support 32-bit Mac OSX platforms due to compiler issues with Rosetta. However, we will try our best to resolve these issues, if possible.

Please post problems related to this update here.

A unit now takes much longer for not a proportionate credit. May take over 20 hours each as opposed to 3 hours or even less time. I liked the previous units better.

Looks like the credit given for these longer 24 hour+ units is given in proportion. However, a heads up before sending them out would have been helpful. Just to alert us that these are expected to take much longer to complete.

Hi Miklos,M,

I believe the normal way of working is for Rosetta to keep calculating new decoys until you have reached your preferred run time and then stop at the next completed decoy. In cases where the final decoy is taking an extremely long time to complete, the watchdog should step in and terminate the task.

A 20 hour task based on a 3 hour preferred run time sounds very strange.

Can you post a link to the results page for the affected task(s) (or just the task ID)? That will help the project scientists to investigate the problem.

662522208 601098858 21 May 2014 2:16:13 UTC 23 May 2014 19:45:50 UTC Over Success Done 84,811.41 511.02 617.13

Hi Miklos,M

I just had a look at 2 of your rigs the i7-4960X and FX-8150 they both have

# cpu_run_time_pref: 86400 seconds you selected which is about 24hrs run time, so what's the problem?

If the W.U. can finish faster then your selected run time for some reason like hitting (99)decoys they will but otherwise they will run the full length of time.

---

Hi Miklos,M

I just had a look at 2 of your rigs the i7-4960X and FX-8150 they both have

# cpu_run_time_pref: 86400 seconds you selected which is about 24hrs run time, so what's the problem?

If the W.U. can finish faster then your selected run time for some reason like hitting (99) they will but otherwise they will run the full length of time.

5/24/2014 8:30:46 PM | rosetta@home | Computation for task syil2dnd2v4_2_fold_SAVE_ALL_OUT_166165_580_0 finished
5/24/2014 8:30:46 PM | rosetta@home | Starting task rb_05_22_48582_94175_ab_stage0_t000___robetta_cstwt_3.0_IGNORE_THE_REST_03_09_166190_90_0
5/24/2014 8:30:50 PM | rosetta@home | Started upload of syil2dnd2v4_2_fold_SAVE_ALL_OUT_166165_580_0_0
5/24/2014 8:30:55 PM | rosetta@home | Finished upload of syil2dnd2v4_2_fold_SAVE_ALL_OUT_166165_580_0_0

Hi Miklos,M

I just had a look at 2 of your rigs the i7-4960X and FX-8150 they both have

# cpu_run_time_pref: 86400 seconds you selected which is about 24hrs run time, so what's the problem?

If the W.U. can finish faster then your selected run time for some reason like hitting (99)decoys they will but otherwise they will run the full length of time.

Would that explain why my computers suddenly take over a day to work one unit, when in the past it used to be about 3 hours and I see many others are still taking about 3 hours with their work units? How do I change I back, if I chose to do so?

Thanks.

When you have several host computers, you can organize them by "venue". There is a setting on R@h for Target CPU run time. The default value is 3hrs, the maximum is 24hrs. This value can be set for each venue. This is done here on the website. Click the "Participants" link at the top, then click on the Rosetta@home preferences.

---

Rosetta Moderator: Mod.Sense

When you have several host computers, you can organize them by "venue". There is a setting on R@h for Target CPU run time. The default value is 3hrs, the maximum is 24hrs. This value can be set for each venue. This is done here on the website. Click the "Participants" link at the top, then click on the Rosetta@home preferences.

Thank you. gave it a try at 4 hours.

The minirosetta application has been updated to 3.50. This version includes improvements to the score function and protocols amended for distributed computing which include docking and optimized forward folding.

With this update, we may no longer support 32-bit Mac OSX platforms due to compiler issues with Rosetta. However, we will try our best to resolve these issues, if possible.

Please post problems related to this update here.

My huge apologies. The mistake was on my end as I just found out. Somehow I set it on "one day", as opposed to the default of 3 hours where it was for a long time.