[G12] Meeting today: Monday, March 9, 2015

[William Phelps]

This is a reminder that there is a g12 Meeting in room A110 today at 2:00 pm EST. 
http://clasweb.jlab.org/rungroups/g12/wiki/index.php/Mar2015
-Will


Latest information from the wiki:
March 2, 2015
Agenda
     -g12 analysis note update
          -normalization issue: addressed in Lei's email on Feb 27
          -known resonances in g12 with all g12 corrections applied
     -other analysis updates?
     -Lei's email
Following our discussion from Monday on the g12 normalization factor in all cross section calculation, I had a very productive discussion with MK today, together with what we discussed on Monday’s g12 meeting: I’d like to summarize what we have now.
There are really two things that are contributing, and nothing is really pointing to a specific “trigger inefficiency”.
1. Beam current dependent inefficiency. As Will has shown in his beam current dependent omega normalized yields, this is a small factor and sub-5% issue. But this needs to be verified since we weren’t sure the omega yields were extracted after applying any cuts on the photon multiplicity. That 5% could be just a photon multiplicity effect, or a real effect that we need to correct for.
2. Photon multiplicity. At g12 beam currents, there are non-negligible fraction of the data that has more than one photon in the same 2ns window. (There are also chances with three photons). This multiplicity could be both topology and beam energy dependent. So, this correction probably should not be a flat correction that’s good for all topoligies and all energies. But fortunately, deriving this is trivial and shouldn’t take too long.
3. Reconstruction/Simulation(in)efficiency. MK has done extensive studies using ppi+pi- events to study each track’s reconstruction efficiency in both real data and simulation. The method was look at the efficiency of proton, e.g., detection, if there is a missing proton. Do this for both data and MC, you will end up with a ratio that’s 1— ideally. However, he has a slightly inefficiency in data for each kind of tracks. This study was not dependent on the lepton trigger, and should be applicable for all g12 cross section measurements that involve the detection of charged triggers. However, there could be double counting there since the study was not done requiring only one good photon in the same time bucket.
But I think overall, we are pretty close to finish this issue. Let’s meet on Monday. And MK should be able to attend, especially since I might have misinterpreted his study.
See you!
Minutes
<!--
NewPP limit report
Preprocessor visited node count: 11/1000000
Preprocessor generated node count: 16/1000000
Post-expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Expensive parser function count: 0/100
-->



To join the Meeting:
https://bluejeans.com/391243710

To join via Browser:
https://bluejeans.com/391243710/browser

To join with Lync:
https://bluejeans.com/391243710/lync

To join via Cisco Jabber Video:
https://bluejeans.com/391243710/jabber


To join via Room System:
Video Conferencing System: bjn.vc -or- 199.48.152.152
Meeting ID: 391243710

To join via Phone:
1) Dial:
+1 408 740 7256
+1 888 240 2560(US Toll Free)
+1 408 317 9253(Alternate Number)
(see all numbers - http://bluejeans.com/numbers)
2) Enter Conference ID: 391243710