9/23/08G080469-00-Z Status of the S5 calibration Michael Landry For the Calibration Committee LSC September 2008 Michael Landry For the Calibration Committee.

Slides:



Advertisements
Similar presentations
RECOVERING HARDWARE INJECTIONS IN LIGO S5 DATA Ashley Disbrow Carnegie Mellon University Roy Williams, Michele Vallisneri, Jonah Kanner LIGO SURF 2013.
Advertisements

LIGO-G Z S3/S4 Calibration A cast of thousands… including Peter Fritschel, Gabriela González, Corey Gray, Mike Landry, Greg Mendell, Brian O’Reilly,
LIGO-G Z Beating the spin-down limit on gravitational wave emission from the Crab pulsar Michael Landry LIGO Hanford Observatory for the LIGO.
1 What’s New in the Therapy Prior Authorization Review Process? December 2011 Therapy Clinical Webinars.
Kansas SMART (Statewide Management, Accounting, and Reporting Tool) Workflow for General Ledger.
Orchard Harvest™ LIS Review Results Training
© Devon M.Simmonds, 2007 CSC 550 Graduate Course in Software Engineering ______________________ Devon M. Simmonds Computer Science Department University.
LIGO- G Z March 22, 2006March 2006 LSC Meeting - DetChar 1 S5 Spectral Line Catalogue Status Keith Thorne (PSU) for the Spectral Line Catalogue.
LIGO-G D LIGO calibration during the S3 science run Michael Landry LIGO Hanford Observatory Justin Garofoli, Luca Matone, Hugh Radkins (LHO),
LIGO-G D 1 S3 expectations, S2 calibration M. Landry LHO CW Search Group F2F Milwaukee, Jun
LIGO- G Z AJW, Caltech, LIGO Project1 Use of detector calibration info in the burst group
1 Time-Domain Calibration Update Xavier Siemens, Mike Landry, Gaby Gonzalez, Brian O’Reilly, Martin Hewitson, Bruce Allen, Jolien Creighton.
ALLEGRO G Z LSC, Livingston 23 March, Calibration for the ALLEGRO resonant detector -- S2 and S4 Martin McHugh, Loyola University New Orleans.
SE-02 CONFIGURATION MANAGEMENT Today we talk about Software Configuration Management (SCM for short): - What? - Why? - How?
Systematic effects in gravitational-wave data analysis
GLAST LAT Project Test Planning Meeting Dec 5, 2005 E. do Couto e Silva 1/5 Final Proposal for Phase 1 and 2 SVAC, E2E Tests (hereafter LAT 70X, 80X) Eduardo,
Report From Joint Run Planning Committee R. Passaquieti & F. Raab - LSC / VIRGO Collaboration Meeting rd July 2007 – LIGO-G Z.
CLAS12 CalCom Activity CLAS Collaboration Meeting, March 6 th 2014.
1 Ist Virgo+ review Cascina H. Heitmann Alignment: Virgo+ changes.
Software Configuration Management (SCM)
S4/S5 Calibration The Calibration team G Z.
LIGO-G W News From Joint Run Planning Committee Roberto Passaquieti & Fred Raab 23May2007.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
LIGO- G Z AJW, Caltech, LIGO Project1 Use of detector calibration info in the burst group
LIGO- G Z LSC ASIS Meeting LIGO Scientific Collaboration - University of Wisconsin - Milwaukee 1 S2 Hardware Pulsar Injections Bruce.
Software Development Process and Management (or how to be officious and unpopular)
Calibration of LIGO data in the time domain X. Siemens, B. Allen, M. Hewitson, M. Landry.
1 What’s Next for Financial Management Line of Business (FMLoB)? AGA/GWSCPA 6 th Annual Conference Dianne Copeland, Director, FSIO May 8, 2007.
3/19/08G D S5 Calibration Status Brian O’Reilly For the Calibration Committee LSC March 2008 Brian O’Reilly For the Calibration Committee LSC.
LIGO-G I S5 calibration status Michael Landry LIGO Hanford Observatory for the LSC Calibration Committee LSC/Virgo Meeting May 22, 2007 Cascina,
The Project – Database Design. The following is the high mark band for the Database design: Analysed a given situation and produced and analysed a given.
The Role of Data Quality in S5 Burst Analyses Lindy Blackburn 1 for the LIGO Scientific Collaboration 1 Massachusetts Institute of Technology, Cambridge,
Software Engineering 2003 Jyrki Nummenmaa 1 CONFIGURATION MANAGEMENT Today we talk about Software Configuration Management (SCM for short): -
Scholarly Publication: Responsibilities for Authors and Reviewers Jean H. Shin, Ph.D. Director, Minority Affairs Program American Sociological Association.
Project Management All projects need to be “managed” –Cost (people-effort, tools, education, etc.) –schedule –deliverables and “associated” characteristics.
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.
Problem 3.26, when assumptions are violated 1. Estimates of terms: We can estimate the mean response for Failure Time for problem 3.26 from the data by.
3/30/04 16:14 1 Lessons Learned CERES Data Management Presented to GIST 21 “If the 3 laws of climate are calibrate, calibrate, calibrate, then the 3 laws.
DevelopersCommitters Users I’m getting the following exception…. Anybody have any clue why??? +1, I like that idea… Source & Binary Code Repository Bug.
LIGO-G DM. Landry – Hanover LSC Meeting, August 18, 2003 LIGO S2 Calibration Michael Landry LIGO Hanford Observatory Representing the calibration.
Software Configuration Management (SCM). Product Developer Disciplines One view of the world is that there are three types of activities are required.
15 Dec 2005GWDAW 10 LIGO-G Z1 Overview of LIGO Scientific Collaboration Inspiral Searches Alexander Dietz Louisiana State University for the LIGO.
Program Development Cycle
S5 BNS Inspiral Update Duncan Brown Caltech LIGO-G Z.
3/21/06G D S4/S5 Calibration Status Brian O’Reilly For the Calibration Committee LSC March 2006 Brian O’Reilly For the Calibration Committee LSC.
MODELING THE CALIBRATED RESPONSE OF THE ADVANCED LIGO DETECTORS Luke Burks 2013 LIGO Caltech SURF Mentors: Alan Weinstein, Jameson Rollins Final Presentation.
Offline Status Report A. Antonelli Summary presentation for KLOE General Meeting Outline: Reprocessing status DST production Data Quality MC production.
LIGO-G Z S2 and S3 calibration status Michael Landry LIGO Hanford Observatory for the Calibration team Justin Garofoli, Luca Matone, Hugh Radkins.
MNP1163/MANP1163 (Software Construction).  Minimizing complexity  Anticipating change  Constructing for verification  Reuse  Standards in software.
1 12th CAA Cross-Calibration meeting, Toulouse, Oct 2010 STAFF/SC Calibration & Cross-Calibration activities Patrick ROBERT & STAFF Team, LPP 2)
LIGO-G E1 Reviewer Report for the S2 Time-Domain Pulsar Search Teviet Creighton, Andri Gretarsson, Fred Raab, B. Sathyaprakash, Peter Shawhan.
LIGO- G D Experimental Upper Limit from LIGO on the Gravitational Waves from GRB Stan Whitcomb For the LIGO Scientific Collaboration Informal.
LSC Meeting LIGO Scientific Collaboration - University of Wisconsin - Milwaukee 1 Software Coordinator Report Alan Wiseman LIGO-G Z.
S.Klimenko, LSC, August 2004, G Z BurstMon S.Klimenko, A.Sazonov University of Florida l motivation & documentation l description & results l.
LIGO-G Z Detector Characterization SummaryK. Riles - University of Michigan 1 Summary of Detector Characterization Sessions Keith Riles (University.
LIGO-G Z Detector Characterization SummaryK. Riles - University of Michigan 1 Summary of Detector Characterization Sessions Keith Riles (University.
LIGO- G Z AJW, Caltech, LIGO Project1 First look at Injection of Burst Waveforms prior to S1 Alan Weinstein Caltech Burst UL WG LSC meeting, 8/21/02.
G Z August 17, 2004 S2/S3 Calibration Gabriela González, Louisiana State University For the Calibration Team ( cast of thousands!) LIGO Science.
ALLEGRO GWDAW-9, Annecy 16 December, Generating time domain strain data (h(t)) for the ALLEGRO resonant detector or calibration of ALLEGRO data.
LIGO-G Z Detector Characterization Summary K. Riles - University of Michigan 1 Summary of the Detector Characterization Sessions Keith.
LSC at LHO LIGO Scientific Collaboration - University of Wisconsin - Milwaukee 1 Summary of LSC Data Analysis Activities: Alan Wiseman G Z.
Calibration/validation of the AS_Q_FAST channels Rick Savage - LHO Stefanos Giampanis – Univ. Rochester ( Daniel Sigg – LHO )
LIGO-G E Data Simulation for the DMT John Zweizig LIGO/Caltech.
LIGO-G Z Status of the LIGO-TAMA Joint Bursts Search Patrick Sutton LIGO Laboratory, Caltech, for the LIGO-TAMA Joint Working Group.
Tau31 Tracking Efficiency at BaBar Ian Nugent UNIVERSITY OF VICTORIA Sept 2005 Outline Introduction  Decays Efficiency Charge Asymmetry Pt Dependence.
Welcome. Contents: 1.Organization’s Policies & Procedure 2.Internal Controls 3.Manager’s Financial Role 4.Procurement Process 5.Monthly Financial Report.
WEC meeting TED status and WEC timing.
S2/S3 calibration Gabriela González, Louisiana State University Plus
h(t): are you experienced?
Calibration: S2 update, S3 preliminaries
Presentation transcript:

9/23/08G Z Status of the S5 calibration Michael Landry For the Calibration Committee LSC September 2008 Michael Landry For the Calibration Committee LSC September 2008

9/23/08G Z Outline  h(f) Status  V3 summary.  V4 status - improvements.  Expectations for S6 calibration.  Next talk: Xavier Siemens: h(t) report  V3 h(t) - validation, systematics, hardware injections.  S6.  h(f) Status  V3 summary.  V4 status - improvements.  Expectations for S6 calibration.  Next talk: Xavier Siemens: h(t) report  V3 h(t) - validation, systematics, hardware injections.  S6.

9/23/08G Z V3 h(f) Calibration  Valid throughout S5, from Hz.  Employed in several publications (e.g. Crab, GRB070201, SGR).  DC values from V4 employed in final V3 calibration.  Valid throughout S5, from Hz.  Employed in several publications (e.g. Crab, GRB070201, SGR).  DC values from V4 employed in final V3 calibration.

9/23/08G Z Reminder of DC issues  Significant effort has gone into understanding the DC calibrations.  at the outset of S5, DC methods (3) disagreed at the 20% level.  Now, the multiple DC methods agree within the one-sigma error bars of the official method  Significant effort has gone into understanding the DC calibrations.  at the outset of S5, DC methods (3) disagreed at the 20% level.  Now, the multiple DC methods agree within the one-sigma error bars of the official method

9/23/08G Z Resultant V3 strains  DC calibration shifts  H1: 7.4%   H2: 6.2%   L1: 4%   High-water BNS marks for S5 shift accordingly to:  H Mpc   H2 7.3 Mpc   L1: 15.7 Mpc   DC calibration shifts  H1: 7.4%   H2: 6.2%   L1: 4%   High-water BNS marks for S5 shift accordingly to:  H Mpc   H2 7.3 Mpc   L1: 15.7 Mpc 

9/23/08G Z V3, V4 OLG Comparisons L1 V3 V4

9/23/08G Z Epochs Changes in Im(  ) occur due to changes in the detector configuration or time- delay shifts. We see time-delay shifts after front-end reboots. (<30  s) No new epochs for V4

9/23/08G Z Status of V4  Many improvements in OLG model, measurement agreement.  Time delay validation by direct measurements  Code mods and bug fixes (Pade approximation, sign error in complex conjugation)  Residuals aid high-frequency agreement  Request from burst group to go to 6.5kHz (as high as we can go, given the butterfly resonance).  L1 models complete, factors being generated.  H1, H2 models nearly done.  Many improvements in OLG model, measurement agreement.  Time delay validation by direct measurements  Code mods and bug fixes (Pade approximation, sign error in complex conjugation)  Residuals aid high-frequency agreement  Request from burst group to go to 6.5kHz (as high as we can go, given the butterfly resonance).  L1 models complete, factors being generated.  H1, H2 models nearly done.

9/23/08G Z What’s left?  Finalize H1, H2 models and generate files.  Produce error budget.  Release models for h(t) generation.  Release S5 V4 calibration documents.  Get reviewed.  Publish calibration papers.  Finalize H1, H2 models and generate files.  Produce error budget.  Release models for h(t) generation.  Release S5 V4 calibration documents.  Get reviewed.  Publish calibration papers.

9/23/08G Z Expectations for S6  New sensing scheme will modify the calibration some for S6. Otherwise, propose doing nothing new for this science run. Leverage what was learned in S5.  Have to have photon calibrators running in S6.  Our early calibrations for S5 were accurate at the level of 10% (plus systematics). Expect the same for S6, but with systematics correctly accounted for.  Need access to the machines prior to run in order to obtain h(f) and h(t) for online analyses.  Clearly we need to move to a quicker release of finalized h(t) for searches.  Recruitment of volunteers for h(t) was successful (see following talk), we’re recruiting for h(f).  DAC summit: we’ll ask the search groups, what calibration can they live with.  New sensing scheme will modify the calibration some for S6. Otherwise, propose doing nothing new for this science run. Leverage what was learned in S5.  Have to have photon calibrators running in S6.  Our early calibrations for S5 were accurate at the level of 10% (plus systematics). Expect the same for S6, but with systematics correctly accounted for.  Need access to the machines prior to run in order to obtain h(f) and h(t) for online analyses.  Clearly we need to move to a quicker release of finalized h(t) for searches.  Recruitment of volunteers for h(t) was successful (see following talk), we’re recruiting for h(f).  DAC summit: we’ll ask the search groups, what calibration can they live with.