There will be no assimilator yet, so still time to tune things in the validator.
Sad that it seems to still need a tuning
On the other hand, if "it" refers to the validator, how can it be "sad" if the Devs are taking extra precautions to make sure the validator isn't wrongly invalidating otherwise 'correct' results or allowing through 'incorrect' results?
-> one complete workday for trying to find a solution. Myself being long around at various projects and knowing very well how good Bernd is at finding a solution. So if it takes this time its not so trivial as thought, and im feeling with him. And _that_ im calling -sad- about it
There's still something seriously wrong with the "S3" validator. Turned off for now. Sorry for all the "validate errors", these will eventually be fixed and credited.
Intermediate report on the validation problem: we're still working on it. It's definitely not a simple technical problem in the validator. From my (validator) side this looks more like a problem in the app that's triggered by the new "S3" data. Investigation is ongoing, but will take a bit.
While investigating, we send out only minimal O2MD* tasks.
Thank you for keeping us informed about your/our headache.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
We need to re-start the "O2MDFS3" run (new tasks will show up with "O2MDFS3a"). I hope to get this done (ie.e. the first new tasks sent) today.
The old tasks that ended up as "validate error"s have been reset, these will be credited by a modified validator. This is likely not to happen today, but on Monday.
Also on Monday we will start the CPU part of the search, "O2MD1S3".
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
There are two validators running now: "O2MDFS3" which should validate the tasks of the old, now aborted run, and "O2MDFS3a" for the tasks of the new, restarted run. Both have undergone preliminary testing with tasks from 1000 workunits each, so should not be completely off.
The CPU part of the run ("O2MD1S3") is also running now. The validator will be started when there are enough successful tasks returned to test it with. This may take another day or two. BTW the result will be uploaded to yet another upload server that we set up on old hardware, to further relieve the pressure on our oldest one.
Gary Roberts
)
-> one complete workday for trying to find a solution. Myself being long around at various projects and knowing very well how good Bernd is at finding a solution. So if it takes this time its not so trivial as thought, and im feeling with him. And _that_ im calling -sad- about it
OK, I'm sorry that I
)
OK, I'm sorry that I misunderstood your intent. (I'm not sad - I'm just sorry for not understanding :-) ).
I thought you were being critical rather than offering condolences. My mistake :-).
Cheers,
Gary.
There's still something
)
There's still something seriously wrong with the "S3" validator. Turned off for now. Sorry for all the "validate errors", these will eventually be fixed and credited.
BM
Intermediate report on the
)
Intermediate report on the validation problem: we're still working on it. It's definitely not a simple technical problem in the validator. From my (validator) side this looks more like a problem in the app that's triggered by the new "S3" data. Investigation is ongoing, but will take a bit.
BM
While investigating, we send
)
While investigating, we send out only minimal O2MD* tasks.
BM
Bernd Machenschalk
)
Thank you for keeping us informed about your/our headache.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
We need to re-start the
)
We need to re-start the "O2MDFS3" run (new tasks will show up with "O2MDFS3a"). I hope to get this done (ie.e. the first new tasks sent) today.
The old tasks that ended up as "validate error"s have been reset, these will be credited by a modified validator. This is likely not to happen today, but on Monday.
Also on Monday we will start the CPU part of the search, "O2MD1S3".
BM
Yahoo :)
)
Yahoo :)
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Ditto!!!
)
Ditto!!!
Proud member of the Old Farts Association
There are two validators
)
There are two validators running now: "O2MDFS3" which should validate the tasks of the old, now aborted run, and "O2MDFS3a" for the tasks of the new, restarted run. Both have undergone preliminary testing with tasks from 1000 workunits each, so should not be completely off.
The CPU part of the run ("O2MD1S3") is also running now. The validator will be started when there are enough successful tasks returned to test it with. This may take another day or two. BTW the result will be uploaded to yet another upload server that we set up on old hardware, to further relieve the pressure on our oldest one.
BM