Single Spin Asymmetry Analysis » History » Revision 20
Revision 19 (Alicia Postuma, 02/06/2023 10:02 AM) → Revision 20/23 (Alicia Postuma, 05/26/2023 01:08 PM)
{{>toc}}
h1. Single Spin Asymmetry Analysis
---
h2. Resources
* "Stefan Diehl's DNP2022 Talk":https://redmine.jlab.org/attachments/1679
* "Steve Wood's Slides (03/11/22)":https://redmine.jlab.org/attachments/1678
* "Steve Wood's (old as of 03/11/22) Polarisation Spreadsheet":https://redmine.jlab.org/attachments/1677
* "Steve Wood's (old as of 03/11/22) HWP List":https://redmine.jlab.org/attachments/1676
* "Alicia's HWP list from 03/11/22":https://redmine.jlab.org/attachments/1680
h2. Overview
During the fall 2018 running of the Kaon-LT experiment, polarized beam was delivered to Hall B. According to Dave Gaskell, at the energy we ran at, the spin precession in the Hall C arc was such that we got nearly as much polarization as Hall B, so we had a polarization of about 85%. This means that, for hadron production out of the plane defined by the beam and scattered electron, we should see an asymmetry in the yield between the two beam helicity states. This asymmetry is known variously as the single spin asymmetry, σ ~LT'~, or the fifth structure function.
As a function of φ, the azimuthal angle about q, the asymmetry should vary as (A+Bsin(φ))/(1+Ccos(2φ)+Dcos(φ)) where the C and D terms come from the σ ~TT~ and σ ~LT~ modulations of the cross section.
h2. References
Hall B paper exclusive pion production single spin asymmetries, "Park et. al. 2008":http://dx.doi.org/10.1103/PhysRevC.77.015208
Latest results from PREX and CREX, "Adhikari et al. 2022":https://arxiv.org/pdf/2111.04250.pdf
Hall C report from Qweak, "Waidwawansa 2016":https://arxiv.org/pdf/1604.04602.pdf
Eta photoproduction asymmetry from GlueX, "Adhikari et al. 2019":https://arxiv.org/pdf/1908.05563.pdf
Elastic scattering off heavy nuclei at MAMI, "A. Esser et al. 2020":https://www.researchgate.net/publication/343330738_Beam-normal_single_spin_asymmetry_in_elastic_electron_scattering_off_28Si_and_90Zr
h2. How to add helicity to ROOT files.
The helicity of the beam potentially reversed every 1/30 of a second according to a pseudorandom sequence. The helicity signals delivered to the hall are delayed by 8*(1/30) second. This delayed helicity signal is recorded in several ADCs which are read each event. In order to extract the helicity and undo the delayed reporting of helicity, a recent version of `hcana` which includes the class `THcHelicity` is needed. In order to add the true beam helicity to each event in the root tree, make sure that the following are implemented in the replay script and analysis def file.
After the trigger apparatus is defined, add the following lines to the analysis script:
// Add helicity detector to trigger apparatus
THcHelicity* helicity = new THcHelicity("helicity","Helicity Detector");
TRG->AddDetector(helicity);
In the def file (coin_production.def) add these lines:
block T.helicity.hel
block T.helicity.helrep
block T.helicity.mps
T.helicity.hel will be +/-1 indicating the actual helicity of the beam, event-by-event. If it is zero, then either the event was during the MPS (settling time between helicity reversals.) or the analyzer was unable to decode the helicity properly. helrep is the reported T.helicity.helrep which is delayed. T.helicity.mps is 1 if the event was during the MPS.
h2. Tasks
* Get the history of the status of the Insertable Half Wave Plate (EPICS signal IGL1I00DI24_24M). The IHWP is a passive optical element on the injector laser table that reverses the helicity of the electron beam, but does not reverse the reported helicity. Experimental asymmetries will be reversed when the IHWP is in, so the analysis must reverse the asymmetries for runs when this IHWP was in. It is possible that the state of the IHWP was changed in the middle of one of runs. Any such runs need to be identified and analyzed specially.
* Get the history of Hall B beam polarization measurements. Translate these polarizations into Hall C polarizations.
* FIgure out how to bin and display results. Should asymmetries be presented as a function of _t_ or θ ~hq~ (cm or lab). How finely can we bin in _t_ or θ?
* For pion asymmetries. Determine accidental background. This asymmetry from accidental backgrounds should be zero, but this background will reduce or dilute the observed asymmetry.
* For Kaon asymmetries it is more complicated. As well as a dilution from accidentals, the radiative tail from exclusive pions misidentified as Kaons contributes to the observed Kaon asymmetries. The asymmetry from these pions will not be zero. In order to correct for this to get Kaon asymmetries, the accepted yield of the tail and its asymmetry needs to be determined.
* Determine if it is possible to get any meaningful asymmetries from the baryons beyond the Lambda.
h2. Analysis Teaser
These two asymmetry plots were made from an analysis of all the Q ^2^ =3.0, W=2.32, x=0.40 data using a modified version of the `KaonYield_Q3W2Center.C` script. The pion asymmetry has a cut around the neutron missing mass, while the kaon asymmetry has a cut missing mass cut on the Lambda mass. The kaon asymmetry certainly has a pion contamination. All accepted _t_ (or θ ~hq~) are included. There is a 50% chance that the sign is correct. The asymmetries are fit with the above functional form. These asymmetries do not necessarily need to follow that form as each φ bin has a different _t_ coverage range.
!a_pion.png!
!a_kaon.png!
A repeat analysis of some of this data (Q ^2^ =3.0, W=2.32, x=0.40, high &epsilon, SHMS center) by Alicia is attached under "Files."
!Q3W2p32center_highe_out_PionAsymmetry.pdf!
h2. Alicia's progress updates
* Nov 23: [[https://redmine.jlab.org/attachments/1704]]
* Dec 07: [[https://redmine.jlab.org/attachments/1715]]
* Jan 19: [[https://redmine.jlab.org/attachments/1728]]
* Error calculations Jan 19: [[https://redmine.jlab.org/attachments/1729]]
* Feb 2: [[https://redmine.jlab.org/attachments/1748]]
* May 11: [[https://redmine.jlab.org/attachments/1924]]
** Missing mass study:
* [[https://redmine.jlab.org/attachments/1925]]
* [[https://redmine.jlab.org/attachments/1926]]