On the weekend we began to send out the first tasks of the first search for Continuous Gravitational Waves in "O2" data, i.e. data from the second Observation Run of the LIGO detectors. This "Tuning" run will be a short one (targeted for about a month) where we will test and tune the application and setup for the actual analysis run, which will follow immediately (or will even be started before the tuning run is fully finished).
As the name indicates, this will be an all-sky search, covering the frequencies 20-500Hz. For the tuning run, however, we will focus on a few smaller frequency bands in that range.
Currently this is marked as a "Beta test" application (meaning you have to accept "Beta work" in your preferences to get it), but this is meant to be changed soon (today or tomorrow). We still have trouble building the OSX version of the application, so there currently is no such for Macs, but that should get fixed within this week.
BM
Copyright © 2024 Einstein@Home. All rights reserved.
On my system, it looks like
)
On my system, it looks like they take ~40% longer than the most recent chunks of LAT data, which is about what I recall for O1-High (although I guess LAT can be highly variable).
Consider tuning the number of "T"s in "Gravittational"...
Thanks!
)
Thanks!
BM
Are we expecting similar
)
Are we expecting similar memory usage with the O2 run to what we had in the O1 run? (ie up to 1500MB per work unit).
BOINC blog
Actually there were three
)
Actually there were three "O1" runs ("O1AS" (all-sky), "O1MD" (multi-directed) and the recent "O1Spot" (single-directional)).The "directional" searches were looking up to much higher frequencies than the "all-sky" search, that's where most of the memory usage came from.
I think the O2 all-sky run will be in the same order of magnitude than the O1 all-sky run (250-300MB), possibly up to a factor of two higher (600MB). Our model of memory-usage per data is certainly not perfect, we'll use the "tuning" run to improve this as well.
BM
9 tasks successfully
)
9 tasks successfully completed and 1 failed with exit status 13 on my i7 Windows 10 Pro system so far.
Runtime is comparable to that reported by Darren Peets (~9 hours and 1000 credits for O2, ~5 hours and 693 credits for FGRP5).
The failure ran for 4 hours and was reissued to and successfully completed by a Linux system (WU h1_0117.90_O2C01Cl1In1__O2AS20-500T_118.00Hz_83.
End of stderr on my system:
298..............ERROR: Stepped outside the coarse grid (79:14971:15049:15461)!
And on the Linux system:
685........c
The first task from the WU was sent to another Linux system and immediately failed with exit status 1 and the following in stderr (all 9 O2 tasks on that system have failed in the same way):
einstein_O2AS20-500T_0.01_x86_64-pc-linux-gnu: option `--getMaxFperSeg' was set more than once!
"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer
The first tasks instantiated
)
The first tasks instantiated from the first <500 workunits had indeed been generated with a broken command-line, so they failed immediately, but without wasting any computing time. This was fixed; all tasks generated after Saturday noon (UTC) should not exhibit this problem.
"ERROR: Stepped outside the coarse grid" is pretty unusual, in particular if this doesn't happen on a different host. I'll take a look and try to reproduce it.
BM
Hi! I don't see an app to
)
Hi!
I don't see an app to select in my account, Beta option is ACTIVATED but since there MUST be at least one app selected I only get tasks from this instead of the Beta ones.
Is there a way to get tasks for this app which I probably don't see?
Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
Thanks for the reminder.
)
Thanks for the reminder. Should be fixed (i.e. available in your preferences) now.
BM
Bernd Machenschalk
)
Thank you, that helps.
Ah, that explains why haven't
)
Ah, that explains why haven't been able to get any.