November 2, 2016 Calibration

From GlueXWiki
Revision as of 12:19, 2 November 2016 by Sdobbs (Talk | contribs) (Agenda)

Jump to: navigation, search

GlueX Calibration Meeting
Wednesday, November 2, 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 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/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. 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)

Agenda

  1. Announcements
  2. Reconstruction Launch Readiness
  3. Run Planning
  4. Calibration Updates
  5. Simulations
    • Data/Simulation comparisons
  6. AOB


Minutes

Attending: Sean (NU); Simon, Adesh, Alex A., Eugene, Elton, Thomas, Mike S., Lubomir, Mark I., Beni, Alex B. (JLab); Will M., Curtis (CMU); Matt S. (IU); Nacer (GSI); Cris (MIT); Justin (W&M)

  1. Announcements
    • Beam is expected in ~2 weeks
  2. Reconstruction Launch Readiness
    • Alex A. reported that the last week was busy with launch preparations. Updates included new FDC time calibrations, TAGM timing updates, and fixes to the CDC geometry.
    • Monitoring version 9 has been started, should be finished within a day. If the data is promptly looked at, we can start the next reconstruction run this week.
    • Mark I.: A new official version of HDDS should be tagged.
    • AA: tried doing timing alignment to individual FDC planes, saw some improvement but needs more study
    • Mike S.: New FDC calibration procedures are solid, will check in new scripts soon.
  3. Run Planning
    • Sean, Naomi and David have ironed out issues with filling out the BOR record with the new firmware versions. This data is properly processed in sim-recon, but David is still ironing out some issues about making it available.
      • Mike S.: Is this information used for production data? Sean: Yes, it's needed to get the number of samples used for calculation the pulse integrals and the pedestals to properly perform the pedestal subtraction.
      • Mike S.: Isn't there other configuration information in each event? Sean: Yes, but is inconsistent with BOR information. Needs to ask David about this, but it is a low priority - we should rely on the BOR data which reflects the configurations actually set in the firmware in any case.
    • Several people have been looking at the new f250 firmware output. Sean has updated the emulation code in sim-recon. Looking at a file of BCAL cosmic data, he sees consistent results for pulse parameters, except the timing is wrong at the sub-percent level. The status flags make no sense, though. Alex S. is aware of these issues, and had found a couple of particular bugs, and is waiting for a new firmware version.
    • Naomi has been looking at the new f125 firmware, but was not able to be at the meeting. She has said that things are looking better. Beni will check to make sure that all of the firmware is up to date.
    • Sean has also been working on testing the new version of the calibration train processing with runs from the spring. He is also adding a pass over the skimmed PS data. He is currently working on resolving some CCDB bugs with Dmitry, and hopes to show something next week.
  4. Calibration Updates
  5. Simulations
    • Data/Simulation comparisons