Message boards : Number crunching : Problems and Technical Issues with Rosetta@home
Previous · 1 . . . 343 · 344 · 345 · 346
Author | Message |
---|---|
Sid Celery Send message Joined: 11 Feb 08 Posts: 2414 Credit: 46,260,948 RAC: 28,743 ![]() |
...bumping runtimes further to 12hrs will quadruple your credits compared to that of the faulty default settingNot wanting to mislead anyone, I wrote that wrong Credits per Rosetta Beta v6.06 task will quadruple. Credits per hour of CPU runtime will be about the same. Point being, Rosetta Beta v6.06 tasks set to a target time of: - Not selected: runs for 3hrs and you get 3hrs worth of credit - even though Boinc initially says they'll run for 8hrs - 8 hours: runs for 8hrs and you get 8hrs worth of credit - 12 hours: runs for 12hrs and you get 12hrs worth of credit - even though Boinc initially says they'll run for 8hrs This doesn't apply to Rosetta v4.20 tasks you may occasionally see, where: - Not selected: runs for 8hrs and you get 8hrs worth of credit 8hrs is the ideal as you get the intended Rosetta default runtime and credit (instead of falling short every time), doesn't 'waste' our limited remaining queue of tasks and doesn't screw up Boinc's task scheduling. 12hrs (or 10hrs) is an option to get you more credits per task <if you're meeting deadlines comfortably> without messing up Boinc's scheduling too much and further extends how long our limited queue of tasks lasts for. ![]() ![]() |
Message boards :
Number crunching :
Problems and Technical Issues with Rosetta@home
©2025 University of Washington
https://www.bakerlab.org