Idea for more accurate progress meter

Questions and Answers : Wish list : Idea for more accurate progress meter

To post messages, you must log in.

AuthorMessage
Jesse Viviano

Send message
Joined: 14 Jan 10
Posts: 42
Credit: 2,481,359
RAC: 4,083
Message 76391 - Posted: 31 Jan 2014, 21:27:51 UTC

I have noticed that the progress meter becomes wildly inaccurate when Rosetta@home processes work units that cause it to shut down early because it has created enough decoys (typically 99) to force it to terminate early rather than create too many decoys for the server. I believe that a more accurate progress meter would be generated if the progress was defined as the maximum of the original CPU time-based progress meter or the number that is generated by dividing the number of decoys completed by the number of decoys allowed before an early shutdown is triggered.
ID: 76391 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Jesse Viviano

Send message
Joined: 14 Jan 10
Posts: 42
Credit: 2,481,359
RAC: 4,083
Message 76393 - Posted: 2 Feb 2014, 5:52:00 UTC

Oops, I forgot that I posted this idea over three years ago.
ID: 76393 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Questions and Answers : Wish list : Idea for more accurate progress meter



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