"Completed, waiting for validation"
14 Jul 2017 12:41:10 UTC
Topic 208761
(moderation:
I have 97 tasks in total that are "Completed, waiting for validation". Of these, 29 are Continuous Gravitational Wave search Galactic Center highFreq, whereas 68 of them are Gamma-ray pulsar binary search #1 on GPUs. I am running Ubuntu 16.04 on an i7-4770 with a GTX 1070.
I have seen mention of the occasional problems with validation, but don't see an explanation for both the CPU and the GPU. I have had to suspend crunching in hopes that the backlog would diminish, but it has not for several days now. Is there work going on to address this problem?
It looks like business as
)
It looks like business as usual to me.
Your workunits won't leave pending status until your wingman completes calculating the same workunit you did. Normally you and your wingman takes about the same time to complete the workunit. But sometimes the wingman will fail to complete (many reasons for this) and then it's a 14 day wait until the workunit gets sent to a 3:rd computer.
Boinc will try to pair you up with the same wingman for many workunits and if you're unlucky the wingman is very slow or just stops running his machine. Then you can amass a lot of pending units.
Fear not, eventually all your pending workunits will get validated against a wingman. Keep crunching new ones, sometimes you have lots of pending, sometimes few. It all gets sorted in the end.
OK, but it is more than I
)
OK, but it is more than I have seen before. However, it appears that there is no reason to stop work, which is the important point.
EDIT: Part of the reason may be that I usually run Einstein on Windows, which may be easier to match up. The Linux machine may have more delays in validating. I will check out the difference, but thanks for the advice.
Jim1348 wrote:The Linux
)
This is not the case. There is no 'matching' based on OS. With GW tasks, 'matching' is based on the frequency bands of the large data files. Your machine could be 'sharing' the same frequency band with a quite limited number of other hosts irrespective of OS. If those hosts were slow to return or not returning, you could get lots of pendings. There is no issue about ultimately getting credit.
Cheers,
Gary.
I also have tasks that are
)
I also have tasks that are waiting for validation, but those tasks do not have a "wingman" so it may be a while before anything happens. The workunits are 306921748 and 307139581, and the wingman tasks are "unsent". My tasks were sent on July 25th and 28th, so it does not appear to be a one time glitch. Is there anything that I can do to correct this?
m2a2b2 wrote:I also have
)
My oldest were sent on July 3, but the wingman timed out on all three. Two of them have not been resent yet. The third at least has been resent. After that, my next group was sent on July 21. Many are still waiting for a wingman, but at least some are in progress. Maybe I will someday bother to look up all the reasons why the delays, but for now I will just live with them. They do get taken care of eventually, I suppose.