January 27, 2016 Calibration

From GlueXWiki
Jump to: navigation, search

GlueX Calibration Meeting
Wednesday, January 27, 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. Announcements
  2. Collaboration Meeting
  3. Calibration Tasks
  4. Subdetector Reports
  5. Future Simulations
    • Simulations will start with run 10000 to match beginning of run period.
  6. AOB


Attending: Sean (NU); Simon, Paul M., Mark I., David L., Luke, Alex B., Justin (JLab); Eric, Mahmoud (FIU); Curtis, Will, Naomi (CMU); Matt S. (IU); Cristiano (MIT)

  1. Announcements
    • Accelerator still on schedule.
    • Solenoid is filled with Helium, testing to begin next Wednesday.
    • Daily run meetings to start next week.
  2. Collaboration Meeting
    • Sean will give an overview talk on the status of calibrations. We discussed what other software talks might be given, Mark will revisit next Offline meeting.
  3. Calibration Tasks
    • Sean updated the list of data amounts required for calibrations based on information presented at the run meetings. An open question is the amount of data needed to calibrate the outer rings of the FCAL.
    • After the Physics meeting on Monday, Sean drew up an initial list of reconstruction items that should be addressed in the short term (Spring/Summer). The focus is on understanding the reconstruction efficiencies of physics objects and putting more realistic resolutions into the reconstruction (many are hardcoded or incomplete). The key step for detector groups is getting resolution parameterizations into the CCDB - these can then be integrated into the reconstrucion. Mahmoud and Sean have already done so for the Start Counter. This list can be a regular item for discussion.
      • Simulations will also need to be tuned to match the data - this is a related but more complicated question that needs to be addressed.
    • Calibration Challenge: Sean has added some more recent plugins. He is currently tracking down an issue with how the challenge setup affects the RF calibration that is throwing off the results.
  4. Subdetector Reports
    • Summary: Most people are busy preparing hardware for the run, or awaiting new data.
    • FCAL - Matt reported that John Z. and Adesh are working to fix bad channels before the run. Adesh's latest pi0 calibration gives good pi0 masses and pi0 energy resolution close to design. The next step is to understand the non-linearities of the energy dependence. Adesh and John are also working on timing calibrations.
    • BCAL - Beni took cosmic data over the weekend which can be used for calibrations.
    • CDC - Mike S. is working on calibrations with the new fADC125 algorithm - he is on vacation so no news on that. In press: Sean forgot to mention that he is working with Cristiano (from MIT) on some issues related to electron reconstruction.
    • Start Counter - Mahmoud is now working on a plugin to perform the attenuation corrections, so be ready for the new data when it arrives.
    • TOF - Mark reported that Beni has performed a calibration of the CAEN TDCs. The parameters have been passed to the online group.
    • Other issues
      • Sean reported that the scripts for processing online monitoring data and publishing it to the website are working, but need to keep an eye on if the files are properly being shipped from the counting house.
      • There will be another offline monitoring run this weekend. After that, Paul will take another look at the scripts used to run over the data as it comes in.
      • It would be good to let the CC know that our farm usage will be high during data taking.
        • Justin mentioned that if you submit jobs to the farm that request at least 24 threads, it will be matched to a queue of "exclusive" nodes, where one job runs on one node. There are currently 4 of these nodes, but Sandy mentioned that they could move more nodes to exclusive status if there is demand for it. We do want the farm to move in this direction, to take full advantage of multithreading. We may want to invite Sandy to the next Offline meeting.
      • David reported that he's added (untested) support for the beginning-of-run (BOR) record to the online and offline software. This would be an entry created at the beginning of the run and appended to the beginning of all raw data files. The primary use to store firmware configuration values for decoding raw data, instead of including the values with every event, and are read directly from the modules over VME. This system is flexible enough that other information can be stored.
        • The BOR and EPICS events have been flagged as "barrier" events, so that they are always processed in the correct order in multithreaded running.
  5. Future Simulations
    • Simulations will start with run 10000 to match beginning of run period.
    • The conditions and software are ready. Mark has run some test jobs.
    • We'd like to generate as many simulations as possible before data taking starts.
    • The volatile disk was overwhelmed with files from DC3. Mark has requested more space.
  6. AOB