July 15, 2015 Calibration

From GlueXWiki
Revision as of 16:45, 15 July 2015 by Sdobbs (Talk | contribs)

Jump to: navigation, search

GlueX Calibration Meeting
Wednesday, July 15, 2015
11:00 am, EDT
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 199.48.152.152 or bjn.vc
    • Enter meeting ID above
    • Use *4 to unmute

Slides

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

Agenda

  1. Announcements
  2. Calibration Processing
    • Potential uses of git?
    • Run quality criteria
  3. Summary of Detector Performance
  4. Subdetector Reports
  5. Simulations
  6. Action Item Review
  7. AOB

Action Items

  • Produce updated calibration plots and performance numbers, preferably within a week.
  • Polish calibration routines, including testing of results, documentation (GlueX note).
  • Update simulation parameters.

Minutes

Attending: Sean (NU); Simon, Beni, Mark I., Justin, Eric, Lubomir, Paul, Eugene, Adesh, Mark D. (JLab); Curtis, Will M., Mike S. (CMU)

Announcements

  1. S&T Review
    • Plots from all of the detectors have been collected and put on both DocDB and the plot database in the GlueX portal.
    • Justin is putting together his talk, and will send out requests for more information as needed.
  2. Latest monitoring run
    • The most recent offline monitoring run was started last Friday. Database problems delayed processing of the results, but they should be done today. REST files are available as described in the email linked above.
  3. moving to git
    • The repositories for sim-recon and HDDS are moving from Subversion to git. Basic instructions on how to interact with the new system are linked to above. If you plan to contribute code, you will need an account on github; if you just plan on using the latest code for analysis, you can just check out the main branch as described in the instructions.
    • Note that before the move, all sim-recon and online plugins have been moved into a new directory in sim-recon: src/plugins
    • A new directory for storing DANA calibration plugins has been created in sim-recon: src/plugins/Calibration

Calibration Processing

Sean has been testing this system in the past few weeks, and plans to make the first "official" run next week. He is shooting for Tuesday, and will make any annoucements related to this on the offline software mailing list.

Since a lot of progress has been made in calibration procedures, Sean went through a few guidelines that should be followed to standardize them:

  • DANA plugins should be stored in the sim-recon directory src/plugins/Calibration
  • Other scripts should be stored in some common area
    • Suggestion: One directory per subdetector, organization in each directory is up to the subdetector groups
    • Version control: Either a common location in SVN or individual git repositories. Feedback from detector groups would be helpful.
    • The calibration jobs execute ROOT scripts in a common environment where libraries (compiled or ROOT scripts) can be pre-loaded.
  • Quality testing routines should be included for each calibration procedure
  • All output should be to files, not the screen, so that results can be properly staged to disk
  • Documentation: both how to run scripts and GlueX note draft.

Sean also suggested that detector groups start coming up with data quality criteria so that we can start working on automatically classifying run quality. There was a lot of discussion on what this would mean, and Sean offered to come up with a more concrete plan that could be further discussed. Some points that were brought up:

  • Subdetectors can have transitory problems. We might want to track these (in the CCDB perhaps?), and then map these to lists of files which should be excluded.
  • In the current software, calibrations can only be done on a per-run basis. Changing to a finer grained system would involve a lot of work.
  • Determination of pedestals on a per-file basis is desirable, based on the data collected so far.
  • Mark D. shared his experience from QWeak. They took long runs and did calibrations/data quality on a per-file basis, since they found they were losing ~6% of run time due to starting and stopping CODA. Eugene pointed out that the newer CODA we are using is much faster than the old one.


  1. Summary of Detector Performance