Analysis Mtg 240905

From Moller Wiki
Jump to: navigation, search

Back to Main Page >> Analysis Software overview >> Analysis Meetings

previous meeting << >> following meeting

Meeting information

 Meeting time:  3:30pm Eastern
 
 Location at JLab:  CC F326-327
 
 Zoom connection information is sent out to the moller_analysis mailing list.  Please subscribe if you are interested.

Agenda

  • Updates
  • General discussion

Minutes

Participants: S. Chatterjee, P. King, K. Paschke, W .Deconinck, A. Hurley, D. Spayde, J. Shirk, J. Mott, J. Mammei, J. Tsakanikas, Z. Demiroglu, Michael K., R. Conaway, J. Datta

  • Status of the pull requests
    • Paul was delayed in finishing these this week; will try to finish this week
    • Ole had cancelled the "re-enable TMapFile" pull request last week; Paul will check with him to understand what was the problem
  • Joachim presents work on incorporating correlations between detector elements
    • Detectors have rate contributions from both "non-overlap" and "overlapping" regions on the tiles
    • Simple model to incorporate this shared rate would just have a single pure rate and a single rate shared with one neighbor, which would be randomized independently
    • More general would allow sharing rate between several adjacent elements
      • We'd want to randomize the "non-overlap" rates independently and then randomize each of the rates in an overlapping region to be used for all of the tiles that share that overlap region
    • Wouter asks if all this can be extended to "overlap" between the Ring5 and the Showermax? Pion detector?
    • Maybe the way to proceed is to think about the different sub-regions would be as a fictional detector array that then could have elements combined to form the "physical" detectors?
      • Maybe eventually the fictional array could also be used as input for ShowerMax and Pion detector?
      • Do we need to handle beam correlations independently for each sub-region? Right now Kent thinks this is a second order effect that we can initially ignore
      • Kent and Joachim will start to think about what non-overlap and overlap regions we'd want to have.