SETI Estimated Time to Completion Error


log in

Advanced search

Questions and Answers : Web site : SETI Estimated Time to Completion Error

Author Message
Vito
Send message
Joined: 6 Dec 12
Posts: 4
Credit: 136,737
RAC: 0
United States
Message 1315635 - Posted: 15 Dec 2012, 17:25:26 UTC
Last modified: 15 Dec 2012, 17:26:45 UTC

I am a newbie to SETI. So I really don't know where to post this.

After successfully completing 40-50 WU’s in both SETI and PEOM, this morning after downloading 4 and running 2 SETI jobs I had this problem. The two SETI jobs runs froze. They showed no activity. The estimated time was not decreasing. After suspending the jobs and resuming several times the jobs began to run. But I noticed that estimated time to completion was rolling backwards. Time would decrease but after a while it would default to an earlier time. And it continued to do this as in a loop. I finally aborted all 2 jobs and the two remaining jobs started and displayed the same issue so I aborted them also.

Is this a known SETI problem?

John McLeod VII
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 15 Jul 99
Posts: 24806
Credit: 530,998
RAC: 330
United States
Message 1315710 - Posted: 15 Dec 2012, 19:45:40 UTC - in response to Message 1315635.

I am a newbie to SETI. So I really don't know where to post this.

After successfully completing 40-50 WU’s in both SETI and PEOM, this morning after downloading 4 and running 2 SETI jobs I had this problem. The two SETI jobs runs froze. They showed no activity. The estimated time was not decreasing. After suspending the jobs and resuming several times the jobs began to run. But I noticed that estimated time to completion was rolling backwards. Time would decrease but after a while it would default to an earlier time. And it continued to do this as in a loop. I finally aborted all 2 jobs and the two remaining jobs started and displayed the same issue so I aborted them also.

Is this a known SETI problem?

Time to completion is an estimate based on an estimate of work to be done for the task (this is not always very accurate), the history of completion time vs estimate (Duration Correction Factor - again, not always very accurate), time spent, and reported % complete by the application. If the DCF is under estimated or the estimate of work to be done is an underestimate, then the time to completion can grow for a long time before it starts shrinking again. NOTE that DCF is per project and the different applications do not always have estimates that will generate a similar DCF on your particular equipment.

If the time spent rolls backwards, there are two cases. The first is that BOINC has stopped for some reason and unloaded the task from memory. This loses all work since the last check point. The second is that the task hit some glitch and reset back to the previous checkpoint. If this happens once or twice for a given checkpoint, it is OK. If it happens repeatedly for the same check point, it would be time to give up on the task.
____________


BOINC WIKI

Questions and Answers : Web site : SETI Estimated Time to Completion Error

Copyright © 2014 University of California