Burst Advocate Check List

1
Burst Advocate Check List

• Including notes from useful discussions with
  Anders, Luca B., Julie, Eduardo and the GRB group

2
Intro

• This is a Proposal for a check list for helping
  Burst Advocate during LEO
• Only for LEO (No hurry! Weekly time frame)
• Evolving (experience will drive this checklist)
• Four steps checklist
• Preparation/setup
• Monitoring
• Get the data/analysis
• Reports
• Special handling on GCN circulars during LEO
  require a formal approval

3
B/A D/S interactions

• Burst Advocate should have direct knowledge of
  the status of the instrument.
• Duty Scientist should be encouraged to
  participate to the meeting where the burst is
  discussed.
• I know D/S are busy but probably a 5 minutes
  log-in to say all is fine is not such a big
  deal!
• Tools for helping the interaction Data Quality
  Flags, DataMonitor, Reports

4
(GRB) Data Quality Flags

• Quality flags only the D/S should set the
  Quality Flags, with the responsibility of the
  S/C.
• Quality Flags for GRB Two level of data
  quality check.
• A) Required for first circulars (not needed in
  LEO).
• We will report position, time, intensity, only
  from onboard information
• Flag available Immediately at the burst. Burst
  data could have not been downloaded yet! This
  flag could flag the status of LAT at the latest
  downlink (warning! Not valid for analysis!)
• B) Required for analysis and second circular
• Second circular Detailed report of the burst
  characteristics.
• Flag only the portion of the data whit the GRB.
• Couple of hrs after the downlink.

5
a) Preparation/Set up/Acknowledge

• If you receive a GCN during your shift
• Acknowledge that you are going to be B/A for this
  burst. (lt30 minutes after the alert)
• Send an email to the GRB list and to the Shift
  list (is there a way to avoid duplicated mail?)
• No EVO meeting (we don't have onboard
  information)
• Contact the GBM Burst Advocate, or GBM Duty
  Scientist. (TRIGDAT data available few minutes
  after the GBM trigger)
• 2. Check if the Burst is in the LAT field of
  view.
• GBM burst TRIGDAT date provides this
  information.
• All bursts real time telemetry (could be a
  useful tool)
• 3. Open a confluence (you can use the template).
  Start filling it.
• 4. Check if the relative data are available.
  (Data Processing Tool)
• 6-12 hrs after the GCN notice ? go to next slide
• ASP could detect burst, also during LEO.

6
b) Monitoring

• 5. Check the LAT status
• Data quality flags (GRB quality flag)
• DataFastMon From the various plots that already
  exist, select few of them and create a GRB
  folder
• Collect the useful info info (quality flags,
  grb fastmon in a report (pdf)
  (http//glast-ground.slac.stanford.edu/Reports/)
• 6. Check ASP results (1 day) (ASPDataViewer)

7
c) Get the data/Analysis

• 8. Get the data (DataCatalog, GSSC)
• 9. Make your own analysis (Including Upper Limit)
• 10. Discuss the results with the GRB group

8
d) Reports

• 11 - Report the results (Confluence)
• 12- Add a B/A table (ASP viewer)
• 13 - Write a Circular (3 steps for formal
  approval)

9
EVO meeting for discussion the Circular

• Burst Advocate meets the GRB group in a EVO
  meeting to discuss the analysis and write the
  Circular
• Attendees B/A, GRB group, the Duty Scientist and
  Shift Coordinator (possibly).
• Authors All the participants
• Contact Author B/A
• Approval process
• First Circulars PI and 2 out of 6 publication
  board member
• Transition 2 out of 6 publication board members
• Plateau Science group leads.
• Circulars must be sent to the Publ. Board.
  Mailing list
• Circulars will be archived in the Publ. Board.
  Site.