Currently-running all-sky gravitational wave search

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

Comments

bcavnaugh
bcavnaugh
Joined: 25 Jan 14
Posts: 13
Credit: 149781167
RAC: 158

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.

mshap
mshap
Joined: 22 Apr 18
Posts: 8
Credit: 1681763
RAC: 19637

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?

eskercurve
eskercurve
Joined: 15 Mar 07
Posts: 3
Credit: 21085058
RAC: 348619

Should we be aborting all

Should we be aborting all existing O2 All-Sky 1.01 tasks then?

MarkJ
MarkJ
Joined: 28 Feb 08
Posts: 361
Credit: 52836004
RAC: 115

Patrick_130 wrote:Should we

Patrick_130 wrote:
Should we be aborting all existing O2 All-Sky 1.01 tasks then?

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.

Bruce Allen
Bruce Allen
Moderator
Joined: 15 Oct 04
Posts: 1109
Credit: 172125663
RAC: 0

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

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 3780
Credit: 167300832
RAC: 56952

bcavnaugh wrote:To many

bcavnaugh wrote:

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

I don't quite get this message - is there anything we can help you with?

BM

mshap
mshap
Joined: 22 Apr 18
Posts: 8
Credit: 1681763
RAC: 19637

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.

Holmis
Joined: 4 Jan 05
Posts: 876
Credit: 314111297
RAC: 1058703

mshap wrote:Hmmm. In the last

mshap wrote:
Hmmm. In the last 24 hours I received some new O2 All-Sky 1.01 tasks. I thought these were on hold.

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.

tullio
tullio
Joined: 22 Jan 05
Posts: 1980
Credit: 28135989
RAC: 12669

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

earthbilly
earthbilly
Joined: 4 Apr 18
Posts: 15
Credit: 204793560
RAC: 2526642

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!

100% powered by SOLAR

Sunny regards,

 

 

 

okar
okar
Joined: 31 Oct 14
Posts: 2
Credit: 15046035
RAC: 58249

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.

Holmis
Joined: 4 Jan 05
Posts: 876
Credit: 314111297
RAC: 1058703

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_".

okar
okar
Joined: 31 Oct 14
Posts: 2
Credit: 15046035
RAC: 58249

Awesome, it's all clear

Awesome, it's all clear now.

Thanks a lot.

DanNeely
DanNeely
Joined: 4 Sep 05
Posts: 1205
Credit: 925632003
RAC: 1178890

earth_4 wrote: because some

earth_4 wrote:

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!

 

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.)