Difference between revisions of "December 4, 2013 Calibration"

From GlueXWiki
Jump to: navigation, search
m (Text replacement - "/halldweb1.jlab.org/" to "/halldweb.jlab.org/")
 
(One intermediate revision by one other user not shown)
Line 18: Line 18:
 
# Status Update
 
# Status Update
 
# Tracking
 
# Tracking
#* CCDB Tables - [https://halldweb1.jlab.org/wiki/images/2/28/CDC_v0.2.pdf CDC] [https://halldweb1.jlab.org/wiki/images/8/89/FDC_v0.2.pdf FDC]
+
#* CCDB Tables - [https://halldweb.jlab.org/wiki/images/2/28/CDC_v0.2.pdf CDC] [https://halldweb.jlab.org/wiki/images/8/89/FDC_v0.2.pdf FDC]
 
# Calorimetry
 
# Calorimetry
 
# Other systems
 
# Other systems
Line 34: Line 34:
 
#** '''CDC:''' The tables used solely for MC should be moved into their own namespace for clarity.  Naomi asked for some text changes on the description for the drift distance tables.  
 
#** '''CDC:''' The tables used solely for MC should be moved into their own namespace for clarity.  Naomi asked for some text changes on the description for the drift distance tables.  
 
#** '''FDC:''' Mark suggested we should consider breaking up the tables for the cathode strips into separate tables.  Additional alignment constants will be needed beyond the current table for wire alignments, e.g. pitch, cathode deformations, etc.  Procedures for determining these are still being developed, but hopefully by next meeting we can define what of the potential constants would be.
 
#** '''FDC:''' Mark suggested we should consider breaking up the tables for the cathode strips into separate tables.  Additional alignment constants will be needed beyond the current table for wire alignments, e.g. pitch, cathode deformations, etc.  Procedures for determining these are still being developed, but hopefully by next meeting we can define what of the potential constants would be.
 +
#* Some of the tables exist for historical reasons.  A separate software meeting is needed to go through and figure out which should be deprecated.
 
#* Simon is working on FDC alignment using straight tracks.
 
#* Simon is working on FDC alignment using straight tracks.
 
# Calorimetry
 
# Calorimetry

Latest revision as of 19:17, 31 March 2015

Meeting Time and Place

Wednesday December 4, 2013 at 11:00am At Jefferson Lab, the meeting will be held in F326

Connections

To connect from the outside, please use ESNET

  1. ) ESNET: 8542553
  2. )To connect by telephone, dial:
  • You can look up toll-free number at http://www.readytalk.com/intl
  • US and Canada: (866)740-1260 (toll free)
  • International: (303)248-0285 (toll call)
  • enter access code followed by the # sign: 3421244#

Agenda

  1. Announcements
  2. Status Update
  3. Tracking
  4. Calorimetry
  5. Other systems


Minutes

Attending: Sean, Amiran (NU); Mark, Lubomir, Simon, Beni (JLab); Curtis, Naomi, Paul (CMU); Sasha (FSU)

  1. Announcements
    • Curtis mentioned two comments from the recent software review: (1) using the L3 trigger to tag events to be later used in calibration procedures; (2) testing calibration procedures using simulated data. As the definition of tables is progressing, we should start tracking progress in procedure development/testing.
  2. Tracking
    • New sets of table definitions were discussed:
      • CDC: The tables used solely for MC should be moved into their own namespace for clarity. Naomi asked for some text changes on the description for the drift distance tables.
      • FDC: Mark suggested we should consider breaking up the tables for the cathode strips into separate tables. Additional alignment constants will be needed beyond the current table for wire alignments, e.g. pitch, cathode deformations, etc. Procedures for determining these are still being developed, but hopefully by next meeting we can define what of the potential constants would be.
    • Some of the tables exist for historical reasons. A separate software meeting is needed to go through and figure out which should be deprecated.
    • Simon is working on FDC alignment using straight tracks.
  3. Calorimetry
    • BCAL discussion is delayed until next week. Sean will follow up with Matt on FCAL constants.
  4. Other systems
    • Sasha presented a comprehensive list of the constants needed for the TOF system
    • The high voltage constants are used for determining other calibration constants and for the slow controls, and therefore don't need to be stored in the CCDB.
    • The functional form of the time-walk corrections is still being determined. The per X-Y intersection (second-order?) time-walk corrections will need actual data to be determined.
    • There seems to be some room for consolidation in the TDC constants needed.
    • Sean will distill this into a concrete proposal for CCDB tables.