Gravitational Wave search O2 All-Sky search ("O2AS20-500")
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4312
Credit: 250428254
RAC: 34810
6 Apr 2018 12:27:31 UTC
Topic 214401
(moderation:
Following the "tuning" run, we have just launched the actual analysis run for the full frequency range. This will be E@H's first analysis of data from the second Observation Run of the LIGO detectors, and search the whole sky, covering the frequencies 20-500Hz.
We'll leave the workunit generation run somewhat throttled over the weekend and ramp it up next week (unless we see signs of serious trouble).
Also validation will be suspended until we got back the first results and are back ourselves at our desks to monitor the validator.
BM
Can we get a 14 day deadline
)
Can we get a 14 day deadline please? Saves me a lot of aborting
This will also be changed
)
This will also be changed after the weekend.
BM
almost 1/3rd of the tasks
)
almost 1/3rd of the tasks reported so far are failing. This doesn't look promising...
Actually, if you look at the
)
Actually, if you look at the results. None have validated, invalidated or been diagnosis as inconclusive. 1022 are pending, 408 have failed. So we will need to wait and see what happens
It looks like the percentage
)
It looks like the percentage of successes is increasing. I know personally I have not had any failures . It will be interesting to see if that trend continues.
Down to around 10% now; which
)
Down to around 10% now; which suggests that the fails are happening around app start. A bad batch of WUs, or one app/system combo not working perhaps. It'll be interesting to see what happens when the devs start looking Monday morning.
Errors are always what's
)
Errors are always what's returned first, I don't care much about these and ignore them at least for the duration it takes to successfully complete & report a task (here: ~12h), unless some particular error occurs on a large variety of hosts, which may indicate a real problem.
Currently we are down to a ('computing") error rate below 2%.
BM
Thanks Bernd for the update.
)
Thanks Bernd for the update. Looks like just a hair over 9 hours per work unit on my computer. Would add a second to help out but having internet problems at the moment.
No errors at all for me so
)
No errors at all for me so far, running well. Tuning run was good also.
Conan
Mine are running well and
)
Mine are running well and completing, but with a hitch. After starting up and running for 8 minutes, the estimated time remaining jumps up to a very high value, typically 7 to 9 days and briefly even more. Then, after running for maybe half an hour or so, the time estimate returns to a reasonable value. (They typically run for about 11 to 12 1/2 hours on this i7-4790 running Ubuntu 16.04.)
However, this brief jump causes most of them to run "high priority", and creates havoc with the scheduling of other projects that are running (or trying to run) at the time. This has been going on for a couple of days, and I hoped it would correct itself, but it has not yet.