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 18 February 2008 08:00 Pacific / 11:00 Eastern

Minutes: Monday 18 February 2008 08:00 Pacific / 11:00 Eastern

Agenda and Contact Info


  1. Announcements
  2. Reports from Burst Review Teams
  3. Review of BurstMDC Simulation
    • What's left to do? [ PDF ]
    • GravEn code [ HTML ]
    • BurstMDC Bulletin Board [ HTML ]
  4. 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. Announcements: SGR-Flare Search vs. 1st Year All-Sky S5 Search
    • Options for handling cWB part of review:
      1. Drop cWB from SGR-Flare analysis: cWB and Flare have similar sensitivities; alleviates questions about how to obtain a single result; allows reviewing of cWB for 1st year all-sky search ASAP.
      2. Include cWB in the SGR-Flare analysis and schedule review of this use of cWB first with the 1st year all-sky search to follow the conclusion of the SGR-Flare review.
      3. Include cWB in the SGR-Flare analysis and have a team reviewing this in parallel with the team reviewing the 1st-year all-sky search. This requires more cWB-savvy reviewers!
    • Peter will chat with Sergey and come to some conclusion about how he wishes to proceed.
  2. Reports from Burst Review Teams: No report.
  3. Review of BurstMDC Simulation
    • Patrick will send Keith the PPT of the code tree diagram so that Keith can mark those routines that need to be reviewed.
    • Looked at gpssum, gpsdiff, etc. test cases. These look good. Worry about small errors: these may grow bigger for large GPS times. Need to check circa 1000000000 seconds after the GPS epoch. Also suggest running a bunch of random times to make sure that there are no holes due to even spacings.
    • Interpolation in BurstMDC. Worried that linear interpolation is a low-pass filter. This will affect high frequency injections most. Proper interpolation is sinc interpolation. Can done efficiently by taking a FFT, applying a complex phase shift, then taking the inverse FFT. Perhaps there is a matlab routine that does this already.
    • Need to review logfile generation routine.
  4. A.O.B.
$Id: minutes-2008-02-18.html,v 1.3 2008/02/25 21:01:39 jolien Exp $