Posts by DizzyD

1) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 101270)
Posted 13 Apr 2021 by DizzyD
Post:
/edit. Just to add a datapoint. While it's not conclusive, all the Miniprotein_relax8 units I'm getting that run long do "complete" and show as valid, even after going 10 hours over. Of these units that run over, many are "seconds" sent to me from other machines that failed to process the WU. My machine is running OSX and completes them fine (beyond running 10hrs over). All the failed machines are windows or linux based. That said, I know Macs make up a small percentage of computers on this project, so I might have just not gotten a resend from a Mac in my small sample.

I am also running on a Mac. The mini protein_relax8 units also do complete after ~18.7 hours and provide credit; however, the credit is in the "two-hundred" range for 67,000+ seconds of work. So, I've gone in and aborted all of the "ready to start" mini protein_relax8 units and now I have all pre-helical-bundles_round1_attempt1 queued up.
2) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 101240)
Posted 11 Apr 2021 by DizzyD
Post:
I've noticed than some of the latest Tasks aren't checkpointing properly, so if you interrupt them they will revert back to the last successful checkpoint.
Next time, just let it run- the default time is 8 hours, and there is a 10 hour watchdog timer in case it's not done within 8 hours. If it's still going after 20hours, then you might want to kill it off.


Grant, thank you for your reply. I don't quite understand your "20 hours" comment. I let the task run for 16 hours. If there is a watchdog timer at 10 hours, what is the different between anything over 10 hours (e.g. 11 hours, 16 hours and 20 hours) not completing? Isn't it just stuck at that point?
3) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 101217)
Posted 10 Apr 2021 by DizzyD
Post:
It sometimes helps to shut down BOINC, then restart BOINC and then the task.

Progress seeming to freeze near the end of a task is often a sign that the task was created with a severe underestimate of how long the task would run.


OK, thank you. I just tried that (rebooted in between as well), and it reset to ~16% complete... Maybe I just kill it if it's going to run forever?
4) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 101215)
Posted 10 Apr 2021 by DizzyD
Post:
I just suspended a task that has been running for 16:19:35 (stuck at 00:10:15 remaining). Any ideas how to get this one to finish and get credit for it?
5) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 101111)
Posted 7 Apr 2021 by DizzyD
Post:


But, of course, during this holiday period people here expect to demand the creation and issue of sufficient work to serve at least a third of a million tasks per day to the world at large, with no respite.
And the amazing thing is, a fair few do seem to have come down. Maybe my caches aren't quite completely full, but near enough.



Maybe we are all just waiting for the resurrection of this project? Isn't that what Easter is all about?
6) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 101023)
Posted 3 Apr 2021 by DizzyD
Post:
Who is the guilty party submitting tasks that all "Error while computing"? I have 70 tasks on April 4th that have errored with no credit. My stats have dropped over 10% in the past day.






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