[Hps] trident summit

[Graham, Mathew Thomas]

Hi All,

As we mentioned yesterday, we are trying to set up a 1.5-2 day meeting so that we can converge on the trident problem.  The plan is to get together experts in every ingredient of the analysis (theory, simulation, detector, recon, analysis) AND also some "fresh eyes” so we can determine if we are missing something.
I’ve set up a doodle poll here…please fill it in with dates you can attend (via bluejeans).

http://doodle.com/poll/ttbq3xts95yicv8e


This is a link to a few slides shown at yesterdays meeting:
https://confluence.slac.stanford.edu/download/attachments/213889243/hps-dawg-trident-summit-proposal.pdf?version=1&modificationDate=1466780132000&api=v2

and here is the start of a confluence page Sho set up:
https://confluence.slac.stanford.edu/display/hpsg/Esum+anomaly+brainstorming


Proposed topics/agenda:

  *   Introduction:  why the trident measurement is important (reach from radiative fraction) and what the problem is

  *   logically, what sorts of issues could cause the eSum issue we are seeing?

  *   Expected trident cross-section:

  *   previous trident XS measurements
  *   MadGraph -- details of how it is calculated, show distributions in wider phase-space and then focus on ~ HPS acceptance
     *   Radiative-only, BH-only, FullTri...
  *   Beranak's calculation and simulation of that -- Luca & Ani
     *   are there differences between these and FullTri from MadGraph?

  *   Detector and Readout Simulation (with particular focus on where things can go wrong):

  *   Overview of simulation steps and how various sub-samples are put together
  *   Overview of geometry and SLIC simulation?
  *   detailed overview of readout simulation (both SVT and ECal) including time evolution
  *   detailed overview of trigger simulation

  *   Reconstruction (with particular focus on where things can go wrong):

  *   detailed overview of hit reco & clustering:  ECal
  *   detailed overview of hit reco & clustering:  SVT
  *   detailed overview of tracking and track+cluster matching

  *   Data studies (vs MC where appropriate):

  *   trigger efficiency vs track/cluster energy, angle/position?  ESum?
  *   tracking efficiency vs momentum, angle
  *   pulser trigger studies

  *   Alternate approaches (data-driven) to extracting  f_rad?
  *
What do we do if we can't figure this out in a reasonable amount of time?


Thanks, Matt

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/hps/attachments/20160625/c50cd802/attachment.html>