Hello

The WU started and jumped on 100% the next second.
It keeps running and time increases normally.
____________

Hi,
I just get a WU 5.55: 1l2x__BOINC_INCREASE_CYCLES10_RNA_ABINITIO-1l2x_-_1868_11_0

It starts crunching with a % in Progress = 100%. But it continues to crunch.
The screen saver is normal except that the % is written : 1 then 00000000.... through the entire screen.

I don\'t mess about if a WU says 100% complete and CPU time increases. Sorry but as soon as I saw that I aborted both WUs - been caught by this sort of thing before and wasted a lot of cycles! It may have carried on to completion but I wasn\'t going to try to find out just in case!

http://ralph.bakerlab.org/workunit.php?wuid=416831
http://ralph.bakerlab.org/workunit.php?wuid=416907 refers
____________

Another usability issue, which may be simple to improve is at step 340,000, which apparently is a magic number in the processing. This is where you clear out the histogram of energy and RMSD. It then \"hangs\" for 15 seconds or so, (more like a minute I suppose on a slower machine) and then takes another 10 seconds or so to do the first step or two after that.

Any program that suddenly has portions of the screen blank out, and then shows no activity (unless of course you notice the CPU seconds counting up) for more then the attention span of the caffine-loaded viewer is immediately diagnosed as being \"hung\" and requiring manual intervention... (as if the 5 seconds you\'ve waited already wasn\'t enough for the program to trash your computer if it was going to).

...anyway, if you could just NOT blank out those graphs until you complete the initialization or whatever is happening there as step 340,000 chuggs, then it would be a sizable smidge less alarming in appearance. It would be even better if you could impose a few more \"steps\" in to that long processing of step 340,000.
____________

Hello

The WU started and jumped on 100% the next second.
It keeps running and time increases normally.

I am having the same thing happening. I will let the run for a couple of hours and then abort them if they have not completed.

Hopefully this will not be a waste of CPU time, just a simple programming error. Please post a message when this is fixed as I have stopped this project from recieving any more task.

My 5.55 WU has just finished...no error...points granted - I think there is no need to abort them.
____________

The WU mentioned above finished normally.

CPU time (sec) - claimed credit - granted credit
3,347.68 -------- 9.89 ------------- 7.60

____________

This one errored out on 5.55:

Resid 472582

1wrpA_BOINC_SYMM_FOLD_AND_DOCK-1wrpA-truncate__1873_21_1

ERROR:: Exit at: .\\fold_tree.cc line:809

I haven\'t been able to reproduce the Mac issue (process not found) noted on the R@H message boards yet. But I\'m hoping to find a fix for the next update

This task is Rosetta, but was wondering, I\'ve got 24hr run time preference... this bad boy has been crunching for 14hrs and isn\'t complete with model 3 yet. The % complete shows 42.1%.

Still seems to be crunching just fine, but was wondering, does this mean it\'s only taken 1 checkpoint during this third model? Or, is there any way from the graphic to tell when a checkpoint has been actually taken? It\'s on step 395,000, so it must have been crunching for several hours.
____________

Anders n, actually, wait, when did this start happening for you? Is there a discussion thread on this?

I haven\'t been able to reproduce the Mac issue (process not found) noted on the R@H message boards yet. But I\'m hoping to find a fix for the next update

How about the other MAC issue where Ralph/Rosetta hangs after beening preemted and then resumed.
I just checked my MAC and 1 WU on each project was hanging.

Anders n

Had these errors overnight on machines at work, so I didn\'t see what they did:

resultid=471512
resultid=472465

One\'s a -161, other\'s an \"incorrect function\". I\'ve got one running here right now that has the 100000000000000000000.... problem, resultid=471927, but it looks like it otherwise is operating normally, so I\'ll let it finish.

____________

Had this WU fail with MAXIMUM DISK SPACE EXCEEDED, I have many GigaBytes so this should not be the problem
http://ralph.bakerlab.org/result.php?resultid=471223

Also had these two fail with the old ERROR -161,
http://ralph.bakerlab.org/result.php?resultid=471479
http://ralph.bakerlab.org/result.php?resultid=471480

I currently have one running that may be a 5.55 or a 5.56 not sure, but it has jumped straight to 100% as some others have reported with the time to complete still going up but only 1 hour 40 minutes done on a 6 hour preferance. Windows machine.

Strangely I have two others that have switched and are \'Waiting to run\' but the Time to completion is still ticking over and also the percentage done is moving up, yet the CPU Time is not moving. I have a dual cpu dual core machine so 4 cores are running and they are all accounted for so Why is Boinc saying I have 6 cores doing something? Very strange. Linux machine.
____________

I have a workunit on my home laptop that\'s up to 203% completion right now.

Curiously enough, according to Boinc it says that Chess960 is running, but the only one accumulating % is RALPH.

Wow good eye! I haven\'t seen that hang, but your explanation makes sense. Let me see what we can do.

On the other issues -- my mac screensaver says that the percentage complete is \"inf%\". This sounds like the issues reported below, too with large percentage complete values. Dang!

I haven\'t been able to reproduce the Mac issue (process not found) noted on the R@H message boards yet. But I\'m hoping to find a fix for the next update.

Finally, one of our old style protein WUs is consistently failing, so I need to ask the other developer about that. Weird.

Thanks for all the posts so far! This kind of quick feedback helps tremendously!

Another usability issue, which may be simple to improve is at step 340,000, which apparently is a magic number in the processing. This is where you clear out the histogram of energy and RMSD. It then \"hangs\" for 15 seconds or so, (more like a minute I suppose on a slower machine) and then takes another 10 seconds or so to do the first step or two after that.

Any program that suddenly has portions of the screen blank out, and then shows no activity (unless of course you notice the CPU seconds counting up) for more then the attention span of the caffine-loaded viewer is immediately diagnosed as being \"hung\" and requiring manual intervention... (as if the 5 seconds you\'ve waited already wasn\'t enough for the program to trash your computer if it was going to).

...anyway, if you could just NOT blank out those graphs until you complete the initialization or whatever is happening there as step 340,000 chuggs, then it would be a sizable smidge less alarming in appearance. It would be even better if you could impose a few more \"steps\" in to that long processing of step 340,000.

Hello
The WU started and jumped on 100% the next second.
It keeps running and time increases normally.