We just found an error in the scientific parameters used in the search. This is not repairable afterwards so we need to cancel the O1MD1 run right away. I already paused sending out tasks and we have a plan how to send an abort signal to all of your hosts once they connect to our server. Unfortunately this has to wait until tomorrow.
Edit: we are now sending the abort signal automatically.
In the meantime anyone who reads this message may abort all O1MD1 work currently on their hosts. The rerun with fixed parameters will start later this week.
I'm very sorry for the wasted computing cycles so far especially because I'm the one who introduced the error. I'll keep you posted about the rerun that will start within the next days.
We just found an error in the scientific parameters used in the search. This is not repairable afterwards so we need to cancel the O1MD1 run right away. I already paused sending out tasks and we have a plan how to send an abort signal to all of your hosts once they connect to our server. Unfortunately this has to wait until tomorrow.
In the meantime anyone who reads this message may abort all O1MD1 work currently on their hosts. The rerun with fixed parameters will start later this week.
I'm very sorry for the wasted computing cycles so far especially because I'm the one who introduced the error. I'll keep you posted about the rerun that will start within the next days.
We just found an error in the scientific parameters used in the search.
Thanks for the heads up. I feel your pain at the moment!!
Does the fix involve the large data files or the app (or both) or perhaps something else? In particular, I'm interested to know if all existing large data files and apps will need to be replaced or not?
I'll keep you posted about the rerun that will start within the next days.
Thanks Christian for posting the details and seeing the problem, and i'd just call it a successful SPARST stage 1 (sciene parameter and abort run sequence testing).
I just configured the server to send out the abort signal for all O1MD1CV and O1MD1G tasks. You don't need to abort them manually from now on. The command should also abort already running tasks. If you have a really old Client you may need to abort manually.
The fix is related to the parameters we use when we create the tasks. The datafiles and the applications are fine and will be reused. They should not get deleted on your hosts.
I believe I only lost the credit for about 4 work units that were completed and returned but the validating work units were then cancelled so no validation is possible for them.
On the bright side at least the hours were counted on WUProp@Home and contribute to my next badge there.
(Edit : well looks like a few more of those work units were around and I have now lost around a dozen work units either completed and can't be validated or cancelled whilst they were running, so no points there either and the loss of a lot of hours work.
Work flowing again and some validated work units have now been processed.
We just found an error in the
)
We just found an error in the scientific parameters used in the search. This is not repairable afterwards so we need to cancel the O1MD1 run right away. I already paused sending out tasks and we have a plan how to send an abort signal to all of your hosts once they connect to our server. Unfortunately this has to wait until tomorrow.
Edit: we are now sending the abort signal automatically.
In the meantime anyone who reads this message may abort all O1MD1 work currently on their hosts. The rerun with fixed parameters will start later this week.
I'm very sorry for the wasted computing cycles so far especially because I'm the one who introduced the error. I'll keep you posted about the rerun that will start within the next days.
Christian Beer wrote:We just
)
Ok, cancelled.
Christian Beer wrote:We just
)
Thanks for the heads up. I feel your pain at the moment!!
Does the fix involve the large data files or the app (or both) or perhaps something else? In particular, I'm interested to know if all existing large data files and apps will need to be replaced or not?
Cheers,
Gary.
Christian Beer wrote: I'll
)
Thanks Christian for posting the details and seeing the problem, and i'd just call it a successful SPARST stage 1 (sciene parameter and abort run sequence testing).
Hi, So per Christian Beer we
)
Hi,
So per Christian Beer we should abort both O1MD1CV and O1MD1G tasks, correct?
Thanks,
Stu
I just configured the server
)
I just configured the server to send out the abort signal for all O1MD1CV and O1MD1G tasks. You don't need to abort them manually from now on. The command should also abort already running tasks. If you have a really old Client you may need to abort manually.
The fix is related to the parameters we use when we create the tasks. The datafiles and the applications are fine and will be reused. They should not get deleted on your hosts.
I believe I only lost the
)
I believe I only lost the credit for about 4 work units that were completed and returned but the validating work units were then cancelled so no validation is possible for them.
On the bright side at least the hours were counted on WUProp@Home and contribute to my next badge there.
(Edit : well looks like a few more of those work units were around and I have now lost around a dozen work units either completed and can't be validated or cancelled whilst they were running, so no points there either and the loss of a lot of hours work.
Work flowing again and some validated work units have now been processed.
Conan
I had 5 cancelled about 30
)
I had 5 cancelled about 30 hours wasted, oh well I shall crunch on.
Work is flowing again.
)
Work is flowing again.
Thank you Christian
)
Thank you Christian Beer,
I'll be looking for these work units on my cpu's from Cassiopeia A!