The 1.02 version contains a small fix related to error reporting so we could better investigate the failed tasks. It should be as fast as the 1.01 version. Regarding the errors that happen right at startup, we are working on a 1.03 version that should fix this. It should be ready on Monday.
I deployed a version 1.03 app for O1MD1TCV that should find it's way to your hosts with the remaining workunits of this run. We generated everything there is for this tuningrun today. So far we've learned a lot and are now finetuning the upcoming science run where we will cover the whole frequency space from 20 to 1500 Hz.
We are currently preparing the next run with the refined data. This will be a new set of applications and data files that will be released as soon as possible.
I have to retract my earlier statement about all work generated. I just discovered that there are 1622 jobs missing that where never generated. In order to not slow down the next run I configured the O1MD1TCV application to be a normal application (non locality scheduling) and bulk generated all the missing jobs with a deadline of 3 days in the hope that this will speed up the turnaround.
Woke up this morning and found that all of my Multi-Directed Continuous Gravitational Wave work units canceled out by the server, and one of my machines sitting idle.
Woke up this morning and found that all of my Multi-Directed Continuous Gravitational Wave work units canceled out by the server, and one of my machines sitting idle.
I believe the answer to your question is in this forum post in another thread. Summary: There was an error in the search parameter, and the run was aborted, with a new run to start later this week.
The 1.02 version contains a
)
The 1.02 version contains a small fix related to error reporting so we could better investigate the failed tasks. It should be as fast as the 1.01 version. Regarding the errors that happen right at startup, we are working on a 1.03 version that should fix this. It should be ready on Monday.
Thanks for that info CB!
)
Thanks for that info CB!
Christian Beer
)
Thanks Christian, will there also be a new run for the G tasks as well or only CV?
I deployed a version 1.03 app
)
I deployed a version 1.03 app for O1MD1TCV that should find it's way to your hosts with the remaining workunits of this run. We generated everything there is for this tuningrun today. So far we've learned a lot and are now finetuning the upcoming science run where we will cover the whole frequency space from 20 to 1500 Hz.
No more tasks?
)
No more tasks?
Reno, NV Team: SETI.USA
We are currently preparing
)
We are currently preparing the next run with the refined data. This will be a new set of applications and data files that will be released as soon as possible.
I have to retract my earlier
)
I have to retract my earlier statement about all work generated. I just discovered that there are 1622 jobs missing that where never generated. In order to not slow down the next run I configured the O1MD1TCV application to be a normal application (non locality scheduling) and bulk generated all the missing jobs with a deadline of 3 days in the hope that this will speed up the turnaround.
Woke up this morning and
)
Woke up this morning and found that all of my Multi-Directed Continuous Gravitational Wave work units canceled out by the server, and one of my machines sitting idle.
What happened?
We found an error in the
)
We found an error in the scientific parameters used in the search. See my comment there: https://einsteinathome.org/goto/comment/152281
TLDR; we had to cancel the whole search and will start a rerun soon with fixed parameters. It will still use the same datafiles and applications.
Jonathan Jeckell wrote:Woke
)
I believe the answer to your question is in this forum post in another thread. Summary: There was an error in the search parameter, and the run was aborted, with a new run to start later this week.
Einstein@Home Project