task showing completed but continue to run
19 Oct 2015 6:03:46 UTC
Topic 198278
(moderation:
Tasks Gamma-ray pulsar search #4 1.14 (FGRP4-SSE2) LATeah1078E_80.0_2267_-3.7E-10_0 continues to run but shows same time remaining (estimated) and same application name LATeah1081E_48.0_1256_-4.4e-10_1 shows 100% progress no time remaining but continues to show status as running. I had same problem 2 years or so ago. Please advise what I can do go get credit for this tasks, over 26 hours of work.
task showing completed but continue to run
)
Here is a list of tasks for one of your computers that appears to contain both the tasks you mention. Look at the two that are well past their deadlines - they are listed in red. If you individually click on the workunit IDs for each of those two, you will see that both quorums are already complete (two duplicate tasks have returned and validated) and the credit has been allocated. Unfortunately, both your tasks, even if completed now, will be too late to be given credit. You should just abort them.
For future reference, Gamma ray pulsar tasks progress in step-wise fashion and you should never see them actually progressing continuously and reaching 100%. It you are seeing continuous, second by second progress still occurring after say 10-20% of progress, (perhaps a couple of hours of elapsed time) it is likely something has gone wrong with the science app. You should stop BOINC, reboot your computer and restart BOINC.
Cheers,
Gary.
Thank you for the reply. A
)
Thank you for the reply. A little confusion here, should the elapsed and remaining times count but the progress not go continuously upward, but that it will jump up some percent at a time. I have 1 task running that is showing this behavior.
RE: ... should the elapsed
)
Yes, that is exactly what will happen and the jump in progress can be relatively large and well spaced timewise. If you can use the advanced view for BOINC Manager and go to the Tasks tab, you can select any crunching task and then click on 'Properties' to see the CPU time, the elapsed time and, importantly, when the last checkpoint was saved.
The percentage jumps when a new checkpoint is written. For your machine, I would guess that it could be around 20 mins between checkpoints and a jump of around 3% in progress each time. This is not precisely the same for every task. There are some which checkpoint more frequently with a smaller % jump each time. If you are currently crunching the 'in progress' task in this quorum, I expect it might well be one of these doing smaller, more frequent jumps.
When this task is finished, it's not going to validate immediately because it will be compared with a much older task that was crunched with the 1.14 version app. Yours is 1.15 and the results wont agree. What will happen is that a further task will be issued which will be crunched by 1.15 also so eventually you should get a validated result.
Cheers,
Gary.