Currently-running all-sky gravitational wave search
Submitted on 16 Aug 2018 12:10:22 UTC
In order to run a new gravitational wave search on LIGO open data, we are putting the ongoing all-sky gravitational wave search on hold. In part this is because some questions have surfaced related to the de-jittering used in the preparation of the LIGO O2 data. These must first be understood. We will of course make the fullest possible use of the results obtained so far.
Bruce Allen, Einstein@Home Director
M.Alessandra Papa, Lead Scientist for gravitational-wave searches
Language
Copyright © 2024 Einstein@Home. All rights reserved.
Comments
To many bugcheck 0x00000133
)
To many bugcheck 0x00000133 BSOD Under Windows 10 1803 x64 Pro
But then give this CPU App a test run
I been running PG LLR Tasks hard so I know the issue is not my Host of 6 months of age.
This Host https://einsteinathome.org/host/12626014
Crunching@EVGA The Number One Team in the BOINC Community. Folding@EVGA The Number One Team in the Folding@Home Community.
What are the practical
)
What are the practical implications for those of us who have been running predominantly Continuous Gravitational Wave search O2 All-Sky 1.01 tasks?
Should we be aborting all
)
Should we be aborting all existing O2 All-Sky 1.01 tasks then?
Patrick_130 wrote:Should we
)
While we wait for an official answer I would suggest setting Einstein to no new tasks and let it finish off whatever tasks you have on board. It may turn out that the data is usable.
BOINC blog
Please don't abort existing
)
Please don't abort existing tasks! We hope to make use of these results, and letting them run to completion also means that you'll get properly credited for the work.
Bruce and Marialessandra
Director, Einstein@Home
bcavnaugh wrote:To many
)
I don't quite get this message - is there anything we can help you with?
BM
Hmmm. In the last 24 hours I
)
Hmmm. In the last 24 hours I received some new O2 All-Sky 1.01 tasks. I thought these were on hold.
mshap wrote:Hmmm. In the last
)
I think that no new work will be issued but already started workunits will have tasks generated to fill the quorum.
If you look at the Task IDs of the "O2 All-Sky 1.01" tasks you received they all end with _X where X is greater than 1.
New tasks for a workunit will have _0 and _1 at the end of the Task ID, a resend generated because one of the tasks failed or wasn't returned will have higher numbers.
I finished one in 4 days on
)
I finished one in 4 days on my HP laptop running SuSE Leap 15.0 which has a new kernel 4.12 equal to that of the Enterprise version of SuSE Linux. Another is nearing its end.
Tullio
because some questions have
)
because some questions have surfaced related to the de-jittering used in the preparation of the LIGO O2 data. These must first be understood.
Is it just my rigs or does this include an issue with Continuous G W tasks hording CPU's away from GPU cards and doing odd things with "Options-computing preferences-usage limits?
All this works perfectly with just our gamma-ray tasks. Throw back into the mix some new C.G.W. tasks and I hope my dual and triple GPU computers stay fully working!
Work runs fine on Bosons reacted into Fermions,
Sunny regards,
earthbilly
I have 3 systems running
)
I have 3 systems running Einstein@Home tasks, 2 of them 24/7. 3 weeks after the announcement of the project on hold, I'm still getting tasks, several of the most recent ones end with _0, and they now start with LATeah.
I'm no longer clear on what I'm helping with, I hope Bruce Allen or someone else on the project could shine some light on the subject.
There's 2 different CPU
)
There's 2 different CPU searches running on Einstein@home, one is the "Continuous Gravitational Wave search O2 All-Sky" search discussed in this news announcement and the other is called "Gamma-ray pulsar search #5". As the announcement here states the Gravity wave search has been stopped and no new tasks will be issued until further notice. On the other hand the Gamma-ray search is still ongoing.
When I take a look at the tasks for one of your computers I see that you have been working on the Gamma-ray search and that corresponds to the task name starting with "LATeah". If you follow the link I posted you will see that the name of the tasks in the leftmost column start with "LATeah" and the application in the rightmost column is named "Gamma-ray pulsar search #5 v1.08 () windows_intelx86" for CPU tasks.
Tasks for the Gravity wave search have names starting with "h1_".
Awesome, it's all clear
)
Awesome, it's all clear now.
Thanks a lot.
earth_4 wrote: because some
)
No. This would be a potential problem in how they prepared the data we're crunching.
Problems with GPU/GPU allocation are due to the boinc client, at leat the 1st half of your problem can be worked around via client settings (ask in crunchers corner). Your other problem might be addressable there as well if you ask. (Not sure what it is, and it's off topic in news.)
Interesting feed, the feeling
)
Interesting feed, the feeling is that dejittering ... makes some data unavailable for use... The same is true for camera filters!
https://einsteinathome.org/content/simplified-hpc-pack-install-guide-scienceserver-web
Looks like the 1st few
)
Looks like the 1st few hundred test WU's for the next GW search have been released.
I just noticed Gravitational
)
I just noticed Gravitational All-sky search on LIGO O1 Open Data 0.01 jobs showing up in my BOINC managers. Does this mean that the problems with the previous LIGO jobs has been fixed?
I cancelled my task in my
)
I cancelled my task in my configuration, but you are still using my computer ? why?? you are cheating. I want to delete my account
Anonymous wrote:I cancelled
)
You need to tell the boinc client you don't want to do any more work for E@H, if you don't it'll assume you do and keep requesting more to replace whatever you manually cancelled.
If you just want to pause E@H temporarily you can:
1) Set its resource share to 0 in settings on the website and do a project update to pull down the changed configuration. This will stop E@H on all of your computers if you have more than one. Depending on the order that things are processed, it may or may not pull down one final batch of work first.
or
2) On the projects tab of the boinc client, select E@H and click No New Tasks or Suspend. Either will stop any new E@H work from being done. The functional difference is that NNT will still run any work already downloaded as normal (unless you manually abort it), suspend won't run them but will leave them lingering in your task list until they expire of old age unless aborted.
If you never want to run E@H again, you can go a step farther and:
3) On the projects tab of the boinc client, select E@H and click Remove. (If you're using an account manager, eg BAM you'll need to remove E@H there. If you don't know what this means you're almost certainly not.)
If you don't want to run any Boinc projects in the future you can go another step farther and:
4) Uninstall Boinc entirely using whatever the standard method for your operating system is.
I have completed 8
)
I have completed 8 gravitational wave search tasks on my new HP PC with a Ryzen 5 1400 CPU and they all validated.
Tullio