Posts by Hermes

1) Message boards : Number crunching : Miscellaneous Work Unit Errors (Message 11243)
Posted 23 Feb 2006 by Hermes
WU 9531208 already failed twice.
2) Message boards : Number crunching : Warning: Don't shut down BOINC Manager..!! (Message 143)
Posted 18 Sep 2005 by Hermes
Does anyone know if this is a boinc client issue or something that can be coded into the application to make sure the cpu time does not reset? I really want to make sure people get appropriate credit for their cpu time.

It's an application issue, as this problem only occurs with rosetta but not with others like seti, einstein, mfold, sixtrack, hadsm, etc. I think something is missing in the boinc documentation as this is a problem mainly encountered by new projects.

I'm guessing the manager just displays the current cpu time since restart, but will report the total cpu time for the workunit. Does anyone know if this is correct?

I would argue no.
To remember the cpu time at the checkpoint it needs to be saved in the client_state.xml in the active_task section under checkpoint_cpu_time . This number stays at 0.000000 througout the complete work unit, so when the application ist restartet, the amount of cpu time spent so far is read as zero.

©2021 University of Washington