Ron, I'd say your results speak for themselves. The only ones that have any sign of error, are the ones that were aborted by user.

Anders n is correct, the only thing that's really changed here is that the progress % completed is updated more frequently. It used to only update at the end of each model. Now it updates every 5 seconds. And with that new change there is a new quirk, that being that upon a full restart of a task (i.e. it was removed from memory), the % complete will start at zero, even though many hours of work may be retained in the task already. These will still finish at the normal time. It is simply the indication of how far along we are in the task that is incorrect.

...and yes, I've been saying many many times in threads throughout the boards that the checkpointing is the next big thing (from a user's point of view) that we will see in the next Rosetta release.

Hi Ron

If you check your Wu when it has restarted does the CPU-time reset to 0?

And if you check the grafics what model does it start at?

Anders n

Yes this is correct. Can you provide a link to the result?

This? http://boinc.bakerlab.org/rosetta/result.php?resultid=11875393

I have had this happen a number of times on my computer. I find that instead of aborting, just close BOINC itself out. Wait a minute and then restart. Everytime I have done this my workunit went on to complete succesfully.

ciao.......:)

Yes this is correct. Can you provide a link to the result?

If there is no 'stepping' on the graphic display then it is stuck.......kill!

Well?

Sorry, I am not here 24/7. Yea let it run, but check the grafic display and make sure it is doing steps. If not then you might have a problem.

That type of WU will run longer than you time setting, I would estimate that it might run 9 - 10 hours based on your time setting and the type of WU. But I am only gussing as to which one you are talking about. I think I found the right system, but it has two WUs running, and I assume it it the oldest of the two.

a) go to your Account Prefs page and Change the ROSETTA prefs....

And change which?

I think it is:

Target CPU run time
(not selected defaults to 8 hours)

This Question is in the Rosetta FAQ list

a) go to your Account Prefs page and Change the ROSETTA prefs....

Resource share
If you participate in multiple BOINC projects, this is the proportion of your resources used by Rosetta@home	10
Percentage of CPU time used for graphics	not selected
Number of frames per second for graphics	not selected
Target CPU run time	not selected
Miscellaneous
Should Rosetta@home send you email newsletters?	yes
Should Rosetta@home show your computers on its web site?	yes
Default computer location	home

Ron... keep an eye on Boinc Downloads, refresh it every hour today (use CTRL+F5 or SHIFT+F5). A new version of Boinc is about to be released today.

This new version will work with RAH. This new version will fix a lot of problems you have today. You will need to uninstall your present version to install the new one. Everyone will need to do this.

Ron, I am running Boinc 5.2.1
You will get 5.2.2 or 5.2.3 later on today.

The good day is here. Just keep an eye on it. It will fix a lot of things.

(@David: I hope you see the changes before you try to find fixes for your problems where there are none ;))

Didn't work. Still crashed on a pause. How did such buggy code get released?

Perhaps because the test beds were set up to never remove from memory. Perhaps because with 200 machines to monitor, the fact that one or two machines died over a work unit was missed. Perhaps because like many things the project is on a low budget, have few people on staff, and there is lots to do.

I try to work on the Wiki every day, for as long as I can. As many hours as I put in, there are still hundreds, if not thousands of errors. As a former developer I can tell you that no matter how rigerous the testing regime, the software will always fail in the field.

Lastly, though perfection is fail free operation is desired. The BOINC System is designed to be robust in the presence of error. Note, that this does not mean your personal experience will be without problem. But, the scientific results are protected. As in the cases we see here. Your result failed, someone elses will succeed, the project moves on.

I am not saying that they don't want to fix this, and "knowing" the project people as I do (yes, I do have a little more "access" than many people, but it is not THAT much more), all project members on all projects take all problems seriously. But, there are only so many hours in a day...

Last point, I know that I have similar problems to what the projects do, too much to do, and not enough Paul. So, the thought is hostile. They really do care. But, none of us is well served with comments like these. Yes, worse examples abound, but, it starts small, like this, and it is not fair to those that do work so hard. To sum it up, we all are working on it. Please be kind ...

May I ask how you set it? Did you just go to your preferences webpage here and set the option to leave the application in memory? Or did you also Update RAH through Boinc Manager afterwards?

The memory usage will not go up much. When switching between work units, if you have the option to leave them in memory set on, BOINC will write the units to your page file (swap file, virtual memory). Only a very small part is being kept active in the RAM, less even than the Windows Task Manager shows!

you can avoid this error (beside when it is disturbed by benchmark) with setting your preferences to "leave app in memory" until science app 4.77 is replaced with a newer one. note though that this will inc rease your memmory usage