Difference between revisions of "January 28, 2015 Calibration"

From GlueXWiki
Jump to: navigation, search
(Agenda)
(Timing Offset Calibrations)
Line 51: Line 51:
 
* tests with other runs for stability and robustness of calibrations
 
* tests with other runs for stability and robustness of calibrations
 
* monitoring of results
 
* monitoring of results
 +
* investigate automated running of procedure (once/twice a day? offline v. online farms?)
  
 
=== REST file status ===
 
=== REST file status ===

Revision as of 17:05, 28 January 2015

GlueX Calibration Meeting
Wednesday, January 28, 2014
11:00 am, EDT
JLab: CEBAF Center, F326

Connection Using Bluejeans

  1. To join via Polycom room system go to the IP Address: 199.48.152.152 (bjn.vc) and enter the meeting ID: 630804895.
  2. To join via a Web Browser, go to the page [1] https://bluejeans.com/630804895.
  3. To join via phone, use one of the following numbers and the Conference ID: 630804895
    • US or Canada: +1 408 740 7256 or
    • US or Canada: +1 888 240 2560
  4. Upon connection all microphones are automatically muted. To unmute your mike on a Polycom or equivalent unit, enter *4
  5. More information on connecting to bluejeans is available.

Agenda

  1. Announcements
    1. Software Review, February 10-11, 2015
    2. Collaboration Meeting February 19-21 at Jefferson Lab
  2. Timing Offset Calibrations (Mike S.)
  3. REST data status (Justin)
  4. Calibration status/updates
    1. FCAL
    2. BCAL
    3. CDC
    4. FDC
    5. TOF
    6. Start Counter
    7. TAGH
    8. TAGM
    9. Calibration Dashboard
  5. Simulations
  6. Data Monitoring
    1. Status Update (Kei)
    2. Commissioning Software
    3. Run Browser, Plot Browser, and Time Series webpages
  7. AOB

Minutes

Attending: Sean (NU); Simon, Mike S., Paul, Mark I., Mark D., Nathan, Adesh, Eric, Alex B., Will M., Lubomir, Eugene, Beni, Kei (JLab); Curtis, Naomi (CMU); Justin (MIT); Mahmoud (FIU); Andrei (Regina)

Timing Offset Calibrations

Mike Staib gave a report on his work on automatically calculating timing offsets for the whole detector. This procedure leverages the tracking information, and takes into account the correlations. He starts with all time offsets set to zero, first does a rough timing alignment on the calibrated hit objects, then does a rough calibration of the TDC times with respect to the ADC times, and finally uses negative tracks to calculate offsets relative to the start counter time and derive a finer calibration (in some cases, per-channel). He gets calibrations that looks as good as those currently in the CCDB, sometimes better. For example, the start counter timing resolution for his example run was reduced from 1.4 ns to 1.1 ns, and a larger number of tracks were reconstructed.

There was some discussion about how to best structure this effort. This plugin gives a good start on timing calibrations, but the ultimate calibrations should be done by the detector groups which have the best understanding of their detector. Either Mike's procedure will need to be modular enough so that other people can contribute, or more refined efforts can build on top of these calibrations. A major open question is how interdependent these calibrations are, e.g., if a small epsilon change in one detector necessarily means that we need to recalibrate all subsystems.

  • tools for submission of constants to central CCDB
  • tests with other runs for stability and robustness of calibrations
  • monitoring of results
  • investigate automated running of procedure (once/twice a day? offline v. online farms?)

REST file status

  1. Timing Offset Calibrations (Mike S.)
  2. REST data status (Justin)
  3. Calibration status/updates
    1. FCAL
    2. BCAL
    3. CDC
    4. FDC
    5. TOF
    6. Start Counter
    7. TAGH
    8. TAGM
    9. Calibration Dashboard
  4. Simulations
  5. Data Monitoring
    1. Status Update (Kei)
    2. Commissioning Software
    3. Run Browser, Plot Browser, and Time Series webpages
  6. AOB