September 6, 2017, Production & Analysis Working Group

From GlueXWiki
Jump to: navigation, search

Meeting Time and Place

The meeting will be on Wednesday September 6, 2017 at 2:00 pm EDT. For those people at Jefferson Lab, the meeting will be in room F326.

Meeting Connections

  1. To join via a Web Browser, go to the page [1] https://bluejeans.com/115815824.
  2. To join via Polycom room system go to the IP Address: 199.48.152.152 (bjn.vc) and enter the meeting ID: 115815824.
  3. To join via phone, use one of the following numbers and the Conference ID: 115815824.
    • US or Canada: +1 408 740 7256 or
    • US or Canada: +1 888 240 2560
  4. More information on connecting to bluejeans is available.

Reconstruction & Analysis Studies Status

Agenda

  1. Announcements
  2. Data Production
  3. Analysis Focus
  4. This Week's Studies
  5. Any other studies
  6. Upcoming Study Schedule

This Week's Topics

  • Talks: Summary/overviews only. Detailed discussions should be held in the appropriate working groups.
  • Talks should be limited to 10 + 5 minutes.

Data Production

  1. Monitoring Update --- Thomas Britton
  2. Processing Update --- Alex Austregesilo
  3. Calibration Update --- Sean Dobbs
  4. Simulations Update --- Sean Dobbs

Simulation Reports

15 Minute summaries of progress and future plans on the 2017 mcsmear Workplan.

Analysis Focus: Total Cross Sections, Acceptance Corrections

  1. J/Ψ, φ --- Lubomir
  2. η, ρ, ω, φ --- Simon
  3. φxsec --- Thomas
  4. ω --- Cristiano
  5. Any others?

Studies: Hit Efficiencies & Triggering

(i.e. Is the detector working?) Updates on experiment, simulation, and the comparison between the two.

  1. Trigger emulation --- Alex Somov
  2. Triggering efficiency --- Alex Somov
  3. CDC Hit Efficiencies --- Naomi Jarvis
  4. FDC Hit Efficiencies --- Alex Austregesilo
  5. BCAL Hit Efficiencies --- Elton Smith
  6. FCAL Hit Efficiencies --- Jon Zarling

Upcoming Study Schedule

  • Updates on experiment, simulation, and the comparison between the two.
  • Summary/overviews only. Detailed discussions should be held in the appropriate working groups.
  • All talks should be limited to 10 + 5 minutes.

Next week: Alignment & Track/Shower Efficiencies (i.e. Is the detector working?) Updates on experiment, simulation, and the comparison between the two.

  1. Drift chamber alignment --- Mike Staib, Alex Barnes
  2. Tracking Efficiencies --- Paul Mattione, Cristiano Fanelli
  3. BCAL Shower Efficiencies --- Elton Smith
  4. FCAL Shower Efficiencies --- Jon Zarling

The week after next: Other Updates on experiment, simulation, and the comparison between the two.

  1. FCAL Shower Efficiencies --- Jon Zarling
  2. Track / Hit Matching: BCAL, FCAL, TOF, SC --- Paul Mattione, Simon
  3. Efficiencies: TOF, SC --- Beni, Mahmoud
  4. Means & Resolutions (time, energy, dE/dx): Tracking, BCAL, FCAL, SC, TOF
  5. Uncertainties: PID (BCAL, FCAL, TOF, dE/dx), Kinfit (BCAL, FCAL, tracking)
  6. Channel/Analysis Studies: Branching ratios, cross sections, SDMEs, beam asymmetries
  7. Other reconstruction/analysis issues

The following week: Beamline & Triggering

  1. Flux --- Justin
  2. Beam energy --- Beamline Group
  3. Polarization (TPOL & lineshape) --- Beamline Group
  4. Beam Asymmetries --- Alex Austregesilo
  5. Trigger emulation --- Alex Somov
  6. Triggering efficiency --- Alex Somov

Minutes

Data Production

  1. Monitoring Update --- Thomas: Same as usual.
  2. Processing Update --- Paul M.: Analysis launch has finished. There are some potential issues with neutral-containing final states, may have to re-run these.
    • Sean: When can we have another monitoring launch? Paul M.: Alex A. is coming back on Thursday, coordinate with him on Friday or Monday.
  3. Calibration Update --- Sean: Coordinating calibration updates from various groups, working towards a stable set for a new reconstruction run.
  4. Simulations Update --- Sean: Finishing off integrating some CDC updates, trigger simulations, and changes to the HDDM event model to store pulse peak information. A few more are in the works. Plan is to finish these studies then do another mini-launch before performing another full launch. Accurate trigger simulation is a must for physics analyses.
    • Also looked at some early results by Naomi on CDC per-straw efficiencies. Threshold updates (first since ~2007) lead to slightly lower efficiencies, trying to understand drop in efficiency in outer rings, but it's likely a quirk of the tracking information passed to the calculation.

Simulation Reports

Will revisit these after the next mini-launch.

Analysis Focus: Total Cross Sections, Acceptance Corrections

  1. J/Ψ, φ --- Lubomir: Still need feedback from high-rate channels.
  2. φxsec --- Thomas: comparison of cross sections of phi -> K+K-, 3pi, eta gamma show:
    • Difference between 2016 and 2017 results
    • Dip near E(g) ~ 8.5 GeV only in K+K- final state, maybe a fitting issue?
    • Difference between 2017 low and high rates only in K+K- final state
    • Trying to understand these, many ideas thrown out. Efficiency calculations could be the cause. Paul M.: could try having Simon and Thomas analyze each other's final states

Studies: Hit Efficiencies & Triggering

(i.e. Is the detector working?) Updates on experiment, simulation, and the comparison between the two.

  1. Trigger efficiencies --- Alex Somov provided an update based on the new simulation code, looking at several final states
    • Looking at exclusive omega -> pi0 gamma events, there is an overall reconstruction efficiency of ~50% (acceptance + reconstruction), trigger inefficiency is <1%.
      • Eugene: Where does the inefficiency come from? Paul M.: Would be good to look at p-theta plots of reconstructed particles to see there are effects from e.g. photons converting in the FDC support structure.
    • Exclusive rho -> pi+ pi- events have a trigger efficiency of ~90 - 95%.
  2. FCAL Hit Efficiencies --- Mike Staib pointed out that there are some gain pathologies in ~10 blocks in the inner rings for 2016 data. Will discuss more in Calorimetry meeting tomorrow, but a good idea to use fiducial cuts to exclude this area.