I've resumed cosmology@home 2 times and both it lost the work done before.
First time work done at 16%, second time done at 21%.

Thank you.

I've resumed cosmology@home 2 times and both it lost the work done before.
First time work done at 16%, second time done at 21%.

Thank you.

Luke, as far as I can tell these WUs are resuming from a checkpoint. Scott is currently working on a problem where the WU is not talking properly to BOINC. This means that when you resume the CPU time recorded by BOINC resets to zero and the progress can also appear to drop back. Dave.

My computers work on many projects and change projects every 2.5 hours. I too have had this problem. I worked on one C@H workunit for over 2.5 hours and it got to 46% completed before pausing. When it restarted, the progress and time went back to Zero (0). This workunit will never get done at this rate. What is being done to fix this. Remember, it never happened previously. Thanks.

My computers work on many projects and change projects every 2.5 hours. I too have had this problem. I worked on one C@H workunit for over 2.5 hours and it got to 46% completed before pausing. When it restarted, the progress and time went back to Zero (0). This workunit will never get done at this rate. What is being done to fix this. Remember, it never happened previously. Thanks.

This should be only an appearance and not an actuality....in other words it does pickup where it left off but doesn't appear to...no work lost. It is a bug left over from the wrapper in the 1.xx clients...a known bug... and will be resolved soon.

---

My computers work on many projects and change projects every 2.5 hours. I too have had this problem. I worked on one C@H workunit for over 2.5 hours and it got to 46% completed before pausing. When it restarted, the progress and time went back to Zero (0). This workunit will never get done at this rate. What is being done to fix this. Remember, it never happened previously. Thanks.

This should be only an appearance and not an actuality....in other words it does pickup where it left off but doesn't appear to...no work lost. It is a bug left over from the wrapper in the 1.xx clients...a known bug... and will be resolved soon.

This is correct. I'm working on it now.

---

Scott Kruger
Project Administrator, Cosmology@Home

My computers work on many projects and change projects every 2.5 hours. I too have had this problem. I worked on one C@H workunit for over 2.5 hours and it got to 46% completed before pausing. When it restarted, the progress and time went back to Zero (0). This workunit will never get done at this rate. What is being done to fix this. Remember, it never happened previously. Thanks.

This should be only an appearance and not an actuality....in other words it does pickup where it left off but doesn\'t appear to...no work lost. It is a bug left over from the wrapper in the 1.xx clients...a known bug... and will be resolved soon.

This is correct. I\'m working on it now.

What is the status of this situation? While it won\'t hurt projects outside of your own, it will impact the ability of systems to retrieve work from your project. Why? RDCF is increased by the amount of the miss in the event of an underestimate, but only gradually reduced in the event of overestimates. While I\'m new to this project and haven\'t seen this in action, I would speculate that BOINC then thinks that the \"To Completion\" is at the full amount of the benchmark * RDCF value after a \"reset to zero progress\" happened. When the result completes, RDCF will be erroneously reduced based on the artificially low completion time. The next result to be processed will then likely artificially \"underestimate\" and thus the RDCF will be increased by the percentage of the miss.

If I\'m making more out of this than there is to make, meaning that the fluctuations in runtime wreak havoc on the RDCF anyway and/or this is not a big deal and/or the completion estimate remains intact, then I\'m sure someone will come along and correct me... ;)

Brian

---

Brian, if you select \"leave applications in memory while suspended\" then I find that the CPU time resumes normally after a suspend. Dave.

Brian, if you select \"leave applications in memory while suspended\" then I find that the CPU time resumes normally after a suspend. Dave.

Yep, I am using that option, too. But it doesn\'t help with system freezes and/or when you have to reboot yor box. ;-)
Also it might be a problem to have Cosmo WUs left in memory because the app is using quite a lot of RAM. On multicore systems or on systems with lesser RAM it could be bad for performance. *grin*

---

Lovely greetings, Cori

Hi folks,

Just a quick clarification for a cosmo nOOb! The current wu crunching was at 60+% after 5hrs and I had to reboot, so I exited BOINC and rebooted. On restarting the progress has decreased to 15%...ouch! Is this to be expected as \"normal\" for this project? I don\'t mind \"too much\" loosing a few % but this is too much.

Live long and bOINC!

Paul.

It\'s normal to show less % after Re-Booting but the Wu will still finish in it\'s normal amount of time irregardless of the % showing , so you really haven\'t lost anything & will get full Credit for it ... :)

It\'s normal to show less % after Re-Booting but the Wu will still finish in it\'s normal amount of time irregardless of the % showing , so you really haven\'t lost anything & will get full Credit for it ... :)

Thanks. And it did. :) It completed after 6hr45min.

Welcome to the fold, Paul. Its good to see other fruitcakes here. :-)

---

Hi all.

My first W.U. finished in under 2hrs, the second was running last night

when i shut the puter down for the night. This morning when it restarted

it was at 2hrs 8min at 52% after a couple of minutes it has gone back

to 0.700% and going back up slowly. ;)

pete.

---

Win98se, P4 2.8e (Prescott)1gig Ram + Nvidia 128mb agp 8x card.
Win98se, P4 3.0e (Prescott)1gig Ram + ATI 128mb agp 8x card.
BOINC@Australia Team.

Hi all.
My first W.U. finished in under 2hrs, the second was running last night
when i shut the puter down for the night. This morning when it restarted
it was at 2hrs 8min at 52% after a couple of minutes it has gone back
to 0.700% and going back up slowly. ;)
pete.

That\'s how it acts. I will creep up and then jump to 100%. Everything is normal- It is just the counter that is messed up, it really will finish in the normal time (it isn\'t really starting back @ 0.7%, it is just the display).

---

Boinc Button Abuser In Training >My Shrubbers<

Hi to everybody,
I\'ve the same problem with resuming but now,despite the elapsed time is usually increasing,the time remaining is increasing too instead of decreasing!!Is it the same bug?
Thanks

Hi to everybody,
I\'ve the same problem with resuming but now,despite the elapsed time is usually increasing,the time remaining is increasing too instead of decreasing!!Is it the same bug?
Thanks

Yes,time to completion is a function of/derived from completion percentage.

Thank you,but then when i\'ll finish my WU??Now the percentage is about the 7% and before i restart the client it was about 28%..so if the percentage isn\'t true and the time remaining is increasing,how can i know how much work i still have to do?

Thank you,but then when i\'ll finish my WU??Now the percentage is about the 7% and before i restart the client it was about 28%..so if the percentage isn\'t true and the time remaining is increasing,how can i know how much work i still have to do?

You really don\'t know when---most of us go on past history.....however I will tell you that somewhere around 70% complete it will usually start showing proper % done and will count up correctly from then on til complete even on reboots,suspension,etc....but sometimes it won\'t show correct til 95% which is the same as 100% here and where it uploads.

Ok...thanks for the help.So i\'ll go on with my WU until it finish without watching it!I hope that bug will be correct soon...
Thank you again
Greetings

I guess it\'s a race betwee Cosmology and Reisel to see who can fix this bug first ;) It is annoying.