LIGO-G Z LSC Nov 5, Bruce Allen, U. Wisconsin - Milwaukee and AEI

LIGO-G Z LSC Nov 5, Overview Status of -Users, credits, size -Officially funded as a project by NSF! Status of the “old style” S3 analysis -Done and reviewed! Status of the S4 analysis -Postprocessing underway since mid-summer, still ongoing -First careful estimation of search sensitivity (for practice, not for publication!) Status of the S5 analysis ( workunits x 5 CPU hours x 2) -Processing 49% complete -About 100 more days of processing to go server/project up and operational with no glitches for 143 days! Status of the upcoming hierarchial S5 analysis -First CW analysis that integrates long (> 30 min) coherent and an incoherent methods -Gives us the optimal sensitivity for our CPU power -No large data transfers to or from the host machines.

LIGO-G Z LSC Nov 5, How big is

LIGO-G Z LSC Nov 5, User/Credit History

LIGO-G Z LSC Nov 5, Users/Hosts History

LIGO-G Z LSC Nov 5, Current performance is currently getting 84 Tflops

LIGO-G Z LSC Nov 5, Status of S3 Analysis Finished: -Final S3 analysis and writeup have been reviewed and approved by the CW Review Committee and the LSC Executive Committee. -Results are posted on the web site. -We didn’t find any CW sources

LIGO-G Z Overview of S4 analysis Coherently analyzed 30-hour data stretches (10 LHO, 7 LLO) 540 hours total. Spanned times vary, but all < 40 hours. Searched 50 Hz Hz in 6,731,410 work units from to Near optimal grid (within ~2) on the sky and in frequency and df/dt Explicit search over spindowns (df/dt) corresponding to pulsars older than a few thousand years. Previous searches had |df/dt|<1/(integration time) 2. Each host searches the entire sky and fdot range and a variable-sized region of frequency df ~ f -3 and one stretch of data. It then returns list of ‘top 13,000 events’. Range of frequency that decreases with increasing frequency as f^-3 f 1,000 years f  300 Hz: mismatch 0.5, spin-down ages > 10,000 years Each workunit produces a compressed data file that is about 150kB in size. The total data volume to post-process is 1 TB (compressed) or 4 TB (uncompressed). Many hardware improvements “behind the scenes” to handle this data volume and permit postprocessing on Nemo cluster.

LIGO-G Z LSC Nov 5, S4 post-processing coincidence strategy Search for signals that appear in each of the 17 different data stretches, with consistent parameters Steps: -Shift candidate frequencies to a fixed fiducial time -‘Bin’ candidates in four dimensions (alpha, delta, f, fdot) -Search for bins which have candidates from many of the 17 data stretches Span entire sky, entire frequency band, entire fdot band. Bins are chosen to be as small as possible, consistent with: -Sky bin size > largest grid separations (use Gaussian model in delta) -Frequency bin size > frequency resolution + (grid spacing in fdot) x T -Fdot bin size > Fdot grid spacing Bins are also shifted by 1/2 the bin width in all 2^4 combinations, so as not to miss any candidates on opposite sides of cell faces.

LIGO-G Z LSC Nov 5, How many events to keep? Goal: constant false alarm probability per data stretch per coincidence cell. Why: in the coincidence analysis, this makes it easier to interpret the results and to predict false alarm probability. How: in a given frequency band, keep the same number of events from each data stretch. How many events to keep: to get a false alarm probability of 0.1% to find 7 or more coincidences (out of 17) in random noise in a 1/2 Hz band. Example: band Hz: -Data stretch 1 (10 workunits): keep top 1000 events per workunit -Data stretch 2 (5 workunits): keep top 2000 events per workunit -Data stretch 3 (8 workunits): keep top 1250 events per workunit … -Data stretch 17 (20 workunits): keep top 500 events per workunit

LIGO-G Z LSC Nov 5, Coincidence Analysis Grids Typical sky grid has points separated more broadly near the equator. Each of the 17 data segments has a different grid In doing the coincidence analysis we use a Gaussian fit to the declination differences to ensure that we don’t miss correlated events.

LIGO-G Z LSC Nov 5, Sample results ( Hz) Number of events: 54,841 x 17 per 1/2 Hz Number of coincidence cells per 1/2 Hz: 5,398,250 Max coincidences found: 5

LIGO-G Z LSC Nov 5, Sample results ( Hz) Number of events: 166,033 x 17 per 1/2 Hz Number of coincidence cells per 1/2 Hz: 19,747,000 Max coincidences found: 7 (Line: “Yousuke’s 8 Hz comb”, only in L1)

LIGO-G Z LSC Nov 5, Sample results ( Hz) Number of events: 40,364 x 17 per 1/2 Hz Number of coincidence cells per 1/2 Hz: 5,398,250 Max coincidences found: 11 This is fake pulsar #3. Injection was off for 5 of the 17 data stretches.

LIGO-G Z LSC Nov 5, Complete S4 results ( Hz) More work still needed: -Postprocessing being repeated to fix some mistakes made the first time (wrong counting of coincidence cells led to wrong false alarm rate). -After removal of hardware injections, need to follow up outliers

LIGO-G Z LSC Nov 5, Determining S4 sensitivity Holger Pletsch has developed methods to estimate the sensitivity and has tested this using software injections. For a given signal, did analytic estimate the 2F values in each of the 17 data segments to determine how many times it falls in the top list of candidates. This method correctly predicts how many coincidences would be observed. Repeat for 500 randomly placed and oriented simulated signals per 0.5 Hz band Note: v1 calibration

LIGO-G Z LSC Nov 5, Current S5 run Very similar to previous S4 run, but more data (22 x 30 hours) which is also more sensitive Postprocessing not even started yet Search has been underway for about 140 days About 100 days of work left

LIGO-G Z LSC Nov 5, Next S5 Search The CW group is planning to start running the first true hierarchical search in about 3 months! All-sky, TBD: f years A new search code (union of multi-detector Fstat and Hough). A stack- slide incoherent option is also “in the works”. This will use approximately 96 x 20 hours of coincident H1/L1 data (adding strains to gain factor of sqrt(2) in strain sensitivity) Combines coherent Fstat method with incoherent Hough method (48 25-hour stacks) Many CW group members are working very hard on this: Krishnan, Prix, Machenschalk, Siemens, Hammer, Mendell, Sintes, Papa, and others. Should permit a search that extends hundreds of pc into the Galaxy This should become the most sensitive blind CW search possible with current knowledge and technology As soon as we can: a coherent follow-up integration stage.

LIGO-G Z LSC Nov 5, Next S5 search: data selection T data = N stack T coherent and h min ~ T coherent -1/2 N stack -1/4 Constraints and tradeoffs -Practical: smaller data T data volume is good for users; larger data volume gives more sensitivity & confidence -Sensitivity: larger T coherent gives more sensitivity but less data. Coincident data increases sensitivity by sqrt(2) but yields less data -CPU cost: larger T coherent increases cost of coherent stage relative to incoherent Hough stage Study carried out by Siemens, Prix, and Krishnan -Determine much data would be available as a function of T coherent with and without 2-detector coincidence -Extrapolate to January 2007, and estimate –sensitivity h min –total data volume T data –computational cost = sum of the two different search stages

LIGO-G Z LSC Nov 5, Next S5 search: data selection Tdata Tstack Nstack hmin CPU_inc CPU_coh CPU data_volume 12h 16h h 20h h 25h … LHO LLO … … TdataTstack LHO LLO Tdata Tstack Nstack hmin CPU_inc CPU_coh CPU data_volume 12h 16h h 20h h 25h

LIGO-G Z LSC Nov 5, Coherent + incoherent “merge” FFT … Keep 1/5 of peaks (lots of data!) Make Hough maps Fstat … Keep 1/4 of peaks Too much data to store or transmit Make Hough maps For the multi-IFO Fstat (Code 1) and Hough (Code 2) had to be merged into a single stand-alone executable that could pass the needed data between the two stages. This has been done by Krishnan. Also planned: integrate the Stack-Slide incoherent step as an alternative to Hough. Current Hough analysis Integrated code for analysis Code 1Code 2 Detector Frequency Source Frequency Time

LIGO-G Z LSC Nov 5, Conclusions is healthy and growing, and providing 10x more CPU cycles than other LSC resources. S4 analysis postprocessing is making good progess. First reliable estimates of the sensitivity. Similar S5 analysis should be finished in months. Ambitions plans to run the first true hierarchical search under on S5 data in just a few months.