ive jst started this project, use to do others

but are you caying that there isnt a set length of time for a save point. and there could be a 5 hour gap between a save point then thats stupid and should be like others with set times or set percentages. evon one you could set it to save its self every 3 mins for slow unrelyable pc's

I'm not sure its a trend, but from my post a bit up, i got again as has also been reported by others

This time i killed it 01:41 UTC on 7.20.06. This afternoon (7.19.06) i properly 'snoozed' this WU, properly closed the UD Agent by right-clicking and exit, so that i could boot...when it resumed it started off right when the initial docking was done about 20/25 minutes into the crunch, so lost there 5 hours, plus that it went around since from about 4.5 hours thru 12.5 hours clock time. The UD program dir still got a copy of that original crunch file of 29mb, if interested?

thx

Hi Lawrence,
can you confirm then, that cycling from 47.7 to 50.0% and back and up, eventually made your copy go past that 50.0 hurdle....but in 1 hour or so, and not the 8 hours my copy used or worse as has been advised on in posts here above? So how often should it try, as it takes about 20 minutes to do this 2.3% cycle on my machine.....dont see the line graph rescaling, just see retreating of the green line....the left hand initial descend of the curve remains static.......meantime its sodding evil, that also as reported by others, the WU returns to this post-init 0.0% state on proper pausing/closing.....should come with a 'do-not-interrupt...only good for 24/7 zero boot machines" warning.

Wikkel reported 4 hours before passing the 50.0 hurdle, so what's the maximum wait....science cant be pushed, but how often does one inject the patient before it dies? It's curious its on UD agent.....never observed on BOINC. UD crediting in clock time, irrespective however long it was 'allowed' to run with accumulated checkpoints....seemingly not stored on this particular hefty batch.

because of having practally no save points ive lost over 10 hours of work. i cant see why they dont just put check points in like every other one like this i have done. most people have over 10 gbs of hdd space so space isnt a factor. it realy anoys me to think that all my work is wasted andalmost make me want to look for an other project.

advice make check points every 15 mins so not alot of work is wasted.

Yes, this is an unusual workunit. I myself received it last night and watched it oscillate for a while. The docking eventually completed and continued on to the next docking. There is nothing wrong with the workunit other than it's very difficult. But that's the whole point of the grid: to use this power to solve the difficult problems. Not everything is simple and predictable.

The oscillation of the percent is explained by the fact that we make a guess as to how long a docking will take. If the docking is not finished as predicted, we recalculate the docking length..and so on. Every recalculation causes the percent to drop a little bit until it passes (which it will eventually). The opposite is also true: many times a docking finishes before the estimate and the percent jumps up....but you don't hear people complaining about that

It's good to be vigilant for strange behavior, but people also need to be a bit more patient.