January 13, 2016 Calibration

From GlueXWiki
Revision as of 16:13, 24 February 2017 by Marki (Talk | contribs) (Text replacement - "http://argus.phys.uregina.ca/cgi-bin/private" to "https://halldweb.jlab.org/doc-private")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

GlueX Calibration Meeting
Wednesday, January 13, 2015
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
  6. AOB


Attending: Sean (NU); Simon, Paul M., Nathan, Justin, Alex B. (JLab); Curtis, Mike S., Will M., Naomi (CMU); Mahmoud (FIU)

  1. Announcements
    • Low attendance due to run coordination meeting that ran late; start of meeting pushed back 45 minutes
    • Spring running is planned with multiple concurrent triggers, this information is now in the data stream. The exact definition of the triggers is believed to be still under development.
    • Paul asked if a new monitoring run was needed and which data sets should be run over. There have been several sim-recon updates, so he will run over the Spring and Fall 2015 data this weekend. The deadline to get code in for this run is 3 PM on Friday.
  2. Time to start thinking about Collaboration meeting talks
  3. Calibration Tasks
    • Calibration Challenge update: The jobs all finish, but the current run (which hasn't finished), is the first starting with zero-ed out constants. Sean had run into some poorly-understood CCDB problems which have been worked around. Going forward, we'll need to think of how to adapt our accounting/profile tools to deal with multi-pass workflows. He is currently working on presenting the results in a useful format.
    • Tagging calibration events: We started discussing the prospects for tagging events in L3, where full reconstruction would not be available. According to Justin, in the spring run the L3 is just being commissioned, so this would be mostly useful as a proof of concept. If we tag events using the JANA Event Tag feature, there are 64 different tags available for all tasks, so we need to come up with a menu of the different tags we would want to apply for calibrations. Justin suggested it would be useful for people working on specific analysis channels to show how much of a speed increases could be expected through the use of tagging.
    • Will is the latest person to provide some documentation. These wiki pages are currently being collected on the main Calibration page.
    • More validation outputs and procedures are needed.
  4. Subdetector Reports
    • BCAL - Will has been looking at the fall 2015 data and obtaining updated calibrations and event rate estimates. Andrei had recently obtained new gains from an analysis of cosmic data, and Will is using these as his starting point.
    • CDC - Mike has been working on hit factories for the new fADC125 data format, and will be committing these to sim-recon in the next couple of days. Then validation and calibration of the new data can begin. The config data banks for the fADC125's are all wrong, and David needs to update them. The times are now reported in 1/10th's of an fADC125 time bin - the gain constants in CCDB need to be rethought as well. An HV scan will need to be done for the new run.
    • FDC - Simon has been working on integrating Lubomir's new algorithms into the tracking code. Integrating the gain constants is also on his list.
    • TAGH - Nathan has been analyzing HV scan data taken in the fall. This took a few iterations, using calibrations from run 3185 since the RF signal on the PSC crate was not available. He is currently looking at the efficiencies as a function of voltage. The timing resolutions are similar to previous data, but look more gaussian.
    • TAGM - Alex has been studying the bias scan data. The conclusions regarding fiber quality are the same as from the spring data. Changes in the bias voltage increased the efficiency for some fibers, but the time resolutions for most bundles continue to not meet spec.
  5. Future Simulations
    • Sean committed code to make the new BCAL shower code the default for the analysis code.
    • We mentioned the proposal to start run numbers new run periods at a multiple of 10000. No one objected, this could be construed as approval.
  6. AOB