November 16, 2016 Calibration

From GlueXWiki
Jump to: navigation, search

GlueX Calibration Meeting
Wednesday, November 16, 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
    • 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 .

Calibration Tasks

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

Upcoming Calibrations

  • Add timing information to FCAL clustering/inner ring calibrations? (Adesh/Matt S.)
  • BCAL TDC calibrations (Andrei)
  • TAGH alignment (Nathan)
  • Tagger energy map (Richard J.?)
  • TOF alignment (Beni/Simon)


  1. Announcements
  2. Reconstruction Launch
  3. Run Planning
    • fADC125 data (Naomi/Beni/?)
    • fADC250 data (Sean/Mark D./?)
    • Calibrations to run
      • New procedures: FCAL timing, BCAL timing, BCAL LED monitoring
  4. Calibration Updates
  5. Simulations
  6. AOB


Attending: Sean (NU); Simon, Paul M., Mark D., Thomas, Alex A., Nathan, Nacer (JLab); Naomi, Will M., Mike S. (CMU); Justin (W&M)

  1. Announcements
    • Beam is coming in the next few days. Short meeting as most people are in the hall preparing or at YStar workshop.
  2. Reconstruction Launch
    • Alex A. reports this is running well, about 85% done and expected to be done by Friday.
    • An analysis launch is planned for Monday.
  3. Run Planning
    • Naomi reports that after replacing a board, the f125 data looks good in the offline. There seems to be a lot of noise in the CDC that she is trying to understand.
      • Naomi: Is my noise problem related to the BCAL LED triggers running over the weekend? Sean: It seems worth checking out.
    • Sean reports that new f250 firmware was loaded over the weekend that correctly implement the timing algorithm specification. Unfortunately, the specification leads to some odd behaviors when running with NPEAK>1, such as later noise pulses being assigned times that come before the real pulses that are reconstructed. There are some other bugs and some rare oddities when taking BCAL pulser data. The fast electronics guys are looking into these issues, but in the meantime, we plan to take some data with the full pulses read out right at the beginning of the run to assess the error rate in photon beam data and to make a first look to see if adjusting readout thresholds would be helpful.
    • Sean has been adding new calibrations and redoing some performance studies on the calibration train before the run.
  4. Calibration Updates
    • Mike S. shared some preliminary results on the current status of residuals in the FDC and kinematic fit pulls. There is a substantial amount of alignment work that needs to be done, and the results of the kinematic fit should not be used for angular analyses. He is putting together a wiki page to organize an effort to improve the alignment status and will discuss this at the tracking meeting tomorrow.
  5. Simulations
    • Planning has begun on the next round of simulations, planning on at least 20% of the spring data. A certain amount of the simulations will be run with HDGeant4 to check its status.
    • Sean will coordinate updates on several sub-detectors. He shared a work plan for improving the status of the tracking in simulation.