LSC-Virgo Burst Analysis Working Group


Burst Group Home
ExtTrig Home
CBC Group Home
LSC, LIGO, Virgo


'How-to' docs
[2008, 2007, earlier]
Talks/Posters [pre-wiki]
Paper plans
White papers


Analysis projects
Old notebook [General, S2, S3, S4, S5]
Virgo workarea
External collabs


Main review page

Review Committee Meeting Monday 21 January 2008 08:00 Pacific / 11:00 Eastern

Minutes: Monday 21 January 2008 08:00 Pacific / 11:00 Eastern

Agenda and Contact Info


  1. Review of BurstMDC Simulation
  2. A.O.B.

Contact Info

InterCall telecon service:
   Phone: 1-866-380-5536, participant code: 435 672 9587 #
   International callers ++1-816-249-4731 with same code
   International access numbers (~10 cents/min surcharge for LIGO Lab):
      Paris 017 080 7156 ;
      Lyon 042 603 0036 ;
      Germany toll-free 0800 182 1591 ;
      Berlin 030 726 167 371 ;
      Rome 00645 217 080 ;
      UK toll-free 0808 234 7914 ;
      London 0203 107 0293
   Handy participant command:  Press *6 ["*M"] to mute, #6 to unmute
  1. Review of BurstMDC Simulation
    • Review of getopenloopgain
      • Note: if there are three args (but not four), third is ignored. Is this correct? Only used in a limited number of places....
      • Review of getolgfile
        • Review of getcalibrun
          • Review of ligorun
            • Not clear what the "end of run" means. Is it when the science run ends, or when the configuration actually changes? Depends on how the function is intended to be used.
            • ligorun seems OK but we did not check the actual GPS times.
          • getcalibrun seems OK.
        • Review of getcalibdir
          • Note that the environment LIGO_CALIB_DATA is required.
          • getcalibdir seems OK.
        • Some discussion about what should be the default calibration version. Should there be defaults?
        • getolgfile seems OK.
      • Review of readresponsefile
        • Review of getcommentstyle
          • Line 44: change ones(numStyle) to ones(numStyle,1)
          • getcommentstyle seems OK otherwise.
        • readresponsefile seems OK.
      • getopenloopgain seems OK.
    • Review of getsensefunction
      • Line 24: Change number of args required.
      • Line 26: AS_Q is default. Should this change?
      • Line 65: NUM_SIG = 3? Is this correct? At present, only AS_Q and DARM_ERR files. Do we need more at this time?
      • Review of getsffile
        • What if one requests DARM_ERR in S3? Should this routine fail or return the AS_Q calibration (as it currently does)?

          Option 1: Program should always try to avoid crashing, even if this means that something "good enough" is used.

          Option 2: Program should crash and burn if anything unexpected happens.

          Patrick Sutton and Jolien feel that Option 2 is the correct solution for data analysis. This is somewhat contrary to many aspects of the design of graven. Perhaps incremental shifts toward decreasing the number of default behaviors would be in order.

        • Otherwise getsffile seems OK.
      • Otherwise getsensefunction seems OK.
    • Digression into discussion of interpolation scheme used in h2asq_fd. Not clear how to do linear interpolation of complex numbers. Here it seems that the real and imag parts are interpolated individually. In LAL, Jolien has chosen to interpolate amplitude and phase. What is more correct? Probably shouldn't matter much.
    • This closes the review of the functions:
    • Action: Patrick will troll through minutes to see what functions have been reviewed and compare with dependency trees to see if anything has been missed. Will need to review some routines in gpsutils.
    • Next week we'll take up:
$Id: minutes-2008-01-21.html,v 1.5 2008/01/21 20:43:14 jolien Exp $