Questions and Answers : Wish list : 3 days is too short a deadline
Author | Message |
---|---|
sberk Send message Joined: 6 Jul 18 Posts: 1 Credit: 193,653 RAC: 0 |
I am running 4 projects. 3 days for any type of Rosetta WU, ESPECIALLY the ones that can run 24 hours, does not help making all project timelines. Can you make it 5 days or 7? |
Sid Celery Send message Joined: 11 Feb 08 Posts: 2122 Credit: 41,184,314 RAC: 9,365 |
I am running 4 projects. 3 days for any type of Rosetta WU, ESPECIALLY the ones that can run 24 hours, does not help making all project timelines. Can you make it 5 days or 7? In the absence of a response from the Project team, my memory of this subject when it was raised before is that 3 days is the maximum they can afford for this range of tasks - maybe even a little too long! The deadline used to be much shorter and they compromised as much as they could. But it's a fair question if you're struggling to make deadlines across several projects. But you can still do something about this if you can slightly reduce your buffer of tasks. Whatever you can reduce will slightly affect the number of tasks you hold andor slightly delay the refilling of your buffer so your start (and end times) give you more room to manoeuvre. Under the OptionsComputing Preferences menu option, on the computing tab, what do you have for "Store at least x.x days of work" and "Store up to an additional x.x days of work"? If you have tasks that run up to 24hrs the total of these fields has to be less than 2.0 days if there are potential 3 day deadlines. I'm currently using 0.1 and 1.4 days and it seems to be a balance that works for me. |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
R@h supports a user preference for the work unit runtime. The default is now 6hrs. I'd suggest that a shorter runtime preference might be a better for a host with several other projects. Rosetta Moderator: Mod.Sense |
Sid Celery Send message Joined: 11 Feb 08 Posts: 2122 Credit: 41,184,314 RAC: 9,365 |
R@h supports a user preference for the work unit runtime. The default is now 6hrs. I'd suggest that a shorter runtime preference might be a better for a host with several other projects. While true, reducing the runtime might mean, say, instead of 3 8hr tasks you end up with 4 6hr tasks and I'm not sure how well that would solve potentially missing deadlines - it might even make things worse. I'm still more inclined to reducing an excessive buffer for a solution. May be worth experimenting with both |
Questions and Answers :
Wish list :
3 days is too short a deadline
©2024 University of Washington
https://www.bakerlab.org