June 1, 2016 Calibration

From GlueXWiki
Jump to: navigation, search

GlueX Calibration Meeting
Wednesday, June 1, 2016
11:00 am, EST
JLab: CEBAF Center, F326

Communication Information

Remote Connection

You can connect using BlueJeans using the meeting number 630 804 895 .       (Click "Expand" to the right for more details -->):

  1. Make sure you have created a BlueJeans account via your JLab CUE account using this link:

  2. Meeting ID: 630804895
    • (you may need to type this in, depending how you connect)

  3. If connecting via Web Browser: click this link (no passcode is needed):

  4. If connecting via iOS or Android App:
    • Use your JLab e-mail address to log in and then enter the meeting ID given above to join the meeting

  5. If connecting via Phone: Dial one of the following numbers and then enter the meeting ID above and hit "#" or "##"

  6. If connecting via Polycom unit:
    • Dial or bjn.vc
    • Enter meeting ID above
    • Use *4 to unmute


Talks can be deposited in the directory /group/halld/www/halldweb/html/talks/2016 on the JLab CUE. This directory is accessible from the web at https://halldweb.jlab.org/talks/2016/ .

Calibration Tasks

  1. Spring 2016 Recon Checklist
  2. Mcsmear updates - mcsmear 20160323
  3. GlueX Detector Performance Document
  4. Data Validation
  5. Calibration Train


  1. Announcements
    • sim-recon/CCDB deadline: Thursday, 5 PM
  2. Calibrations for REST Production
  3. Subdetector Reports
  4. Simulations
    • sim1.1 for data/simulation matching studies
      • conditions matching spring data
      • run ranges to generate
  5. AOB


Attending: Sean (NU); Simon, Elton, Paul, Mark D., Adesh, Eugene, Alex B., Justin, Alex A., Beni (JLab); Naomi, Will M., Mike S. (CMU)

  1. Announcements
    • The deadline for additions to sim-recon and CCDB for the start of the production run is Thursday, 5 PM
    • There was a power outage for several hours last night. The Solenoid seems to be okay.
  2. Calibrations for REST Production
    • Sean went over a few firmware issues that were calibrated away but will hopefully be fixed over the summer.
    • Priority run updates
      • Detailed updates of the calibrations for the priority runs were given in yesterday's Analysis meeting. The to-do list was updated based on that meeting.
      • Simon is finalizing his geometry updates.
      • Mike S. added some code to fix some issues with multiple scattering in the tracker
      • Adesh is going to update the FCAL gains today. He might not be finished with the non-linear corrections by Friday.
      • Will has updated the BCAL gains.
    • 500 Mhz data status
      • Sean presented the results of a quick look at the results of analyzing a run with 4 ns and 2 ns bunch spacing. The results for 2 ns runs look generally comparable to those in our priority data. The TAGM timewalks and offsets do need particular attention for these runs. Sean mentioned that we may need to look at some column-dependent handling of the results.
      • Mike S. will upgrade the time to distance relation and any other CDC calibrations that are changed by the different magnetic field (1200A -> 1345A). He said that this will be simple, most of the work is checking to see that it properly applies to these runs.
      • We agreed to discuss the deadline for these calibrations in the Analysis meeting next Tuesday.
  3. Subdetector Reports
    • Beni reported that the efficiency in the inner part of the TOF is low (~90% compared to >95%). This may be correlated to differences in timewalk corrections and higher rates. Paul mentioned that he was the last person to rework the track/TOF matching code and offered to answer any questions.
    • Nathan reported that in the process of calibrating the TAGH, he found a long-time cable swap between counters 3 and 5, which will be fixed before the launch.
  4. Simulations
    • Sean has generated a first set of conditions for simulations that match this data. Needs to check to make sure the beam bunch spacing is correctly reproduced. Simulated data with similar conditions (and run numbers) to the actual data will be produced.
    • Paul suggested that a sample on the order of the size of sim1 will be enough for resolution/efficiency update studies.