3 May 2011 VESF DA schoolD. Verkindt 1 Didier Verkindt Virgo-LAPP CNRS - Université de Savoie VESF Data Analysis School Data Quality and vetos.

Slides:



Advertisements
Similar presentations
S3/S4 BBH report Thomas Cokelaer LSC Meeting, Boston, 3-4 June 2006.
Advertisements

For the Collaboration GWDAW 2005 Status of inspiral search in C6 and C7 Virgo data Frédérique MARION.
GWDAW, Dec 2003 Shawhan, Christensen, Gonzalez1 LIGO Inspiral Veto Studies Peter Shawhan (LIGO Lab / Caltech) Nelson Christensen (Carleton College) Gabriela.
Veto Analysis Marina Del Prete Corso di Dottorato dell’ Universita’ di Siena It is a gravewave? Or did something locally create this ? Seismometer Dark.
Stefan Hild 1LSC/Virgo meeting, Baton Rouge, March 2007 Method for a safe statistical veto using IFO channels Stefan Hild (AEI Hannover) LSC/Virgo meeting,
GWDAW-10 (December 14, 2005, University of Texas at Brownsville, U.S.A.) Data conditioning and veto for TAMA burst analysis Masaki Ando and Koji Ishidoshiro.
GWDAW-8 (December 17-20, 2003, Milwaukee, Wisconsin, USA) Search for burst gravitational waves with TAMA data Masaki Ando Department of Physics, University.
E12 Report from the Burst Group Burst Analysis Group and the Glitch Investigation Team.
LIGO-G Z Coherent Coincident Analysis of LIGO Burst Candidates Laura Cadonati Massachusetts Institute of Technology LIGO Scientific Collaboration.
D Q 19 March. 2008LSC-Virgo meeting1 Status of Data Quality in Virgo D. Verkindt, LAPP-CNRS on behalf of the Virgo DQ team (M. Bizouard, L. Bosi, S. Chatterji,
Results from TOBAs Results from TOBAs Cross correlation analysis to search for a Stochastic Gravitational Wave Background University of Tokyo Ayaka Shoda.
Status of Virgo Gabriele Vajente INFN Pisa and Scuola Normale Superiore di Pisa On behalf of the Virgo Collaboration 11 th Gravitational Wave Data Analysis.
LIGO-G Z Detector characterization for LIGO burst searches Shourov K. Chatterji for the LIGO Scientific Collaboration 10 th Gravitational Wave.
S.Klimenko, G Z, December 21, 2006, GWDAW11 Coherent detection and reconstruction of burst events in S5 data S.Klimenko, University of Florida.
Virgo Commissioning update Gabriele Vajente for the Virgo Collaboration LSC/VIRGO Meeting – MIT 2007, July LIGO-G Z.
Gabriele Vajente ILIAS WG1 meeting - Perugia Couplings of angular noises into dark fringe Diffused light studies.
Adapting matched filtering searches for compact binary inspirals in LSC detector data. Chad Hanna – For the LIGO Scientific Collaboration.
The Role of Data Quality in S5 Burst Analyses Lindy Blackburn 1 for the LIGO Scientific Collaboration 1 Massachusetts Institute of Technology, Cambridge,
LIGO-G Z Peter Shawhan, for the LIGO Scientific Collaboration APS Meeting April 25, 2006 Search for Gravitational Wave Bursts in Data from the.
6-10 Oct 2002GREX 2002, Pisa D. Verkindt, LAPP 1 Virgo Data Acquisition D. Verkindt, LAPP DAQ Purpose DAQ Architecture Data Acquisition examples Connection.
GWDAW12, Dec , Cambridge MA1 Detection Confidence Tests for Burst and Inspiral Candidate Events Romain Gouaty *, for the LSC and the Virgo Collaboration.
Analysis of nonstationarity in LIGO S5 data using the NoiseFloorMon output A proposal for a seismic Data Quality flag. R. Stone for the LSC The Center.
Data Quality Vetoes in LIGO S5 Searches for Gravitational Wave Transients Laura Cadonati (MIT) For the LIGO Scientific Collaboration LIGO-G Z.
1 Data quality and veto studies for the S4 burst search: Where do we stand? Alessandra Di Credico Syracuse University LSC Meeting, Ann Arbor (UM) June.
The Analysis of Binary Inspiral Signals in LIGO Data Jun-Qi Guo Sept.25, 2007 Department of Physics and Astronomy The University of Mississippi LIGO Scientific.
GRBs & VIRGO C7 run Alessandra Corsi & E. Cuoco, F. Ricci.
LIGO-G Z April 2006 APS meeting Igor Yakushin (LLO, Caltech) Search for Gravitational Wave Bursts in LIGO’s S5 run Igor Yakushin (LLO, Caltech)
GWDAW11, Postdam 18th-21th December 2006 E. Cuoco, on behalf of Virgo collaboration 1 “Data quality studies for burst analysis of Virgo data acquired during.
18/01/01GEO data analysis meeting, Golm Issues in GW bursts Detection Soumya D. Mohanty AEI Outline of the talk Transient Tests (Transient=Burst) Establishing.
Veto Selection for Gravitational Wave Event Searches Erik Katsavounidis 1 and Peter Shawhan 2 1 Massachusetts Institute of Technology, Cambridge, MA 02139,
Status of coalescing binaries search activities in Virgo GWDAW 11 Status of coalescing binaries search activities in Virgo GWDAW Dec 2006 Leone.
LIGO-G Z Results of the LIGO-TAMA S2/DT8 Joint Bursts Search Patrick Sutton LIGO Laboratory, Caltech, for the LIGO-TAMA Joint Working Group.
Paolo La Penna ILIAS N5-WP1 meeting Noise analysis in Virgo Cascina, 7-8 July 2004 Analysis of noise in VIRGO.
1 LESSONS FROM VIRGO+ May 17th 2010 E. Calloni for the Virgo collaboration.
Searching for Gravitational Waves from Binary Inspirals with LIGO Duncan Brown University of Wisconsin-Milwaukee for the LIGO Scientific Collaboration.
D Q 20 Oct. 2007Quality flags, D.Verkindt1 Quality flags in Virgo Data Base D. Verkindt, LAPP On behalf of the Virgo « data quality task force »
HACR at Virgo: implementation and results Gabriele Vajente 12 th ILIAS WG1 meeting Geneva, March 29 th -30 th 2007.
1 Status of Search for Compact Binary Coalescences During LIGO’s Fifth Science Run Drew Keppel 1 for the LIGO Scientific Collaboration 1 California Institute.
LIGO-G Z The Q Pipeline search for gravitational-wave bursts with LIGO Shourov K. Chatterji for the LIGO Scientific Collaboration APS Meeting.
Gabriele Vajente ILIAS WG1 meeting - Frascati Noise Analysis Tools at Virgo.
S.Klimenko, G Z, December 2006, GWDAW11 Coherent detection and reconstruction of burst events in S5 data S.Klimenko, University of Florida for.
Joshua Smith, Elba, Italy Elba, Italy Joshua Smith for the GEO 600 team Picture of GEO in stormy weather?? Or pics of tractors with.
May 29, 2006 GWADW, Elba, May 27 - June 21 LIGO-G0200XX-00-M Data Quality Monitoring at LIGO John Zweizig LIGO / Caltech.
1 Locking in Virgo Matteo Barsuglia ILIAS, Cascina, July 7 th 2004.
The 9th Gravitational Wave Data Analysis Workshop (December 15-18, 2004, Annecy, France) Results of the search for burst gravitational waves with the TAMA300.
S.Klimenko, March 2003, LSC Burst Analysis in Wavelet Domain for multiple interferometers LIGO-G Z Sergey Klimenko University of Florida l Analysis.
LIGO-G All-Sky Burst Search in the First Year of the LSC S5 Run Laura Cadonati, UMass Amherst For the LIGO Scientific Collaboration GWDAW Meeting,
Results From the Low Threshold, Early S5, All-Sky Burst Search Laura Cadonati for the Burst Group LSC MIT November 5, 2006 G Z.
LSC meeting – Mar05 Livingston, LA A. Di Credico Syracuse University Glitch investigations with kleineWelle Reporting on work done by several people: L.
Detector Characterisation and Optimisation David Robertson University of Glasgow.
S.Klimenko, LSC, Marcht 2005, G Z BurstMon diagnostic of detector noise during S4 run S.Klimenko University of Florida l burstMon FOMs l S4 run.
Igor Yakushin, December 2004, GWDAW-9 LIGO-G Z Status of the untriggered burst search in S3 LIGO data Igor Yakushin (LIGO Livingston Observatory)
LIGO-G v1 Searching for Gravitational Waves from the Coalescence of High Mass Black Hole Binaries 2014 LIGO SURF Summer Seminar August 21 st, 2014.
November, 2009 STAC - Data Analysis Report 1 Data Analysis report November, 2009 Gianluca M Guidi Università di Urbino and INFN Firenze for the Virgo Collaboration.
Edwige Tournefier for the Virgo Collaboration The status of Virgo.
LIGO-G Z The Q Pipeline search for gravitational-wave bursts with LIGO Shourov K. Chatterji for the LIGO Scientific Collaboration APS Meeting.
LIGO-G05????-00-Z Detector characterization for LIGO burst searches Shourov K. Chatterji For the LIGO Scientific Collaboration 10 th Gravitational Wave.
Search for compact binary systems in LIGO data Craig Robinson On behalf of the LIGO Scientific Collaboration Cardiff University, U.K. LIGO-G
Thomas Cokelaer for the LIGO Scientific Collaboration Cardiff University, U.K. APS April Meeting, Jacksonville, FL 16 April 2007, LIGO-G Z Search.
Data Analysis report November, 2009 Gianluca M Guidi
SC03 failed results delayed FDS: parameter space searches
A 2 veto for Continuous Wave Searches
Back-scattered light noise in Virgo 2nd Science Run data
Advanced Virgo Detector Monitoring and Data Quality
Methods and Milestones
The Q Pipeline search for gravitational-wave bursts with LIGO
S3 Glitch Updates Laura Cadonati
Results from TOBAs Cross correlation analysis to search for a Stochastic Gravitational Wave Background University of Tokyo Ayaka Shoda M. Ando, K. Okada,
M.-A. Bizouard, F. Cavalier
Coherent Coincident Analysis of LIGO Burst Candidates
Presentation transcript:

3 May 2011 VESF DA schoolD. Verkindt 1 Didier Verkindt Virgo-LAPP CNRS - Université de Savoie VESF Data Analysis School Data Quality and vetos

3 May 2011 VESF DA schoolD. Verkindt 2 Outline  Why data analysis needs vetos  Some preliminary definitions  A simple data analysis tool: frequency band rms  Examples of glitches  Some useful tools  How to develop a quality flag  Performance of a DQ flag  Example of DQ flag used as veto

3 May 2011 VESF DA schoolD. Verkindt 3 Why data analysis needs vetos

3 May 2011 VESF DA schoolD. Verkindt 4 The Virgo interferometer is sensitive to several sources of noise: Most of them are non-stationary with various time scales and couplings  short glitches or long transient noisy periods Seismic noise coupled to diffused light Magnetic noise, powerline Injection system TCS system OMC alignment Etc… Why data analysis needs vetos

3 May 2011 VESF DA schoolD. Verkindt 5 The Virgo interferometer is sensitive to several sources of noise: Most of them are non-stationary with various time scales and couplings  short glitches or long transient noisy periods Seismic noise coupled to diffused light Magnetic noise, powerline Injection system TCS system OMC alignment Etc… Why data analysis needs vetos

3 May 2011 VESF DA schoolD. Verkindt 6 One interferometer like Virgo: High glitchiness, large SNR distribution tail  difficulty to separate real GW events from noise background Why data analysis needs vetos

3 May 2011 VESF DA schoolD. Verkindt 7 Several interferometers in coincidence (or in coherence): Lower glitchiness, but still highly non-gaussian SNR distribution tail  Reduced statistical significance of GW events versus background Why data analysis needs vetos freq < 200 Hz freq > 200 Hz

3 May 2011 VESF DA schoolD. Verkindt 8 Several interferometers in coincidence (or in coherence): Apply vetos in each detector’s data set  reduce the distribution tail  improve statistical significance of remaining loud events Why data analysis needs vetos

3 May 2011 VESF DA schoolD. Verkindt 9 Some preliminary definitions

3 May 2011 VESF DA schoolD. Verkindt 10 Some preliminary definitions GPS time Atomic time counted in seconds from January 1 st :00:00 UTC Example: = July 10 th :13:05 UTC Dark fringe / GW channel The channel which contains the GW signal (Pr_B1_Acp or h_16384Hz) Auxiliary channel Any channel recorded which contains information about ITF environment or ITF control SNR (Signal to Noise Ratio) Often defined by the power in the signal divided by the power in the noise background Trigger Event in the analyzed signal that fulfill the criteria of the data analysis pipeline Glitches Transient events in the analyzed signal whose origin is some noise source in the ITF Veto Conditions applied to reject data or data analysis triggers

3 May 2011 VESF DA schoolD. Verkindt 11 Some preliminary definitions GPS time Atomic time counted in seconds from January 1 st :00:00 UTC Example: = July 10 th :13:05 UTC Dark fringe / GW channel The channel which contains the GW signal (Pr_B1_Acp or h_16384Hz) Auxiliary channel Any channel recorded which contains information about ITF environment or ITF control SNR (Signal to Noise Ratio) Often defined by the power in the signal divided by the power in the noise background Trigger Event in the analyzed signal that fulfill the criteria of the data analysis pipeline Glitches Transient events in the analyzed signal whose origin is some noise source in the ITF Veto Conditions applied to reject data or data analysis triggers The environment channels AC* : acoustic channels SE* : seismic channels MA* : magnetometers channels The ITF channels Gx* : beam monitoring channels Bs* : injection system channels (Beam source) Sc_IB* : Suspension control of Injection Bench Sc_NE* : Suspension control of North End mirror The detection photodiodes channels Pr_B1* : Photodiodes signals for the B1 beam (output port after output MC) Pr_B5* : Photodiodes signals for the B1 beam (output port at BS reflective face) Pr_B7* : Photodiodes signals for the B1 beam (output port at North End) Pr_B8* : Photodiodes signals for the B1 beam (output port at West End)

3 May 2011 VESF DA schoolD. Verkindt 12 Some preliminary definitions GPS time Atomic time counted in seconds from January 1 st :00:00 UTC Example: = July 10 th :13:05 UTC Dark fringe / GW channel The channel which contains the GW signal (Pr_B1_Acp or h_16384Hz) Auxiliary channel Any channel recorded which contains information about ITF environment or ITF control SNR (Signal to Noise Ratio) Often defined by the power in the signal divided by the power in the noise background Trigger Event in the analyzed signal that fulfill the criteria of the data analysis pipeline Glitches Transient events in the analyzed signal whose origin is some noise source in the ITF Veto Conditions applied to reject data or data analysis triggers

3 May 2011 VESF DA schoolD. Verkindt 13 Some preliminary definitions Science mode segments Time periods where we consider the detector in good state for science data taking. DQ quality flag segment Time periods where we consider that detector in science mode may be affected by some transient noise source Padding Time extensions to be applied before and after each DQ flag segment. Dead-time Percentage of science mode time vetoed because of a DQ flag Efficiency Percentage of data analysis triggers vetoed by a DQ flag Use percentage Percentage of veto segments which covered at least one data analysis trigger

3 May 2011 VESF DA schoolD. Verkindt 14 Some preliminary definitions Science mode segments Time periods where we consider the detector in good state for science data taking. DQ quality flag segment Time periods where we consider that detector in science mode may be affected by some transient noise source Padding Time extensions to be applied before and after each DQ flag segment. Dead-time Percentage of science mode time vetoed because of a DQ flag Efficiency Percentage of data analysis triggers vetoed by a DQ flag Use percentage Percentage of veto segments which covered at least one data analysis trigger All Omega triggers with SNR>8 Omega triggers with SNR>8 within science mode segments

3 May 2011 VESF DA schoolD. Verkindt 15 Some useful tools for visualization and investigation

3 May 2011 VESF DA schoolD. Verkindt 16 Some useful tools: wscan The wscans: for each loud Omega trigger, look for coincident glitches in a predefined list of auxiliary channels and show associated time-frequency plots See Bs_IMC_DR_AC1Pr_B1_ACp

3 May 2011 VESF DA schoolD. Verkindt 17 Some useful tools: wscan The wscans gives also visual indication about glitch families

3 May 2011 VESF DA schoolD. Verkindt 18 Some useful tools: spectrograms Daily spectrograms gives also indications on the origin of some glitches See

3 May 2011 VESF DA schoolD. Verkindt 19 Some useful tools: dataDisplay dataDisplay allows you to visualize the frame formated data (vesf_rds.ffl, trend.ffl or brmsmon.ffl) And to see various channels in time or frequency domain Type dataDisplay

3 May 2011 VESF DA schoolD. Verkindt 20 Examples of glitches

3 May 2011 VESF DA schoolD. Verkindt 21 Some loud glitches periods well localized in time Many low SNR glitches associated to non-stationary frequency lines Example of glitches Local time (day/month) Frequency (Hz)

3 May 2011 VESF DA schoolD. Verkindt 22 Example of glitches Local time (day/month) Frequency (Hz) And more various types of glitches…

3 May 2011 VESF DA schoolD. Verkindt 23 Some glitches vetoed by seismic DQ flags Example of glitches

3 May 2011 VESF DA schoolD. Verkindt 24 Some glitches on which you will work Example of glitches Local time (day/month) Frequency (Hz)

3 May 2011 VESF DA schoolD. Verkindt 25 DQ flag production

3 May 2011 VESF DA schoolD. Verkindt 26 How is made a veto: general scheme Dark fringe signal Pr_B1_ACp Omega data analysis pipeline Omega triggers Auxiliary channel Em_SEBDNE01 Brms monitor Data Quality segments Coincidence Keep only Omega triggers which are out of DQ segments Auxiliary channel Em_SEBDNE01 KW pipeline KW triggers Or Keep only Omega triggers which are coincident with KW triggers of some well chosen aux. channels Two examples: Brms monitor and KW pipeline

3 May 2011 VESF DA schoolD. Verkindt 27 A simple data analysis tool: Frequency band rms

3 May 2011 VESF DA schoolD. Verkindt 28 Compute FFT of a signal Compute bandrms = FFT 2 integrated from fmin to fmax Compare bandrms to a threshold (fixed or adaptative) Frequency band RMS Bandrms Hz

3 May 2011 VESF DA schoolD. Verkindt 29 Compute FFT of a signal Compute bandrms = FFT 2 integrated from fmin to fmax Compare bandrms to a threshold (fixed or adaptative) Do this in a sliding time window Brmsmon algorithm Bandrms Hz

3 May 2011 VESF DA schoolD. Verkindt 30 How to develop a DQ flag Using the various tools previously presented, you choose some auxiliary channels and frequency bands useful for veto Now, you need to setup the parameters (frequency band and threshold) used by the brmsmon algorithm for each channel And to define what is the best way to use the results of each channel to define a DQ flag

3 May 2011 VESF DA schoolD. Verkindt 31 Keyword input file start GPS time duration FDIN_FILE /virgoData/ffl/vesf_rds.ffl Keyword list of input channels needed FDIN_TAG "Em_SEBDNE* Alp_Main_LOCK_STEP_STATUS Qc_Moni_ScienceMode“ Keyword output files nbr of frames per file channels to write in output file FDOUT_FILE data/V-BRSMonRepro "V1:BRMSMon*" Keyword flag name number of signals needed over th DQ_NAME SE_NE_16_256 2 Keyword channel name FFTlength fmin fmax th adaptative th time scale BRMS_CHANNEL Em_SEBDNE BRMS_CHANNEL Em_SEBDNE BRMS_CHANNEL Em_SEBDNE brmsmon algorithm

3 May 2011 VESF DA schoolD. Verkindt 32 How to develop a DQ flag You have produced the DQ flag values Now, you need to build the DQ segments (time periods where DQ flag is 1)

3 May 2011 VESF DA schoolD. Verkindt 33 Keyword input file start GPS time duration FDIN_FILE brmsmon.ffl Keyword list of input channels needed FDIN_TAG “BRMSMon*“ Keyword output dir period of segments file update SEG_ASCII /users/vesfuser 30 Keyword flag name segments file name comment SEG_FLAG BRMSMon_SE_NE_16_256 V1:SE_NE_16_256 “seismic activity" segonline algorithm

3 May 2011 VESF DA schoolD. Verkindt 34 DQ flag performances

3 May 2011 VESF DA schoolD. Verkindt 35 DQ flag performances First information about a DQ flag: its flagging rate It shows sometimes that quality flags are associated to well defined periods (for instance: seismic activity)

3 May 2011 VESF DA schoolD. Verkindt 36 DQ flag performances For each DQ flag produced, we then need to know some figure of merits: Deadtime: Does it veto too much data? Efficiency: Does it veto a good fraction of the glitches? Use percentage: Does it uses more segments than what would be useful? Eff/deadtime: Does it veto suitably or randomly? (low use percentage and efficiency/deadtime ~ 1 means that it vetoes randomly) DQ segmentScience mode segmentOmega trigger Efficiency=8/16=50% Use percentage=6/9=66% Deadtime=20s/90s=22% Eff./deadtime=50/22= s 0 s

3 May 2011 VESF DA schoolD. Verkindt 37 DQ flag performances Padding of DQ segments: According to the type of data analysis triggers you want submit to veto Or according to the type of glitches you expect to veto You need to search for an optimal padding of the DQ flag segments The padding is an extension of each DQ segment. For instance padding [-3,+2] applied to segment produces segment

3 May 2011 VESF DA schoolD. Verkindt 38 DQ flag performances One DQ flag result: Several loud triggers removed Good use percentage Low deadtime Efficiency Use Percentage Eff/deadtime SNR > 5 45/ = % 11/12= % SNR > 8 8/68389 = % 1/12= % SNR > 15 2/1058 = % 0/12=0% SNR > 30 0/124 =0% 0/12=0% 0 Deadtime: 21/ = %

3 May 2011 VESF DA schoolD. Verkindt 39 DQ flag performances Combine DQ flags: You can then choose the DQ flags of interest for your data analysis triggers and apply a OR of them. Resulting deadtime must not be too high (<10%) Resulting efficiency for loud triggers (SNR>15) must be above 50%

3 May 2011 VESF DA schoolD. Verkindt 40 VSR3 DQ flags performances Efficiency Use percentage Efficiency/deadtime SNR> % % 1.56 SNR> % % 3.08 SNR> % % 8.01 SNR> % 4.64 % Deadtime: % Example of combined DQ flags performances

3 May 2011 VESF DA schoolD. Verkindt 41 Last words Other types of vetoes: Event y event vetoes (like KW vetoes) Signal based vetoes (like waveform consistency check) Followup tests (check of detector status, check event’s pattern, coherence with aux. channels, etc…) The veto developments are a long-term (never-ending) activity It needs strong updates each time the interferometer’s configuration is changed. Vetos are not of marginal use even for coincidence/coherent analyses