I have run a work unit for more than 3 hours and exited BOINC.
Why is the displayed CPU time only 1h 51m for the same work unit when I again launch BOINC?

---

Rosetta sets check points after each step of work. If you interrupt a step while it is being calculated Rosetta will recalculate that step from the beginning. How long the time between check points is depends largely on the nature of the protein calculated and the speed on your machine. The currenct CASP WUs are "real world" problems, so they are complex and may only have check points every hour or two.

Whenever you end the Rosetta program (either by BOINC scheduling another project and a preference that says "remove from memory YES", or by ending BOINC or by turning off your computer)... you will lose some processing time. It is just a question of how much you will lose. With these larger proteins, on average you will lose more time than smaller ones. It is the nature of the work being done. They have to balance the need for checkpoints against the time it takes to perform them. Because taking checkpoints is taking time away from crunching on the WU.

Welcome BACK to Rosetta!

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

Marc,

Rosetta, and all BOINC projects, report CPU time, the amount of time your computer has spent actually crunching a work unit. The computer also needs to do other things to keep itself running, so CPU time on a project will always be less than the amount of "wall clock" time between starting and stopping. The most crunching I've seen here is 99%, so what you said is inevitable. Other factors also reduce CPU time on the project; even moving the mouse requires some calculation by your CPU that doesn't go toward crunching a WU. So anything you do with the computer will cut into crunch time, even though the clock on the wall is still ticking. The projects run at a really low priority, so think of it as unused CPU cycles. Another variable: BOINC allows you to choose general preferences that will further reduce the amount of CPU time spent on the projects.

Regards,

Ardis

Yeah, I know this is a late response Timliness is a virtue with which I have not been inflicted.

---