CPU TIME tallys PROGRESS stays at O.OO

Author	Message
spacecadetrojo Send message Joined: 8 Jul 06 Posts: 2 Credit: 4,866,343 RAC: 0	Message 37798 - Posted: 14 Mar 2007, 13:58:07 UTC Hello, Recently a problem has occured with Rosetta. The CPU TIME tallys normally but the PROGRESS stays at 0.00. Any suggestions? ID: 37798 · Rating: 1 · rate: / Reply Quote

Telescope Adrian Send message Joined: 14 Nov 06 Posts: 9 Credit: 1,906,378 RAC: 0	Message 37823 - Posted: 15 Mar 2007, 0:08:45 UTC I see the same thing . Also CPU time (used) increases , while To Completion also increases ! Different ! ID: 37823 · Rating: 0 · rate: / Reply Quote

Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0	Message 37825 - Posted: 15 Mar 2007, 2:03:09 UTC The two of you are saying very different things. But perhaps not intentionally. Time to completion going up for a period of time is normal, odd, but normal. More details here. "Progress stays at 0.00" would be a different situation. spacecadetrojo, please use the terms that are displayed in the BOINC Manager for the columns you are asking about, and we'll see if we can shed some light on what you are observing. Rosetta Moderator: Mod.Sense ID: 37825 · Rating: 0 · rate: / Reply Quote

spacecadetrojo Send message Joined: 8 Jul 06 Posts: 2 Credit: 4,866,343 RAC: 0	Message 37829 - Posted: 15 Mar 2007, 2:31:19 UTC - in response to Message 37825. The two of you are saying very different things. But perhaps not intentionally. Time to completion going up for a period of time is normal, odd, but normal. More details here. "Progress stays at 0.00" would be a different situation. spacecadetrojo, please use the terms that are displayed in the BOINC Manager for the columns you are asking about, and we'll see if we can shed some light on what you are observing. For example on one work unit, CPU Time is 00:59:45, Progress is at 1.000%, To Completion is 02:50:50 which is an hour longer than the time shown for a work unit that has not been activated. This is the second work unit that this has occured on. I aborted the first and am about ready to abort this on and just do Einstein and Seti until someone figures out whats going on. I've not had any problems with Rosetta previously in over 11,300 work units. ID: 37829 · Rating: 0 · rate: / Reply Quote

Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0	Message 37855 - Posted: 15 Mar 2007, 14:23:49 UTC So the progress says 1%, rather then 0.00. This is normal and described in the link I posted previously. ...Once you complete that first model, the progress % will be updated and the estimated time to completion will sharply decline. It's been doing that all along, you just didn't notice. Or perhaps the difference now is that you are getting more tasks that take significant time to complete that first model. Also, if the task is an RNA task, I believe the models were not increasing normally. This issue is fixed in the next Rosetta release and the RNA tasks are no longer being added to the queue of work, pending that next release. If a task runs abnormally, the watchdog will end it for you. There is no need to abort tasks. Rosetta Moderator: Mod.Sense ID: 37855 · Rating: 0 · rate: / Reply Quote