Gravitational Wave search O1 all-sky tuning (O1AS20-100T)
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4312
Credit: 250434360
RAC: 34952
10 Feb 2016 14:36:57 UTC
Topic 198418
(moderation:
We will soon start to Beta-Test the first search for Continuous Gravitational Waves using data from the first Observation run of the Advanced LIGO detectors ("O1").
This first "tuning" run is set up to run for about two weeks, after which we will set up another, longer analysis run using information we got out of this tuning run.
CPU only, currently Beta test
BM
BM
Gravitational Wave search O1 all-sky tuning (O1AS20-100T)
)
Thanks Bernd,
Just got up and first thing I check mine and saw that in the list of projects and mine was auto-set to do those and I will at least have my 8-core ready for these and I may have the free cores on my quad-cores to run them too.
And I know we have others ready to go too.
I've had one running on a
)
I've had one running on a 4GHz i7-6700K Windows 10 system for 3 hours. It's checkpointing every 17 minutes or so but the progress is stuck at 0% (hopefully just a case of it not being updated in the checkpoints).
Edit: correction. The task is from the other Beta application "Gamma-ray pulsar binary search #1 (beta test)".
"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer
Yes the Server still says
)
Yes the Server still says none of these tasks are available yet
Not intended to be a nitpick,
)
Not intended to be a nitpick, but the Mac OS X on Intel app has Altivec listed, which is on PPC Macs.
Also, the Linux and Windows versions have AVX optimized versions. Will there be an optimized version for Mac OS X on Intel as well? AVX would limit the app to newer machines, whereas everything from the Core Duo onward have SSE4.1 and SSSE3.
Either way, I am very excited to see this show up in the app list today!
Is there some explanation
)
Is there some explanation somewhere explaining how a continuous gravitational wave search is different than the previous gw searches?
Thanks!
Edit: Found it! http://www.ligo.org/science/GW-Continuous.php
I guess the first LIGO was searching for Inspiral http://www.ligo.org/science/GW-Inspiral.php
or Burst gravity waves? http://www.ligo.org/science/GW-Burst.php
RE: Is there some
)
In fact it isn't. All GW searches on E@H so far were targeting continuous gravitational waves (see e.g. front page).
Sorry, my phrasing in the initial post was ambiguous - It's the first search that uses O1 data, not the first for Continuous GWs.
We are currently exploring the feasibility of a search for other types of Gravitational Waves on E@H. To prepare for the case we will have such a different search on E@H we included the "Continuous" in the name of this one.
BM
BM
RE: Not intended to be a
)
Right. In fact this is a PPC version. However, this version shouldn't have been released at all, since PPC Macs are way too slow to finish these tasks on time. Withdrawn.
Possibly. The AVX versions are still experimental, we'll see how much speedup we get, and whether it's worth the effort to make a version for the relatively small OSX population on E@H.
BM
BM
With all the changes going on
)
With all the changes going on and in the excitement of dealing with advanced LIGO data, it might be appropriate to issue a couple of warnings about beta tests.
* The announcement said "soon". This could easily mean days or more, rather than minutes or hours so please curtail your impatience :-). There is a *lot* of planning and preparation that has to be done so please have sympathy for those doing the work.
* There will likely be two different 'CPU only' beta tests running concurrently - the Gamma-ray pulsar binary run (FGRPB1) and the new GW run. If you allow beta test tasks you will likely get both types, even if you deselect the FGRPB1 run. The option to allow test tasks does NOT look at which science runs are selected so in your eagerness to get GW tasks you may also get FGRPB1 as well until they are moved out of beta.
* It is not considered to be 'good etiquette' to abort large numbers of tasks just because you don't like the 'hand' you've been dealt. Please be mindful of the extra strain this puts on the project servers, or the possible angst it may cause to your quorum partners (wingmen).
* If you wish to have control over what type of beta test tasks you receive, I don't think there is any easy way to do so, short of the Devs deciding to make the beta test mechanism actually pay attention to the science runs you have selected. In this time of major change, it would not be fair to ask for such a feature to be added immediately. Maybe when the dust settles :-).
* I've been refreshing my memory on the BOINC application configuration mechanism, towards the bottom of the
Client Configuration page. I had wondered if setting max_concurrent to zero for the unwanted test app might work. My thinking is that it might stop them crunching but wouldn't stop them downloading on a work request. I've never tried it so I don't know. If you have a multi-core machine and you set it to 1 for the app you don't want, you could perhaps maximise your participation in the test you do want to run.
The above are just personal thoughts about things to be aware of now that the exciting times we've all been waiting for are just about upon us. I wish the Devs every success in getting this new show on the road and I sincerely thank them for all the hard work they are doing to bring it to fruition.
Cheers,
Gary.
RE: With all the changes
)
Well said Gary.
{ Chance favors only the prepared mind ... Louis Pasteur }
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Maybe a bit of explanation on
)
Maybe a bit of explanation on the AVX support is useful.
It is our final goal to have one application version for both AVX and non-AVX enabled clients of a given platform. AVX is enabled only for one module (FFTW) that can do the switching between AVX and SSE2 on its own. In fact the exectables we ship now for AVX PCs only should actually be able to do this already, we will test this at a later time "in the field". So owners of AVX enabled clients should look forward to at least some speedup, while owners of older machines w/o AVX need not fear to be left out of the search.
HB