Lately, all the tasks I am getting from gamma-ray pulsar searches keep getting stuck at 89.959% completion. What is going on?
As Keith said they are using the cpu to compile all the results, they do that at around 49.??% as well getting the data ready to send back to Einstein as a finished task. There's no way around this as it's part of the task design.
Lately, all the tasks I am getting from gamma-ray pulsar searches keep getting stuck at 89.959% completion. What is going on?
Hello Jay Trang,
Welcome to the einstein@home forum!!!
The final ~10% are used to reevaluate a toplist of the ten most promising signal candidates. The science app doesn't update the progress meter during this final phase; don't know why...
If you urgently want to monitor progress during this final phase, you can still observe the stderr.txt logfile in BOINC's slots subdirectory ([..]/BOINC/slots/[slotID]/stderr.txt).
if you use Linux or some POSIX extension to Windows like "cygwin": tail -n [..]/BOINC/tasks/[slotID]/stderr.txt
You will at least witness the checkpoints which are written after each finished candidate (10 checkpoints until 100% progress).
example:
[...]
% C 19 0
% C 20 0
% C 21 0
% C 22 0 --> regular progress up to 89.959% until this checkpoint
% C 23 2 --> 1st toplist candidate
% C 24 3 --> 2nd top...
% C 25 4 --> 3rd
% C 26 5 ...
% C 27 6
% C 28 7
% C 29 8
% C 30 9
% C 31 10
% C 32 11 --> 10th toplist candidate --> finished 100%.
FPU status flags: PRECISION
01:08:31 (7096): [normal]: done. calling boinc_finish(0).
01:08:31 (7096): called boinc_finish
As Keith said they are using the cpu to compile all the results, they do that at around 49.??% as well getting the data ready to send back to Einstein as a finished task. There's no way around this as it's part of the task design.
you're confusing the O3AS tasks (GPU) with the gamma ray tasks (CPU) that the OP is talking about. he's asking about the FGRP5 CPU-only work. they do CPU computation 100% of the time, not only at that toplist section.
O3AS for apps v1.07 (OpenCL) and v1.08/1.15 (CUDA),"pauses" at 49.5% and 99.5% during this time calculations are being done on CPU.
O3AS for app 1.14 (CUDA) "pauses" at 37.5% and 87.5%, during this time calculations are being done on GPU
FGRP5 CPU work will "pause" at 89.99%, and jump to 100% when done. the old GPU app for FGRPB1G did the same thing.
in all of these cases, nothing is actually stopped or paused. calculations of some kind are still happening somewhere (depending on which app you're looking at), it's only BOINCs completion percentage reporting that's a little iffy.
The are NOT stuck. That is
)
The are NOT stuck. That is exactly what they are supposed to do. Just let them finish.
Jay Trang wrote: Lately, all
)
As Keith said they are using the cpu to compile all the results, they do that at around 49.??% as well getting the data ready to send back to Einstein as a finished task. There's no way around this as it's part of the task design.
Jay Trang schrieb:Lately,
)
Hello Jay Trang,
Welcome to the einstein@home forum!!!
The final ~10% are used to reevaluate a toplist of the ten most promising signal candidates. The science app doesn't update the progress meter during this final phase; don't know why...
If you urgently want to monitor progress during this final phase, you can still observe the stderr.txt logfile in BOINC's slots subdirectory ([..]/BOINC/slots/[slotID]/stderr.txt).
if you use Linux or some POSIX extension to Windows like "cygwin": tail -n [..]/BOINC/tasks/[slotID]/stderr.txt
You will at least witness the checkpoints which are written after each finished candidate (10 checkpoints until 100% progress).
example:
mikey wrote: As Keith said
)
you're confusing the O3AS tasks (GPU) with the gamma ray tasks (CPU) that the OP is talking about. he's asking about the FGRP5 CPU-only work. they do CPU computation 100% of the time, not only at that toplist section.
O3AS for apps v1.07 (OpenCL) and v1.08/1.15 (CUDA),"pauses" at 49.5% and 99.5% during this time calculations are being done on CPU.
O3AS for app 1.14 (CUDA) "pauses" at 37.5% and 87.5%, during this time calculations are being done on GPU
FGRP5 CPU work will "pause" at 89.99%, and jump to 100% when done. the old GPU app for FGRPB1G did the same thing.
in all of these cases, nothing is actually stopped or paused. calculations of some kind are still happening somewhere (depending on which app you're looking at), it's only BOINCs completion percentage reporting that's a little iffy.
_________________________________________________________________________
+1
)
+1
Proud member of the Old Farts Association
Ian&Steve C. schrieb: O3AS
)
[off-topic:]
Seems like we could use a 'Wiki' here that collects all this useful information. ;-)