Weird. Nothing validated since the 9th for me. I ask about it this morning, and now another 11 have validated, for a total of 15. But my pending is now over 430 tasks, and growing quickly.
So if validation is turned on, as it seems, why is the backlog growing so dramatically? They are no longer using CPU tasks to validate, right? Is there another problem?
Sure, I know what pending means. The point is that the validation end of the process has stalled. A few tasks have squeezed through, but at this rate there is clearly a problem.
The point is that the validation end of the process has stalled. A few tasks have squeezed through, but at this rate there is clearly a problem.
There is no way that you can make that claim with any certainty. You have obviously forgotten how locality scheduling works :-). If you don't have active quorum partners assigned to the frequency bins you are currently crunching, then there's no way for your completed tasks to be presented for validation until there are. You just need to be patient. It can take up to 7 days to have quorum partners assigned. Some will be lucky and some will not. It's just the luck of the draw in these early stages.
There turned up a number of problems related to the currently active GW searches, two of which were solved today, particularly the validation of "O1MD1V1" tasks. "Validate errors" should mostly be replaced by "valids" (and credit given).
There is no way that you can make that claim with any certainty. You have obviously forgotten how locality scheduling works :-). If you don't have active quorum partners assigned to the frequency bins you are currently crunching, then there's no way for your completed tasks to be presented for validation until there are. You just need to be patient. It can take up to 7 days to have quorum partners assigned. Some will be lucky and some will not. It's just the luck of the draw in these early stages.
You are suggesting that I am the only one crunching these WUs. Or close enough to it that there is no one else crunching ANY of the same hundreds of WUs that I have for the past 5 days. Okay then, there is no problem at all. Never mind.
You are suggesting that I am the only one crunching these WUs.
No I'm not. I'm suggesting that for certain frequencies in those that you've been crunching, there is no wingman yet. Take a look at this page of results that belong to one of your machines doing the O2MDF tasks. Some are validated but many are not. Click on the WUID for one that's not. The couple I checked show that the companion task is "unsent". That is why your claim of a validator problem doesn't apply.
If you look at the 'frequency' part of the task name - eg. 0693.50 - for the very first pending task in that list and then compare that value with the same part of the name for a validated task - eg. 0693.70 - then you might see the problem. You have quorum partners for one frequency bin and not for the other. Then think about how many different bins there must be and perhaps you can appreciate that there are bound to be some where there are not enough contributing hosts to fill them all instantly.
I repeat, you just need to be patient and not start making accusations about problems that can't be supported by the evidence.
Due to an error in the configuration all app versions for "O2MDF" up to now we're still marked "Beta test". Actually this should only be the case for the AMD versions. It is now, and even that restriction might be changed soon.
I have a page full of
)
I have a page full of validations from today and yesterday.
Are you interested in
)
Are you interested in Validate errors on CPUs?
https://einsteinathome.org/workunit/426360738https://einsteinathome.org/workunit/426192383
Weird. Nothing validated
)
Weird. Nothing validated since the 9th for me. I ask about it this morning, and now another 11 have validated, for a total of 15. But my pending is now over 430 tasks, and growing quickly.
So if validation is turned on, as it seems, why is the backlog growing so dramatically? They are no longer using CPU tasks to validate, right? Is there another problem?
Reno, NV
Team: SETI.USA
Pending just means you are
)
Pending just means you are waiting on slow wingmen. I have over 2300 pending between the 2.01 app and the 2.02 app.
Sure, I know what pending
)
Sure, I know what pending means. The point is that the validation end of the process has stalled. A few tasks have squeezed through, but at this rate there is clearly a problem.
Reno, NV
Team: SETI.USA
zombie67 wrote:The point is
)
There is no way that you can make that claim with any certainty. You have obviously forgotten how locality scheduling works :-). If you don't have active quorum partners assigned to the frequency bins you are currently crunching, then there's no way for your completed tasks to be presented for validation until there are. You just need to be patient. It can take up to 7 days to have quorum partners assigned. Some will be lucky and some will not. It's just the luck of the draw in these early stages.
Cheers,
Gary.
There turned out a number of
)
There turned up a number of problems related to the currently active GW searches, two of which were solved today, particularly the validation of "O1MD1V1" tasks. "Validate errors" should mostly be replaced by "valids" (and credit given).
BM
Gary Roberts wrote:There is
)
You are suggesting that I am the only one crunching these WUs. Or close enough to it that there is no one else crunching ANY of the same hundreds of WUs that I have for the past 5 days. Okay then, there is no problem at all. Never mind.
Reno, NV
Team: SETI.USA
zombie67 wrote:You are
)
No I'm not. I'm suggesting that for certain frequencies in those that you've been crunching, there is no wingman yet. Take a look at this page of results that belong to one of your machines doing the O2MDF tasks. Some are validated but many are not. Click on the WUID for one that's not. The couple I checked show that the companion task is "unsent". That is why your claim of a validator problem doesn't apply.
If you look at the 'frequency' part of the task name - eg. 0693.50 - for the very first pending task in that list and then compare that value with the same part of the name for a validated task - eg. 0693.70 - then you might see the problem. You have quorum partners for one frequency bin and not for the other. Then think about how many different bins there must be and perhaps you can appreciate that there are bound to be some where there are not enough contributing hosts to fill them all instantly.
I repeat, you just need to be patient and not start making accusations about problems that can't be supported by the evidence.
Cheers,
Gary.
Due to an error in the
)
Due to an error in the configuration all app versions for "O2MDF" up to now we're still marked "Beta test". Actually this should only be the case for the AMD versions. It is now, and even that restriction might be changed soon.
BM