Table of Contents

Back to LIST WG1B home.

The definition of the challenges is work very much in progress; things will change


Challenge 1

Goal: Code validation (known parameters) and single source analysis
Release date: June 2006
Due date: December 2006 [known source analysis reported in September 2006]
Note: I would propose to distribute two data sets (with just slightly different source parameters) for each sub-challenge: (i) one with known parameters mainly for code validation (this is a “known source analysis, and we should have report around Septermber) and (ii) one with unknown parameters

Challenge 1.1 - White Dwarfs

Challenge 1.1.1 - Single Galactic Binaries
Challenge 1.1.2 - Verification Binaries
Challenge 1.1.3 - Resolvable Binaries
Challenge 1.1.4 - Source Confusion

Challenge 1.2 - MBHs

Challenge 1.2.1
Challenge 1.2.2

Challenge 1.3 - EMRIs

Since this challenge has different completion date, I’d suggest to have more data streams. We have agreed 5 data streams with SNR more or less equally spaced between ~30 and 100. Data set duration is 2 years. [Results are actually expected in June 2007, as part of challenge 2]

Challenge 1.3.1a,b,c,d,e
Comment on "2 and 4" years, some participants might not have PC with large RAM, but probably would want to read the whole data at 
once, that is the main reason behind 2 years of data. (SB)
Comment on physical params: I think the early challenges should concentrate on the stronger sources--BHs of about 10 Msun--
which we also expect to detect more of. LIkewise, might as well make the MBH about 10^6 (CC).
Comment on e=0.0: the inspirals get more eccentric at the end, not less, so I don't think e=0 is very realistic (CC).
Comment on challenge set-up: I'd favor breaking the EMRI challenge into 2: very bright sources (like the SNR =100 above) and 
the presumably more typical ones with SNR = 30 (in single IFO).  I think we should issue 2 different data sets: one with
a bright SNR=100 source, and one with SNR =30, since the methods for the 2 problems might be quite different.  The weaker
source should come will a restricted parameter range (e.g., we tell people a small patch on the sky to look in, and perhaps
a narrow mass range, to make up for our poor computational resources relative to 2015 (CC).
Comment on number of sources: As we discussed in the telecon, for each SNR (100 and 30) I think we should produce 2 data
sets: one w/ a single source and one with ~10 overlapping sources, since I can imagine some methods that might succeed for
the former but have real troubles w/ the latter (CC).
Comment on e=0.20: of course we have to say "when" it's 0.2; I'd suggest e=0.2 at very end of inspiral, or maybe
e=0.3  when the m=2 harmonic sweeps thru 3mHz (which amounts to pretty much the same thing, for a 10/10^6 pair) (CC).
Comment on e=0.20: I (AV) propose that we use: m1 = 10^6 and m2 = 10; e=0.3  when the m=2 harmonic sweeps thru 3mHz;
random parameters for the geometry and distance is adjusted in order to have the desired SNR

/* —————————– */

Challenge 2

Goal: Entirely dedicated to “global data analysis”
Release date: December 2006
Due date: June 2007

Challenge 2.1 - Galactic Foreground

Challenge 2.1 details

A ~2-yr long (to be precise: 2^22 data points with cadence 15 seconds) data set containing:

Note: This data set provides also the first challange for a non-stationary and anisotropic stochastic background

Challenge 2.2 - The Whole Enchilada ("Global data analysis")

Challenge 2.2 details

A ~2-yr long (to be precise: 2^22 data points with cadence 15 seconds) long data set containing:

Challenge 3

Goal: Test analysis adding more complex waveforms, new classes of signals and asymmetric instrument noise
Release date: December 2007
Due date: December 2008

The plan is to have a mixture of easy and difficult data sets that introduce new facets to the analysis. One new ingredient in some of the data sets will be “asymmetric” instrument noise, in which the strain spectral density of the shot and acceleration noise differs in each component.

Challenge 3.1 - Galactic binaries

Challenge 3.1.1
Challenge 3.1.2
Challenge 3.1.3

Challenge 3.2 - Massive black hole binaries

Challenge 3.2.1
Challenge 3.2.2

Challenge 3.3 - EMRIs

Challange 3.4 - Bursts

Challenge 3.4.1
Challenge 3.4.2
Challenge 3.4.3

Challange 3.5 - stochastic backgrounds

Challenge 3.5.1

Challenge 4

Goal: Test analysis with realistic noise behaviour (non-stationarities, non-Gaussianity, data dropouts..)
Release date: December 2007
Due date: June 2008

/* —————————– */

Discussion

/* —————————– */

As I have mentioned in the previous teleconference, I think we are missing a very important branch of challenges: we need to include more sophisticated (mean realistic) models in the latest challenges. It would be good to have another branch of challenges which aims at the detection of more complicated signals. For instance for galactic binaries it would mean including eccentricity, interacting binaries, etc,; for SMBH it would mean going to higher PPN orders, including spins, eccentricity and higher harmonics; for EMRIs it is including numerical kludge or even waveform based on the Teukolsky formalism.

* It was mentioned several times that we should not oversimplify the problem. Here I suggest to include study of more complicated signals starting with a “single source” challenge and introducing the confusion problem much later. Some numbers given for simplified models might not work that well for more complicated signals. One good example is parameter estimation for SMBH. We know that including the spins and higher harmonics can improve parameter estimation, and, since we want to study problem of issuing “early warning “, I think it is important to cover this in our challenges as well.

* My second point is that we can learn a lot from the study when the injected signal and templates do not match exactly. We use this strategy successfully for ground-based ifos. I am sure we can use the simplified models for detection in many cases, we need to learn whether we can estimate parameters as well (or rather “how well”). One of the problem we will face is removal of strong signals and estimation of residuals. Another reason is that we use some assumption when we model the GW signal, and the “best-of-our-knowledge” model might not match the true signal perfectly.

* My third point was already mentioned by Curt, the use of simple model and nice (hopefully) result of simplified analysis might make people too comfortable. This false comfort can hide the amount of work which has to be done in reality! Use of more complicated models might require NEW data analysis methods. This challenges should be introduced early enough, so people can start working on it. I do not suggest here to start running before we learned to crawl, I rather suggest to give people more time to think and start working in the directions outlined above.

Stas Babak, 19th April 2006