STAR Spin Working Group
Unraveling the quark and gluon substructure of nucleons and nuclei is one of the major goals in nuclear physics today. A great deal has been learned about the partonic structure of the nucleon at leading twist and with collinear factorization, but much is still unknown. Furthermore, new avenues have been opened during the past decade to explore the nucleon structure beyond leading twist and collinear factorization. The ability to collide polarized beams at RHIC provides unique information regarding these issues.
- STAR Decadal Plan (2010)
This is a feed of Drupal items targeting the "Spin" Audience.
Detailed information about physics analyses in the spin pwg
Link to STAR spin task force (2008)
(page started in March of 2008)
The 2006 EEMC cross section, ALL, and AN were published in Physical Review D 89, 012001 (2014). Please, see the paper home page for links to detailed information.
Gamma-jet cross sections for forward gammas in proton-proton collisions at root(s) = 200 GeV/c
Keith Krueger (ANL), Hal Spinka (ANL), Dave Underwood (ANL)
Physical Review D
A measurement is presented of the cross section vs. transverse momentum (pT) for gamma + jet production in proton-proton collisions. The data were measured in the STAR detector at RHIC at √s = 200 GeV/c. The jet was detected at central pseudorapidity (|η| < 0.8) and the γ at intermediate pseudorapidity (1.2 < η < 2.0). These regions were chosen to access lower x of the gluon relative to a central-pseudorapidity-only measurement, and also because a large partonic spin asymmetry, All, in the parton cm is selected. The technique of finding single γ’s in the background of photons from π0 decay is based on a standard chi-squared method for the shower shape in the shower maximum detector of an electromagnetic calorimeter.
Presentations:
Preliminary released on SPIN 2012 and DNP 2012.
Presentation @ SPIN 2012 by Jian Deng (SDU)
Presentation @ DNP 2012 by Ramon Cendejas (UCLA)
lam_pt | dac2 | dcaV0 | dca_p | dca_pi | nsigma | dlength | cosrp | jet_det_eta | jet_Rt | jet_dr |
2,3 | <0.7 | <1.2 | >0.2 | (0.4,30) | <3 | (3,130) | >0.98 | (-0.7,0.7) | (0.01,0.94) | <0.7 |
3,4 | <0.5 | <1.2 | 0 | (0.4,30) | <3 | (3.5,130) | >0.98 | (-0.7,0.7) | (0.01,0.94) | <0.7 |
4,5 | <0.5 | <1.2 | 0 | (0.4,30) | <3 | (4,130) | >0.98 | (-0.7,0.7) | (0.01,0.94) | <0.7 |
5,8 | <0.5 | <1.2 | 0 | (0.4,30) | <3 | (4.5,130) | >0.98 | (-0.7,0.7) | (0.01,0.94) | <0.7 |
Lambda pT | Lambda JP1 | AntiLambda JP1 | Lambda L2JetHigh | AntiLambda L2JetHigh |
2, 3 | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html |
3, 4 | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html |
4, 5 | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html |
5, 8 | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html |
Lambda pT | Lambda JP1 | AntiLambda JP1 | Lambda L2JetHigh | AntiLambda L2JetHigh |
2, 3 | FiredJet .html noFire .html | FiredJet .html noFire .html | FiredJet .html noFire .html | FiredJet .html noFire .html |
3, 4 | FiredJet .html noFire .html | FiredJet .html noFire .html | FiredJet .html noFire .html | FiredJet .html noFire .html |
4, 5 | FiredJet .html noFire .html | FiredJet .html noFire .html | FiredJet .html noFire .html | FiredJet .html noFire .html |
5, 8 | FiredJet .html noFire .html | FiredJet .html noFire .html | FiredJet .html noFire .html | FiredJet .html noFire .html |
Lambda pT | Lambda JP1 | AntiLambda JP1 | Lambda L2JetHigh | AntiLambda L2JetHigh |
2, 3 | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html |
3, 4 | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html |
4, 5 | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html |
5, 8 | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html | FiredJet.pdf .txt .html noFire .pdf .txt .html |
lamdba pt | JP1 | L2JetHigh |
2_3 | file | file |
3_4 | file | file |
4_5 | file | file |
5_8 | file | file |
A-lamdba pt | JP1 | L2JetHigh |
2_3 | file | file |
3_4 | file | file |
4_5 | file | file |
5_8 | file | file |
lamdba pt | MB | JP1 | L2JetHigh |
2_3 | file | file | file |
3_4 | file | file | file |
4_5 | file | file | file |
5_8 | file | file | file |
f_z | feed down | parton | subprocess | |
Lambda | file1 file2 | file | file | file |
A-lambda | file1 file2 | file | file | file |
Systematic uncertainties summary
η > 0 | η < 0 | |||||||||
Lambda | Anti-lambda | Lambda | Anti-lambda | |||||||
pt | JP1 | L2J | JP1 | L2J | JP1 | L2J | JP1 | L2J | ||
decay | 2.4 | 0.0009 | 0.0018 | 0.0001 | 0.0003 | 0.0001 | 0 | 0.0001 | 0.0001 | |
3.4 | 0.0008 | 0.0011 | 0.0004 | 0.0003 | 0 | 0.0001 | 0 | 0 | ||
4.4 | 0.002 | 0.0027 | 0.0008 | 0.0008 | 0.0003 | 0.0004 | 0.0001 | 0.0002 | ||
5.9 | 0.0017 | 0.0024 | 0.0013 | 0.0022 | 0.0005 | 0.0009 | 0.0003 | 0.0007 | ||
fz | 2.4 | 0.0011 | 0.0028 | 0.0003 | 0.0015 | 0.0002 | 0.0001 | 0.0001 | 0.0001 | |
3.4 | 0.001 | 0.0034 | 0.0006 | 0.0024 | 0.0003 | 0.0005 | 0.0003 | 0 | ||
4.4 | 0.0056 | 0.008 | 0.0053 | 0.0079 | 0.0005 | 0.0007 | 0.0009 | 0.0013 | ||
5.9 | 0.009 | 0.0121 | 0.0154 | 0.0191 | 0.0021 | 0.0028 | 0.0037 | 0.0046 | ||
fparton | 2.4 | 0.0005 | 0.0008 | 0.0004 | 0.0012 | 0.0001 | 0.0001 | 0.0001 | 0.0002 | |
3.4 | 0.0011 | 0.0021 | 0.0002 | 0.0013 | 0.0003 | 0.0005 | 0 | 0.0003 | ||
4.4 | 0.0019 | 0.0038 | 0.0003 | 0.0011 | 0.0005 | 0.0009 | 0.0001 | 0.0003 | ||
5.9 | 0.0034 | 0.0062 | 0.0016 | 0.0027 | 0.0011 | 0.002 | 0.0005 | 0.0009 | ||
pile-up | 2.4 | 0.0182 | 0.0057 | 0.0184 | 0.0063 | 0.0182 | 0.0057 | 0.0184 | 0.0063 | |
3.4 | 0.0023 | 0.0007 | 0.0022 | 0.001 | 0.0023 | 0.0007 | 0.0022 | 0.001 | ||
4.4 | 0.0023 | 0.0007 | 0.0022 | 0.001 | 0.0023 | 0.0007 | 0.0022 | 0.001 | ||
5.9 | 0.0068 | 0.0023 | 0.0064 | 0.0023 | 0.0068 | 0.0023 | 0.0064 | 0.0023 | ||
bkgd | 2.4 | 0.005 | 0.001 | 0.0001 | 0.0002 | 0.005 | 0.001 | 0.0001 | 0.0002 | |
3.4 | 1.00E-06 | 0.0001 | 0.0001 | 0.0006 | 1.00E-06 | 0.0001 | 0.0001 | 0.0006 | ||
4.4 | 0.0007 | 4.00E-05 | 0.0004 | 0.0002 | 0.0007 | 4.00E-05 | 0.0004 | 0.0002 | ||
5.9 | 0.0002 | 0.0002 | 0.001 | 0.0001 | 0.0002 | 0.0002 | 0.001 | 0.0001 | ||
all | 2.4 | 0.0189 | 0.0067 | 0.0184 | 0.0066 | 0.0189 | 0.0058 | 0.0184 | 0.0063 | |
3.4 | 0.0029 | 0.0042 | 0.0023 | 0.0030 | 0.0023 | 0.0010 | 0.0022 | 0.0012 | ||
4.4 | 0.0067 | 0.0093 | 0.0058 | 0.0081 | 0.0025 | 0.0014 | 0.0024 | 0.0017 | ||
5.9 | 0.0119 | 0.0140 | 0.0168 | 0.0196 | 0.0072 | 0.0042 | 0.0075 | 0.0053 |
1, Trigger bias parameters (fz_shift, feed-down fraction, fragmenting parton flavor fraction, subprocess fraction) plots
2, Uncertainty to D_TT from trigger bias
Presentations:
Dataset: pp200trans_2012
Integrated Luminosity: 18.4 pb^-1
Selected Triggers: JP0, JP1, JP2, AJP
Trigger | JP0 | JP1 | JP2 | AJP | Combined |
---|---|---|---|---|---|
HardXSoft | 2.461964e+07 | 8.525444e+07 | 1.797188e+07 | 1.391969e+07 | 1.417656e+08 |
The reconstruction of Lambda and anti-Lambda hyperons.
Identification cut on track’s dE/dx measured in TPC is used to find pion and (anti-)proton.
Sketch for Topological Cuts
a) Statistics of Lambda and anti-Lambda Reconstruction, Inclusive
b) Statistics of Lambda and anti-Lambda Reconstruction, Jet near-side
Only the jet near-side Lambda used to extract D_TT.
The comparison about the reconstruction status with two sets of cut are shown here.
The loose one is the cut set used in run09 D_LL analysis and the tight one.
D_TT analysis Record, Rec_Step: all_cut_crp0995
====> Lambda
1~2 | 1.1154 | 0.0016 | 364262 | 0.0536 | 1.1155 | 0.0016 | 1394859 | 0.0570 | 1.1155 | 0.0016 | 280707 | 0.0666 | 1.1155 | 0.0016 | 338322 | 0.0546 | 1.1155 | 0.0016 | 2378150 | 0.0572 |
2~3 | 1.1157 | 0.0021 | 96583 | 0.0609 | 1.1157 | 0.0021 | 496180 | 0.0654 | 1.1157 | 0.0022 | 122363 | 0.0758 | 1.1157 | 0.0021 | 118569 | 0.0631 | 1.1157 | 0.0021 | 833695 | 0.0660 |
3~4 | 1.1158 | 0.0027 | 25879 | 0.0612 | 1.1158 | 0.0028 | 186321 | 0.0649 | 1.1158 | 0.0028 | 57674 | 0.0748 | 1.1158 | 0.0027 | 38191 | 0.0609 | 1.1158 | 0.0028 | 308065 | 0.0659 |
4~5 | 1.1161 | 0.0035 | 6360 | 0.0616 | 1.1160 | 0.0034 | 65638 | 0.0644 | 1.1159 | 0.0034 | 25367 | 0.0703 | 1.1160 | 0.0035 | 11204 | 0.0565 | 1.1160 | 0.0034 | 108569 | 0.0648 |
5~6 | 1.1162 | 0.0041 | 1782 | 0.0791 | 1.1162 | 0.0042 | 25415 | 0.0720 | 1.1162 | 0.0042 | 11736 | 0.0745 | 1.1163 | 0.0042 | 3484 | 0.0669 | 1.1162 | 0.0042 | 42417 | 0.0726 |
6~8 | 1.1168 | 0.0051 | 729 | 0.0938 | 1.1166 | 0.0051 | 14932 | 0.0884 | 1.1166 | 0.0052 | 8622 | 0.0912 | 1.1169 | 0.0051 | 1853 | 0.0835 | 1.1166 | 0.0051 | 26136 | 0.0891 |
====> anti-Lambda
1~2 | 1.1155 | 0.0015 | 299136 | 0.0755 | 1.1155 | 0.0016 | 1048977 | 0.0834 | 1.1155 | 0.0015 | 195241 | 0.0999 | 1.1155 | 0.0015 | 284645 | 0.0735 | 1.1155 | 0.0017 | 1827999 | 0.0823 |
2~3 | 1.1157 | 0.0020 | 102267 | 0.0676 | 1.1157 | 0.0020 | 468030 | 0.0743 | 1.1157 | 0.0021 | 97877 | 0.0931 | 1.1157 | 0.0020 | 114900 | 0.0702 | 1.1157 | 0.0020 | 783074 | 0.0751 |
3~4 | 1.1159 | 0.0026 | 26961 | 0.0663 | 1.1159 | 0.0026 | 183094 | 0.0680 | 1.1158 | 0.0027 | 46292 | 0.0860 | 1.1159 | 0.0027 | 34646 | 0.0694 | 1.1159 | 0.0027 | 290993 | 0.0709 |
4~5 | 1.1162 | 0.0033 | 5659 | 0.0660 | 1.1161 | 0.0034 | 61114 | 0.0635 | 1.1160 | 0.0034 | 19641 | 0.0741 | 1.1161 | 0.0035 | 8582 | 0.0678 | 1.1161 | 0.0034 | 94996 | 0.0662 |
5~6 | 1.1166 | 0.0043 | 1301 | 0.0707 | 1.1163 | 0.0041 | 20461 | 0.0756 | 1.1162 | 0.0041 | 8679 | 0.0798 | 1.1164 | 0.0041 | 2292 | 0.0794 | 1.1163 | 0.0041 | 32733 | 0.0768 |
6~8 | 1.1168 | 0.0057 | 459 | 0.1046 | 1.1168 | 0.0053 | 10175 | 0.1061 | 1.1166 | 0.0051 | 5581 | 0.1092 | 1.1172 | 0.0053 | 972 | 0.1086 | 1.1168 | 0.0052 | 17187 | 0.1072 |
Trigger: JP0 Distribution Statistics
Trigger: JP1 Distribution Statistics
Trigger: JP2 Distribution Statistics
Trigger: AJP Distribution Statistics
Trigger: Combined Distribution Statistics
Trigger: JP0 Distribution Statistics
Trigger: JP1 Distribution Statistics
Trigger: JP2 Distribution Statistics
Trigger: AJP Distribution Statistics
Trigger: Combined Distribution Statistics
Trigger: JP0 decay length dca2 dcaV0 cosrp
Trigger: JP1 decay length dca2 dcaV0 cosrp
Trigger: JP2 decay length dca2 dcaV0 cosrp
Trigger: AJP decay length dca2 dcaV0 cosrp
Trigger: Combined decay length dca2 dcaV0 cosrp
Trigger: JP0 decay length dca2 dcaV0 cosrp
Trigger: JP1 decay length dca2 dcaV0 cosrp
Trigger: JP2 decay length dca2 dcaV0 cosrp
Trigger: AJP decay length dca2 dcaV0 cosrp
Trigger: Combined decay length dca2 dcaV0 cosrp
dca of daughters is also used as cut
Trigger: Combined p_T eta phi dca
Trigger: Combined p_T eta phi dca
Trigger: Combined p_T eta phi dca
1, MC production summary: hard_pT weight
2, MC and data comparison for inclusive hyperons
3, MC and data comparison for jet near-side hyperons
MC samples before and after trigger conditions applying are used for trigger bias study.
• changes in the fractional momentum z of the produced Lambda and anti-Lambda within the associated jet,
• changes in the relative contributions from different hard sub-processes and fragmenting partons with different flavors in the production.
• possible differences in the fraction of feed-down contributions.
Please maximize your web browser before open the following links or some plots may not show up.
1, Trigger bias parameters plots
1, Trigger bias parameters (fz_shift, feed-down fraction, fragmenting parton flavor fraction, subprocess fraction) plots
2, Uncertainty to D_TT from trigger bias
Presentations:
Credit goes to Kevin Adkins for the User's guide below:
With the current state of storage on RCF, several users are becoming regular users of PDSF. Anselm and others have requested that I write a short introduction to PDSF. So this blog will hold the keys for successful operation on PDSF. It will expand as issues are broght forth and addressed.
Getting started at PDSF:
1. Get your username at this website: https://nim.nersc.gov/nersc_account_request.php
Once you submit this form you will receive an email that includes a link. This link will only be valid for 72 hours, and will point you to a location where you can set your password. So don't postpone! If you have trouble the email will include a phone number to call, the staff is very helpful so don't hesitate to contact them.
2. Get logged in using the same terminal command as RCF:
ssh -Y username@pdsf.nersc.gov : where username, of course, will be your username.
3. When entering your password, you only have three chances. After your third chance you'll be "locked out" and you must call to have your password reset. To avoid the hassle, make your password something you can remember!
Storage disks at PDSF:
There are two disks that STAR-spin has access to on PDSF:
/eliza14/star/pwg/starspin/
/eliza17/star/pwg/starspin/
You must email Jeff Porter ( rjporter@bnl.gov ) with your username once you can log in. He will give you access to write on these disks. Once you have the access you can create yourself a folder to write your data to on one or both of the above disks.
Transferring data to PDSF:
PDSF has two Data Transfer Nodes (DTN) that are dedicated to the transfer of data at a high rate. These are
pdsfdtn1.nersc.gov
pdsfdtn2.nersc.gov
Transferring data is best with the rsync command. As an example, assume we have several subdirectories of jets stored in /star/data05/scratch/jkadkins/run12_Jets/ on RCF. To transfer this directory as is to the directory /eliza17/star/pwg/starspin/jkadkins/ on PDSF we would use:
rsync -r -v /star/data05/scratch/jkadkins/run12_Jets jkadkins@pdsfdtn1.nersc.gov:/eliza17/star/pwg/starspin/jkadkins/
Note that I left off the "/" at the end of the run12_Jets directory above. This means that we will copy all subdirectories to PDSF in the same structure. If the directory at PDSF doesn't exist, it will be created. If there is data already in a directory of the same name on PDSF then the new data will simply be added. If we had left "/" on the end of run12_Jets then we would have copied all files and subdirectories to /eliza17/star/pwg/starspin/jkadkins and not group it into a directory named run12_Jets on PDSF. Give it a test with a few files in a directory to see exactly how this works.
Note: Transferring large volumes of data takes time. To transfer ~90 gigs of data it will take ~60 minutes. So transferring large jet trees or something similar can take a really long time. It may be best to break it up into smaller segments that are more time manageable.
Running code on PDSF:
Code runs EXACTLY the same on PDSF as it does on RCF. PDSF has the same CVS code up to date as on RCF (I'm not sure how often it's updated, but it's all there). So if you use code in CVS on RCF, then you can also use it on PDSF. The only thing that changes is that PDSF doesn't support is the STAR development library. So when running you'll need to use "starpro" or another library.
Submitting jobs is also EXACTLY the same. You'll need an XML (if it works on RCF, it'll work on PDSF without changes) and you'll use the same star-submit command that you use on RCF. The changes come when you want to check the status of your jobs. The two most common commands to manage jobs are:
qstat -u username : Check the status of all jobs you have submitted
qdel -u username : Remove all jobs you currently have submitted
A full list of queue commands can be found here: http://www.nersc.gov/users/computational-systems/pdsf/using-the-sge-batch-system/monitoring-and-managing-jobs/
Finally, problems should be reported to the PDSF hypernews ( pdsf-hn@sun.star.bnl.gov ).
Who | Institution | Data | Topic |
---|---|---|---|
Jan Balewski | MIT | 2009 | W production |
Michael Betancourt | MIT | 2009/6 | prompt gamma mid-rap A_LL/cross sec. |
Alice Bridgeman | ANL | 2009 | EEMC gammas |
Thomas Burton | Birmingham | 2006 | Lambda trans. pol. |
Ramon Cendejas | UCLA/LBL | 2008 | di-jet cross section |
Ross Corliss | MIT | 2006/9 | photons 1 |
Pibero Djawotho | TAMU | 2009 | inclusive and di-jet |
Xin Dong | LBL | ||
Jim Drachenberg | TAMU | 2008 | FMS+FTPC jets Sivers/Collins |
Len Eun | PSU | 2006/8 | eta SSA |
Robert Fersch | Kentucky | 2009/6 | tbd /mid-rapidity jet Collins |
Oleksandr Grebenyuk | LBL | 2009/6 | TBD/pi0 |
Weihong He | IUCF | 2006 | EEMC pi0 |
Alan Hoffman | MIT | 2005/6 | neutral pions A_LL |
Liaoyuan Huo | TAMU | 2009 | inclusive and di-jet |
Christopher Jones | MIT | 2009/6 | inclusive jets A_LL/cross section |
Adam Kocoloski | MIT | 2005/6 | charged pions A_LL |
Priscilla Kurnadi | UCLA | 2006 | non photonic electron A_LL |
William Leight | MIT | 2009 | Mid-rapidity hadron production |
Xuan Li | Shandong U | hyperons | |
Brian Page | IUCF | 2009 | dijets |
Donika Plyku | ODU | 2009 | Spin dep. in pp elastic scattering from pp2pp |
Nikola Poljak | Zagreb | 2006/8 | Collins Sivers separation forward SSA |
Tai Sakuma | MIT | 2005/6 | dijets cross section/A_LL |
Joe Seele | MIT | 2009 | Ws and dijet cross section |
Ilya Selyuzhenkov | IUCF | 2006-9 | Forward gamma-jet |
David Staszak | UCLA | 2006 | Inclusive Jet A_LL |
Justin Stevens | IUCF | 2010 | TBD |
Naresh Subba | KSU | 2006 | Non-Photonic Elect. 1>eta>1.5 xsec |
Matthew Walker | MIT | 2006/9 | dijets cross section/A_LL |
Grant Webb | Kentucky | 2009/6 | mid-rap gamma or di-jet/ UEvent |
Wei Zhou | Shandong U | hyperons | |
Wei-Ming Zhang | KSU | 2008 | non-photonic electrons EEMC A_LL |
root [1] TFile::Open("root://deltag5.lns.mit.edu//Volumes/scratch/common/run6/spinTree/spinAnalyses_7156028.tree.root"); root [2] .ls TXNetFile** root://deltag5.lns.mit.edu//Volumes/scratch/common/run6/spinTree/spinAnalyses_7156028.tree.root TXNetFile* root://deltag5.lns.mit.edu//Volumes/scratch/common/run6/spinTree/spinAnalyses_7156028.tree.root KEY: TProcessID ProcessID0;1 00013b6e-72c3-1640-a0e8-e5243780beef KEY: TTree spinTree;1 Spin PWG common analysis tree KEY: TTree ConeJets;1 this can be a friend KEY: TTree ConeJetsEMC;1 this can be a friend KEY: TTree chargedPions;1 this can be a friend KEY: TTree bemcPions;1 this can be a friend root [3] spinTree->AddFriend("ConeJets"); root [4] spinTree->AddFriend("chargedPions"); root [5] spinTree->Draw("chargedPions.fE / ConeJets.fE","chargedPions.fE>0")
If you have the class definitions loaded you can also access member functions directly in the interpreter: root [6] spinTree->Draw("chargedPions.Pt() / ConeJets.Pt()","chargedPions.Pt()>0")
//create a new reader StSpinTreeReader *reader = new StSpinTreeReader(); //add some files to analyze, one at a time or in a text file reader->selectDataset("$STAR/StRoot/StSpinPool/StSpinTree/datasets/run6_rcf.dataset"); //reader->selectFile("./spinAnalyses_6119039.tree.root");
Ok, so we created a new reader and told it we'd be using the files from Run 6 stored on RCF. You can also give it specfic filenames if you'd prefer, but there's really no reason to do so. //configure the branches you're interested in (default = true) reader->connectJets = true; reader->connectNeutralJets = false; reader->connectChargedPions = true; reader->connectBemcPions = true; reader->connectEemcPions = false; reader->connectBemcElectrons = false; //optionally filter events by run and trigger //reader->selectRunList("$STAR/StRoot/StSpinPool/StSpinTree/filters/run6_jets.runlist"); reader->selectRun(7143025); //select events that passed hardware OR software trigger for any trigger in list reader->selectTrigger(137221); reader->selectTrigger(137222); reader->selectTrigger(137611); reader->selectTrigger(137622); reader->selectTrigger(5); //we can change the OR to AND by doing reader->requireDidFire = true; reader->requireShouldFire = true;
In this block we configured the reader to pick up the jets, chargedPions and BEMC pi0s from the files. We also told it that we only wanted to analyze run 7132001, and that we only cared about events triggered by BJP1, L2jet, or L2gamma in the second longitudinal running period. Finally, we required that one of those trigIds passed both the hardware and the software triggers. StJetSkimEvent *ev = reader->event(); TClonesArray *jets = reader->jets(); TClonesArray *chargedPions = reader->chargedPions(); TClonesArray *bemcPions = reader->bemcPions(); long entries = reader->GetEntries(); for(int i=0; i
Error in <tclass::new>: cannot create object of class StHelix</tclass::new>
Everything as a single pdf file (341 pages, 8.2Mb)
Pibero Djawotho
Indiana University
July 31, 2006
Simulation were done by Jason for the SVT review.
Figure 1: Fitted peak integral vs. fit residual sum (U+V) from st_jpsi input stream (J/psi trigger only). | Figure 2: Fitted peak integral vs. fit residual sum (U+V) from st_physics input stream (all triggers except express stream triggers). |
The separation between photons and pions was achieved by using Les cut in the above figures where photons reside above the curve and pions below. The data set used is the st_jpsi express stream.
The transverse profile of an electromagnetic shower in the SMD can be parametrized by the equation below in each SMD plane:
f(x) is the energy in MeV as a function of SMD strip x. The algorithm performs a simultaneous fit in both the U and V plane. The maximal residual (data - fit) is then calculated. A single photon in the SMD should be well descibed by the equation above and therefore will have a smaller maximal residual. A neutral pion, which decays into two photons, should exhibit a larger maximal residual. Typically, the response would be a double peak, possibly a larger peak and a smaller peak corresponding to a softer photon.
This directory contains images of single event SMD responses in both U and V plane. The file name convention is SMD_RUN_EVENT.png. The fit function for a single peak is the one described in the section above with 5 parameters:
Pibero Djawotho
Indiana University
August 4, 2006
The dataset used in this analysis is the 2005 p+p collision at √s=200 GeV with the endcap calorimeter high-tower-1 (eemc-ht1-mb = 96251) and high-tower-2 (eemc-ht2-mb = 96261) triggers.
The file catalog query used to locate the relevant files is:
get_file_list.pl -keys 'path,filename' -delim / -cond 'production=P05if, trgsetupname=ppProduction,filetype=daq_reco_MuDst,filename~st_physics, tpc=1,eemc=1,sanity=1' -delim 0
Pibero Djawotho
Indiana University
August 6, 2006
A detailed description of the EEMC slow simulator is presented at the STAR EEMC Web site.
The following settings were used in running the slow simulator:
//-- //-- Initialize slow simulator //-- StEEmcSlowMaker *slowSim = new StEEmcSlowMaker("slowSim"); slowSim->setDropBad(1); // 0=no action, 1=drop chn marked bad in db slowSim->setAddPed(1); // 0=no action, 1=ped offset from db slowSim->setSmearPed(1); // 0=no action, 1=gaussian ped, width from db slowSim->setOverwrite(1); // 0=no action, 1=overwrite muDst values slowSim->setSource("StEvent"); slowSim->setSinglePeResolution(0.1); slowSim->setNpePerMipSmd(2.0); slowSim->setNpePerMipPre(3.9); slowSim->setMipElossSmd(1.00/1000); slowSim->setMipElossPre(1.33/1000);
EEMC Fast Simulator |
EEMC Slow Simulator |
The plots that follow are sums of individual SMD responses in each plane centered around a common mean (here 0), over a +/-40 strips range. The convention for the parameters in the fits below is:
The simulation is from single photons thrown at the EEMC with the following pT distribution:
The highest tower above 4 GeV in total energy is selected and the corresponding SMD sector fitted for peaks in both planes, where the area of the peaks in the U plane is constrained to be identical to that of the peak in the V plane. The peak is shifted to be centered at 0 where peaks from other events are then summed. The summed SMD response in each plane is displayed below:
Ditto in log scale.
Ditto by sector.
Sector # | SMD-u σcore | SMD-u σtail | SMD-v σcore | SMD-v σtail |
Sector 1 | 0.869033 ± 0.0142868 | 3.42031 ± 0.10226 | 0.84379 ± 0.0185107 | 3.03287 ± 0.0775009 |
Sector 2 | 0.814959 ± 0.0169271 | 2.99941 ± 0.0730426 | 0.889892 ± 0.0163065 | 3.35288 ± 0.0911979 |
Sector 3 | 0.84862 ± 0.0148706 | 3.07648 ± 0.0909689 | 0.914377 ± 0.014706 | 3.72821 ± 0.0966915 |
Sector 4 | 0.924398 ± 0.0144207 | 3.74458 ± 0.10611 | 0.888146 ± 0.0180771 | 3.06618 ± 0.0647075 |
Sector 5 | 0.934218 ± 0.0163887 | 3.45149 ± 0.0944309 | 0.911209 ± 0.0175273 | 3.28633 ± 0.0890581 |
Sector 6 | 0.797976 ± 0.0148133 | 3.20464 ± 0.0986085 | 0.822437 ± 0.018835 | 3.30595 ± 0.118813 |
Sector 7 | 0.836936 ± 0.0150085 | 3.28589 ± 0.0853598 | 0.873338 ± 0.0173883 | 3.16654 ± 0.0838938 |
Sector 8 | 0.828403 ± 0.0167005 | 3.05517 ± 0.075584 | 0.891045 ± 0.0152102 | 3.34806 ± 0.0836394 |
Sector 9 | 0.832881 ± 0.0127855 | 3.3214 ± 0.0762928 | 0.8436 ± 0.0175466 | 3.0183 ± 0.079444 |
Sector 10 | 0.804059 ± 0.0160906 | 3.0943 ± 0.0897946 | 0.874845 ± 0.015788 | 3.18113 ± 0.0748357 |
Sector 11 | 0.930286 ± 0.0187086 | 3.40024 ± 0.0951671 | 0.854395 ± 0.0167265 | 3.21076 ± 0.0812402 |
Sector 12 | 3.33227 ± 0.111911 | 0.848668 ± 0.0142344 | 0.895174 ± 0.0160939 | 3.48527 ± 0.12061 |
In this sample, high tower triggers, eemc-ht1-mb (96251) and eemc-ht2-mb (96261), from the 2005 p+p at √s=200 GeV ppProduction are selected. The highest tower above 4 GeV is chosen and the corresponding SMD sector is searched for peaks in both planes. Peaks from several events are summed together taking care of shifting them around to have a common mean.
Ditto in log scale.
Here, I try to pick a representative sample of electrons from the 2005 pp200 dataset. The cuts used to pick out electrons are:
The selection for electrons is illustrated in the dE/dx plot below, where the pions should be on the left and the electrons on the right.
This study is motivated by Weihong's photon energy loss study where an eta-dependence of reconstructed photon energy to generated photon energy in EEMC simulation was observed.
In this study, the eta-dependence is investigated by running the EEMC slow simulator with the new readjusted weights for the preshower and postshower layers of the EEMC. Details on this are here.
The parameters from the fits are used to plot the fit functions for comparison between Weihong's and Pibero's results.
While the adjusted weights for the different EEMC layers contribute to bringing the ratio of reconstructed energy to generated energy closer to unity, they do not remove the eta-dependence.
In the plot below, I use the energy of the single tower (tower with max energy) presumably the tower the photon hit. The nonlinearity seems to disappear.
In the plot below, I use the energy of the 3x3 cluster of tower centered around the tower with the max energy. The nonlinearity is restored.
The plot below shows Etower/Ecluster vs. eta where the cluster consists of 3x3 towers centered around the max energy tower.
Below is the profile of E_tower/E_cluster vs. eta.
The plot below shows the energy sampled by the entire calorimeter as a function of eta, i.e. sampling fraction as a function of eta.
Sampling fraction integrated over all eta's.
10k muons thrown by Will with:
E=1 GeV |
E=2 GeV |
Summary of Reconstructed/Monte Carlo Photon Energy |
Description |
The study presented here uses Monte Carlo data sets generated by Will Jacobs at different photon energies (5, 10, 20, 40, 80, 160 GeV):
For each photon energy, the ratio E_reco/E_MC vs. eta was plotted and fitted to the function p0+p1*(1-eta), where E_reco is the reconstructed photon energy integrated over the
entire
EEMC. The range of the fit was fixed from 1.15 to 1.95 to avoid EEMC edge effects. The advantage of parametrizing the eta-dependence of the ratio in this way is that p0 is immediately interpretable as the ratio in the middle of the EEMC. The parameters p0 and p1 vs. photon energy were subsequently plotted for the EEMC fast and slow simulator.
EEMC Fast/Slow Simulator Results |
Conclusions |
The parameter p0, i.e. the ratio E_reco/E_MC in the mid-region of the EEMC, increases monotonically from 0.74 at 5 GeV to 0.82 at 160 GeV, and the parameter p1, i.e. the slope of the eta-dependence, also increases monotonically from -0.035 at 5 GeV to 0.038 at 160 GeV. There appears to be a magic energy around 10 GeV where the response of the EEMC is nearly flat across its entire pseudorapidity range. The anomalous slope p1 at 160 GeV for the EEMC slow simulator is an EEMC hardware saturation effect. The EEMC uses 12-bit ADC's for reading out tower transverse energies and is set for a 60 GeV range. Any particle which deposits more than 60 GeV in E_T will be registered as depositing only 60 GeV as the ADC will return the maximum value of 4095. This translates into a limit on the eta range of the EEMC for a particular energy. Let's say that energy is 160 GeV and the EEMC tops at 60 GeV in E_T, then the minimum eta is acosh(160/60)=1.6. This limitation is noticeable in a plot of E_reco/E_MC vs. eta. This anomaly is not observed in the result of the EEMC fast simulator because the saturation behavior was not implemented at the time of the simulation (it has since been corrected). The energy-dependence of the parameter p0 is fitted to p0(E)=a+b*log(E) and the parameter p1 to p1(E)=a+b/log(E). The results are summarized below:
EEMC fast simulator fit p0(E)=a+b*log(E) a = 0.709946 +/- 0.00157992 b = 0.022222 +/- 0.000501239 EEMC slow simulator fit p0(E)=a+b*log(E) a = 0.733895 +/- 0.00359237 b = 0.0177537 +/- 0.0011397 EEMC fast simulator fit p1(E)=a+b/log(E) a = 0.0849103 +/- 0.00556979 b = -0.175776 +/- 0.0138241 EEMC slow simulator fit p1(E)=a+b/log(E) a = 0.0841488 +/- 0.0052557 b = -0.187769 +/- 0.0130445
The following
from the IUCF STAR Web site gives a brief overview of the SMD gamma/pi0 discrimination algorithm using the method of maximal sided fit residual (data - fit). This technique comes to STAR EEMC from the Tevatron via Les Bland via Jason Webb. The specific fit function used in this analysis is:
f(x)=[0]*(0.69*exp(-0.5*((x-[1])/0.87)**2)/(sqrt(2*pi)*0.87)+0.31*exp(-0.5*((x-[1])/3.3)**2)/(sqrt(2*pi)*3.3))
x is the strip id in the SMD-u or SMD-v plane. The widths of the narrow and wide Gaussians are determined from empirical fits of shower shape response in the EEMC from simulation.
In the rest of this analysis, only those photons which have reconstructed pt > 5 GeV are kept. There is no requirement that the photon doesn't convert. The dividing curve between photons and pions is:
f(x)=4*x+1e-7*x**5
The y-axis is integrated yield over the SMD-u and SMD-v plane, and the x-axis is the sum of the maximal sided residual of the SMD-u and SMD-v plane.
Following exchanges with Scott Wissink, the idea is to move from a quintic to a quadratic to reduce the number of parameters. In addition, the perpendicular distance between the curve and a point in the plane is used to estimate the likelihood of a particle being a photon or pion. Distances above the curve are positive and those below are negative. The more positive the distance, the more likely the particle is a photon. The more negative the distance, the more likely the particle is a pion.
Hi Pibero, With your new "linear plus quintic" curve (!) ... how did you choose the coefficients for each term? Or even the form of the curve? I'm not being picky, but how to optimize such curves will be an important issue as we (hopefully soon) move on to quantitative comparisons of efficiency vs purity. As a teaser, please see attached - small loss of efficiency, larger gain in purity. Scott
Hi Pibero, I just worked out the distance of closest approach to a curve of the form y(x) = a + bx^2 and it involves solving a cubic equation - so maybe not so trivial after all. But if you want to pursue this (not sure it is your highest priority right now!), the cubic could be solved numerically and "alpha" could be easily calculated. More fun and games. Scott
Hi Pibero, I played around with the equations a bit more, and I worked out an analytic solution. But a numerical solution may still be better, since it allows more flexibility in the algebraic form of the 'boundary' line between photons and pions. Here's the basic idea: suppose the curved line that cuts between photons and pions can be expressed as y = f(x). If we are now given a point (x0,y0) in the plane, our goal is to find the shortest distance to this line. We can call this distance d (I think on your blackboard we called it alpha). To find the shortest distance, we need a straight line that passes through (x0,y0) and is also perpendicular to the curve f(x). Let's define the point where this straight line intersects the curve as (x1,y1). This means (comparing slopes) (y1 - y0) / (x1 - x0) = -1 / f'(x1) where f'(x1) is the derivative of f(x) evaluated at the point (x1,y1). Rearranging this, and using y1 = f(x1), yields the general result f(x1) f'(x1) - y0 f'(x1) + x1 - x0 = 0 So, given f(x) and the point (x0,y0), the above is an equation in only x1. Solve for x1, use y1 = f(x1), and then the distance d of interest is given by d = sqrt[ (x1 - x0)^2 + (y1 - y0)^2 ] Example: suppose we got a reasonable separation of photons and pions using a curve of the form y = f(x) = a + bx^2 Using this in the above general equation yields the cubic equation (2b^2) x1^3 + (2ab + 1 - 2by0) x1 - x0 = 0 Dividing through by 2b^2, we have an equation of the form x^3 + px + q = 0 This can actually be solved analytically - but as I mentioned, a numerical approach gives us more flexibility to try other forms for the curve, so this may be the way to go. I think (haven't proved rigorously) that for positive values of the constants a, b, x0, and y0, the cubic will yield three real solutions for x1, but only one will have x1 > 0, which is the solution of interest. Anyway, it has been an interesting intellectual exercise! Scott
I made use of the ROOT function TMath::RootsCubic to solve the cubic equation numerically for computing distances of each point to the curve. With the new quadratic curve f(x)=100+0.1*x^2 the efficiency is 63% and the rejection is 82%.
The plot on the left below shows the efficiency of identifying photons over the pt range of 10-30 GeV and the one on the right shows the rejection rate of single neutral pions. Both average about 75% over the pt range of interest.
The plot below shows background rejection vs. signal efficiency for different energy ranges of the thrown gamma/pi0.
Below on the left is a plot of the ratio of the sum of preshower 1 and 2 to tower energy for both photons (red) and pions (blue). On the right is the rejection of pions vs. efficiency of photons as I cut on the ratio of preshower to tower. It is clear from these plots that the preshower layer is not a good gamma/pi0 discriminator, although can be used to add marginal improvement to the separation preovided by the shower max.
ALL ENERGIES |
|
E=20-40 GeV |
|
E=40-60 GeV |
|
E=60-80 GeV |
|
E=80-90 GeV |
|
The plots below show the distribution of clusters in the endcap calorimeter for different partonic pT ranges. 2000 events were generated for each pT range. A cluster is made up of a central high tower above 3 GeV in pT and its surounding 8 neighbors. The total cluster pT must exceed 4.5 GeV.
Below is the pT of direct and decay photons from the Pythia record. Note how the two subsets are well separated at a given partonic pT. Any contamination to the direct photon signal would have to come from higher partonic pT.
Jet |
Gamma |
The gamma fitter runs out of the box. The code consists of the classes StGammaFitter
and StGammaFitterResult
in CVS. After checking out a copy of offline/StGammaMaker, cd into the offline directory and run:
root4star StRoot/StGammaMaker/macros/RunGammaFitterDemo.C
The following plots will be generated on the ROOT canvas and dumped into PNG files.
The class
computes the maximal sided residual of the SMD response in the u- and v-plane for gamma candidates. It is based on C++ code developed by Jason Webb from the original code by Les Bland who got the idea from CDF (?) The algorithm follows the steps below:
[0]*(0.69*exp(-0.5*((x-[1])/0.87)**2)/(sqrt(2*pi)*0.87)+0.31*exp(-0.5*((x-[1])/3.3)**2)/(sqrt(2*pi)*3.3))
/star/institutions/iucf/balewski/prodOfficial06_muDst/
The parameters of the isolation cut were suggested by Steve Vigor:
Hi Pibero,
In general, I believe people have used smaller cone radii for isolation
cuts than for jet reconstruction (where the emphasis is on trying to
recover full jet energy). So you might try something like requiring
that no more than 10 or 20% of the candidate cluster E_T appears
in scalar sum p_T for tracks and towers within a cone radius of
0.3 surrounding the gamma candidate centroid, excluding the
considered cluster energy. The cluster may already contain energy
from other jet fragments, but that should be within the purview of
the gamma/pi0 discrimination algo to sort out. For comparison, Les
used a cone radius of 0.26 for isolation cuts in his original simulations
of gamma/pi0 discrimination with the endcap. Using much larger
cone radii may lead to accidental removal of too many valid gammas.
Steve
This analysis is based on the work of Jan and Justin on SMD Profile Analysis for different TPC momenta. See here for a list of cuts. The original code used by Jan and Justin is here.
/star/institutions/iucf/balewski/prodOfficial06_muDst/
Figure 1: Number of tracks surviving each successive cut
Figure 2a: Number of tracks per trigger id for all electron candidates. Most common trigger ids are:
127652
eemc-jp0-etot-mb-L2jet
EEMC JP > th0 (32, 4 GeV) and ETOT > TH (109, 14 GeV), minbias condition, L2 Jet algorithm, reading out slow detectors, transverse running
127271
eemc-jp1-mb
EEMC JP > th1 (49, 8 GeV) && mb, reading out slow detectors, transverse running
127641
eemc-http-mb-l2gamma
EEMC HT > th1 (12, 2.6 GeV, run < 7100052;13, 2.8 GeV, run >=7100052) and TP > TH1 (17, 3.8 GeV, run < 710052; 21, 4.7 GeV, run>=7100052 ), minbias condition, L2 Gamma algorithm, reading out slow detectors, L2 thresholds at 3.4, 5.4, transverse running
127622
bemc-jp0-etot-mb-L2jet
BEMC JP > th0 (42, 4 GeV) and ETOT > TH (109, 14 GeV), minbias condition, L2 Jet algorithm, reading out slow detectors, transverse running; L2jet thresholds at 8.0,3.6,3.3
Figure 2b: Number of tracks per trigger id for all electron candidates for pT > 4 GeV. The dominant trigger ids become:
127641 | eemc-http-mb-l2gamma | EEMC HT > th1 (12, 2.6 GeV, run < 7100052;13, 2.8 GeV, run >=7100052) and TP > TH1 (17, 3.8 GeV, run < 710052; 21, 4.7 GeV, run>=7100052 ), minbias condition, L2 Gamma algorithm, reading out slow detectors, L2 thresholds at 3.4, 5.4, transverse running |
127262 | eemc-ht2-mb-emul | EEMC HT > th2 (22, 5.0 GeV) && mb, reading out slow detectors, emulated in L2, transverse running, different threshold from 117262 |
127271 | eemc-jp1-mb | EEMC JP > th1 (49, 8 GeV) && mb, reading out slow detectors, transverse running |
127652 | eemc-jp0-etot-mb-L2jet | EEMC JP > th0 (32, 4 GeV) and ETOT > TH (109, 14 GeV), minbias condition, L2 Jet algorithm, reading out slow detectors, transverse running |
Figure 3: pT distribution of tracks before E/p, dE/dx and pT cut
Figure 4: pT distribution of electron candidates with pT > 4 GeV
Figure 5: η distribution of electron candidates (all pT)
Figure 6: φ distribution of electron candidates (all pT)
Figure 7: dE/dx of tracks before E/p and dE/dx cuts (all pT)
Figure 8: dE/dx of tracks before E/p and dE/dx cuts (pT > 4 GeV)
Figure 9: dE/dx of tracks before E/p and dE/dx cuts (all pT and 0.8 < η < 1.0)
Figure 10: dE/dx of tracks before E/p and dE/dx cuts (all pT and 1.0 < η < 1.2)
Figure 11: dE/dx of tracks before E/p and dE/dx cuts (all pT and 1.2 < η < 1.4)
Figure 12: dE/dx of tracks before E/p and dE/dx cuts (all pT and 1.4 < η < 1.6)
Figure 13: dE/dx of tracks before E/p and dE/dx cuts (all pT and 1.6 < η < 1.8)
Figure 14: dE/dx of tracks before E/p and dE/dx cuts (all pT and 1.8 < η < 2.0)
/star/institutions/iucf/hew/2006ppLongRuns/
Figure 2.1
Figure 2.2: The dominant trigger ids are:
137273 | eemc-jp1-mb | EEMC JP > th1 (52, 8.7 GeV) && mb, reading out slow detectors, longitudinal running 2 |
137641 | eemc-http-mb-l2gamma | EEMC HT > th1 (16, 3.5 GeV) and TP > th1 (20, 4.5 GeV), minbias condition, L2 Gamma algorithm, reading out slow detectors, L2 thresholds at 3.7, 5.2, longitudinal running 2 |
137262 | eemc-ht2-mb-emul | EEMC HT > th2 (22, 5.0 GeV) && mb, reading out slow detectors, emulated in L2, longitudinal running 2 |
137222 | bemc-jp1-mb | BEMC JP > th1 (60, 8.3 GeV) && mb, reading out slow detectors, longitudinal running 2 |
Figure 2.3a
Figure 2.3
Figure 2.4
Figure 2.5
Figure 2.6
Figure 2.7
Figure 2.8
Figure 2.9
Figure 2.10
Click here for a tarball of the code used in this analysis.
f(x)=p0*(0.69*exp(-0.5*((x-p1)/0.87)**2)/(sqrt(2*pi)*0.87)+0.31*exp(-0.5*((x-p1)/3.3)**2)/(sqrt(2*pi)*3.3))
p0 = yield
p1 = centroid
21 electrons
99 electrons
This analysis to look for etas at higher energy is in part motivated by this study. The interest in etas, of course, is that their decay photons are well separated at moderate energies (certainly more separated than the photons from pi0 decay). I ran Weihong's pi0 finder with tower seed threshold of 0.8 GeV and SMD seed threshold of 5 MeV (I believe his default SMD seed setting is 2 MeV). I then look in the 2-photon invariant mass region between 0.45 and 0.65 GeV (the PDG nominal mass for the eta is 0.54745 +/- 0.00019 GeV). I observe what looks like a faint eta peak. The dataset processed is the longitudinal 2 run of 2006 from the 20 runs sitting on the IUCF disk in Weihong's directory (/star/institutions/iucf/hew/2006ppLongRuns/).
Within the reconstructed mass window 0.45 to 0.65 GeV, I take a look at the decay photon shower profiles in the SMD. The samples are saved in the file etas.pdf. For the most part, these shower shapes are cleaner than the original sample. Although the statistics are not great.
Hal did a comparison of the widths of the shower shapes between Monte Carlo and data. Below is a description of what was done.
I took the nominal central value, either from the maxHit or the nominal central value, and added the energy in the +/- 12 strips. Then I computed the mean strip (which may have been different from the nominal central value!!). I normalized the shape to give unit area for each smd cluster, and added to the histograms separately for U and V and for MC and data (= Will's events). I did NOT handle Will's events correctly, just using whatever event was chosen randomly, rather than going through his list sequentially. Note I ran 1000 events, and got 94 events in my shower shape histos. So, there are several minor problems. 1) I didn't go through Will's events sequentially. 2) I normalized, but perhaps not to the correct 25 strips, because the mean strip and the nominal strip may have differed. 3) there may have been a cutoff on some events due to being close to one end of the smd plane (near strip 0 or 287). My sense from looking at the plots is that these don't matter much. The conclusion is that the MC shape is significantly narrower than the shape from Will's events, which is obviously narrower than the random clusters we were using at first with no selection for the etas. Hence, we are not wasting our time with this project.
A few histograms were added to the code:
Figure 1:
Data vs. MC mean u-strip
Figure 2:
Data vs. MC mean v-strip
Figure 3:
Data vs. MC u-strip sigma
Figure 4:
Data vs. MC v-strip sigma
Figure 5:
MC E
v
vs. E
u
Figure 6:
Data E
v
vs. E
u
Figure 7:
MC energy asymmetry in SMD planes
Figure 8:
Data energy asymmetry in SMD planes
Figure 9:
Shower shape library index used (picked at random)
Single events shower shapes are displayed in
or
.
In case you missed it, the first look is
. I processed
from the 2006 pp longitudinal 2 runs and picked events tagged with the L2gamma trigger id (137641). I ran the StGammaMaker on the MuDst files from these runs and produced gamma trees. These gamma trees are available at
/star/institutions/iucf/pibero/2007/etaLong/
. Within the StGammaMaker framework, I developed code to seek candidate etas with emphasis on high purity. The macros and source files are:
Note, the workhorse function is
StEtaFinder::findTowerPoints()
.
I fit the diphoton invariant mass with two Gaussians, one for the pi0 peak (p0-p2) and another one for the eta peak (p3-p5) plus a quadratic for the background (p6-p8). The Gaussian is of the form p0*exp(0.5*((x-p1)/p2)**2)
and the quadratic is of the form p6*+p7*x+p8*x**2
. A slightly better chi2/ndf in the fit is achieved by using Breit-Wigner functions instead of Gaussians for the signal here. I calculate the raw yield of etas from the fit as p3*sqrt(2*pi)*p5/bin_width = 85
where each bin is 0.010 GeV wide. I select candidate etas in the mass range 0.45 to 0.55 GeV and plot their photon response in the shower maximum detector here. Since we are interested in collecting photons of pT > 7 GeV, only those candidate photons with pT > 5 GeV will be used in the shower shape library. I also calculate the background under the signal region by integrating the background fit from 0.45 to 0.55 GeV and get 82 counts.
Pibero Djawotho Last updated at Tue Mar 4 16:21:13 EST 2008
The following is a revisited study of E_reco/E_MC for photons with the addition of the SMD energy to E_reco.
SectorVsRunNumber.png 10-Feb-2010 12:22 14K ShowerShapes.png 10-Feb-2010 12:22 17K chiSquareMC.png 10-Feb-2010 12:22 13K chiSquarePibero.png 10-Feb-2010 12:22 16K chiSquareWill.png 10-Feb-2010 12:22 16K chiSquareWillAndMC.png 10-Feb-2010 12:22 17K
The plots below show the conversion process before the Endcap. I look at prompt photons heading towards the Endcap from a MC gamma-jet sample with a partonic pT of 9-11 GeV. I identify those photons that convert using the GEANT record. The top left plot shows the total number of direct photons and those that convert. I register a 16% conversion rate. This is consistent with Jason's 2006 SVT review. The top right plot shows the source of conversion, where most of the conversions emanate from the SVT support cone, also consistent with Jason's study. The bottom left plot shows the separation in the SMD between the projected location of the photon and the location of the electron/positron from conversion.
This
file shows several shower shapes in a single plot for comparison:
These Shower Shapes are binned by:
(pre1==0&&pre2==0)
and (pre1>0||pre2>0)
They are then fitted with a triple-Gaussian of the form:
[0]*([2]*exp(-0.5*((x-[1])/[3])**2)/(sqrt(2*pi)*[3])+[4]*exp(-0.5*((x-[1])/[5])**2)/(sqrt(2*pi)*[5])+(1-[2]-[4])*exp(-0.5*((x-[1])/[6])**2)/(sqrt(2*pi)*[6]))
All fits to MC are with reference to the old Monte carlo fit function:
[0]*(0.69*exp(-0.5*((x-[1])/0.87)**2)/(sqrt(2*pi)*0.87)+0.31*exp(-0.5*((x-[1])/3.3)**2)/(sqrt(2*pi)*3.3))
All fits to the data are with reference to a single
. The fit function is:
[0]*([2]*exp(-0.5*((x-[1])/[3])**2)/(sqrt(2*pi)*[3])+[4]*exp(-0.5*((x-[1])/[5])**2)/(sqrt(2*pi)*[5])+(1-[2]-[4])*exp(-0.5*((x-[1])/[6])**2)/(sqrt(2*pi)*[6]))
Partonic pT=9-11 GeV | Partonic pT=9-11 GeV |
During Run 6, the L2-gamma trigger (trigger id 137641) sampled 4717.10 nb-1 of integrated luminosity. By restricting the jet to the Barrel, |ηjet|<1, and the gamma to the Endcap, 1<ηgamma<2, the yield of gamma-jets is estimated as the product of the luminosity, the cross section, and the fraction of events in the phasespace above. The total cross section reported by Pythia for gamma-jet processes at different partonic pT thresholds is listed in the table below. No efficiencies are included.
pT threshold [GeV] | Total cross section [mb] | Fraction | Ngamma-jets |
5 | 6.551E-05 | 0.0992 | 30654 |
6 | 3.075E-05 | 0.1161 | 16840 |
7 | 1.567E-05 | 0.1150 | 8500 |
8 | 8.654E-06 | 0.1131 | 4617 |
9 | 4.971E-06 | 0.1223 | 2868 |
10 | 2.953E-06 | 0.1151 | 1603 |
The pT slope is exp(-0.69*pT)=2^(-pT)
, so the statistics are halved with each 1 GeV increase in pT.
The purpose of this study is to estimate the photon yield per trigger in the Endcap Electromagnetic Calorimeter during Run 6. The trigger of interest is the L2-gamma trigger. Details of the STAR triggers during Run 6 were compiled in the 2006 p+p run (run 6) Trigger FAQ by Jamie Dunlop. The triggers relevant to this study are reproduced in the table below for convenience.
Trigger id | Trigger name | Description |
117641 | eemc-http-mb-l2gamma | EEMC HT > th1 (12, 2.6 GeV) and TP > TH1 (17, 3.8 GeV), minbias condition, L2 Gamma algorithm, reading out slow detectors, L2 thresholds at 2.9, 4.5 |
127641 | eemc-http-mb-l2gamma | EEMC HT > th1 (12, 2.6 GeV, run < 7100052;13, 2.8 GeV, run >=7100052) and TP > TH1 (17, 3.8 GeV, run < 710052; 21, 4.7 GeV, run>=7100052 ), minbias condition, L2 Gamma algorithm, reading out slow detectors, L2 thresholds at 3.4, 5.4, transverse running |
137641 | eemc-http-mb-l2gamma | EEMC HT > th1 (16, 3.5 GeV) and TP > th1 (20, 4.5 GeV), minbias condition, L2 Gamma algorithm, reading out slow detectors, L2 thresholds at 3.7, 5.2, longitudinal running 2 |
The luminosity sampled by each trigger was also caclulated here by Jamie Dunlop. The luminosity for the relevant triggers is reproduced in the table below for convenience. The figure-of-merit (FOM) is calculated as FOM=Luminosity*PB*PY for transverse runs and FOM=Luminosity*PB2*PY2 for longitudinal runs where PB is the polarization of the blue beam and PY is the polarization of the yellow beam. Naturally, in spin physics, the FOM is the better indicator of statistical precisison.
Trigger | First run | Last run | Luminosity [nb-1] | Figure-of-merit [nb-1] |
117641 | 7093102 | 7096017 | 118.88 | 11.89 |
127641 | 7097009 | 7129065 | 3219.04 | 1099.43 |
137641 | 7135050 | 7156028 | 4717.10 | 687.65 |
For this study, only the trigger of longitudinal running 2 (137641) is used. As mentioned above, at level-0, an EEMC high tower above 3.5 GeV and its associated trigger patch above 4.5 GeV in transverse energy coupled with a minimum bias condition, which is simply a BBC coincidence to ensure a valid collision, is required for the trigger to fire. The EEMC has trigger patches of variable sizes depending on their location in pseudorapidity. (The BEMC has trigger patches of fixed sizes, 4x4 towers.) At level-2, a high tower above 3.7 GeV and a 3x3 patch above 5.2 GeV in transverse energy is required to accept the event.
In addition to selecting events that were tagged online by the L2-gamma trigger, the offline
looks for tower clusters with minimum transverse energy of 5 GeV. These clusters along with their associated TPC tracks, preshower and postshower tiles, and SMD strips form gamma candidates. Gamma trees for the 2006 trigger ID 137641 with primary vertex are located at
/star/institutions/iucf/pibero/2006/gammaTrees/
.
The gamma candidate is required to have no track pointing to any of its towers.
The gamma candidate is required to have 85% of the total transverse energy in a cone of radius 0.3 in eta-phi space around the position of the gamma candidate. That is E
Tgamma
/E
Tcone
> 0.85 and R=√Δη
2
+Δφ
2
=0.3 is the cone radius.
The gamma candidate is matched to the best away-side jet with neutral fraction < 0.9 and cos(φ
gamma
-φ
jet
) < -0.8. The 2006 jet trees are produced by Murad Sarsour at PDSF in
/eliza13/starprod/jetTrees/2006/trees/
. A local mirror exists at RCF under the directory
/star/institutions/iucf/pibero/2006/jetTrees/
.
Jan Balewski has an excellent write-up, Offline spin DB at STAR, on how to get spin states. I obtain the spin states from the skim trees in the jet trees directory. In brief, the useful spin states are:
Blue Beam Polarization | Yellow Beam Polarization | Spin4 |
P | P | 5 |
P | N | 6 |
N | P | 9 |
N | N | 10 |
L2-gamma triggers | 730128 |
Endcap gamma candidates | 723848 |
Track isolation | 246670 |
EMC isolation | 225400 |
Away-side jet | 99652 |
SMD max sided residual | 19281 |
Barrel-only jet | 15638 |
Note the number of L2-gamma triggers include only those events with a primary vertex and at least one gamma candidate (BEMC or EEMC).
After selecting Endcap gamma candidates out of L2-gamma triggers, applying track and EMC isolation cuts, and matching the Endcap gamma candidate to an away-side jet, I record the number of jets below per event. Surprisingly, 8% of the events only have 1 jet. Those are events where the Endcap gamma candidate was not reconstructed as a neutral jet by the jet finder. The question is why.
I display both Barrel and Endcap calorimeter towers (the z-axis represents tower energy) and draw a circle of radius 0.3 around the gamma candidate and a circle of radius 0.7 around the away-side jet for 2006 pp200 run 7136022. Even though many of the gamma candidates not reconstructed by the jet finder are at the forward edge of the Endcap, it is not at all clear why those that are well within the detector are not being reconstructed.
Note:
No cuts on residuals applied.
jet A_LL systematic possibility
While Pythia does a pretty good job of simulating prompt photon production in p+p collisions, it does not include polarization for the colliding protons nor partons. A statistical method for assigning polarization states for each event based on ALL [1] is demonstrated in this section. For an average number of interactions for each unpolarized bunch crossing, Neff, the occurence of an event with a particular polarization state obeys a Poisson distribution with average yield of events per bunch crossing:
For simplicity, the polarizations of the blue and yellow beams are assumed to be P
B
=P
Y
=0.7 and N
eff
=0.01. The "+" spin state defines the case where both beams have the same helicities and the "-" spin state for the case of opposite helicities. The asymmetry A
LL
is calculated from the initial states polarized and unpolarized parton distribution functions and parton-level asymmetry:
The algorithm then consists in alternatively drawing a random value N
int
from the Poisson distributions with mean μ
+
and μ
-
until N
int
>0 at which point an interaction has occured and the event is assigned the current spin state. The functioning of the algorithm is illustrated in Figure 1a where an input A
LL
=0.2 was fixed and N
trials
=500 different asymmetries were calculated. Each trial integrated N
total
=300 events. It is then expected that the mean A
LL
~0.2 and the statistical precision~0.1:
Indeed, both the A
LL
and its error are reproduced. In addition, variations on the number of events per trial were investigated (N
total
) in Figure 1b. The extracted width of the Gaussian distribution for A
LL
is consistent with the prediction for the error (red curve).
Figure 1a | Figure 1b |
For this study, the gamma-jets Monte Carlo sample for all partonic pT were used. As an example, the prompt photon processes for the partonic pT bin 9-11 GeV and their total cross sections are listed in the table below. Each partonic pT bin was divided into 15 files each of 2000 events.
============================================================================== I I I I I Subprocess I Number of points I Sigma I I I I I I----------------------------------I----------------------------I (mb) I I I I I I N:o Type I Generated Tried I I I I I I ============================================================================== I I I I I 0 All included subprocesses I 2000 9365 I 3.074E-06 I I 14 f + fbar -> g + gamma I 331 1337 I 4.930E-07 I I 18 f + fbar -> gamma + gamma I 2 8 I 1.941E-09 I I 29 f + g -> f + gamma I 1667 8019 I 2.579E-06 I I 114 g + g -> gamma + gamma I 0 1 I 1.191E-10 I I 115 g + g -> g + gamma I 0 0 I 0.000E+00 I I I I I ==============================================================================
The cross sections for the different partonic pT bins has been tabulated by Michael Betancourt and is reproduced here for convenience.
Partonic pT [GeV] | Cross Section [mb] |
3-4 | 0.0002962 |
4-5 | 0.0000891 |
5-7 | 0.0000494 |
7-9 | 0.0000110 |
9-11 | 0.00000314 |
11-15 | 0.00000149 |
15-25 | 0.000000317 |
25-35 | 0.00000000990 |
35-45 | 0.000000000449 |
These events were processed through the 2006 pp200 analysis chain, albeit without any cuts on the SMD. The simulated quantities were taken from the Pythia record and the reconstructed ones from the analysis.
Figure 2 |
Figure 3 |
Figure 4 |
Figure 5 |
Figure 6 |
Figure 7 |
Figure 8 |
Figure 9 |
PartonicKinematics.C |
DeltaG.C |
pythia6.tar.gz
from the ROOT site ftp://root.cern.ch/root/pythia6.tar.gz and unpack.
tar zxvf pythia6.tar.gzA directory
pythia6/
will be created and some files unpacked into it. Cd into it and compile the Pythia 6 interface to ROOT.
cd pythia6/ ./makePythia6.linuxFor more information, consult Installing ROOT from Source and skip to the section Pythia Event Generators.
tar zxvf pythia8108.tgzA directory
pythia8108/
will be created. Cd into it and follow the instructions in the README
file to build Pythia 8. Set the environment variables PYTHIA8
and PYTHIA8DATA
(preferably in /etc/profile.d/pythia8.sh
):
export PYTHIA8=$HOME/pythia8108 export PYTHIA8DATA=$PYTHIA8/xmldocRun configure with the option for shared-library creation turned on.
./configure --enable-shared make
tar zxvf root_v5.20.00.source.tar.gz cd root/ ./configure linux --with-pythia6-libdir=$HOME/pythia6 \ --enable-pythia8 \ --with-pythia8-incdir=$PYTHIA8/include \ --with-pythia8-libdir=$PYTHIA8/lib make make installSet the following environment variables (preferably in
/etc/profile.d/root.sh
):
export ROOTSYS=/usr/local/root export PATH=$PATH:$ROOTSYS/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ROOTSYS/lib:/usr/local/pythia6 export MANPATH=$MANPATH:$ROOTSYS/manYou should be good to go. Try running the following Pythia 6 and 8 sample macros:
root $ROOTSYS/tutorial/pythia/pythiaExample.C root $ROOTSYS/tutorial/pythia/pythia8.C
7136022.pdf 7136033.pdf 7136034.pdf 7137036.pdf 7138001.pdf 7138010.pdf 7138032.pdf 7140046.pdf 7143012.pdf 7144014.pdf 7145018.pdf 7145024.pdf 7146020.pdf 7146077.pdf 7147052.pdf 7148027.pdf 7149005.pdf 7152062.pdf 7153008.pdf 7155052.pdf
My blog pages, from first to last:
01/25: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/jan/25/photon-analysis-progress-week-1-21-08-1-25-08. This post discusses the problem with the spike in secondary tracks at eta=1 in our single-particle simulations.
01/28: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/jan/28/further-qa-plots. This post has QA plots for every particle sample Ross generated, both in the barrel and in the endcap.
02/01: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/feb/01/more-qa-plots-time-efficiencies. This post has QA plots for gamma and piminus (barrel and endcap) as well as reconstruction efficiencies.
02/04: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/feb/04/photon-qa-efficiency-plots-error-bars. This post adds error bars to the reconstruction efficiencies for the photon barrel sample.
02/05: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/feb/05/first-clustering-plots. This post has the first clustering plots, for muons and gammas (barrel only), showing cluster energy, energy-weighted cluster eta and phi, and the number of seeds and clusters passing the thresholds for each event.
02/12: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/feb/12/preshower-plots. This post has preshower plots from the gamma barrel sample, but the plots are of all preshowers in the event and use the preshower information generated by the BEMC simulator and so are not useful.
02/13: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/feb/13/more-clustering-plots. This post has geant QA plots combined with the clustering plots from 02/05 above, but for the gamma and piminus barrel samples.
02/19: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/feb/19/cluster-track-matching-plots. This post investigates the cluster-to-track matching for the gamma barrel sample, using a simple distance variable d=sqrt((delta eta)^2+(delta phi)^2)) to match clusters to tracks and plotting the resulting energy distributions, the energy ratio, etc.
02/21: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/feb/21/more-preshower-plots. This post plots preshower distributions but uses the preshower information from the BEMC simulator and so is not useful.
02/28: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/feb/28/further-preshower-plots-not-completed-yet. Figures 1, 3, and 5 in this post plot the geant preshower energy deposition for gammas, piminuses, and muons (Figs 2, 4, and 6 plot reconstructed preshower information again and so are not useful).
03/04: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/mar/04/muon-preshower-plots. This post expands on the post of 02/28, with additional plots using the geant preshower information, including preshower cluster energy vs. tower cluster energy.
03/06: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/mar/06/first-physics-cuts. This post basically recaps the previous post and adds a cut: unfortunately the cut is based partly on the thrown particle energy and so is not useful.
03/18: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/mar/18/smd-qa-plots. This post plots energy-weighted SMD phi and eta distributions, as well as the total energy deposited in the BSMDE and BSMDP strips located behind a cluster.
03/28: http://drupal.star.bnl.gov/STAR/blog-entry/wleight/2008/mar/28/smd-clustering-plots. This post contains SMD clustering plots for barrel gamma and piminus samples.
Information about the 2005 Spin analysis (focused on A_LL and <z>, some QA plots for cross section comparisons) will be archived here. The goal is obviously the 2005 Pi0 spin paper.
Here I show the invariant masses and corresponding widths I obtain using my cross section binning. These are compared to MC values.
The Method:
The results are shown in the two figures below.
Mass:
Width:
Neutral Pion Paper for 2005 data: Final Results.
There are two spin plots planned for the paper, one with the 2005 A_LL and one with the <z>. In addition to this the cross section will be included (analysis by Oleksandr used for publication).
Figure 1: Double longitudinal spin asymmetry for inclusive Pi0 production. The curves show predictions from NLO pQCD calculations based on the gluon distributions from the GRSV, GS-C and DSSV global analyses. The systematic error shown by the gray band does not include a 9.4% normalization uncertainty due to the polarization measurement.
The chi2/ndf for the different model curves are:
GRSV Std: 0.740636
GRSV Max: 3.49163
GRSV Min: 0.94873
GRSV Zero: 0.546512
GSC: 0.513751
DSSV: 0.543775
Figure 2: Mean momentum fraction of Pi0s in their associated jet as a function of p_T for electromagnetically triggered events. The data points are plotted at the bin center in pion p_T and are not corrected for acceptance or trigger effects. Systematic errors, estimated from a variation of the cuts, are shown by the grey band underneath the data points. The lines are results from simulations with the PYTHIA event generator. The solid line includes detector effects simulated by GEANT, while the dotted line uses jet finding on the PYTHIA particle level. The inset shows the distribution of pT, π / pT, Jet for one of the bins, together with a comparison to PYTHIA with a full detector response simulation.
Below are links to details about the two results.
<z> Details
The goal of this analysis is to relate the neutral pions to the jets they are embedded in. The analysis is done using the common spin analysis trees, which provide the necessary tools to combine the jet and neutral pion analysis.
A neutral pion is associated to a parent jet if it is within the jet cone of 0.4 in eta and phi. To avoid edge effects in the detector, only neutral pions with 0.3 < eta < 0.7 are accepted.
E_neutral / E_total < 0.95
higher energy photon of Pi0 > 2.8 GeV (HT1 trigger); > 3.6 GeV (HT2 trigger)
combination HT1/HT2: below 5.7 GeV only HT1 is used, above that both HT1 and HT2 are accepted
The final result uses both HT1 and HT2 triggers, but a trigger separated study has also been done, as shown below. There, HT2 includes only those HT2 triggers that do not satisfy HT1 (because of prescale).
Figure 1: <z> for Pi0 in jets as a function of p_T for HT1 and HT2 triggers. Also shown is the mean jet p_T as a function of pion p_T.
Figure 2: Bin-by-bin ratio of pion to jet p_T. The <z> is taken from the mean of these distributions, the error is the error on the mean. A small fraction of all entries have higher Pi0 p_T than jet p_T. Similar behavior is also observed for Pythia MC with GEANT jets. This obviously increases the <z>. An alternative would be to reject those events. The agreement with MC becomes worse if this is done.
Here is the data - MC comparison for 3 of the above bins. For the simulation, the reconstruction of the Pi0 is not required to keep statistics reasonable, so the true Pi0 pt is used. However, the MC jet finding uses all momenta after Geant, this is why the edges are "smoother" in the MC plot than in the data plots. Since <z> is an average value, this is not expected to be affected by this, since on average the Pi0 pt is reconstructed right.
Figure 3: Data / MC for Bin 5: 6.7 to 8 GeV
Figure 4: Data / MC for Bin 6: 8 to 10 GeV
Figure 5: Data / MC for Bin 7: 10 to 12 GeV
Details on the A_LL result and the systematic studies:
Bin | <p_T> [GeV] in bin | A_LL | stat. error | syst. error |
1 | 4.17 | 0.01829 | 0.03358 | 0.01603 |
2 | 5.41 | -0.01913 | 0.02310 | 0.01114 |
3 | 7.06 | 0.00915 | 0.03436 | 0.01343 |
4 | 9.22 | -0.06381 | 0.06366 | 0.01862 |
Figure 1: A_LL as a function of p_T for HT1 (black) and HT2 (red) triggers separately. HT1 here is taken as all triggers that satisfy the HT1 requirement, but not HT2. Since the HT2 prescale is one, there are very little statistics for HT1 at the highest p_T. The highest p_T point for HT1 is outside the range of the plot, and has a large error bar. The high p_T HT1 data is used in the combined result.
Bin 1 | Bin 2 | Bin 3 | Bin4 | |
relative luminosity | 0.0009 | 0.0009 | 0.0009 | 0.0009 |
non-longitudinal pol. | 0.0003 | 0.0003 | 0.0003 | 0.0003 |
beam background | 0.0012 | 0.0084 | 0.0040 | 0.0093 |
yield extraction | 0.0144 | 0.0044 | 0.0102 | 0.0116 |
invariant mass background | 0.0077 | 0.0061 | 0.0080 | 0.0108 |
total | 0.01603 | 0.01114 | 0.01343 | 0.01862 |
The first two systematics are common to all spin analyses. The numbers here are taken from the jet analysis. No Pi0 non-longitudinal analysis has been performed due to lacking statistics. These systematics are irrelevant compared to the others.
The analysis specific systematics are determined from the data, and as such are limited by statistics. The real systematic limit of a Pi0 analysis with a very large data sit will be much lower.
For the yield extraction systematic the invariant mass cuts for the pion yield extraction are varied. The systematic is derived from the maximum change in asymmetry with changing cuts.
For the beam background, the systematic is derived by studying how much A_LL changes when the beam background is removed. This is a conservative estimate that covers the scenario that only half of the background is actually removed. The asymmetry of the background events is consistent with zero.
For the invariant mass background systematic, A_LL is extracted in three invariant mass bins outside the signal region. The amount of background under the invariant mass peak (includes combinatorics, low mass and others) is estimated from the invariant mass distribution as shown below. For all three bins, the background A_LL is consistent with zero, a "worst case" of value + 1 sigma is assumed as deviation from the signal A_LL.
Figure 2: Invariant mass distribution for HT1 events, second p_T bin. The red lines are the MC expectations for Pi0 and Eta, the green line is low mass background, the magenta line is combinatoric background, the thick blue line is a pol2 expectation for the other background, the blue thinner line is the total enveloppe of all contributions, compared to the data. At low mass, the background is overestimated.
False asymmetries (parity-violating single spin asymmetries) were studied to exclude systematic problems with spin asignments and the like. Of course the absence of problems in the jet analysis with the same data set makes any issues very unlikely, since jet statistics allow much better verifications than Pi0s. Still, single spin asymmetries were studied, and no significant asymmetries were observed. For both triggers, both asymmetries (yellow and blue) and for all p_T bins the asymmetries are consistent with zero, in most cases within one sigma of zero. So there are no indications for systematic effects. The single spin asymmetries are shown below:
Figure 3: Single spin asymmetry epsilon_L for the blue beam.
Figure 4: Single spin asymmetry epsilon_L for the yellow beam.
Here is information regarding my analysis of transverse asymmetries in neutral strange particles using 2006 p + p TPC data. This follows-on from and expands upon the earlier analysis I did, which can still be found at star.bnl.gov/protected/strange/tpb/analysis/. Comments, questions, things-you'd-like-to-see-done and so forth are welcomed. I'll catalogue updates in my blog as I make them.
The links listed below are in 'analysis-order'; best to use these for navigation rather than the alphabetically listed links Drupal links below/in the sidebar.
e-mail me at tpb@np.ph.bham.ac.uk
Data used for this analysis is 2006 p+p 200 GeV data taken with transverse polarisation, trigger setup "ppProductionTrans". This spanned days 97 (7th April) to 129 (9th May) inclusive. Trigger bemc-jp0-etot-mb-l2jet (ID 127622) is used. A file catalogue query with the following conditions gives a list of runs for which data is available:
trgsetupname=ppProductionTrans,tpc=1,year=2006,sanity=1,collision=pp200,
magscale=FullField,filename~physics,library=SL06e,production=P06ie
This generates a list of 549 runs. These runs are then compared against the spin PWG run QC (see http://www.star.bnl.gov/protected/spin/sowinski/runQC_2006) and are rejected if any of the following conditions are true:
This excludes 172 runs, leaving 377 runs to be analysed.
I use a Maker class to create TTrees of event objects with V0 and spin information for these runs. Code for the Maker and Event classes can be found at /star/u/tpb/StRoot/StTSAEventMaker/ and /star/u/tpb/StRoot/StV0NanoDst/ respectively. Events are accepted only if they fulfill the following criteria:
TTrees are produced for 358 runs (19 produce no/empty output), yielding 2,743,396 events.
The vertex distribution of events from each run are then checked by spin bits. A Kolmogorov test (using ROOT TH1::KolmogorovTest) is used to compare the vertex distributions for (4-bit) spin bits values 5, 6, 9 and 10. If any of the distributions are inconsistent, the run is rejected. Each run's mean event vertex z position is then plotted. Figure 1 shows the distribution, fitted with a Gaussian. A 3σ cut is applied and outlier runs rejected. 38 runs are rejected by these further cuts. The remaining 320 runs, spanning 33 RHIC fills and comprising 2,500,421 events, are used in the analysis.
Figure 1: Mean event vertex z for each run. The red lines indicate the 3σ cut. |
I measure a double spin asymmetry defined as follows
Equation 1 |
where N-(anti)parallel indicates yields measured in one half of the detector when the beam polarisations are aligned (opposite) and P1 and P2 are the polarisations of the beams. Accounting for the relative luminosity, these yields are given by
Equation 2 |
Equation 2 |
where the arrows again indicate beam polarisations. Figures one and two show the fill-by-fill measurement of ATT, corrected by the beam polarisation, summed over all pT.
Figure 1: K0S ATT fill-by-fill |
Figure 2: Λ ATT fill-by-fill |
The Bethe-Bloch equation can be used to predict charged particle energy loss. Hans Bichsel's model adds to this and the Bichsel function predictions for particle energy loss are compared with measured values. Tracks with dE/dx sufficiently far from the predicted value are rejected. e.g. when selecting for Λ hyperons, the positive track is required to have dE/dx consistent with that of a proton, and the negative track consistent with that of a π-minus.
The quantity σ = sqrt(N) x log( measured dE/dx - model dE/dx ) / R is used to quantify the deviation of the measured dE/dx from the model value. N is the number of track hits used in dE/dx determination and R is a resolution factor. A cut of |σ| < 3 applied to both V0 daughter tracks was found to significantly reduce the background with no loss of signal. Figures one to three below show the invariant mass distriubtions of the V0 candidates accepted and rejected and table one summarises the results of the cut. Background rejection is more successful for (anti-)Λ than for K0S because most background tracks are pions; the selection of an (anti-)proton daughter rejects the majority of the background tracks.
Figure 1a: Invariant mass spectrum of V0 candidates under K0s hypothesis passing dE/dx cut |
Figure 1b: Invariant mass spectrum of V0 candidates under K0s hypothesis failing dE/dx cut |
Figure 2a: Invariant mass spectrum of V0 candidates under Λ hypothesis passing dE/dx cut |
Figure 2b: Invariant mass spectrum of V0 candidates under Λ hypothesis failing dE/dx cut |
Figure 3a: Invariant mass spectrum of V0 candidates under anti-Λ hypothesis passing dE/dx cut |
Figure 3b: Invariant mass spectrum of V0 candidates under anti-Λ hypothesis failing dE/dx cut |
Species | Pass (millions) | Fail (millions) | % pass |
---|---|---|---|
K0S | 95.5 | 48.9 | 66.2 % |
Λ | 32.5 | 111.9 | 22.5 % |
anti-Λ | 11.8 | 132.5 | 8.2 % |
Table 1
Energy loss cuts are successful in eliminating a significant portion of the background, but further reduction is required to give a clear signal. In addition final yields are calculated by a bin counting method, which requires that the background around the signal peak has a straight line shape. Therefore additional cuts are placed on the V0 candidates based on the geometrical properties of the decay. There are five quantities on which I chose to cut:
I wrote a class to help perform tuning of these geometrical cut quantities (see /star/u/tpb/StRoot/StV0CutTuning/) by a "brute force" approach; different permutations of the above quantities were attempted, and the resulting mass spectra analysed to see which permutations gave the best balance of background reduction and signal retention. In addition, the consistency of the background to a straight-line shape was required. Due to the limits on statistics, signal retention was considered a greater priority than background reduction. The cut values I decided upon are summarised in table one. Figures one to three show the resulting mass spectra (data are from all runs). Yields are calculated from the integral of bins in the signal (red) region minus the integrals of bins in the background (green) regions. Poisson (√N) errors are used. The background regions are fitted with a straight line, skipping the intervening bins. The signal to background quoted is the ratio of the maximum bin content to the value of the background fit evaluated at that mass. Note that the spectra have the the dE/dx cut included in addition to the geometrical cuts.
Species | Max DCA V0 to PV* | Max DCA between daughters | Min DCA + daughter to PV | Min DCA − daughter to PV | Min V0 decay distance |
---|---|---|---|---|---|
K0S | 1.0 | 1.2** | 0.5 | 0.0** | 2.0** |
Λ | 1.5 | 1.0 | 0.0** | 0.0** | 3.0 |
anti-Λ | 2.0** | 1.0 | 0.0** | 0.0** | 3.0 |
Table 1: Summary of geometical cuts. All cut values are in centimetres.
* primary vertex
** default cut present in micro-DST
Figure 1: Final K0S mass spectrum with all cuts applied. |
Figure 2: Final Λ mass spectrum with all cuts applied. |
Figure 3: Final anti-Λ mass spectrum with all cuts applied. |
Equation one shows the cross-formula used to calculate the single spin asymmetry.
Equation 1 |
where N is a particle yield, L(eft) and R(ight) indicate the side of the polarised beam to which the particle is produced and arrows indicate the polarisation direction of the beam. Equation one cancels acceptance and beam luminosity and allows simply the raw yields to be used for the calculation. The asymmetry can be calculated twice; once for each beam, summing over the polarisation states of the other beam to leave it "unpolarised". I previously used only particles produced at forward η when calculating the blue beam asymmetry, and backward η for yellow, but I now sum over the full η range for each. Equations two and three give the numbers for up/down polarisation for blue (westward at STAR) and yellow (eastward) beams respectively in terms of the contributions from the four different beam polarisation permutations, and these permutations are related to spin bits numbers in table one.
Equation 2 |
Equation 3 |
(in e.g. N(upUp), The first arrow refers to yellow beam polarisation, the second to blue beam.)
Beam polarisation | 4-bit spin bits | |
---|---|---|
Yellow | Blue | |
Up | Up | 5 |
Down | Up | 6 |
Up | Down | 9 |
Down | Down | 10 |
Table 1 |
The raw asymmetry is calculated for each RHIC fill, then divided by the polarisation for that fill to give the physics asymmetry. Final polarisation numbers (released December 2007) are used. The error on the raw asymmetry is calculated by propagation of the √(N) errors calculated for each particle yield. The final asymmetry error incorporates the polarisation error (statistical and systematic errors summed in quadrature). The fill-by-fill asymmetries for each K0S and Λ for each beam are shown in figures one and two. Anti-Λ results shall be forthcoming. An average asymmetry is calculated by performing a straight line χ2 fit through the fill-by-fill values with ROOT. Table one summarises the asymmetry results. The asymmetry error is the error from the ROOT fit and is statistical only. All fits give a good χ2 per degree of freedom and are consistent with zero within errors.
Figure 1a: K0S blue beam asymmetry |
Figure 1b: K0S yellow beam asymmetry |
Figure 2a: Λ blue beam asymmetry |
Figure 2b: Λ yellow beam asymmetry |
The above are summed over the entire pT range available. I also divide the data into different transverse momentum bins and calculate the asymmetry as a function of pT. Figures three and four show the pT-dependent asymmetries. No pT dependence is discernible.
Figure 3a: K0S pT-dependent blue beam AN |
Figure 3b: K0S pT-dependent yellow beam AN |
Figure 4a: Λ pT-dependent blue beam AN |
Figure 4b: Λ pT-dependent yellow beam AN |
I also calculate the asymmetry via an alternative method, making use of Tai Sakuma's relative luminosity work. The left-right asymmetry is defined as
Equation 1 |
where NL is the particle yield to the left of the polarised beam. The decomposition of the up/down yields into contributions from the four different beam polarisation permutations is the same as given in the cross-asymmetry section (equations 2 and 3). Here, the yields must be scaled by the appropriate relative luminosity, giving the following relations:
Equation 2 |
Equation 3 |
The relative luminosities R4, R5 and R6 are the ratios of luminosity for, respectively, up-up, up-down and down-up bunches to that for down-down bunches. I record the particle yields for each polarisation permutation (i.e. spin bits) on a run-by-run basis, scale each by the appropriate relative luminosity for that run, then combine yields from all the runs in a given fill to give fill-by-fill yields. These are then used to calculate a fill-by-fill raw asymmetry, which is scaled by the beam polarisation. The figures below show the resultant fill-by-fill asymmetry for each beam and particle species, summed over all pT. The fits are again satisfactory, and give asymmetries consistent with zero within errors, as expected.
Figure 1a: Blue beam asymmetry for K0S |
Figure 1b: Yellow beam asymmetry for K0S |
Figure 2a: Blue beam asymmetry for Λ |
Figure 2b: Yellow beam asymmetry for Λ |
The appearance of the decay of an unobserved neutral strange particle into two observed charged daughter particles gives rise to the terminology 'V0' to describe the decay topology. The following neutral strange species have been analysed:
Species | Decay channel | Branching ratio | K0S | π+ + π- | 0.692 |
---|---|---|
Λ | p + π- | 0.639 |
anti-Λ | anti-p + π+ | 0.639 |
Candidate V0s are formed by combining together all possible pairs of opposite charge-sign tracks in an event. The invariant mass of the V0 candidate under different decay hypotheses can then be determined from the track momenta and the daughter masses (e.g. for Λ the positive daughter is assumed to be a proton, the negative daughter a π-minus). Raw invariant mass spectra are shown below. The spectra contain three contributions: real particles of the species of interest; neutral strange particles of a different species; combinatorial background from chance positive/negative track crossings.
Figure 1: Invariant mass spectrum under K0s hypothesis |
Figure 2: Invariant mass spectrum under Λ hypothesis |
Figure 3: Invariant mass spectrum under anti-Λ hypothesis |
Selection cuts are applied to the candidates to suppress the background whilst maintaining as much signal as possible. There are two methods for reducing background; energy-loss particle identification and geometrical cuts on the V0 candidates.
Ilya Selyuzhenkov January 30, 2008
jet trees by Murad Sarsour for pp2006 run, runId=7136022 (~60K events, no triggerId cuts yet)
R_EM1 >0.9 and R_EM2 < 0.9
cos(phi1 - phi2) < -0.9
nChargeTracks1 < 2
0 < nEEMCtowers1 < 3
Ilya Selyuzhenkov February 13, 2008
Gamma-jet selection cuts are discussed here. There are 278 candidates found for runId=7136022.
Transverse momentum distribution for the gamma-jet candidates can be found here.
Figure 1: Vertex z distribution.
Red line presents gamma-jet candidates (scaled by x50). Black is for all di-jet events.
Same data on a log scale is here.
EEMC response event by event for all 278 gamma-jet candidate can be found in this pdf file.
Each page shows SMD/Tower energy distribution for a given event:
First row on each page shows SMD response
for the sector which has a maximum energy deposited in the EEMC Tower
(u-plane is on the left, v-plane is on the right).
In the left plot (u-plane energy distribution) numerical values for
pt of the first jet (with maximum EM fraction) and the second jet are given.
In addition, fit results assuming gamma (single Gaussian, red line) or
neutral pion (double Gaussian, blue line ~ red+green) hypotheses are given.
If m_{gamma gamma} value is negative, then the reconstruction procedure has failed
(for example, no uv-strips intersection found, or tower energy and uv-strips intersection point mismatch, etc).
EEMC response for these "bad" events can be found in this pdf file.
If reconstruction procedure succeded, then
m_{gamma gamma} gives reconstructed invariant mass assuming that two gammas hit the calorimeter.
Figure 3: invariant mass distribution (assuming pi0 hypothesis).
Note, that I'm still working on my fitting algorithm (which is not explained here),
and fit results and the invariant mass distribution will be updated.
It is also shown the ratio for each u/v plane
of the integrated single Gaussian fit (red line) to the total energy in the plane
(look for "gamma U/V " values on the right v-plane plot).
Second and third rows on each page show the energy deposition in the
tower, pre-shower1, pre-shower2, and post-shower as a function of eta:phi (etaBin:phiBin).
Trying to isolate the real gammas which hits the calorimeter,
I have sorted events into different subsets based on the following set of cuts:
if (invMass < 0) reject
if (jet2_pt > jet1_pt) reject
if (jet1_pt < 7) reject
if (minFraction < 0.75) reject
(minFraction = gamma U/V - is a fraction of the integrated single Gaussian peak to the total energy in the uv-plane)
Figure 4: Sample gamma-jet candidate EEMC response
(all gamma-jet candidates selected according to these conditions can be found in this pdf file):
if (invMass < 0) reject
if (jet2_pt < jet1_pt) reject
if (jet2_pt < 7) reject
if (minFraction < 0.75) reject
Event by event EEMC response for pi0 (di-jet) candidates
selected according to these conditions can be found in this pdf file.
Ilya Selyuzhenkov February 20, 2008
After processing all available jet-trees for pp2006 (ppProductionLong),
and applying all "gamma-jet" cuts (which are described below):
there are 47K di-jet events selected
for pt1>7GeV there are 5,4K gamma-jet candidates (3,7K with an additional cut of pt1>pt2)
Figure 1: 2,4K events with both pt1, pt2 > 7GeV
721 candidates within a range of pt1>pt2 and both pt1, pt2 > 7 GeV
jet trees by Murad Sarsour for pp2006 run, number of runs processed: 323
4.7M di-jet events found (no triggerId cuts yet)
R_EM1 >0.9 and R_EM2 < 0.9
cos(phi1 - phi2) < -0.9
nChargeTracks1 < 2
0 < nEEMCtowers1 < 3
Ilya Selyuzhenkov February 27, 2008
Gamma-jet isolation cuts:
R_EM1 >0.9 and R_EM2 < 0.9
cos(phi1 - phi2) < -0.8
nCharge1 = 0
for each gamma-jet candidate finding a tower with a maximum energy
associated with a jet1 (jet with a maximum EM fraction).
Calculating energy of the cluster by finding all adjacent towers and adding their energy together.
R_cluster is defined as a ratio of the cluster energy
to the total energy in the calorimeter associated with a jet1.
Note, that with a cut Ncharge1 =0, energy in the calorimeter is equal to the jet energy.
Figure 4: R_cluster vs number of towers fired in EEMC (left) and BEMC (right). No pt cuts.
Figure 5: R_cluster vs number of towers fired in EEMC (left) and BEMC (right). Additional cut: pt1>7GeV
Figure 6: jet1 pseudorapidity vs number of towers fired in EEMC (left) and BEMC (right).
EEMC candidates: nTowerFiredBEMC=0
BEMC candidates: nTowerFiredEEMC=0
Figure 7: Pseudorapidity (left EEMC, right BEMC candidates)
Figure 8: Azimuthal angle (left EEMC, right BEMC candidates)
Figure 9: Transverse momentum (left EEMC, right BEMC candidates)
Figure 10: Transverse momentum (left EEMC, right BEMC candidates): pt1>7GeV
Figure 11: Transverse momentum (left EEMC, right BEMC candidates): pt1>7 and pt2>7
Ilya Selyuzhenkov March 03, 2008
Data set: ppLongitudinal, runId = 7136033.
Some observations/questions:
In general distributions look clean and good
Sectors 7 and 9 for v-plane and sector 7 for u-plane are noise.
Sector 9 has a hot strip (id ~ 120)
In sector 3, strips id=0-5 in v-plane are hot (see figure 2 right, bottom)
Sectors 2 and 8 in u-plane and sectors 3 and 9 in v-plane have missing strips id=283-288?
Strips 288 are always empty?
Figure 1:Average energy E in the strip vs sector and strip number (max < E > = 0.0027)
same figure on a log scale
Figure 2: Average energy E for E>0.02 (max < E > = 0.0682)
Same figure on a log scale
Ilya Selyuzhenkov March 12, 2008
Note: Di-jet transverse momentum distribution for these candidates can be found on figure 11 at this page
Figure 1:Invariant mass distribution for gamma-jet candidates assuming pi0 (2-gammas) hypothesys
Figure 2:Invariant mass distribution for gamma-jet candidates assuming pi0 (2-gammas) hypothesys
with an additional SMD isolation cut: gammaFraction >0.75
GammaFraction is defined as ratio of the integral
other SMD strips for the first peak to the total energy in the sector
pdf file (first 100 events) with event by event EEMC response for the candidates reconstructed into pion mass (gammaFraction >0.75)
pdf file with event by event EEMC response for the candidates not reconstructed into pion mass
(second peak not found), but has a first peak with gammaFraction >0.75.
Ilya Selyuzhenkov March 20, 2008
The procedure to discriminate gamma candidate from pions (and other background)
based on the SMD response is described at Pibero's web page.
Figure 1: Fit integral vs maximum residual for gamma-jet candidates requesting
no energy deposited in the EEMC pre-shower 1 and 2
(within a 3x3 clusters around tower with a maximum energy).
Black line is defined from MC simulations (see Jason's simulation web page, or Pibero's page above).
Figure 2: Fit integral vs maximum residual for gamma-jet candidates requesting requesting
no energy deposited in pre-shower 1 cluster and
no energy deposited in post-shower cluster (this cut is not really essential in demonstrating the main idea)
Figure 3: Fit integral vs maximum residual for gamma-jet candidates requesting requesting
non-zero energy deposited in both clusters of pre-shower 1 and 2
Event by event EEMC response for gamma-jet candidates for the case of
no energy deposited in the EEMC pre-shower 1 and 2 can be found in this pdf file
Figure 4: Fit integral vs maximum residual for gamma-jet candidates requesting
no energy deposited in the EEMC pre-shower 1 and 2
Figure 5: Fit integral vs maximum residual for gamma-jet candidates requesting requesting
no energy deposited in pre-shower 1 cluster and
no energy deposited in post-shower cluster
Figure 6: Fit integral vs maximum residual for gamma-jet candidates requesting requesting
non-zero energy deposited in both clusters of pre-shower 1 and 2
Event Monte Carlo shape allows to distinguish gammas from background by cutting at chi2/ndf < 0.5
(although the distribution looks wider than for the case of Will's shape).
Figure 7: Chi2/ndf for gamma-jet candidates using Monte Carlo shape requesting
no energy deposited in both clusters of pre-shower 1 and 2
Figure 8: Chi2/ndf for gamma-jet candidates using Monte Carlo shape requesting
non-zero energy deposited in both clusters of pre-shower 1 and 2
Less clear where to cut on chi2?
Figure 9: Chi2/ndf for gamma-jet candidates using Monte Carlo shape requesting
no energy deposited in both clusters of pre-shower 1 and 2
Figure 10: Chi2/ndf for gamma-jet candidates using Monte Carlo shape requesting
non-zero energy deposited in both clusters of pre-shower 1 and 2
Ilya Selyuzhenkov March 26, 2008
Definitions:
All results are for combined distributions from u and v planes: ([u]+[v])/2
Gamma-jet isolation cuts described here
Additional quality cuts:
Figure 1: F_peak vs maximum residual
for various cuts on energy deposited in the EEMC pre-shower 1 and 2
(within a 3x3 clusters around tower with a maximum energy).
Figure 2: F_data vs D_tail^max
Note:This plot is fit independend (only the peak position is defined based on the fit)
Figure 3: F_data vs D_tail^max-D_tail^max
Figure 4: Gamma transverse momentum vs jet transverse momentum
Figure 5: F_peak vs maximum residual
for various cuts on energy deposited in the EEMC pre-shower 1 and 2
(within a 3x3 clusters around tower with a maximum energy).
Figure 6: F_data vs D_tail^max
Note:This plot is fit independend (only the peak position is defined based on the fit)
Figure 7: F_data vs D_tail^max-D_tail^max
Figure 8: Gamma transverse momentum vs jet transverse momentum
Figure 9: Gamma pseudorapidity vs jet pseudorapidity
Figure 10: Gamma azimuthal angle vs jet azimuthal angle
Note: for the case of Pre1>1 && Pre2==0 there is an enhancement around phi_gamma = 0?
Figure 11: maximum strip in v-plane vs maximum strip in u-plane
Figure 12:Chi2/ndf for gamma-jet candidates using Monte Carlo shape (combined for [u+v]/2 plane )
Figure 13:Chi2/ndf for gamma-jet candidates (combined for [u+v]/2 plane ) using Will's shape
Ilya Selyuzhenkov March 28, 2008
One interpretation of this can be that in Monte Carlo simulations
the contribution from the material in front of the detector is underestimated
Triple Gaussian fit gives a better description of the data shapes,
compared to the double Gaussian function (compare red and black lines on Figure 1-4)
Figure 1: EEMC SMD shape comparison for various preshower cuts
(black points shows u-plane shape only, v-plane results can be found here)
Figure 2: EEMC SMD shape comparison for various preshower cuts with gamma-jet pt cut of 7GeV
(black points shows u-plane shape only, v-plane results can be found here)
Figure 3: Shapes with an additional cut on 2-gamma candidates within pi0 invariant mass range.
Sample invariant mass distribution using "simple" pi0 finder can be found here
(black points shows u-plane shape only, v-plane results can be found here)
Figure 4: Shapes for the candidates when "simple" pi0 finder failed to find a second peak
(black points shows u-plane shape only, v-plane results can be found here)
Figure 5: Strip by strip SMD energy distribution.
Only 12 strips from the right side of the maximum are shown.
Zero strip (first upper left plot) corresponds to the high strip in the shape
Note, that already at the 3rd strip from a peak,
RMS values are comparable to those for a mean, and for a higher strips numbers RMS starts to be bigger that mean.
(results for u-plane only, v-plane results can be found here)
Results for side residual (together with pt, eta, phi distributions) for gamma-jet candidates can be found at this web page
Red histograms on Figures 6-8 shows chi2 distribution from MC-photons (normalized at chi2=1.4)
Blue histograms on Figures 6-8 shows chi2 distribution from MC-pions (normalized at chi2=1.4)
Figure 6: Chi2/ndf for gamma-jet candidates using Monte Carlo shape
Figure 7: Chi2/ndf for gamma-jet candidates using Will's shape (derived from eta candidates based on Weihong's pi0-finder)
Figure 8: Chi2/ndf for gamma-jet candidates using Pibero's shape (derived from eta candidates)
Ilya Selyuzhenkov April 02, 2008
Figure 1: EEMC SMD shape comparison for various preshower cuts
Note:Only MC gamma-jet shape (open red squares) is the same on all plots
Ilya Selyuzhenkov April 02, 2008
Figure 1: Side residual for various cuts on energy deposited in the EEMC pre-shower 1 and 2
No EEMC SMD based cuts
Figure 2: Side residual for various cuts on energy deposited in the EEMC pre-shower 1 and 2
"Simple" pi0 finder can not find a second peak
Figure 3: Side residual for various cuts on energy deposited in the EEMC pre-shower 1 and 2
"Simple" pi0 finder reconstruct the invarian mass within [0.1,0.18] range
Figure 4: Side residual distribution (Projection for side residual in Figs.1-3 on vertical axis)
Figure 5: Signal (green: m < 0) vs background (black, red) separation
Ilya Selyuzhenkov April 02, 2008
Figure 1: Side residual for various cuts on energy deposited in the EEMC pre-shower 1 and 2
No EEMC SMD based cuts
Ilya Selyuzhenkov April 03, 2008
Hi Ilya,
I think you gave up on the chi-squared method too quickly, and am sorry I missed the phone meeting last week. So, I would like to make a request that will hopefully take a minimal amount of your time to show that all is okay. Then, if there is a delay in getting the sided residual information out and into the beam use request, you can still fall back on the chi-squared method.
In your March 28 posting, Figure 8 at the bottom, I would like to get numerical values for the events per bin for the black curves. I won't use the preshower1>0 and preshower2=0 data, so those you don't need to send. Also, I won't use the red or blue curve information.
I think your problem has been that you normalized your curves at chi-squared/ndf = 1.4 instead of the peak. What I plan to do is to normalize the (pre1=0, pre2=0) to the (pre1=0, pre2>0) data in the peak and subtract. The (pre1=0, pre2=0) set should have some single photons, but also some multiple photons. The (pre1=0, pre2>0) should also have single photons, and more multiple photons, since the chance that one of them will convert is larger. The difference should look roughly like your blue curve, though perhaps not exactly if Pibero's mean shower shape is not perfect (which it isn't). I will do the same thing with taking the difference between (pre1>0, pre2>0) and (pre1=0, pre2=0), and again the difference should look roughly like your blue curve. The (pre1>0, pre2>0) data should have even larger fraction of multiple photons than either of the other two data sets. I would expect the two difference curves to look approximately the same.
Hope this is possible for you to do. Since our reduced chi-squared curve looks so much like the one from CDF, I am pretty confident that we are okay, but this should be checked to convince people that we are not doing anything terribly wrong.
Dear Hal,
I have tried to implement your idea and produce a figure attached.
There are 4 plots in it:
1. Upper left plot shows normalized to unity (at maximum) chi2 distribution (obtained with Pibero shape for gamma-jet candidates) for a different pre1, pre2 conditions
2. Upper right plot shows bin-by-bin difference: a) between normalized chi2 for pre1=0, pre2>0 and pre1=0, pre2=0 (red) and b) between normalized chi2 for pre1>0, pre2>0 and pre1=0, pre2=0 (blue)
3. Bottom left Same as upper right, but normalization were done based on the integral within [-4,4] bins around maximum.
4. Bottom right Same as for upper right, but with a different normalization ([-4,4] bins around maximum)
I have also tried to normalized by the total integral, but the results looks similar.
Figure 1: See description above
Ilya Selyuzhenkov April 09, 2008
Data sample:
Monte-Carlo gamma-jet sample for partonic pt range of 5-7, 7-9, 9-11,11-15, 15-25, 25-35 GeV.
Analysis: Simulated MuDst files were first processed through jet finder algorithm (thanks to Renee Fatemi),
and later analyzed by applying gamma-jet isolation cuts (see this link for details) and studying EEMC SMD response (see below).
To test the algorithm, Geant records were not used in this analysis.
Further studies based on Geant records (yield estimates, etc) are ongoing.
Figure 1:Comparison between shower shape profile for data and MC.
Black circles shows results for MC gamma-jet sample (all partonic pt).
For v-plane results see this figure
Figure 2:Gamma vs jet transverse momentum.
Figure 3:Gamma vs jet azimuthal angle.
Figure 4:Gamma vs jet pseudo-rapidity.
Definitions for F_peak, D_peak, D_tail^max (D_tail^min) can be found here
Figure 5:F_peak vs maximum residual
for various cuts on energy deposited in the EEMC pre-shower 1 and 2
(within a 3x3 clusters around tower with a maximum energy).
Shower shape used to fit data is fixed to the shape from the previous gamma-jet study of real events
(see black point on Fig.1 [upper left plot] at this page)
Figure 6: F_peak vs D_tail^max: click here
Figure 7: F_peak vs D_tail^max-D_tail^min: click here
Figure 8:Logarithmic fraction of energy in post shower (3x3 cluster) to the total energy in SMD u- and v-planes
Figure 8a:
Same as figure 8, but for gamma-jet candidates from the real data (no pt cuts).
Logarithmic fraction of energy in post shower (3x3 cluster) to the total energy in SMD u- and v-planes
Figure 8b:
Comparison between gamma-jet candidates from data with different preshower conditions.
Points are normalized in peak to the case of pre1 > 0, pre2 > 0
Logarithmic fraction of energy in post shower (3x3 cluster) to the total energy in SMD u- and v-planes
Figure 8c:
Comparison between gamma-jet candidates from Monte-Carlo simulations with different preshower conditions.
Points are normalized in peak to the case of pre1 > 0, pre2 > 0
Logarithmic fraction of energy in post shower (3x3 cluster) to the total energy in SMD u- and v-planes
Figure 9: Jet neutral energy fraction
Figure 10: High v-strip vs u-strip
Figure 11: energy post shower (3x3 cluster)
Figure 12: Peak energy SMD-u
Figure 13: Peak energy SMD-v
Figure 14: Gamma phi
Figure 15: Gamma pt
Figure 16: Gamma eta
Figure 17: Delta gamma-jet pt
Figure 18: Delta gamma-jet eta
Figure 19: Delta gamma-jet phi
Figure 20:chi2 distribution using "standard" MC shape
Ilya Selyuzhenkov April 16, 2008
Figure 1: Sided residual for raw MC (partonic pt 9-11)
Figure 2: Sided residual for data-driven MC (partonic pt 9-11)
Figure 3: Sided residual for data (pp Longitudinal 2006)
Figure 4: Number of events which passed various cuts (MC data, partonic pt 9-11)
Ilya Selyuzhenkov April 17, 2008
MC data for different pt weigted according to Michael Betancourt web page:
weight = xSection[ptBin] / xSection[max] / nFiles
Figure 1: Sided residual for raw MC (partonic pt 5-35)
(same plot for partonic pt 9-11)
Figure 2: Sided residual for data-driven MC (partonic pt 5-35)
(same plot for partonic pt 9-11)
Figure 3: Sided residual for data (pp Longitudinal 2006)
Figure 4: Sided residual for data (pp Longitudinal 2006)
Figure 5: Sided residual for data (pp Longitudinal 2006)
Figure 6: pt(gamma) from geant record vs
pt(gamma) from energy in 3x3 tower cluster and position for uv-intersection wrt vertex
(same on a linear scale)
Figure 7: pt(gamma) from geant record vs
pt(jet) as found by the jet-finder
Figure 8: gamma pt distribution:
data-driven MC (red) vs gamma-jet candidates from pp2006 longitudinal run (black).
MC distribution normalized to data at maximum for each preshower condition
Figure 9: Number of events which passed various cuts (MC data, partonic pt 5-35)
Red: cuts applied independent
Black: cuts applied sequential from left to right
Ilya Selyuzhenkov April 23, 2008
MC data for different partonic pt are weigted according to Michael Betancourt web page:
weight = xSection[ptBin] / xSection[max] / nFiles
Figure 1:Sided residual for data-driven gamma-jet MC events (partonic pt 5-35)
Figure 2:Sided residual for data-driven jet-jet MC events (partonic pt 3-55)
Figure 3:Sided residual for data (pp Longitudinal 2006)
Figure 4:pt(gamma) vs pt(jet) for data-driven gamma-jet MC events (partonic pt 5-35)
Figure 5:pt(gamma) vs pt(jet) for data-driven jet-jet MC events (partonic pt 3-55)
Figure 6:pt(gamma) vs pt(jet) for data (pp Longitudinal 2006)
Ilya Selyuzhenkov May 05, 2008
Data samples:
Figure 1:pt distribution. MC data are scaled to the same luminosity as data
(Normalization factor: Luminosity * sigma / N_events).
Figure 2:Integrated gamma yield vs pt.
For each pt bin yield is defined as the integral from this pt up to the maximum available pt.
MC data are scaled to the same luminosity as data.
Figure 3:Signal to background ratio (all results divided by the data)
You can find sided residual 2-D plots here
Figure 4:Maximum sided residual for pt_gamma>7GeV; pt_jet>7GeV
Figure 5:Fitted peak for pt_gamma>7GeV; pt_jet>7GeV
Figure 6:Max data tail for pt_gamma>7GeV; pt_jet>7GeV
Figure 7:Max minus min data tails for pt_gamma>7GeV; pt_jet>7GeV
Ilya Selyuzhenkov May 08, 2008
Figure 1:y:x EEMC position for gamma-jet candidates:
Pythia gamma-jet sample (~170K events). Partonic pt range 5-35 GeV.
Figure 2:y:x EEMC position for gamma-jet candidates:
Pythia QCD bg sample (~4M events). Partonic pt range 3-65 GeV.
Figure 3:y:x EEMC position for gamma-jet candidates:
pp2006 (long) data [eemc-http-mb-l2gamma:137641 trigger]
Figure 3b:y:x EEMC position for gamma-jet candidates:
pp2006 (long) data [eemc-http-mb-l2gamma:137641 trigger]
pt cut of 7 GeV for gamma and 5GeV for the away side jet has been applied.
Figure 4:High v-strip vs high u-strip.
Pythia gamma-jet sample (~170K events). Partonic pt range 5-35 GeV.
Figure 5:High v-strip vs high u-strip:
Pythia QCD bg sample (~4M events). Partonic pt range 3-65 GeV.
Figure 6:High v-strip vs high u-strip:
pp2006 (long) data [eemc-http-mb-l2gamma:137641 trigger]
Figure 6b:High v-strip vs high u-strip:
pp2006 (long) data [eemc-http-mb-l2gamma:137641 trigger]
pt cut of 7 GeV for gamma and 5GeV for the away side jet has been applied.
Ilya Selyuzhenkov May 09, 2008
For a three data samples (pp2006 [long], MC gamma-jet, and MC QCD background events)
the EEMC detector eta cut of 1< eta < 1.4 has been applied.
Although a poor statistics available for MC background QCD sample,
the signal to background ratio (red to green line ratio)
getting closer to 1:3 (expected signal to background ratio from Les study).
Figure 1:Gamma pt distribution. MC data are scaled to the same luminosity as data
(Normalization factor: Luminosity * sigma / N_events).
Figure 2:Gamma yield vs pt. MC data are scaled to the same luminosity as data.
Figure 3:Signal to background ratio (MC results are normalized to the data)
Ilya Selyuzhenkov May 14, 2008
Correlation between gamma-candidate 3x3 cluster energy ratio (R_cluster) and
number of EEMC towers in a jet1 can be found here (Fig. 4).
Gamma pt distribution, yield and signal to background ratio plots
for a cut of R_cluster >0.9 can be found here (Figs. 1-3).
Gamma pt distribution, yield and signal to background ratio plots
for a cut of R_cluster >0.99 are shown below in Figs. 1-3.
One can see that by going from R_cluster>0.9 to R_cluster>0.99
improves signal to background ratio from ~ 1:10 to ~ 1:5 for gamma pt>10 GeV
Figure 1:Gamma pt distribution for R_cluster >0.99.
MC results scaled to the same luminosity as data
(Normalization factor: Luminosity * sigma / N_events).
Figure 2:Integrated gamma yield vs pt for R_cluster >0.99
For each pt bin yield is defined as the integral from this pt up to the maximum available pt.
MC results scaled to the same luminosity as data.
Figure 3:Signal to background ratio for R_cluster >0.99 (all results divided by the data)
Compare this figure with that for R_cluster>0.9 (Fig. 3 at this link)
Figure 4: pt asymmetry between gamma and the away side jet (R_cluster >0.9)
for a three data samples (pp2006[long] data, gamma-jet MC, QCD jets background).
pt cut of 7 GeV for both gamma and jet has been applied.
Figure 5: signal to background ratio (R_cluster >0.9)
as a function of pt asymmetry between gamma and the away side jet
pt cut of 7 GeV for both gamma and jet has been applied.
Figure 6: pt asymmetry between gamma and the away side jet (R_cluster >0.99)
for a three data samples (pp2006[long] data, gamma-jet MC, QCD jets background).
pt cut of 7 GeV for both gamma and jet has been applied.
Figure 7: signal to background ratio
as a functio of pt asymmetry between gamma and the away side jet (R_cluster >0.99)
pt cut of 7 GeV for both gamma and jet has been applied.
Figure 8: pt asymmetry between gamma and the away side jet (R_cluster >0.99)
for a three data samples (pp2006[long] data, gamma-jet MC, QCD jets background).
pt cut of 7 GeV for gamma and 5GeV for the away side jet has been applied.
Figure 9: signal to background ratio
as a function of pt asymmetry between gamma and the away side jet (R_cluster >0.99)
pt cut of 7 GeV for gamma and 5GeV for the away side jet has been applied.
Ilya Selyuzhenkov May 15, 2008
Figure 1:Vertex z distribution for pp2006 (long) data [eemc-http-mb-l2gamma:137641 trigger]
Note: In the upper right plot (pre1=0, pre2>0) one can see
a hole in the acceptance in the range bweeeen z_vertex -10 to 30 cm (probably due to SVT construction)
Figure 1b:Vertex z distribution for pp2006 (same as Fig. 1, but on a linear scale)
Figure 2:Vertex z distribution for three different data samples
MC results scaled to the same luminosity as data
Figure 3:Vertex z distribution for three different data samples
pt cut of 7 GeV for gamma and 5GeV for the away side jet has been applied.
Ilya Selyuzhenkov May 20, 2008
Selecting only di-jet events identified by the STAR jet finder algorithm,
with jets pointing opposite in azimuth:
cos(phi_jet1 - phi_jet2) < -0.8
Data sample:
Note, that all shapes are normalized at peak to unity
Figure 1:Shower shapes for different detector eta bins
Figure 2:Shower shapes for different detector phi bins
Figure 3:Shower shapes for different gamma pt bins
Figure 4:Shower shapes for different z-vertex bins
Ilya Selyuzhenkov May 21, 2008
Data sample:
Subset of 441 eta-meson candidates from Will's analysis.
additional QA info (detector eta, pre1, pre2, etc)
has been added to pi0-tree reader script:
/star/institutions/iucf/wwjacobs/newEtas_fromPi0finder/ReadEtaTree.C
pi0 trees from this RCF directory has been used to regenerate etas NTuple:
/star/institutions/iucf/wwjacobs/newEtas_fromPi0finder/out_23/
Some observations:
eta-meson purity within the invariant mass region [0.5, 0.65] is about 72%
Most of the eta-candidates has detector pseudorapidity less or about 1.4,
what may limits applicability of data-driven shower shapes
derived from these candidates for higher pseudo-rapidity region,
where we have most of the background for the gamma-jet
analysis due to lack of TPC tracking
z-vertex distribution is very asymmetric, and peaked around -50cm.
Only a few candidates has a positive z-vertex values.
Figure 1: Eta-meson invariant mass with signal and background fits and ratio (upper left).
Pseudorapidity [detector and wrt vertex] distributions (right top and bottom plots),
vertex z distributions (bottom left)
Figure 2:2D plots for the eta-meson invariant mass vs
azimuthal angle (upper left), pseudorapidity (upper right),
z-vertex (bottom right), and detector pseudorapidity (bottom right)
Ilya Selyuzhenkov May 27, 2008
Figure 1: Shower shapes and triple Gaussian fits for photons from eta-meson
sorted by different conditions of EEMC 1st and 2nd pre-shower layers.
Note: All shapes have been normalized at peak to unity
Triple Gaussian fit parameters:
Pre1=0 Pre2=0
0.669864*exp(-0.5*sq((x-0.46016)/0.574864))+0.272997*exp(-0.5*sq((x-0.46016)/-1.84608))+0.0585682*exp(-0.5*sq((x-0.46016)/5.49802))
Pre1=0 Pre2>0
0.0694729*exp(-0.5*sq((x-0.493468)/5.65413))+0.615724*exp(-0.5*sq((x-0.493468)/0.590723))+0.314777*exp(-0.5*sq((x-0.493468)/2.00192))
Pre1>0 Pre2>0
0.0955638*exp(-0.5*sq((x-0.481197)/5.59675))+0.558661*exp(-0.5*sq((x-0.481197)/0.567596))+0.345896*exp(-0.5*sq((x-0.481197)/1.9914))
Shower shapes comparison between different data sets:
Some observations:
Shapes for gammas from eta-meson decay
are in a good agreement with those from MC gamma-jet sample
(compare red squares with blue triangle in Fig. 2 and 3).
MC gamma-jet shapes obtained by running a full gamma-jet reconstruction algorithm,
and this agreement indicates that we are able to reconstruct gamma shapes
which we put in with data-driven shower shape library.
MC gamma-jet shapes match pp2006 data shapes
for pre1=0 condition, where we expect to be very efficient in background rejection
(compare red squares with black circles in upper plots of Fig. 2 and 3).
This indicates that we are able to reproduce EEMC SMD of direct photons with data-driven Monte-Carlo.
There is no match between Monte-Carlo QCD background jets and pp2006 data
for the case when both pre-shower layer fired (pre1>0 and pre2>0).
(compare green triangles with black circes in bottom right plots of Fig.2 and 3).
This is the region where we know background dominates our gamma-jet candidates.
This shows that we still do not reproduce SMD response for our background events
in our data-driven Monte-Carlo simulations
(note, that in Monte-Carlo we replace SMD response with real shapes for all background photons
the same way we do it for direct gammas).
Figure 2: Shower shapes comparison between different data sets.
Shapes for gamma-jet candidates obtained with the same gamma-jet reconstruction algorithm
for three different data samples (pp2006, gamma-jet and QCD jets MC).
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 3:Same as Fig. 2, but with no cuts on gamma and jet pt.
All shapes are similar to those in Fig. 2 with an additional pt cuts.
Note, that blue triangles are the same as in Fig. 2.
Ilya Selyuzhenkov May 30, 2008
Three data sets:
Figure 1: Gamma eta distribution.
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 2: Gamma pt distribution.
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 3: Gamma phi distribution.
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 4: Away side jet eta distribution.
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 5: Away side jet pt distribution.
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 6: Gamma-jet delta pt distribution.
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 7: Gamma-jet delta eta distribution.
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 8: Gamma-jet delta phi distribution.
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Ilya Selyuzhenkov June 04, 2008
Three data sets:
Figure 1: Gamma candidate EEMC pre-shower 1 energy (3x3 cluster).
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 2: Gamma candidate EEMC pre-shower 2 energy (3x3 cluster).
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 3: Gamma candidate EEMC tower energy (3x3 cluster).
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 4: Gamma candidate EEMC post-shower energy (3x3 cluster).
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 5: Gamma candidate EEMC SMD u-plane energy [5-strip cluster] (Figure for v-plane)
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 6: Total minus gamma candidate (3x3 cluster) energy in EEMC pre-shower 1 layer
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 7: Total minus gamma candidate (3x3 cluster) energy in EEMC pre-shower 2 layer
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 8: Total minus gamma candidate (3x3 cluster) energy in EEMC tower
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 9: Total minus gamma candidate (3x3 cluster) energy in EEMC post-shower layer
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Figure 10: Total (sector) energy minus gamma candidate (5-strip cluster) energy in EEMC SMD[u-v] layer
pt cuts of 7GeV for the gamma and of 5 GeV for the away side jet have been applied.
Ilya Selyuzhenkov June 09, 2008
Three data sets:
Numerical values for different pt-bins from Fig. 1-2
Figure 1: Gamma pt distribution for R_cluster >0.9.
No energy in both pre-shower layer (left plot), and
No energy in pre-shower1 and non-zero energy in pre-shower2 (right plot)
Same figure for R_cluster>0.99 can be found here
Figure 2: Gamma pt distribution for R_cluster >0.9.
No energy in first EEMC pre-shower1 layer (left plot), and
non-zero energy in pre-shower1 (right plot)
For more details (yield, ratios, all pre12 four conditions, etc) see figures 1-3 here.
Figure 3: Gamma pt distribution for R_cluster >0.99.
For more details (yield, ratios, all pre12 four conditions, etc) see figures 1-3 here.
Ilya Selyuzhenkov June 10, 2008
Note: No background subtraction has been done yet
The case of pre-shower1=0 (left plots) roughly has 1:1 signal to background ratio,
while pre-shower1>0 (right plots) have 1:10 ratio (See MC to data comparison for details).
Data sets:
Figure 1: Gamma-jet candidate A_LL vs gamma pt.
Figures for related epsilon_LL and 1/Lum scaled by a factor 10^7
(see pdf/html links above for epsilon_LL and 1/Lum definitions)
Figure 2: Gamma-jet candidate A_LL vs x_gluon.
Figures for related epsilon_LL and 1/Lum scaled by a factor 10^7
Figure 3: Gamma-jet candidate A_LL vs x_quark.
Figures for related epsilon_LL and 1/Lum scaled by a factor 10^7
Figure 4: Gamma-jet candidate A_LL vs away side jet pt.
Figures for related epsilon_LL and 1/Lum scaled by a factor 10^7
Ilya Selyuzhenkov June 18, 2008
Photon-jet reconstruction with the EEMC detector - Part 1: pdf or odp
Data samples (pp2006, MC gJet, MC QCD bg)
and gamma-jet reconstruction algorithm:
Comparing pp2006 with Monte-Carlo simulations scaled to the same luminosity
(EEMC pre-shower sorting):
EEMC SMD shower shapes from different data samples
(pp2006 and data-driven Monte-Carlo):
Sided residual plots: pp2006 vs data-driven Monte-Carlo
(gammas from eta meson: 3 gaussian fits)
Various cuts study:
Some QA plots:
A_LL reconstruction technique:
Work in progress... To do list:
Ilya Selyuzhenkov July 07, 2008
Data sets:
Figure 1: Correlation between 3x3 cluster energy in pre-shower2 vs. pre-shower1 layers
Figure 1a: Distribution of the 3x3 cluster energy in pre-shower1 layer (zoom in for Epre1<0.03 region)
(pp2006 data vs. MC gamma-jet and QCD events)
Figure 2: Shower shapes after pre-shower1 < 5MeV cut.
Shapes are narrower than those without pre1 cut (see Fig. 2)
Figure 3: Gamma pt distribution with pre-shower1 < 5MeV cut.
Compare with distribution withoud pre-shower1 (Fig. 3)
Figure 4: Fitted peak vs. maximum sided residual (no pre-shower1 cuts)
Only points for pp2006 data are shown.
Figure 5: Fitted peak vs. maximum sided residual (after pre-shower1 < 5MeV cut).
Only points for pp2006 data are shown.
Note that distribution for pre1>0,pre2>0 case are narrower
compared to that in Fig.4 (without pre-shower1 cuts).
Figure 6: Distribution of maximum sided residual with pre-shower1 < 5MeV cut.
Ilya Selyuzhenkov July 16, 2008
Three data sets:
My simple gamma-gamma finder is trying to
find a second peaks (clusters) in each SMD u and v planes,
match u and v plane high strip intersections,
and calculate the invaraint mass from associated tower energies (3x3 cluster)
according to the energy sharing between SMD clusters.
Figure 1: Gamma-gamma invariant mass plot.
Only pp2006 data are shown: black: no pt cuts, red: gamma pt>7GeV and jet pt>5 GeV.
Clear pi0 peak in the [0.1,0.2] invariant mass region.
Same data on the log scale
Figure 2: Gamma pt distribution (no inv mass cuts).
Figure 3: Gamma pt distribution (m_invMass<0.11 or no second peak found).
This cut improves signal to background ratio.
Figure 4: Gamma pt distribution (m_invMass>0.11).
Mostly background events.
Figure 5: Shower shapes (no pre1 and no invMass cuts).
Good match between shapes in case of no energy in pre-shower1 layer (pre1=0 case).
Figure 6: Shower shapes (pre1<5MeV, no invMass cuts).
For pre1&2>0 case shapes getting closer to ech other, but still do not match.
Figure 7: Shower shapes (cuts: pre1<5MeV, invMass<0.11 or no second peak found).
Note, the surprising agreement between eta-meson shapes (blue) and data (black).
Figure 8: Invariant mass distribution (MC vs. pp2006 data): no pre1 cut
Figure 9: Invariant mass distribution (MC vs. pp2006 data): pre1<5MeV
Left side is the same as in Figure 8
Figure 10: Invariant mass distribution (MC vs. pp2006 data): pre1>5MeV
Left side plot is empty, since there is no events with [pre1=0 and pre1>5MeV]
Ilya Selyuzhenkov July 22, 2008
Figure 1: Shower shapes: no energy cuts, only 12 strips from peak (left u-plane, right v-plane).
Figure 1a: Shower shapes: no energy cuts, 150 strips from peak (left u-plane, right v-plane).
Figure 2: Shower shapes Energy>8GeV (left u-plane, right v-plane).
Figure 3: Shower shapes Energy<=8GeV (left u-plane, right v-plane).
Figure 8: Number of library candidates per sector.
Figure 9: Transverse momentum vs. energy.
Figure 10: Distance from center of the detector vs. energy.
Ilya Selyuzhenkov July 29, 2008
Data sets:
Latest data-driven shower shape replacement library:
Figure 1: Shower shapes for u-plane [12 strips]
Shower shapes for the library are for the E>8GeV bin.
Figure 2: Shower shapes for v-plane [12 strips]
Figure 3: Shower shapes for u-plane [expanded to 40 strips]
Figure 4: Shower shapes for v-plane [expanded to 40 strips]
Ilya Selyuzhenkov August 14, 2008
Data sets:
Data-driven maker with bug fixed multi-shape replacement:
Figure 1: Shower shapes for u-plane [12 strips]
Shower shapes for the library are for the E>8GeV bin.
Open squares and triangles represents raw [without dd-maker]
MC gamma-jet and QCD background shower shapes respectively
Figure 2: Shower shapes for v-plane [12 strips]
Figure 3: Shower shapes for u-plane [expanded to 40 strips]
Dashed red and green lines represents raw [without dd-maker]
MC gamma-jet and QCD background shower shapes respectively
Figure 4: Shower shapes for v-plane [expanded to 40 strips]
Ilya Selyuzhenkov August 19, 2008
Data sets:
Note: Due to lack of statistics for 2008 data, no pt cuts applied on gamma-jet candidates for both 2006 and 2008 date.
Figure 1: Shower shapes for u-plane [pp2006 data: eemc-http-mb-l2gamma trigger]
Figure 2: Shower shapes for v-plane [pp2006 data: eemc-http-mb-l2gamma trigger]
Figure 3: Shower shapes for u-plane [pp2008 data: fmsslow trigger]
Figure 4: Shower shapes for v-plane [pp2008 data: fmsslow trigger]
Ilya Selyuzhenkov August 25, 2008
Data sets:
Event selection:
Figure 1: Vertex z distribution (left: pp2008; right: 2006 data)
Figure 2: eta vs. phi distribution for the jet1 (jet with largest NEF) .
Figure 3: eta vs. z-vertex distribution for the jet1 (jet with largest NEF) .
Figure 4: eta vs. z-vertex distribution for the second jet.
Figure 5: Transverse momentum distribution for jet1.
Ilya Selyuzhenkov August 26, 2008
Data sets:
Data-driven library:
Figure 1: Pre-shower1 energy distribution for Pre1>4 MeV:
Eta meson library for E>8GeV bin [left] and data vs. MC results [right].
Figure 2: Shower shapes for v-plane [Pre1<10MeV cut]
Figure 3: Shower shapes for u-plane [Pre1<10MeV cut]
Definitions for side residual plot (F_peak, F_tal, D_tail) can be found here
For a moment same 3-gaussian shape is used to fit SMD response for all pre-shower bins.
Algo needs to be updated with a new shapes sorted by pre-shower bins.
Figure 4: Sided residual plot for pp2006 data only [Pre1<10MeV cut]
Figure 5: Sided residual projection on "Fitted Peak" axis [Pre1<10MeV cut]
Figure 6: Sided residual projection on "tail difference" axis [Pre1<10MeV cut]
Ilya Selyuzhenkov August 27, 2008
Data sets:
Figure 1: High u vs. v strip id distribution for different pre-shower conditions.
Left column: QCD jets, middle column: gamma-jet, right columnt: pp2006 data
Figure 2: x vs. y position of the gamma-candidate within EEMC detector
for different pre-shower conditions.
Left column: QCD jets, middle column: gamma-jet, right columnt: pp2006 data
Figure 3:Reconstructed vs. generated (from geant record) gamma pt for the MC gamma-jet sample.
Pre-shower1<10MeV cut applied.
Figure 4:Reconstructed vs. generated (from geant record) gamma eta for the MC gamma-jet sample.
Pre-shower1<10MeV cut applied.
Figure 5:Reconstructed vs. generated (from geant record) gamma phi for the MC gamma-jet sample.
Pre-shower1<10MeV cut applied.
Ilya Selyuzhenkov September 02, 2008
Data sets:
Shower shape fitting procedure:
Fitting function "[0]*(exp ( -0.5*((x-[1])/[2])**2 )+[3]*exp ( -0.5*((x-[4])/[5])**2 )+[6]*exp ( -0.5*((x-[7])/[8])**2 ))"
Figure 1: MC gamma-jet shower shapes and fits for u-plane
Results from single, double and triple Gaussian fits (using from 9 to 15 strips) are shown.
Figure 2: Same as figure 1. but from v-plane
Figure 3: MC gamma-jet results using triple Gaussian fits within 12 strips from a peak.
Left: u-plane. Right: v-plane
Figure 4: Combined fit results from MC gamma-jet sample
Figure 5: Fitting parameters [see equation for the fit function above].
Note, that parameters 1, 4, and 7 (peak position) has the same value.
Numerical fit results:
Figure 6: Same as Fig. 3, but for gamma-jet candidates from pp2006 data
Figure 7: Same as Fig. 5, but for gamma-jet candidates from pp2006 data
Ilya Selyuzhenkov September 09, 2008
Data sets:
Procedure to calculate maximum sided residual:
For each event fit SMD u and v energy distributions with
triple Gaussian functions from shower shapes analysis:
[0]*(exp(-0.5*((x-[1])/[2])**2)+[3]*exp(-0.5*((x-[1])/[4])**2)+[6]*exp(-0.5*((x-[1])/[5])**2))
Fit parameters sorted by various pre-shower conditions and u and v-planes can be found here
There are only two free parameters in a final fit: overall amplitude [0] and mean value [1]
Fit range is +-2 strips from the high strip (5 strips total).
Integrate energy from a fit within +-2 strips from high strip.
This is our peak energy from fit, F_peak.
Calculate tail energies on left and right sides from the peak for both data, D_tail, and fit, F_tail.
Tails are integrated up to 30 strips excluding 5 highest strips.
Determine maximum difference between D_tail and F_tail:
max(D_tail-F_tail). This is our maximum sided residual.
Plot F_peak vs. max(D_tail-F_tail). This is sided residual plot.
(implementation for this item is in progress)
Based on MC gamma-jet sided residual plot find a line (some polynomial function)
which will serve as a cut to separate signal and background.
Use that cut line to calculate signal to background ratio
and apply it for the real data analysis.
Figure 1: Maximum sided residual plots for different data sets and various pre-shower condition.
Columns [data sets]: 1. MC QCD background; 2. gamma-jet; 3. pp2006 data
Rows [pre-shower bins]: 1. pre1=0 pre2=0; 2. pre1=0, pre2>0; 3. 0<pre1<4MeV; 4. 4<pre1<10MeV
Results from u and v plane are combined as [U+V]/2
Figure 2: max(D_tail-F_tail) distribution (projection on horizontal axis from Fig.1)
Some observations:
Results for pp2006 and MC gamma-jet are consistent for pre1=0 pre2=0 case (upper left plot)
Results for pp2006 and MC QCD background jets are also in agrees for pre1>0 case (lower left and right plots)
Figure 3: F_peak distribution (projection on vertical axis from Fig.1)
Ilya Selyuzhenkov September 16, 2008
These results are obsolete.
Please use this link instead
Data sets:
Notations used in the plots:
Figure 1: D_peak from [U+V]/2.
Figure 2: U/V asymmetry for D_peak: [U-V]/[U+V]
Figure 3: F_peak from [U+V]/2.
Figure 4: U/V asymmetry for F_peak: [U-V]/[U+V]
Figure 5: (D_peak - F_peak)/D_peak asymmetry
Ilya Selyuzhenkov September 23, 2008
Data sets:
Notations used in the plots:
Figure 1: D_peak from [U+V]/2.
Figure 2: (D_peak - F_peak)/D_peak asymmetry
Ilya Selyuzhenkov September 23, 2008
Figure 1: D_peak vs. [right-left] D_tail
Ilya Selyuzhenkov September 23, 2008
Data sets:
Notations used in the plots:
Figure 1: Maximum sided residual plot
Top get more statistics for MC QCD sample plot is redone with a softer R_cluster > 0.9 cut
Figure 2: D_peak (projection on vertical axis for Fig. 1)
Upper left plot (no pre-shower fired case) reveals some difference
between MC gamma-jet and pp2006 data at lower D_peak values.
This difference could be due to background contribution at low energies.
Still needs more statistics for MC QCD jet sample to confirm that statement.
Figure 3: max(D_tail-F_tail) (projection on horisontal axis for Fig. 1)
One can get an idea of signal/background separation (red vs. black) depending on pre-shower condition.
Figure 4: Mean < max(D_tail-F_tail) > vs. D_peak (profile on vertical axis from Fig. 1)
For gamma-jet sample average sided residual is independent on D_peak energy
and has a slight positive shift for all pre-shower>0 conditions.
For large D_peak values (D_peak>0.16) MC gamma-jet and pp2006 data results are getting close to each other.
This corresponds to higher energy gammas, where we have a better signal/background ratio,
and thus more real gammas among gamma-jet candidates from pp2006 data.
(Note: legend's color coding is wrong, colors scheme is the same as in Fig. 3)
Figure 5: Mean < D_peak > vs. max(D_tail-F_tail) (profile on horisontal axis from Fig. 1)
For "no-preshower fired" case MC gamma-jet sample has a large average values than that from pp2006 data.
This reflects the same difference between pp2006 and MC gamma-jet sample at small D_peak values (see Fig. 2, upper left plot).
(Note: legend's color coding is wrong, colors scheme is the same as in Fig. 3)
Figure 7: D_peak vs. gamma 3x3 tower cluster energy
Figure 8: 3x3 cluster tower energy distribution
Figure 9: Gamma pt distribution
The simplest way to get signal/background separation is to draw a straight line
on sided residual plot (Fig. 1) in such a way that
it will contains most of the counts (signal) on the left side,
and use a distance to that line for both MC and pp2006 data samples
as a discriminant for signal/background separation.
To get the distance to the straight line one can rotate sided residual plot
by the angle which corresponds to the slope of this line,
and then project it on "rotated" max(D_tail-F_tail) axis.
Figure 10: Shows "rotated" sided residual plot by "5/6*(pi/2)" angle (this angle has been picked by eye).
One can see that now most of the counts for gamma-jet sample (middle column)
are on the left side from vertical axis.
Figure 11: "Rotated" max(D_tail-F_tail) [projection on horizontal axis for Fig. 10]
Cut on "Rotated" max(D_tail-F_tail) can be used for signal/background separation.
From figure below one can see much better signal/background separation than in Fig. 3
Figure 12: "Rotated" D_peak [projection on vertical axis for Fig. 10]
Ideally, instead of straight line one needs to use
an actual shape of side residual distribution for MC gamma-jet sample.
This shape can be extracted and parametrized by the following procedure:
The distance to that polynomial function can be used to determine our signal/background rejection efficiency.
This work is in progress...
Just last one figure showing shapes for 6 slices from sided plot.
Figure 13: max(D_tail-F_tail) for different slices in D_peak (scaled by the integral for each slice)
Ilya Selyuzhenkov September 30, 2008
Data sets:
Notations used in the plots:
Figure 1: Sided residual plot: D_peak vs. max(D_tail-F_tail)
Red lines show 4th order polynomial functions, a*x^4,
which have 80% of MC gamma-jet counts on the left side.
These lines are obtained independently for each of pre-shower condition
based on fit procedure shown in Fig. 3 below.
Figure 2: max(D_tail-F_tail) distribution
(projection on horizontal axis from sided residual plot, see Fig. 1 above)
Figure 3: max(D_tail-F_tail) [at 80%] vs. D_peak.
For each slice (bin) in D_peak variable, the max(D_tail-F_tail) value
which has 80% of gamma-jet candidates on the left side are plotted.
Lines represent fits to MC gamma-jet points (shown in red) using different fit functions
(linear, 2nd, 4th order polynomials: see legend for color coding).
Note, that in this plot D_peak values are shown on horizontal axis.
Consequently, to get 2nd order polynomial fit on sided residual plot (Fig. 1),
one needs to use sqrt(D_peak) function.
The same apply to 4th order polynomial function.
Figure 4: D_peak vs. horisontal distance from 4th order polinomial function to max(D_tail-F_tail) values.
(compare with Fig. 1: Now 80% of MC gamma-jet counts are on the left side from vertical axis)
Figure 5: Horizontal distance from 4th order polynomial function to max(D_tail-F_tail)
[Projection on horizontal axis from Fig. 4]
Based on this plot one can obtain purity, efficiency, and rejection plots (see Fig. 6 below)
Horizontal distance plotted in Fig. 5 can be used as a cut
separating gamma-jet signal and QCD-jets background,
and for each value of this distance one can define
gamma-jet purity, efficiency, and QCD-background rejection:
gamma-jet purity is defined as the ratio of
the integral on the left for MC gamma-jet data sample, N[g-jet]_left,
to the sum of the integrals on the left for MC gamma-jet and QCD jets, N[QCD]_left, data samples:
Purity[gamma-jet] = N[g-jet]_left/(N[g-jet]_left+N[QCD]_left)
gamma-jet efficiency is defined as the ratio of
the integral on the left side for MC gamma-jet data sample, N[g-jet]_left,
to the total integral for MC gamma-jet data sample, N[g-jet]:
Efficiency[gamma-jet] = N[g-jet]_left/N[g-jet]
QCD background rejection is defined as the ratio of
the integral on the right side for MC QCD jets data sample, N[QCD]_right,
to the total integral for MC QCD jets data sample, N[QCD]:
Rejection[QCD] = N[QCD]_right/N[QCD]
Figure 6: Shows:
purity[g-jet] vs. efficiency[g-jet] (upper left);
rejection[QCD] vs. efficiency[g-jet] (upper right);
purity[g-jet] vs. rejection[QCD] (lower left);
pp2006 to MC ratio, N[pp2006]/(N[g-jet]+N[QCD]), vs. horizontal distance from Fig. 5 (lower right)
Ilya Selyuzhenkov October 13, 2008
I have finished production of jet trees for Michael's gamma filtered events
You can find jet and skim file lists in my directory at IUCF disk (RCF):
Number of jet events is 1284581 (1020 files).
Production size, including archived log files, is 4.0G.
The script to run jet finder:
/star/institutions/iucf/IlyaSelyuzhenkov/simu/JetTrees/20081008_gJet/StRoot/macros/RunJetSimuSkimFinder.C
JetFinder and JetMaker code:
/star/institutions/iucf/IlyaSelyuzhenkov/simu/JetTrees/20081008_gJet/StRoot/StJetFinder
/star/institutions/iucf/IlyaSelyuzhenkov/simu/JetTrees/20081008_gJet/StRoot/StJetMaker
For more details see these threads of discussions:
Ilya Selyuzhenkov October 14, 2008
Data sets:
Figure 1: Horizontal distance from 4th order polynomial function to max(D_tail-F_tail)
See this page for definition and more details
Figure 2:
purity[g-jet] vs. efficiency[g-jet] (upper left);
rejection[QCD] vs. efficiency[g-jet] (upper right);
purity[g-jet] vs. rejection[QCD] (lower left);
pp2006 to MC ratio, N[pp2006]/(N[g-jet]+N[QCD]), vs. horizontal distance (lower right)
Ilya Selyuzhenkov October 15, 2008
Data sets:
Some observations:
Figure 1a: partonic pt for gamma-jet [old] events
after analysis cuts and partonic pt bin weighting
(Note:Arbitrary absolute scale)
Figure 1b: partonic pt for gamma-jet [gamma-filtered] events after analysis cuts.
Michael's StBetaWeightCalculator has been used to caclulate partonic pt weights
Figure 1c: partonic pt for QCD jets [old] events
after analysis cuts and partonic pt bin weighting
(Note:Arbitrary absolute scale)
Figure 1d: partonic pt for QCD jets [gamma-filtered] events after analysis cuts.
Michael's StBetaWeightCalculator has been used to caclulate partonic pt weights
Figure 2: reconstructed gamma pt: old MC vs. pp2006 data (scaled to the same luminosity)
Figure 3: reconstructed gamma pt: gamma-filtered MC vs. pp2006 data (scaled to the same luminosity)
Ilya Selyuzhenkov October 15, 2008
Data sets:
Figure 1: Horizontal distance from sided residual plot: R_cluster > 0.9
(see Figs. 1-5 from this post for horizontal distance definition)
Figure 2: Purity/efficiency/rejection, and data to MC[gamma-jet+QCD] ratio plots: R_cluster > 0.9
(see text above Fig. 6 from this post for purity, efficiency, and background rejection definition)
Figure 3: Reconstructed gamma pt: R_cluster > 0.98
Figure 4: Horizontal distance from sided residual plot: R_cluster > 0.98
Figure 5: Purity/efficiency/rejection, and data to MC[gamma-jet+QCD] ratio plots: R_cluster > 0.98
Ilya Selyuzhenkov October 21, 2008
Data sets:
Some comments:
Fig. 1-3, upper left plots (pre1=0 pre2=0) show that
average energy per strip in data-driven gamma-jet MC (i.e. solid red square in Fig. 3)
is systematically higher than that for pp2006 data (black circles in Fig. 3).
Note, that there is an agreement between SMD shower shapes
for pp2006 data and data-driven gamma-jet simulations
if one scales them to the same peak value
(Compare red vs. black in upper left plot from Fig. 1 at this link)
Fig. 4, upper left plot (pre1=0 pre2=0):
Integrated SMD energy from 25 strips
in raw gamma-jet simulations (red line) match pp2006 data (black line)
in the region where signal to background ratio is high, E_smd(25-strips)>0.1GeV.
This indicates that raw MC does a good job in
reproducing total energy deposited by direct photon.
Fig. 5, upper left plot (pre1=0 pre2=0):
There is mismatch between distributions of energy in 25 strips cluster
from data-driven gamma-jet simulations and pp2006 data.
This probably reflects the way we scale our library shower shapes
in data-driven shower shape replacement procedure.
Currently, the scaling factor for the library shape is calculated based on the ratio
of direct photon energy from Geant record to the energy of the library photon.
Our library is build out of photons from eta-meson decay,
which has been reconstructed by running pi0 finder.
The purity of the library is about 70% (see Fig. 1 at this post for more details).
The improvement of scaling procedure could be to
preserve total SMD energy deposited within 25 strips from raw MC,
and use that energy to scale shower shapes from the library.
Fig. 6, upper left plot (pre1=0 pre2=0):
Mismatch between integrated 5-strip energy for raw MC and pp2006 in Fig. 6
corresponds to "known" difference in shower shapes from raw Monte-Carlo and real data.
Figure 1: SMD shower shapes: data, raw, and data-driven MC (40 strips).
Vertical axis shows average energy per strip (no overall shower shapes scaling)
Figure 2: Shower shapes: data, raw, and data-driven MC (12 strips)
Figure 3: Shower shapes: data, raw, and data-driven MC (5 strips)
Figure 4: 25 strips SMD cluster energy for raw Monte-Carlo
(Note: type in x-axis lables, should be "25 strip peak" instead of 5)
Figure 5: 25 strips SMD cluster energy for data-driven Monte-Carlo
Figure 6: 5 strips SMD peak energy for raw Monte-Carlo
Figure 7: 5 strips SMD peak energy for data-driven Monte-Carlo
Figure 8:Energy from the right tail (up to 30 strips) for raw Monte-Carlo
Figure 9:Energy from the right tail (up to 30 strips) for data-driven Monte-Carlo
Ilya Selyuzhenkov October 27, 2008
Data sets:
Shower shapes scaling options in data-driven maker:
In all figures below (exept for pp2006 data and raw Monte-Carlo)
the SMD based shower shape scaling has been used.
Figure 1: SMD shower shapes: data, raw, and data-driven MC (40 strips).
Vertical axis shows average energy per strip (no overall shower shapes scaling)
Figure 2: Shower shapes: data, raw, and data-driven MC (12 strips)
Figure 3: Shower shapes: data, raw, and data-driven MC (5 strips)
Figure 4: 25 strips SMD cluster energy for data-driven Monte-Carlo
(SMD based shower shape scaling)
Figure 5: 25 strips SMD cluster energy for raw Monte-Carlo
Note, the difference between results in Fig. 4 and 5. for MC gamma-jets (shown in red)
at low energy (Esmd < 0.04) for pre1=0 pre2=0 case.
This effect is due to the "Number of strips fired in 5-strips cluster > 3" cut.
In data-driven Monte-Carlo we may have shower shapes
with small number of strips fired (rejected in raw Monte-Carlo)
to be replaced by library shape with different (bigger) number of strips fired.
This mostly affects photons which starts to shower
later in the detector and only fires few strips (pre1=0 pre2=0 case)
Ilya Selyuzhenkov October 30, 2008
Below are links to drupal pages
with various SMD energy distributions and shower shapes
for the following set of cuts/conditions:
Figure 1: Case A
Figure 2:Case B
Figure 3:Case C
Figure 4:Case D
Figure 1: Case A
Figure 2:Case B
Figure 3:Case C
Figure 4:Case D
Figure 1: Case A
Figure 2: Case B
Figure 3: Case C
Figure 4: Case D
Figure 1: Case A
Figure 2:Case B
Figure 3:Case C
Figure 4:Case D
Figure 1: Case A
Figure 2:Case B
Figure 3:Case C
Figure 4:Case D
Figure 1: Case A
Figure 2:Case B
Figure 3:Case C
Figure 4:Case D
Figure 1: Case A
Figure 2:Case B
Figure 3:Case C
Figure 4:Case D
Figure 1: Case A
Figure 2:Case B
Figure 3:Case C
Figure 4:Case D
Ilya Selyuzhenkov November 06, 2008
Ilya Selyuzhenkov November 11, 2008
Data sets:
Figure 1: Reconstructed gamma pt for di-jet events and
Geant cuts: pt_gamma[Geant] > 7GeV and 1.05 < eta_gamma[Geant] < 2.0
Total integral for the histogram is: N_total = 5284
(after weighting different partonic pt bins and scaled to 3.164pb^-1).
Compare with number from Jim Sowinski study for
Endcap East+West gamma-jet and pt>7 GeV: N_Jim = 5472
( Jim's numbers are scaled to 3.164pb^-1 : [2539+5936]*3.164/4.9)
Figure 2: Reconstructed jet pt for di-jet events and the same cuts as in Fig. 1
List of cuts (sorted by bin number in Figs. 2 and 3):
Figure 3: Number of accepted events vs. various analysis cuts
The starting number of events (shown in first bin of the plots) is
the number of di-jets with reconstructed gamma_pt>7 GeV and jet_pt>5 GeV
upper left: cuts applied independently
upper right: cuts applied sequentially
lower left: ratio of pp2006 data vs. MC sum of gamma-jet and QCD-jets events (cuts applied independently)
lower right:ratio of pp2006 data vs. MC sum of gamma-jet and QCD jets events (cuts applied sequentially)
Figure 4: Number of accepted events vs. various analysis cuts
Data from Fig. 3 (upper plots) scaled to the initial number of events from first bin:
left: cuts applied independently
right: cuts applied sequentially
Ilya Selyuzhenkov November 18, 2008
all gamma-jet candidate selection cuts except 3x3/r=0.7 energy isolation cut
Figure 4b: 3x3/0.7 ratio but only using towers which passed jet finder threshold
Ilya Selyuzhenkov November 21, 2008
all gamma-jet candidate selection cuts except 3x3/r=0.7 energy isolation cut
There are two sets of figures in links below:
Yield is defined as the integral above given energy fraction
up to the maximum value of 1
Gamma candidate detector eta < 1.5
(eta region where we do have most of the TPC tracking):
Gamma candidate detector eta > 1.5:
(smaller tower size)
Figure 1a: 2x1/3x3 energy fraction [number of counts per given fraction]
Figure 2a: 2x2/3x3 energy fraction [number of counts per given fraction]
Ilya Selyuzhenkov November 25, 2008
Fig.2 [lower right, 5th bin] shows that
charge particle veto also independent from other cuts
List of cuts (sorted according to bin number in Figs. 1-3. [No SMD sided residual cuts]):
Figure 1: Number of accepted events vs. various analysis cuts
The starting number of events (shown in first bin of the plots) is
the number of di-jets with reconstructed gamma_pt>7 GeV and jet_pt>5 GeV
upper left: cuts applied independently
upper right: expept this cut fired
(event passed all other cuts and being rejected by this cut)
lower left: "cuts applied independently" normalized by the total number of events
lower right: "expept this cut fired" normalized by the total number of events
Figure 2: Same as Fig.1 except: no R_cluster cut and photon detector eta < 1.5
(eta region where we do have most of the TPC tracking)
Figure 3: Same as Fig.1 except: no R_cluster cut and photon detector eta > 1.5
Ilya Selyuzhenkov December 08, 2008
Figure 1: EEMC x vs. y position of photon candidate for 2008 data sample
Problem with pre-shower layer in Sector 10 can been seen in the upper left corner
Figure 2: EEMC x vs. y position of photon candidate for 2006 data sample
Figure 3: Average < E_pre1 * E_pre2 > for 3x3 cluster around high tower
vs run number for sectors 9, 10 and 11
Note, zero pre-shower energy for sector 10 (black points) for days 61, 62, 64, and 67.
All di-jet events for pp2008 data are shown (no gamma-jet cuts)
Figure 3a: Same as Fig.3, zoom into day 61
Figure 3b: Same as Fig.3, zoom into day 62
Figure 3c: Same as Fig.3, zoom into day 64
Figure 3d: Same as Fig.3, zoom into day 67
Figure 4: EEMC x vs. y position of photon candidate for 2008 data sample
Same as Fig. 1, but excluding days: 61, 62, 64, and 67
No problem with pp2008 data have been found,
except that for some runs (mostly on days 61, 62, 64, and 67)
EEMC pre-shower layer for sector 10 was off.
Figure 5: Vertex z distribution:
All gamma-jet cuts applied, plus pt_gamma>7 and pt_jet > 5 GeV (exlcuding days 61, 62, 64, and 67)
Results are shown for pp2008 data sample (black), vs. pp2006 data (red).
pp2008 data scaled to the same total number of candidates as in pp2006 data.
Figure 6: Shower shapes within +/- 30 strips from high strip (same cuts as in Fig. 5):
Figure 7: Shower shapes within +/- 5 strips from high strip
(same cuts as in Fig. 5, no scaling):
Ilya Selyuzhenkov December 09, 2008
Ilya Selyuzhenkov December 09, 2008
Figure 1: Vertex z distribution:
All gamma-jet cuts applied, plus pt_gamma>7 and pt_jet > 5 GeV (exlcuding days 61, 62, 64, and 67)
Results are shown for pp2008 data sample (black), vs. pp2006 data (red).
pp2008 data scaled to the same total number of candidates as in pp2006 data.
Figure 2: Shower shapes within +/- 30 strips from high strip (same cuts as in Fig. 1):
Figure 3: Shower shapes within +/- 5 strips from high strip
(same cuts as in Fig. 1, no scaling):
Ilya Selyuzhenkov December 09, 2008
Figure 1: Vertex z distribution:
All gamma-jet cuts applied, plus pt_gamma>7 and pt_jet > 5 GeV (exlcuding days 61, 62, 64, and 67)
Results are shown for pp2008 data sample (black), vs. pp2006 data (red).
pp2008 data scaled to the same total number of candidates as in pp2006 data.
Figure 2: Shower shapes within +/- 30 strips from high strip (same cuts as in Fig. 1):
Figure 3: Shower shapes within +/- 5 strips from high strip
(same cuts as in Fig. 1, no scaling):
Ilya Selyuzhenkov December 09, 2008
Figure 1: Vertex z distribution:
All gamma-jet cuts applied, plus pt_gamma>7 and pt_jet > 5 GeV (exlcuding days 61, 62, 64, and 67)
Results are shown for pp2008 data sample (black), vs. pp2006 data (red).
pp2008 data scaled to the same total number of candidates as in pp2006 data.
Figure 2: Shower shapes within +/- 30 strips from high strip (same cuts as in Fig. 1):
Figure 3: Shower shapes within +/- 5 strips from high strip
(same cuts as in Fig. 1, no scaling):
Ilya Selyuzhenkov December 09, 2008
Figure 1: Vertex z distribution:
All gamma-jet cuts applied, plus pt_gamma>7 and pt_jet > 5 GeV (exlcuding days 61, 62, 64, and 67)
Results are shown for pp2008 data sample (black), vs. pp2006 data (red).
pp2008 data scaled to the same total number of candidates as in pp2006 data.
Figure 2: Shower shapes within +/- 30 strips from high strip (same cuts as in Fig. 1):
Figure 3: Shower shapes within +/- 5 strips from high strip
(same cuts as in Fig. 1, no scaling):
Ilya Selyuzhenkov December 09, 2008
Figure 1: Vertex z distribution:
All gamma-jet cuts applied, plus pt_gamma>7 and pt_jet > 5 GeV (exlcuding days 61, 62, 64, and 67)
Results are shown for pp2008 data sample (black), vs. pp2006 data (red).
pp2008 data scaled to the same total number of candidates as in pp2006 data.
Figure 2: Shower shapes within +/- 30 strips from high strip (same cuts as in Fig. 1):
Figure 3: Shower shapes within +/- 5 strips from high strip
(same cuts as in Fig. 1, no scaling):
Ilya Selyuzhenkov December 11, 2008
Presentation in pdf or open office file format
Ilya Selyuzhenkov December 16, 2008
Gamma-jet isolation cuts except 3x3/r=0.7 energy isolation cut
Figure 1: (reproducing old results with dd-maker fix)
transverse momentum and vertex z distributions
before (with ideal gains/pedestals) and
after (with realistic gains/pedestal tables) dd-maker fix are in a good agreement.
For details on "dd-maker problem", read these hyper news threads:
emc2:2905, emc2:2900, and phana:294
Now we can run L2gamma trigger emulation and Eemc SMD ddMaker
in the same analysis chain.
Figure 2: Vertex z distribution with and without trigger condition in simulations
(emulated trigger: eemc-http-mb-L2gamma [id:137641]).
Solid red/green symbols show results with l2gamma condition applied,
while red/green lines show results for the same analysis cuts but without trigger condition.
Note, good agreement between MC QCD jets with trigger condition on (green solid squared)
and pp2006 data (black solid circles) for pre-shower1>0 case.
Figure 3: pt distribution with/without trigger condition in simulations.
Same color coding as in Fig. 2
Figure 4: Same as Fig. 3 just on a log scale
One can clearly see large trigger effect when applied for QCD jet events,
and a little effect for direct gammas.
Figure 5: gamma candidate pt QCD (right) and prompt photon (left) Monte-Carlo:
no (upper) with (lower) L2e-gamma trigger condition
No photon pt and no jet pt cuts
Figure 6: gamma candidate pt for QCD Monte-Carlo: no L2e-gamma trigger condition
No photon pt and no jet pt cuts
Figure 7: gamma candidate pt for QCD Monte-Carlo: L2e-gamma trigger condition applied (id:137641)
No photon pt and no jet pt cuts
Ilya Selyuzhenkov December 19, 2008
Gamma-jet isolation cuts except 3x3/r=0.7 energy isolation cut
Figure 1: Parton pt distibution for gamma-jet candidates from Pythia QCD sample
with various pt and l2gamma trigger conditions
Figure 2: Parton pt distibution for gamma-jet candidates from Pythia prompt photon sample
with various pt and l2gamma trigger conditions
Ilya Selyuzhenkov January 08, 2009
(concentrated on pre-shower1>0 case
which has better statistics for QCD Monte-Carlo):
Figure 1: Vertex z distribution
Figure 4: gamma-jet pt asymmetry: (pt_gamma - pt_jet)/pt_gamma
Figure 5: gamma pt vs. away side jet pt
1st column: triggered pp2006 data
2nd column: gamma-jet MC (l2gamma trigger on)
3rd column: QCD background MC (l2gamma trigger on)
Ilya Selyuzhenkov January 20, 2009
Note:
this is an update with 10x more statitstics for QCD 9-15GeV parton pt bin.
See this post for old results.
Figure 1: Vertex z distribution
Figure 4: gamma-jet pt asymmetry: (pt_gamma - pt_jet)/pt_gamma
Figure 5: gamma pt vs. away side jet pt
1st column: triggered pp2006 data
2nd column: gamma-jet MC (l2gamma trigger on)
3rd column: QCD background MC (l2gamma trigger on)
Figure 6: pp2006 data to Monte -Carlo sum [QCD + gamma-jet] ratio
for pre-shower1>4MeV (most of statistics)
Left: data to MC ratio vs. reconstructed gamma pt.
Solid line shows constant line fit (p0 ~ 1.3)
Right: data to MC ratio vs. reconstructed vertex position
Ilya Selyuzhenkov January 27, 2009
All figures:
Ilya Selyuzhenkov January 27, 2009
All figures:
Figure 1: Vertex z distribution
Figure 4:Photon pt
Same as in Fig.4 on a log scale: no gamma pt cut and pt>7GeV
Figure 5: Away side jet pt
Same as in Fig.5 on a log scale: no gamma pt cut and pt>7GeV
Ilya Selyuzhenkov February 02, 2009
All figures:
Figure 1: Vertex z distribution with pt_jet>7 cut (left) and without pt_jet cut (rigth)
Figure 2: Photon (left) and away side jet (right) pt
Figure 3: Photon detector eta (left) and corrected for vertex eta (right)
Figure 4: Away side jet detector eta (left) and corrected for vertex eta (right)
Ilya Selyuzhenkov February 03, 2009
Each figure has:
Figure 1: Vertex z distribution
Figure 3: Corrected for vetrex photon eta
Figure 4: Away side jet detector eta
Ilya Selyuzhenkov February 06, 2009
Partonic pt range 2-25 GeV.
Each figure has:
Note: There is a "pre-shower sector 10 problem" for pp2008 data,
which results in migration of small fraction of events with pre-shower>0 into
pre-shower=0 bin (first zero bins in Fig.1 and 2. below).
For pre-shower>0 case this only affects overall normalization of pp2008 data,
but not the shape of pre-shower energy distributions.
I'm running jet-finder+my software to get more statistics from pp2008 data set,
and after more QA will produce list of runs with "pre-shower sector 10 problem",
so to exclude them in the next iteration of my plots.
Ilya Selyuzhenkov February 06, 2009
Partonic pt range 2-25 GeV.
Each figure has:
Figure 6: gamma-jet pt balance
Figure 7: Photon neutral energy fraction
Figure 8: Jet neutral energy fraction
Figure 9: cos(phi_gamma-phi_jet)
Figure 13: Number of charged track associated with photon candidate
Figure 14: Number of Barrel towers associated with photon candidate
Figure 15: Number of Endcap towers associated with photon candidate
Ilya Selyuzhenkov February 16, 2009
Partonic pt range 2-25 GeV.
Each figure has:
Slides: download pdf
Link for CIPANP abstract
Title:
"Photon-jet coincidence measurements
in polarized pp collisions at sqrt{s}=200GeV
with the STAR Endcap Calorimeter"
Abstract: download pdf
Previous versions: v1, v2, v3, v4
Conference link: CIPANP 2009
Multilayer perceptron (MLP) is feedforward neural networks
trained with the standard backpropagation algorithm.
They are supervised networks so they require a desired response to be trained.
They learn how to transform input data into a desired response,
so they are widely used for pattern classification.
With one or two hidden layers, they can approximate virtually any input-output map.
They have been shown to approximate the performance of optimal statistical classifiers in difficult problems.
TMultiLayerPerceptron class in ROOT
mlpHiggs.C example
Netwrok structure:
r3x3, (pt_gamma-pt_jet)/pt_gamma, nCharge, bBtow, eTow2x1: 10 hidden layers: one output later
Figure 1:
Figure 2: Input parameters vs. network output
Row: 1: MC QCD, 2: gamma-jet, 3 pp2006 data
Vertical axis: r3x3, (pt_gamma-pt_jet)/pt_gamma, nCharge, bBtow, eTow2x1
Horisontal axis: network output
ROOT implementation for LDA and MLP:
LDA configuration: default
MLP configuration:
Input parameters (same for both LDA and MLP):
Figure 1: Signal efficiency and purity, background rejection (left),
and significance: Sig/sqrt[Sig+Bg] (right) vs. LDA (upper plots) and MLP (lower plots) classifier discriminants
Figure 2:
Figure 3: Data to Monte-Carlo comparison for LDA (upper plots) and MLP (lower plots)
Good (within ~ 10%) match between data nad Monte-Carlo
a) up to 0.8 for LDA discriminant, and b) up to -0.7 for MLP.
Figure 4: Data to Monte-Carlo comparison for input parameters
from left to right
1) pt_gamma 2) pt_jet 3) r3x3 4) gamma-jet pt balance 5) N_ch[gamma] 6) N_eTow[gamma] 7) N_bTow[gamma]
Colour coding: black pp2006 data, red gamma-jet MC, green QCD MC, blue gamma-jet+QCD
Figure 5: Data to Monte-Carlo comparison:
correlations between input variables (in the same order as in Fig. 4)
and LDA classifier discriminant (horizontal axis).
1st raw: QCD MC; 2nd: gamma-jet MC; 3rd: pp2006 data; 4th: QCD+gamma-jet MC
Endcap photon-jet update at the STAR Collaboration meeting
April 2009 posts
The STAR spin program with longitudinally polarized proton beams
ROOT implementation for LDA:
LDA configuration: default
LDA input parameters:
Figure 1: LDA discriminant (no SMD involved in training)
Figure 2: LDA (no SMD): Efficiency, rejection, purity vs. discriminant
Figure 3: SMD energy in 25 central strips (LDA-dsicriminant>0, no pre-shower1 cut)
Figure 4: SMD energy in 25 central strips (LDA-dsicriminant>0, pre-shower1 < 10MeV)
Figure 5: Maximum residual (LDA-dsicriminant>0, no pre-shower1 cut)
Figure 6: Maximum residual (LDA-dsicriminant>0, pre-shower1 < 10MeV)
SMD info added:
a) energy in 5 central srtips
b) maximum sided residual
Figure 7:LDA with SMD: Efficiency, rejection, purity vs. LDA discriminant
Figure 8: LDA discriminant with SMD
Figure 9: Maximum residual (SMD LDA-dsicriminant>0, pre-shower1 < 10MeV)
Figure 10:LDA (no SMD): Efficiency, rejection, purity plots
Figure 11: LDA with SMD: Efficiency, rejection, purity plots
ROOT implementation for LDA:
LDA configuration: default
LDA input parameters (includes SMD inromation of the distance from max sided residual plot):
The number of strips in SMD u or v planes is required to be greater than 3
Figure 1: SMD energy in 25 central strips sorted by pre-shower energy
Right plot for each pre-shower condition shows the ratio of pp2006 data to sum of the Monte-Carlo samples
Colour coding:
black pp2006 data, red gamma-jet MC, green QCD MC, blue gamma-jet+QCD
(combined plot for all pre-shoer bins can be found here)
Figure 2: SMD energy in 5 central strips sorted by pre-shower energy
(combined plot can be found here)
Figure 3: Maximum residual sorted by pre-shower energy
(combined plot can be found here)
Figure 4: LDA discriminant. Note: LDA algo trained for each pre-shower condition independently
Figure 5: LDA: Efficiency, rejection, purity vs. discriminant, sorted by pre-shower energy
Figure 6: LDA: Efficiency, rejection, purity plots sorted by pre-shower energy
For each pre-shower condition each plot has 4 figures:
ROOT implementation for LDA:
LDA configuration: default
LDA input parameters Set0:
The number of strips in SMD u or v planes is required to be greater than 3
Pre-shower sorting (energy in tiles under 3x3 tower patch):
Photon pt and rapidity cuts:
Figure 0: photon pt distribution for pre-shower1<0.01
Colour coding:
black pp2006 data, red gamma-jet MC, green QCD MC, blue gamma-jet+QCD
Figure 1: LDA discriminant with Set0: Data to Monte-Carlo comparison (pt>7GeV cut)
Right plot for each pre-shower condition shows the ratio of pp2006 data to sum of the Monte-Carlo samples
Colour coding:
black pp2006 data, red gamma-jet MC, green QCD MC, blue gamma-jet+QCD
Figure 2: efficiency, purity, rejection vs. LDA discriminant (pt>7GeV cut)
Figure 3: rejection vs. efficiency
Figure 4: purity vs. efficiency
Figure 5: purity vs. rejection
Figure 6: LDA discriminant with Set1: Data to Monte-Carlo comparison
Figure 7: rejection vs. efficiency
Figure 8: purity vs. efficiency
Figure 9: purity vs. rejection (click link to see the figure)
Figure 10: rejection vs. efficiency (click link to see the figure)
Figure 11: purity vs. efficiency
Figure 12: purity vs. rejection (click link to see the figure)
Figure 13: rejection vs. efficiency (click link to see the figure)
Figure 14: purity vs. efficiency
Figure 15: purity vs. rejection (click link to see the figure)
ROOT implementation for LDA:
LDA configuration: default
LDA input parameters Set0:
The number of strips in SMD u or v planes is required to be greater than 3
Pre-shower sorting (energy in tiles under 3x3 tower patch):
Integrated yields per pre-shower bin:
sample | total integral | pre1=0,pre2=0 | pre1=0, pre2>0 | 0 < pre1 < 0.004 | 0.004 < pre1 < 0.01 | pre1 < 0.01 | pre1 >= 0.01 |
photon-jet | 2.5640e+03 | 3.5034e+02 | 5.2041e+02 | 5.6741e+02 | 5.2619e+02 | 1.9644e+03 | 5.9994e+02 |
QCD | 5.6345e+04 | 1.3515e+03 | 4.3010e+03 | 1.2289e+04 | 1.5759e+04 | 3.3701e+04 | 2.2644e+04 |
pp2006 | 6.2811e+04 | 6.8000e+02 | 2.4310e+03 | 1.2195e+04 | 1.6766e+04 | 3.2072e+04 | 3.0739e+04 |
Photon pt and rapidity cuts:
Figure 1: LDA discriminant with Set0: Data to Monte-Carlo comparison (pt>7GeV cut)
Right plot for each pre-shower condition shows the ratio of pp2006 data to sum of the Monte-Carlo samples
Colour coding:
black pp2006 data, red gamma-jet MC, green QCD MC, blue gamma-jet+QCD
Figure 2: rejection vs. efficiency
Figure 3: purity vs. efficiency
Figure 4: purity vs. rejection
Figure 5: Correlation matrix (pt>7GeV cut)
pre1=0, pre2=0
pre1=0, pre2>0
0 < pre1 < 0.004
0.004 < pre1 < 0.01
pre1 < 0.01
pre1 >= 0.01
For this post LDA input parameters Set4 has been used
LDA for various pre-shower bins is trained independetly,
and later results with pre-shower1<0.01 are combined.
There are a set of plots for various photon pt cuts (pt> 7, 8, 9 10 GeV)
and with different selection of cutoff for LDA
(either based on purity or efficiency).
Number in brackets shows the total yield for the sample.
Link to all plots (16 total) as a single pdf file
Figure 1: pt > 7GeV, efficiency@70
Figure 2: pt > 7GeV, purity@35
Figure 3: pt > 7GeV, purity@40
Figure 4: pt > 7GeV, purity@25 (Note: very similar to results with efficiency@70)
Figure 5: pt > 9GeV, efficiency@70
Figure 6: pt > 9GeV, purity@35
Figure 7: pt > 10GeV, efficiency@70
Figure 8: pt > 10GeV, purity@40
(analysis status update for Spin PWG)
Slides in pdf format:
For this post LDA results with Set1 and Set2 has been used
Note, that LDA for various pre-shower bins is trained independetly
pdf-links with results for pre1=0 and pre2=0 (pre-shower bin 1):
Figures below are for 0.004<pre-shower1<0.01 (pre-shower bin 4).
Photon pt cut: pt> 7, pre-shower bin: 0.004 < pre1 < 0.01
LDA cut with efficiency @ 70%
What is added in Set2 compared to Set1:
smaller cluster size information (r2x1, r2x2), post-shower energy
Figure 1: r2x1
before LDA cut
LDA cut for Set1
LDA cut for Set2
Figure 2: r2x2
before LDA cut
LDA cut for Set1
LDA cut for Set2
Figure 3: r3x3
before LDA cut
LDA cut for Set1
LDA cut for Set2
Figure 4: Residual distance
before LDA cut
LDA cut for Set1
LDA cut for Set2
Note: Only plos for LDA cut @70 efficiency for Set2 are shown
Figure : number of charge particles around photon
Figure 5: number of EEMC tower around photon
Figure 6: number of BEMC tower around photon
Figure 7: photon-jet pt balance
Figure 8: SMD energy in 5 centrapl strips
Figure 9: SMD energy in 25 central strips: u and v plane separately (plot for V plane)
Figure 13: tower energy in r=0.7 radius
Figure 14: 3x3 pre-shower1 energy
Figure 15: 3x3 pre-shower2 energy
Figure 16: 3x3 post-shower energy
Title:
"Photon-jet coincidence measurements
in polarized pp collisions at sqrt{s}=200GeV
with the STAR Endcap Calorimeter"
Title:
"Photon-jet coincidence measurements
in polarized pp collisions at sqrt{s}=200 GeV
with the STAR Endcap Calorimeter"
Data set and cuts:
Figure 1: Average ratio: pt_true / (pt_reco/1.3) vs. pt_reco (GeV/c)
Figure 2:
Average momentum difference: pt_true - (pt_reco/1.3) vs. pt_reco (GeV/c)
Figure 3: Average ratio: (pt_true -1.06) (pt_reco/1.3) vs. pt_reco (GeV/c)
Similar to Fig. 1, but with the true photon pt reduced by 1.06 GeV
Resulting true/reco pt ratio is flat in 4-6 GeV range.
Before further pursuing our efforts in tuning the tower energy response in the Monte-Carlo,
needs to address the observed energy loss difference in the fisrt layer of the BEMC/EEMC detector.
See Jason's blog post from 2009.07.16 for more details:
Comparison muon energy deposit in the 1st BEMC/EEMC layers
Monte-Carlo setup:
Some definitions:
Notations used in the plots:
Note: compare "Left" plots with Brians old results
Figure 1a: Et correction factor vs. pt thrown
Figure 1b: Et correction factor vs. eta thrown
Figure 1c: Et correction factor vs. phi thrown
Note: compare "Right" plots with Jason results with EEMC only geometry
Figure 2a: Sampling fraction vs. pt thrown
Figure 2b: Sampling fraction vs. energy thrown
Figure 2c: Sampling fraction vs. eta thrown
Figure 2d: Sampling fraction vs. phi thrown
Figure 3a: SMD energy vs. energy thrown
Figure 3b: SMD energy vs. eta thrown
Monte-Carlo setup is desribed here
Figure 1:Single photon shower shape before (red) and after (black) EEMC cAir bug fixed
pt=7-8GeV, eta=1.2-1.4 (left), eta=1.6-1.8 (right)
Figure 2: Single photon shower shape vs. data
Monte-Carlo: pt=7-10GeV, eta=1.6-1.8
data: no pre-shower1,2; pt_photon>7, pt_jet>5. no eta cuts.
(see Fig. 1 from here for other pre-shower conditions)
Monte-Carlo setup is desribed here
Color coding:
Single particle shower shape before (left) and after (right) EEMC cAir bug fixed
Single particle kinematic cuts: pt=7-8GeV, eta=1.2-1.4
Eta-meson shower shapes (blue) taken from Fig. 1 from here of this post
All shapes are normalized to 1 at peak (central strip).
Figure 1: Pre-shower bin 0: E_pre1=0; E_pre2=0
Figure 2: Pre-shower bin 1: E_pre1=0; E_pre2>0
Figure 3: Pre-shower bin 2: E_pre1>0; E_pre1<0.004
Figure 4: Pre-shower bin 3: E_pre1>0.004; E_pre1<0.01
Results only for corrected EEMC geometry
All shapes are divided by MC single-photon shower shape.
Figure 5a: Pre-shower bin 0: E_pre1=0; E_pre2=0
Figure 5b: Pre-shower bin 1: E_pre1=0; E_pre2>0
Figure 5c: Pre-shower bin 2: E_pre1>0; E_pre1<0.004
Figure 5d: Pre-shower bin 3: E_pre1>0.004; E_pre1<0.01
Figure 6: Single photon to eta-meson shape ratios only (with error bars):
Pre-shower bins 0 (upper-left),1 (upper-right),2 (lower-left), and 3 (lower-right)
Real data, and signal/background Monte-Carlo samples:
pp@200GeV collisions, STAR produnctionLong.
Trigger: eemc-http-mb-L2gamma [id:137641] (L ~ 3.164 pb^1)
Pythia prompt photon (signal) Monte-Carlo sample.
Filtered Prompt Photon p6410EemcGammaFilter.
Partonic pt range 2-25 GeV.
Pythia 2->2 hard QCD processes (background) Monte-Carlo sample.
Filtered QCD p6410EemcGammaFilter.
Partonic pt range 2-25 GeV.
No studies yet
No studies yet
No studies yet
No studies yet
No studies yet
No comparison yet
Monte-Carlo setup:
Color coding:
Pre-shower bins:
Ep1/Ep2 is the energy deposited in the 1st/2nd EEMC pre-shower layer.
For a single particle MC it is a sum over
all pre-shower tiles in the EEMC with energy of 3 sigma above pedestal.
For eta-meson from pp2006 data the sum is over 3x3 tower patch
Single particle kinematic cuts: pt=7-8GeV, eta=1.2-1.4
Eta-meson shower shapes (blue) taken from Fig. 1 from here of this post
All shapes are normalized to 1 at peak (central strip)
Figure 1: Shower shape sorted by pre-shower conditions.
cAir-Fixed EEMC geometry (NO slow simulator, WITH SVT)
Ratio plot
Figure 2: Shower shape sorted by pre-shower conditions.
cAir-Fixed EEMC geometry (NO slow simulator, NO SVT)
Ratio plot
Figure 3: Shower shape sorted by pre-shower conditions.
cAir-Fixed EEMC geometry (WITH slow simulator, WITH SVT)
Ratio plot
Figure 4: Shower shape sorted by pre-shower conditions.
Old cAir-bug EEMC geometry (NO slow simulator, WITH SVT)
Click here to see the plot
Starting with a fixed (50K events) for each type of particle.
Change in number of counts for a given pre-shower bin
with different detector configuration shows pre-shower migration
Figure 5: Pre-shower migration.
cAir-Fixed EEMC geometry (WITH SVT)
Figure 6: Pre-shower migration.
cAir-Fixed EEMC geometry (WITHOUT SVT)
Figure 7: Sampling fraction (0.05 E_reco / E_thrown).
cAir-Fixed EEMC geometry (WITHOUT Slow-simulator)
Figure 8: Sampling fraction (0.05 E_reco / E_thrown).
cAir-Fixed EEMC geometry (WITH Slow-simulator)
Slow simulator introduce some non-linearity in the sampling fraction
Figure 9: Sampling fraction (0.05 E_reco / E_thrown).
cAir-Fixed EEMC geometry (WITHOUT SVT, WITHOUT Slow-simulator)
Click here to see the plot
Figure 10: Sampling fraction (0.05 E_reco / E_thrown).
Old cAir-bug EEMC geometry (NO slow simulator, WITH SVT)
Click here to see the plot
Monte-Carlo setup:
Color coding:
Pre-shower bins:
Note: Ep1/Ep2 is the energy deposited in the 1st/2nd EEMC pre-shower layer.
For a single photon MC it is a sum over
all pre-shower tiles in the EEMC with energy of 3 sigma above pedestal.
For eta-meson/gamma-jet candidates from pp2006 data the sum is over 3x3 tower patch
Single particle kinematic cuts: pt=7-8GeV, eta=1.2-1.4
Eta-meson shower shapes (blue) taken from Fig. 1 from here of this post
All shapes are normalized to 1 at peak (central strip)
Figure 1: Shower shape sorted by pre-shower conditions.
Figure 2: Shower shape ratio. All shapes in Fig. 1 are divided by single photon shape
for "SVT+LOW_EM" configuration (black circles in Fig. 1)
Figure 3: Sampling fraction (0.05 * E_reco/ E_thrown)
Figure 4: Pre-shower1 energy (all tiles)
Figure 5: Pre-shower2 energy (all tiles)
Figure 6: Post-shower energy (all tiles)
Figure 7: Pre-shower bin photon migration
Figure 8a: Energy ratio in 2x1 to 3x3 cluster
For the first 4 pre-shower bins total yield in MC is normalized to that of the data
Blue circles indicate photon-jet candidates [pp2006] (points from this post)
Same data on a linear scale
Figure 8b: Energy ratio in 2x1 to 3x3 cluster: 7 < pt < 8 and 1.2 < eta < 1.4
Figure 8c: Energy ratio in 2x1 to 3x3 cluster: 7 < pt < 8 and 1.6 < eta < 1.8
Figure 9: Average energy ratio in 2x1 to 3x3 cluster vs. thrown energy
Figure 10: Average energy ratio in 2x1 to 3x3 cluster vs. thrown energy
LOW_EM option for the STAR geometry (Low cuts on Electro-Magnetic processes)
is equivalent to the following set of GEANT cuts:
All these values are for kinetic energy in GeV.
Cut meaning and GEANT default values:
Some details can be found at this link and in the GEANT manual
Monte-Carlo setup:
Color coding:
Figure 1: Sampling fraction vs. thrown energy (upper plot)
and vs. azimuthal angle (lower left) and rapidity (lower right)
Single particle kinematic cuts: pt=7-8GeV, eta=1.2-1.4
Eta-meson shower shapes (blue) taken from Fig. 1 from here of this post
All shapes are normalized to 1 at peak (central strip)
Pre-shower bins:
Ep1/Ep2 is the energy deposited in the 1st/2nd EEMC pre-shower layer.
For a single particle MC it is a sum over
all pre-shower tiles in the EEMC with energy of 3 sigma above pedestal.
For eta-meson from pp2006 data the sum is over 3x3 tower patch
The number of nested volumes (nv),
is the total number of parent volumes for the sensitive volume
(sensitive volume is indicated by the HITS in the tree structure below).
For the Jason and CVS files this nv number seems to be the same
(see block tree structures below).
Then why volume ids id in g2t tables has changed?
The answer I found (which seems trivial to me know)
is that in the original (CVS) file ECAL
block has been instantiated (positioned) twice.
The second appearance is the prototype (East) version of the Endcap
(Original ecalgeo.g from CVS)
if (emcg_OnOff==1 | emcg_OnOff==3) then Position ECAL in CAVE z=+center endif if (emcg_OnOff==2 | emcg_OnOff==3) then Position ECAL in CAVE z=-center ThetaZ=180 endif
In Jason version the second appearance has been removed
(what seems natural and it should not have any effect)
(ecalgeo.g Jason edits, g23):
IF (emcg_OnOff>0) THEN Create ECAL ..... IF (emcg_OnOff==2 ) THEN Prin1 ('East Endcap has been removed from the geometry' ) ENDIF EndIF! emcg_OnOff
Unfortunately, this affects the way GEANT counts nested volumes
(effectively the total number was reduced by 1, from 8 to 7)
and this is the reason why the volume numbering scheme
in g2t tables has been affected.
I propose to put back these East Endcap line back,
since in this case it will not require any additional
changes to the EEMC decoder and g2t tables.
blue - added volumes in Jason file
red - G10 volume removed in Jason file
HITS - sensitive volumes
---- Jason file ----
ECAL
EAGA
|EMSS
| -EFLP
| |ECVO
| | |EMOD
| | | |ESEC
| | | | |ERAD
| | | | | -ELED
| | | | |EMGT
| | | | | |EPER
| | | | | | |ETAR
| | | | | | | -EALP
| | | | | | | -ESCI -> HITS
| |ESHM
| | |ESPL
| | | |EXSG
| | | | -EXPS
| | | | -EHMS -> HITS
| | | | -EBLS
| | | | -EFLS
| | |ERSM
| -ESSP
| -ERCM
| -EPSB
|ECGH
| -ECHC
---- CVS file ----
ECAL
EAGA
|EMSS
| -EFLP
| |ECVO
| | |EMOD
| | | |ESEC
| | | | |ERAD
| | | | | -ELED
| | | | |EMGT
| | | | | |EPER
| | | | | | |ETAR
| | | | | | | -EALP
| | | | | | | -ESCI -> HITS
| |ESHM
| | |ESPL
| | | |EXSG
| | | | -EHMS -> HITS
| | | -EXGT
| | -ERSM
| -ESSP
| -ERCM
| -EPSB
|ECGH
| -ECHC
Create ECAL Block ECAL is one EMC EndCap wheel Create and Position EAGA AlphaZ=halfi EndBlock Block EAGA IS HALF OF WHEEL AIR VOLUME FORTHE ENDCAP MODULE Create AND Position EMSS konly='MANY' Create AND Position ECGH alphaz=90 kOnly='ONLY' EndBlock Block EMSS is the steel support of the endcap module Create AND Position EFLP z=zslice-center+zwidth/2 Create AND Position ECVO z=zslice-center+zwidth/2 Create AND Position ESHM z=zslice-center+zwidth/2 kOnly='MANY' Create AND Position ECVO z=zslice-center+zwidth/2 Create AND Position ESSP z=zslice-center+zwidth/2 Create ERCM Create EPSB EndBlock Block ECVO is one of endcap volume with megatiles and radiators Create AND Position EMOD alphaz=d3 ncopy=i_sector EndBlock Block ESHM is the shower maxsection Create and Position ESPL z=currentk Only='MANY' Create ERSM EndBlock Block ECGH is air gap between endcap half wheels Create ECHC EndBlock Block ECHC is steel endcap half cover EndBlock Block ESSP is stainless steelback plate EndBlock Block EPSB IS A PROJECTILE STAINLESS STEEL BAR EndBlock Block ERCM is stainless steel tie rod in calorimeter sections EndBlock Block ERSM is stainless steel tie rod in shower max EndBlock Block EMOD (fsect,lsect) IS ONE MODULEOF THE EM ENDCAP Create AND Position ESEC z=section-curr+secwid/2 EndBlock Block ESEC is a single em section Create AND Position ERAD z=length+(cell)/2+esec_deltaz Create AND Position EMGT z=length+(gap+cell)/2+esec_deltaz Create AND Position ERAD z=length+cell/2+esec_deltaz EndBlock Block EMGT is a 30 degree megatile Create AND Position EPER alphaz=myPhi EndBlock Block EPER is a 5 degree slice of a 30 degree megatile (subsector) Create and Position ETAR x=(rbot+rtop)/2ort=yzx EndBlock Block ETAR is a single calorimeter cell, containing scintillator, fiber router, etc... Create AND Position EALP y=(-megatile+emcs_alincell)/2 Create AND Position ESCI y=(-megatile+g10)/2+emcs_alincell _ EndBlock Block ESCI is the active scintillator (polystyrene) layer EndBlock Block ERAD is the lead radiator with stainless steel cladding Create AND Position ELED EndBlock Block ELED is a lead absorber plate EndBlock Block EFLP is the aluminum (aluminium) front plate of the endcap EndBlock Block EALP is the thin aluminium plate in calorimeter cell EndBlock Block ESPL is the logical volume containing an SMD plane Create and Position EXSG alphaz=d3 ncopy=isec kOnly='MANY' Create and Position EXSG alphaz=d3 ort=x-y-z ncopy=isec kOnly='MANY' Create and Position EXSG alphaz=d3 ncopy=isec kOnly='MANY' Create and Position EXSG alphaz=d3 ort=x-y-z ncopy=isec kOnly='MANY' Create and Position EXSG alphaz=d3 ncopy=isec kOnly='MANY' EndBlock Block EXSG Is another logical volume... this one acutally creates the planes Create and Position EXPS kONLY='MANY' Create and Position EHMS x=xc y=yc alphaz=-45 kOnly='ONLY' Create and Position EBLS x=xc y=yc z=(+esmd_apex/2+esmd_back_layer/2) alphaz=-45 kOnly='ONLY' Create and Position EHMS x=xc y=yc alphaz=-45 ort=x-y-z kOnly='ONLY' Create and Position EFLS x=xc y=yc z=(-esmd_apex/2-esmd_front_layer/2) alphaz=-45 ort=x-y-z kOnly='ONLY' EndBlock Block EHMS defines the triangular SMD strips Endblock! EHMS Block EFLS is the layer of material on the front of the SMD planes EndBlock! EFLS Block EBLS is the layer of material on the back of the SMD planes EndBlock! EFLS Block EXPS is the plastic spacer in the shower maximum section EndBlock
Create ECAL Block ECAL is one EMC EndCap wheel Create and Position EAGA AlphaZ=halfi EndBlock Block EAGA is half of wheel air volume forthe EndCap module Create and Position EMSS konly='MANY' Create and Position ECGH AlphaZ=90 konly='ONLY' EndBlock Block EMSS is steel support of the EndCap module Create and Position EFLP z=zslice-center+slcwid/2 Create and Position ECVO z=zslice-center+slcwid/2 Create and Position ESHM z=zslice-center+slcwid/2 Create and Position ECVO z=zslice-center+slcwid/2 Create and Position ESSP z=zslice-center+slcwid/2 Create ERCM Create EPSB EndBlock Block ECVO is one of EndCap Volume with megatiles and radiators Create and Position EMOD AlphaZ=d3 Ncopy=J_section EndBlock Block ESHM is the SHower Maxsection Create and Position ESPL z=current Create ERSM Endblock Block ECGH is air Gap between endcap Half wheels Create ECHC EndBlock Block ECHC is steel EndCap Half Cover EndBlock Block ESSP is Stainless Steelback Plate endblock Block EPSB is Projectile Stainless steel Bar endblock Block ERCM is stainless steel tie Rod in CaloriMeter sections endblock Block ERSM is stainless steel tie Rod in Shower Max endblock Block EMOD is one moduleof the EM EndCap Create and Position ESEC z=section-curr+secwid/2 endblock Block ESEC is a single EM section Create and Position ERAD z=len + (cell)/2 Create and Position EMGT z=len +(gap+cell)/2 Create and Position ERAD z=len + cell/2 Endblock Block EMGT is a megatile EM section Create and Position EPER AlphaZ=(emcs_Nslices/2-isec+0.5)*dphi Endblock Block EPER is a EM subsection period (super layer) Create and Position ETAR x=(RBot+RTop)/2ORT=YZX EndBlock Block ETAR is one CELL of scintillator, fiber and plastic Create and Position EALP y=(-mgt+emcs_AlinCell)/2 Create and Position ESCI y=(-mgt+G10)/2+emcs_AlinCell _ EndBlock Block ESCI is the active scintillator (polystyren) layer endblock Block ERAD is radiator Create and PositionELED endblock Block ELED is lead absorber Plate endblock Block EFLP is First Aluminium plate endblock Block EALP is ALuminiumPlate in calorimeter cell endblock Block ESPL is one of the Shower maxPLanes Create and position EXSG AlphaZ=d3Ncopy=isec Create and position EXSG AlphaZ=d3Ncopy=isec Create and position EXGT z=msecwd AlphaZ=d3 Create and position EXSG AlphaZ=d3 ORT=X-Y-Z Ncopy=isec Create and position EXGT z=-msecwd AlphaZ=d3 Create and position EXSG AlphaZ=d3Ncopy=isec Create and position EXGT z=msecwd AlphaZ=d3 Create and position EXSG AlphaZ=d3 ORT=X-Y-Z Ncopy=isec Create and position EXGT z=-msecwd AlphaZ=d3 Endblock Block EXSG is the Shower maxGap for scintillator strips Create EHMS endblock Block EHMS is sHower Max Strip Endblock Block EXGT is the G10 layer in the Shower Max EndBlock
Original (ecalgeo.g) file from CVS
****************************************************************************** Module ECALGEO is the EM EndCap Calorimeter GEOmetry Created 26 jan 1996 Author Rashid Mehdiyev * * Version 1.1, W.J. Llope * - changed sensitive medium names... * * Version 2.0, R.R. Mehdiyev 16.04.97 * - Support walls included * - intercell and intermodule gaps width updated * - G10 layers inserted * Version 2.1, R.R. Mehdiyev 23.04.97 * - Shower Max Detector geometry added * - Variable eta grid step size introduced * Version 2.2, R.R. Mehdiyev 03.12.97 * - Eta grid corrected * - Several changes in volume's dimensions * - Material changes in SMD * * Version 3.0, O. Rogachevsky 28.11.99 * - New proposal for calorimeter SN 0401 * * Version 4.1, O.Akio 3 Jan 01 * - Include forward pion detectors * Version 5.0, O. Rogachevsky 20.11.01 * - FPD is eliminated in this version * - More closed to proposal description * of calorimeter and SMD structure * ****************************************************************************** +CDE,AGECOM,GCONST,GCUNIT. * Content EAGA,EALP,ECAL,ECHC,ECVO,ECGH,EFLP,EHMS, ELED,EMGT,EMOD,EPER,EPSB,ERAD,ERCM,ERSM, ESHM,ESEC,ESCI,ESGH,ESPL,ESSP,EMSS, ETAR,EXGT,EXSG * Structure EMCG { Version, int Onoff, int fillMode} Structure EMCS { Type,ZOrig,ZEnd,EtaMin,EtaMax, PhiMin,PhiMax,Offset, Nsupsec,Nsector,Nsection,Nslices, Front,AlinCell,Frplast,Bkplast,PbPlate,LamPlate, BckPlate,Hub,Rmshift,SMShift,GapPlt,GapCel, GapSMD,SMDcentr,TieRod(2),Bckfrnt,GapHalf,Cover} * Structure EETR { Type,Etagr,Phigr,Neta,EtaBin(13)} * Structure ESEC { Isect, FPlmat, Cell, Scint, Nlayer } * Structure EMXG {Version,Sapex,Sbase,Rin,Rout,F4} * Structure EXSE {Jsect,Zshift,Sectype(6)} * Integer I_section,J_section,Ie,is,isec,i_str,Nstr,Type,ii,jj, cut,fsect,lsect,ihalf,filled * Real center,Plate,Cell,G10,diff,halfi, tan_low,tan_upp,Tanf,RBot,Rtop,Deta,etax,sq2,sq3, dup,dd,d2,d3,rshift,dphi,radiator,orgkeep,endkeep * Real maxcnt,msecwd,mxgten,curr,Secwid,Section, curcl,EtaTop,EtaBot,slcwid,zslice,Gap,mgt, xleft,xright,yleft,yright,current, rth,len,p,xc,yc,xx,yy,rbotrad, Rdel,dxy,ddn,ddup Integer N Parameter (N=12) * Tanf(etax) = tan(2*atan(exp(-etax))) * * ---------------------------------------------------------------------------- * * FillMode =1 only 2-5 sectors (in the first half) filled with scintillators * FillMode =2 all sectors filled (still only one half of one side) * FillMode =3 both halves (ie all 12 sectors are filled) Fill EMCG ! EM EndCAp Calorimeter basic data Version = 5.0 ! Geometry version OnOff = 3 ! Configurations 0-no, 1-west 2-east 3-both FillMode = 3 ! sectors fill mode Fill EMCS ! EM Endcap Calorimeter geometry Type = 1 ! =1 endcap, =2 fpd edcap prototype ZOrig = 268.763 ! calorimeter origin in z ZEnd = 310.007 ! Calorimeter end in z EtaMin = 1.086 ! upper feducial eta cut EtaMax = 2.0, ! lower feducial eta cut PhiMin = -90 ! Min phi PhiMax = 90 ! Max phi Offset = 0.0 ! offset in x Nsupsec = 6 ! Number of azimuthal supersectors Nsector = 30 ! Number of azimutal sectors (Phi granularity) Nslices = 5 ! number of phi slices in supersector Nsection = 4 ! Number of readout sections Front = 0.953 ! thickness of the front AL plates AlinCell = 0.02 ! Aluminim plate in cell Frplast = 0.015 ! Front plastic in megatile Bkplast = 0.155 ! Fiber routing guides and back plastic Pbplate = 0.457 ! Lead radiator thickness LamPlate = 0.05 ! Laminated SS plate thickness BckPlate = 3.175 ! Back SS plate thickness Hub = 3.81 ! thickness of EndCap hub Rmshift = 2.121 ! radial shift of module smshift = 0.12 ! radial shift of steel support walls GapPlt = 0.3/2 ! HALF of the inter-plate gap in phi GapCel = 0.03/2 ! HALF of the radial inter-cell gap GapSMD = 3.400 ! space for SMD detector SMDcentr = 279.542 ! SMD position TieRod = {160.,195} ! Radial position of tie rods Bckfrnt = 306.832 ! Backplate front Z GapHalf = 0.4 ! 1/2 Gap between halves of endcap wheel Cover = 0.075 ! Cover of wheel half * Rmshift = 2.121 ! radial shift of module * -------------------------------------------------------------------------- Fill EETR ! Eta and Phi grid values Type = 1 ! =1 endcap, =2 fpd EtaGr = 1.0536 ! eta_top/eta_bot tower granularity PhiGr = 0.0981747 ! Phi granularity (radians) NEta = 12 ! Eta granularity EtaBin = {2.0,1.9008,1.8065,1.7168,1.6317,1.5507,1.4738, 1.4007,1.3312,1.2651,1.2023,1.1427,1.086}! Eta rapidities *--------------------------------------------------------------------------- Fill ESEC ! First EM section ISect = 1 ! Section number Nlayer = 1 ! Number of Sci layers along z Cell = 1.505 ! Cell full width in z Scint = 0.5 ! Sci layer thickness * Fill ESEC ! First EM section ISect = 2 ! Section number Nlayer = 1 ! Number of Sci layers along z Cell = 1.505 ! Cell full width in z Scint = 0.5 ! Sci layer thickness * Fill ESEC ! Second EM section ISect = 3 ! Section number Nlayer = 4 ! Number of Sci layers along z Cell = 1.405 ! Cell full width in z Scint = 0.4 ! Sci layer thickness * Fill ESEC ! Third EM section ISect = 4 ! Section Nlayer = 18 ! Number of layers along z Cell = 1.405 ! Cell full width in z Scint = 0.4 ! Sci layer thickness * Fill ESEC ! 4th EM section ISect = 5 ! Section Nlayer = 1 ! Number of layers along z Cell = 1.505 ! Cell full width in z Scint = 0.5 ! Sci layer thickness *---------------------------------------------------------------------------- Fill EMXG ! EM Endcap SMD basic data Version = 1 ! Geometry version Sapex = 0.7 ! Scintillator strip apex Sbase = 1.0 ! Scintillator strip base Rin = 77.41 ! inner radius of SMD plane Rout = 213.922 ! outer radius of SMD plane F4 = .15 ! F4 thickness *---------------------------------------------------------------------------- Fill EXSE ! First SMD section JSect = 1 ! Section number Zshift = -1.215 ! Section width sectype = {4,1,0,2,1,0} ! 1-V,2-U,3-cutV,4-cutU * Fill EXSE ! Second SMD section JSect = 2 ! Section number Zshift = 0. ! Section width sectype = {0,2,1,0,2,3} ! 1-V,2-U,3-cutV,4-cutU * Fill EXSE ! Third SMD section JSect = 3 ! Section number Zshift = 1.215 ! Section width sectype = {1,0,2,1,0,2} ! 1-V,2-U,3-cutV,4-cutU *---------------------------------------------------------------------------- * Use EMCG * sq3 = sqrt(3.) sq2 = sqrt(2.) prin1 emcg_version ('ECALGEO version ', F4.2) * Endcap USE EMCS type=1 USE EETR type=1 orgkeep = emcs_ZOrig endkeep = emcs_ZEnd if(emcg_OnOff>0) then diff = 0.0 center = (emcs_ZOrig+emcs_ZEnd)/2 Tan_Upp = tanf(emcs_EtaMin) Tan_Low = tanf(emcs_EtaMax) rth = sqrt(1. + Tan_Low*Tan_Low) rshift = emcs_Hub * rth dup=emcs_Rmshift*Tan_Upp dd=emcs_Rmshift*rth d2=rshift + dd radiator = emcs_Pbplate + 2*emcs_LamPlate * d3=emcs_Rmshift-2*emcs_smshift dphi = (emcs_PhiMax-emcs_PhiMin)/emcs_Nsector Create ECAL if (emcg_OnOff==1 | emcg_OnOff==3) then Position ECAL in CAVE z=+center endif if (emcg_OnOff==2 | emcg_OnOff==3) then Position ECAL in CAVE z=-center ThetaZ=180 endif if(section > emcs_Zend) then prin0 section,emcs_Zend (' ECALGEO error: sum of sections exceeds maximum ',2F12.4) endif prin1 section (' EndCap calorimeter total depth ',F12.4) endif prin1 ('ECALGEO finished') * * ---------------------------------------------------------------------------- Block ECAL is one EMC EndCap wheel Material Air Medium standard Attribute ECAL seen=1 colo=7 ! lightblue shape CONE dz=(emcs_Zend-emcs_ZOrig)/2, Rmn1=orgkeep*Tan_Low-d2 Rmn2=endkeep*Tan_Low-d2, Rmx1=orgkeep*Tan_Upp+dup Rmx2=endkeep*Tan_Upp+dup do ihalf=1,2 filled=1 halfi = -105 + (ihalf-1)*180 if (ihalf=2 & emcg_FillMode<3) filled = 0 Create and Position EAGA AlphaZ=halfi enddo * EndBlock * ---------------------------------------------------------------------------- Block EAGA is half of wheel air volume for the EndCap module Attribute EAGA seen=1 colo=1 serial=filled ! black Material Air shape CONS dz=(emcs_Zend-emcs_ZOrig)/2, Rmn1=orgkeep*Tan_Low-d2 Rmn2=endkeep*Tan_Low-d2, Rmx1=orgkeep*Tan_Upp+dup Rmx2=endkeep*Tan_Upp+dup, phi1=emcs_PhiMin phi2=emcs_PhiMax if (filled=1) then Create and Position EMSS konly='MANY' curr = orgkeep ; curcl = endkeep Create and position ECGH AlphaZ=90 konly='ONLY' endif EndBlock * ---------------------------------------------------------------------------- Block EMSS is steel support of the EndCap module Attribute EMSS seen=1 colo=1 ! black Material Iron shape CONS dz=(emcs_Zend-emcs_ZOrig)/2, Rmn1=orgkeep*Tan_Low-d2 Rmn2=endkeep*Tan_Low-d2, Rmx1=orgkeep*Tan_Upp+dup Rmx2=endkeep*Tan_Upp+dup, phi1=emcs_PhiMin phi2=emcs_PhiMax zslice = emcs_ZOrig prin1 zslice (' Front Al plane starts at: ',F12.4) slcwid = emcs_Front Create and Position EFLP z=zslice-center+slcwid/2 zslice = zslice + slcwid prin1 zslice (' First calorimeter starts at: ',F12.4) fsect = 1; lsect = 3 slcwid = emcs_SMDcentr - emcs_GapSMD/2 - zslice * Create and Position ECVO z=zslice-center+slcwid/2 slcwid = emcs_GapSMD zslice = emcs_SMDcentr - emcs_GapSMD/2 prin1 section,zslice (' 1st calorimeter ends, SMD starts at: ',2F10.5) Create and Position ESHM z=zslice-center+slcwid/2 zslice = zslice + slcwid prin1 zslice (' SMD ends at: ',F10.5) * slcwid = 0 fsect = 4; lsect = 5 do I_section =fsect,lsect USE ESEC Isect=I_section Slcwid = slcwid + esec_cell*esec_Nlayer enddo slcwid = emcs_bckfrnt - zslice * Create and Position ECVO z = zslice-center+slcwid/2 zslice = emcs_bckfrnt prin1 section,zslice (' 2nd calorimeter ends, Back plate starts at: ',2F10.5) slcwid = emcs_BckPlate * Create and Position ESSP z=zslice-center+slcwid/2 zslice = zslice + slcwid prin1 zslice (' BackPlate ends at: ',F10.5) slcwid = emcs_Zend-emcs_ZOrig Create ERCM do i_str = 1,2 do is = 1,5 xx = emcs_phimin + is*30 yy = xx*degrad xc = cos(yy)*emcs_TieRod(i_str) yc = sin(yy)*emcs_TieRod(i_str) Position ERCM z=0 x=xc y=yc enddo enddo rth = orgkeep*Tan_Upp+dup + 2.5/2 xc = (endkeep - orgkeep)*Tan_Upp len = .5*(endkeep + orgkeep)*Tan_Upp + dup + 2.5/2 yc = emcs_Zend-emcs_ZOrig p = atan(xc/yc)/degrad Create EPSB do is = 1,6 xx = -75 + (is-1)*30 yy = xx*degrad xc = cos(yy)*len yc = sin(yy)*len Position EPSB x=xc y=yc AlphaZ=xx enddo EndBlock * ---------------------------------------------------------------------------- Block ECVO is one of EndCap Volume with megatiles and radiators Material Air Attribute ECVO seen=1 colo=3 ! green shape CONS dz=slcwid/2, Rmn1=zslice*Tan_Low-dd Rmn2=(zslice+slcwid)*Tan_Low-dd, Rmx1=zslice*Tan_Upp+dup Rmx2=(zslice+slcwid)*Tan_Upp+dup do J_section = 1,6 if (1 < J_section < 6 | emcg_FillMode > 1)then filled = 1 else filled = 0 endif d3 = 75 - (J_section-1)*30 Create and Position EMOD AlphaZ=d3 Ncopy=J_section enddo * EndBlock * ---------------------------------------------------------------------------- Block ESHM is the SHower Max section * Material Air Attribute ESHM seen=1 colo=4 ! blue Shape CONS dz=SlcWid/2, rmn1=zslice*Tan_Low-dd, rmn2=(zslice+slcwid)*Tan_Low-dd, rmx1=(zslice)*Tan_Upp+dup, rmx2=(zslice+slcwid)*Tan_Upp+dup, phi1=emcs_PhiMin phi2=emcs_PhiMax USE EMXG Version=1 maxcnt = emcs_SMDcentr prin1 zslice,section,center (' Z start for SMD,section: ',3F12.4) * do J_section = 1,3 USE EXSE Jsect=J_section * current = exse_Zshift secwid = emxg_Sapex + 2.*emxg_F4 section = maxcnt + exse_zshift prin1 j_section,current,section,secwid (' layer, Z, width : ',i3,3F12.4) rbot=section*Tan_Low rtop=section*Tan_Upp prin1 j_section,rbot,rtop (' layer, rbot,rtop : ',i3,2F12.4) Create and position ESPL z=current * end do Create ERSM do i_str = 1,2 do is = 1,5 xx = emcs_phimin + (is)*30 yy = xx*degrad xc = cos(yy)*emcs_TieRod(i_str) yc = sin(yy)*emcs_TieRod(i_str) Position ERSM z=0 x=xc y=yc enddo enddo Endblock * ---------------------------------------------------------------------------- Block ECGH is air Gap between endcap Half wheels Material Air Medium standard Attribute ECGH seen=0 colo=7 ! lightblue shape TRD1 dz=(emcs_Zend-emcs_ZOrig)/2, dy =(emcs_gaphalf+emcs_cover)/2, dx1=orgkeep*Tan_Upp+dup, dx2=endkeep*Tan_Upp+dup rth = emcs_GapHalf + emcs_cover xx=curr*Tan_Low-d2 xleft = sqrt(xx*xx - rth*rth) yy=curr*Tan_Upp+dup xright = sqrt(yy*yy - rth*rth) secwid = yy - xx xx=curcl*Tan_Low-d2 yleft = sqrt(xx*xx - rth*rth) yy=curcl*Tan_Upp+dup yright = sqrt(yy*yy - rth*rth) slcwid = yy - xx xx=(xleft+xright)/2 yy=(yleft + yright)/2 xc = yy - xx len = (xx+yy)/2 yc = curcl - curr p = atan(xc/yc)/degrad rth = -(emcs_GapHalf + emcs_cover)/2 Create ECHC Position ECHC x=len y=rth Position ECHC x=-len y=rth AlphaZ=180 EndBlock * ---------------------------------------------------------------------------- Block ECHC is steel EndCap Half Cover Attribute ECHC seen=1 colo=1 ! black Material Iron shape TRAP dz=(curcl-curr)/2, thet=p, bl1=secwid/2, tl1=secwid/2, bl2=slcwid/2, tl2=slcwid/2, h1=emcs_cover/2 h2=emcs_cover/2, phi=0 alp1=0 alp2=0 EndBlock * ---------------------------------------------------------------------------- Block ESSP is Stainless Steel back Plate * Material Iron Attribute ESSP seen=1 colo=6 fill=1 shape CONS dz=emcs_BckPlate/2, Rmn1=zslice*Tan_Low-dd Rmn2=(zslice+slcwid)*Tan_Low-dd, Rmx1=zslice*Tan_Upp+dup Rmx2=(zslice+slcwid)*Tan_Upp+dup, phi1=emcs_PhiMin phi2=emcs_PhiMax endblock * ---------------------------------------------------------------------------- Block EPSB is Projectile Stainless steel Bar * Material Iron Attribute EPSB seen=1 colo=6 fill=1 shape TRAP dz=(emcs_Zend-emcs_ZOrig)/2, thet=p, bl1=2.5/2, tl1=2.5/2, bl2=2.5/2, tl2=2.5/2, h1=2.0/2 h2=2.0/2, phi=0 alp1=0 alp2=0 endblock * ---------------------------------------------------------------------------- Block ERCM is stainless steel tie Rod in CaloriMeter sections * Material Iron Attribute ERSM seen=1 colo=6 fill=1 shape TUBE dz=slcwid/2, rmin=0, rmax=1.0425 ! nobody knows exactly endblock * ---------------------------------------------------------------------------- Block ERSM is stainless steel tie Rod in Shower Max * Material Iron Attribute ERSM seen=1 colo=6 fill=1 shape TUBE dz=slcwid/2, rmin=0, rmax=1.0425 endblock * ---------------------------------------------------------------------------- Block EMOD is one module of the EM EndCap Attribute EMOD seen=1 colo=3 serial=filled ! green Material Air Shape CONS dz=slcwid/2, phi1=emcs_PhiMin/emcs_Nsupsec, phi2=emcs_PhiMax/emcs_Nsupsec, Rmn1=zslice*Tan_Low-dd Rmn2=(zslice+slcwid)*Tan_Low-dd, Rmx1=zslice*Tan_Upp+dup Rmx2=(zslice+slcwid)*Tan_Upp+dup * * Running parameter 'section' contains the position of the current section * It should not be modified in daughters, use 'current' variable instead. * SecWid is used in all 'CONS' daughters to define dimensions. * * section = zslice curr = zslice + slcwid/2 Do I_section =fsect,lsect USE ESEC Isect=I_section * Secwid = esec_cell*esec_Nlayer if (I_section = 3 | I_section = 5) then ! no last radiator Secwid = Secwid - radiator else if (I_section = 4) then ! add one more radiator Secwid = Secwid - esec_cell + radiator endif Create and position ESEC z=section-curr+secwid/2 section = section + secwid * enddo endblock * ---------------------------------------------------------------------------- Block ESEC is a single EM section Attribute ESEC seen=1 colo=1 serial=filled Material Air Medium standard * Shape CONS dz=secwid/2, rmn1=(section-diff)*Tan_Low-dd, rmn2=(section+secwid-diff)*Tan_Low-dd, rmx1=(section-diff)*Tan_Upp+dup, rmx2=(section+secwid-diff)*Tan_Upp+dup * len = -secwid/2 current = section mgt = esec_scint + emcs_AlinCell _ + emcs_FrPlast + emcs_BkPlast gap = esec_cell - radiator - mgt prin2 I_section,section (' ESEC:I_section,section',i3,F12.4) Do is = 1,esec_Nlayer * define actual cell thickness: Cell = esec_cell plate = radiator * if (is=nint(esec_Nlayer) & (I_section = 3 | I_section = 5)) then Cell = mgt + gap Plate=0 else if (I_section = 4 & is = 1) then ! radiator only Cell = radiator endif * prin2 I_section,is,len,cell,current (' ESEC:I_section,is,len,cell,current ',2i3,3F12.4) if (I_section = 4 & is = 1) then ! radiator only cell = radiator + .14 Create and Position ERAD z=len + (cell)/2 len = len + cell current = current + cell else cell = mgt if(filled = 1) then Create and Position EMGT z=len +(gap+cell)/2 xx = current + (gap+cell)/2 prin2 I_section,is,xx (' MEGA I_section,is ',2i3,F10.4) endif len = len + cell + gap current = current + cell + gap if (Plate>0) then cell = radiator Create and Position ERAD z=len + cell/2 len = len + cell current = current + cell end if end if end do Endblock * ---------------------------------------------------------------------------- Block EMGT is a megatile EM section Attribute EMGT seen=1 colo=1 Material Air Medium standard * Shape CONS dz=mgt/2, rmn1=(current-diff)*Tan_Low-dd, rmn2=(current+mgt-diff)*Tan_Low-dd, rmx1=(current-diff)*Tan_Upp+dup, rmx2=(current+mgt-diff)*Tan_Upp+dup if (I_section=1 | I_section=2 | I_section=5) then Call GSTPAR (ag_imed,'CUTGAM',0.00001) Call GSTPAR (ag_imed,'CUTELE',0.00001) else Call GSTPAR (ag_imed,'CUTGAM',0.00008) Call GSTPAR (ag_imed,'CUTELE',0.001) Call GSTPAR (ag_imed,'BCUTE',0.0001) end if * Do isec=1,nint(emcs_Nslices) Create and Position EPER AlphaZ=(emcs_Nslices/2-isec+0.5)*dphi End Do Endblock *--------------------------------------------------------------------------- Block EPER is a EM subsection period (super layer) * Material POLYSTYREN Attribute EPER seen=1 colo=1 Shape CONS dz=mgt/2, phi1=emcs_PhiMin/emcs_Nsector, phi2=+emcs_PhiMax/emcs_Nsector, rmn1=(current-diff)*Tan_Low-dd, rmn2=(current+mgt-diff)*Tan_Low-dd, rmx1=(current-diff)*Tan_Upp+dup, rmx2=(current+mgt-diff)*Tan_Upp+dup * curcl = current+mgt/2 Do ie = 1,nint(eetr_NEta) EtaBot = eetr_EtaBin(ie) EtaTop = eetr_EtaBin(ie+1) RBot=(curcl-diff)*Tanf(EtaBot) * if(Plate > 0) then ! Ordinary Sci layer RTop=min((curcl-diff)*Tanf(EtaTop), _ ((current-diff)*Tan_Upp+dup)) else ! last Sci layer in section RTop=min((curcl-diff)*Tanf(EtaTop), _ ((current-diff)*Tan_Upp+dup)) endif check RBot<RTop * xx=tan(pi*emcs_PhiMax/180.0/emcs_Nsector) yy=cos(pi*emcs_PhiMax/180.0/emcs_Nsector) Create and Position ETAR x=(RBot+RTop)/2 ORT=YZX prin2 ie,EtaTop,EtaBot,rbot,rtop (' EPER : ie,EtaTop,EtaBot,rbot,rtop ',i3,4F12.4) enddo * EndBlock * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Block ETAR is one CELL of scintillator, fiber and plastic * Attribute ETAR seen=1 colo=4 ! blue * local z goes along the radius, y is the thickness Shape TRD1 dy=mgt/2 dz=(RTop-RBot)/2, dx1=RBot*xx-emcs_GapCel/yy, dx2=RTop*xx-emcs_GapCel/yy * Create and Position EALP y=(-mgt+emcs_AlinCell)/2 G10 = esec_scint Create and Position ESCI y=(-mgt+G10)/2+emcs_AlinCell _ +emcs_FrPlast EndBlock * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Block ESCI is the active scintillator (polystyren) layer * Material POLYSTYREN Material Cpolystyren Isvol=1 Attribute ESCI seen=1 colo=7 fill=0 ! lightblue * local z goes along the radius, y is the thickness Shape TRD1 dy=esec_scint/2, dz=(RTop-RBot)/2-emcs_GapCel Call GSTPAR (ag_imed,'CUTGAM',0.00008) Call GSTPAR (ag_imed,'CUTELE',0.001) Call GSTPAR (ag_imed,'BCUTE',0.0001) Call GSTPAR (ag_imed,'CUTNEU',0.001) Call GSTPAR (ag_imed,'CUTHAD',0.001) Call GSTPAR (ag_imed,'CUTMUO',0.001) * define Birks law parameters Call GSTPAR (ag_imed,'BIRK1',1.) Call GSTPAR (ag_imed,'BIRK2',0.013) Call GSTPAR (ag_imed,'BIRK3',9.6E-6) * HITS ESCI Birk:0:(0,10) * xx:16:H(-250,250) yy:16:(-250,250) zz:16:(-350,350), * px:16:(-100,100) py:16:(-100,100) pz:16:(-100,100), * Slen:16:(0,1.e4) Tof:16:(0,1.e-6) Step:16:(0,100), * none:16: endblock * ---------------------------------------------------------------------------- Block ERAD is radiator * Material Iron Attribute ERAD seen=1 colo=6 fill=1 ! violet Shape CONS dz=radiator/2, rmn1=(current)*Tan_Low-dd, rmn2=(current+cell)*Tan_Low-dd, rmx1=(current)*Tan_Upp+dup, rmx2=(current+radiator)*Tan_Upp+dup Create and Position ELED endblock * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Block ELED is lead absorber Plate * Material Lead Attribute ELED seen=1 colo=4 fill=1 Shape TUBS dz=emcs_Pbplate/2, rmin=(current)*Tan_Low, rmax=(current+emcs_Pbplate)*Tan_Upp, Call GSTPAR (ag_imed,'CUTGAM',0.00008) Call GSTPAR (ag_imed,'CUTELE',0.001) Call GSTPAR (ag_imed,'BCUTE',0.0001) Call GSTPAR (ag_imed,'CUTNEU',0.001) Call GSTPAR (ag_imed,'CUTHAD',0.001) Call GSTPAR (ag_imed,'CUTMUO',0.001) endblock * ---------------------------------------------------------------------------- Block EFLP is First Aluminium plate * Material Aluminium Attribute EFLP seen=1 colo=3 fill=1 ! green shape CONS dz=emcs_Front/2, Rmn1=68.813 Rmn2=68.813, Rmx1=(zslice-diff)*Tan_Upp+dup, Rmx2=(zslice + slcwid-diff)*Tan_Upp+dup, phi1=emcs_PhiMin phi2=emcs_PhiMax endblock * ---------------------------------------------------------------------------- Block EALP is ALuminium Plate in calorimeter cell * Material Aluminium Material StrAluminium isvol=0 Attribute EALP seen=1 colo=1 Shape TRD1 dy=emcs_AlinCell/2 dz=(RTop-RBot)/2 Call GSTPAR (ag_imed,'CUTGAM',0.00001) Call GSTPAR (ag_imed,'CUTELE',0.00001) Call GSTPAR (ag_imed,'LOSS',1.) Call GSTPAR (ag_imed,'STRA',1.) endblock * ---------------------------------------------------------------------------- Block ESPL is one of the Shower max PLanes * Material Air Attribute ESPL seen=1 colo=3 ! blue Shape TUBS dz=SecWid/2, rmin=section*Tan_Low-1.526, rmax=(section-secwid/2)*Tan_Upp+dup, phi1=emcs_PhiMin phi2=emcs_PhiMax USE EMXG Version=1 msecwd = (emxg_Sapex+emxg_F4)/2 do isec=1,6 cut=1 d3 = 75 - (isec-1)*30 if (exse_sectype(isec) = 0 | (emcg_FillMode=1 & (isec=6 | isec=1))) then cut = 0 Create and position EXSG AlphaZ=d3 Ncopy=isec else if(exse_sectype(isec) = 1) then ! V Create and position EXSG AlphaZ=d3 Ncopy=isec Create and position EXGT z=msecwd AlphaZ=d3 else if(exse_sectype(isec) = 2) then ! U Create and position EXSG AlphaZ=d3 ORT=X-Y-Z Ncopy=isec Create and position EXGT z=-msecwd AlphaZ=d3 else if(exse_sectype(isec) = 3) then ! cut V cut=2 Create and position EXSG AlphaZ=d3 Ncopy=isec Create and position EXGT z=msecwd AlphaZ=d3 else if(exse_sectype(isec) = 4) then ! cut U cut=2 Create and position EXSG AlphaZ=d3 ORT=X-Y-Z Ncopy=isec Create and position EXGT z=-msecwd AlphaZ=d3 endif enddo Endblock * ---------------------------------------------------------------------------- Block EXSG is the Shower max Gap for scintillator strips * Attribute EXSG seen=1 colo=7 serial=cut ! black Material Air Shape TUBS dz=SecWid/2, rmin=section*Tan_Low-1.526, rmax=(section-secwid/2)*Tan_Upp+dup, phi1=emcs_PhiMin/emcs_Nsupsec, phi2=emcs_PhiMax/emcs_Nsupsec * Rbot = emxg_Rin Rtop = emxg_Rout if(cut > 0) then if(cut = 1) then Rdel = 3.938 Nstr = 288 else Rdel = -.475 Nstr = 285 endif rth = .53*rdel ! .53 --- tentatavily ddn = sq3*1.713 + Rdel ddup = .5*1.846 + 1.713 prin2 Rbot,Rtop,Nstr (' EXSG: Rbot,Rtop,Nstr',2F12.4,I5) mgt = emxg_Sbase + .01 do i_str = 1,nstr p = .5*(i_str-1)*mgt + 41.3655 * if (p <= (.5*rbot*sq3 + rth)) then dxy = 1.9375*sq2 xleft = .5*sq2*p*(sq3 + 1.) - dxy yleft = .5*sq2*p*(sq3 - 1.) - dxy yright = .5*sq2*(sqrt( rbot*rbot - p*p) - p) xright = sq2*p + yright else if ((.5*rbot*sq3 + rth) < p <= (.5*Rtop + 1.5)) then prin2 i_str,p (' EXSG: 2 - -i_str,p:',i3,F12.4) dxy = 1.9375*sq2 xleft = .5*sq2*p*(sq3 + 1.) - dxy yleft = .5*sq2*p*(sq3 - 1.) - dxy dxy = rdel*sq2/sq3 yright = .5*sq2*p*(1.- 1./sq3) xright = sq2*p - yright - dxy yright = -yright - dxy else if (p > (.5*rtop +1.5)) then prin2 i_str,p (' EXSG: 3 - - i_str,p:',i3,F12.4) yleft = (sqrt(rtop*rtop - p*p) - p)/sq2 xleft = sq2*p + yleft dxy = rdel*sq2/sq3 yright = .5*sq2*p*(1.- 1./sq3) xright = sq2*p - yright - dxy yright = -yright - dxy dxy = 0. if ((.5*sq3*160.- ddn) < p <= (.5*sq3*160.+ ddup) ) then prin2 i_str,p (' EXSG: 4 - - i_str,p:',i3,F12.4) xc = .5*(sq3*160.+1.846) yc = xc - .5*sq3*1.713 if (p > yc) then dxy = .5*sq2*(2/sq3*rdel + .5*sq3*1.846 +_ sqrt(1.713*1.713 - (p-xc)*(p-xc))) else dxy = sq2/sq3*(p - .5*sq3* 160. + ddn) endif else if ((.5*sq3*195.- ddn) < p <= (.5*sq3*195. + ddup) ) then prin2 i_str,p (' EXSG: 5 - - i_str,p:',i3,F12.4) xc = .5*(sq3*195.+1.846) yc = xc - .5*sq3*1.713 if (p > yc) then dxy = .5*sq2*(2/sq3*rdel + .5*sq3*1.846 +_ sqrt(1.713*1.713 - (p-xc)*(p-xc))) else dxy = sq2/sq3*(p - .5*sq3*195. + ddn) endif endif xright = xright + dxy yright = yright + dxy endif dxy = section*Tan_Upp - Rtop xc = .5*(xright+xleft) + dxy yc = .5*(yright+yleft) xx = .5*sq2*(xleft+yleft) yy = .5*sq2*(xright+yright) len = xx-yy prin2 i_str,p,yy,xx,len,xc,yc (' EXSG: i_str,x,y1,y2,len,xc,yc:',i3,6F12.4) * Create EHMS if (mod(i_str,2) != 0 ) then Position EHMS x=xc y=yc AlphaZ=-45 else Position EHMS x=xc y=yc AlphaZ=-45 ORT=X-Y-Z endif end do endif * dcut exsg z 0 0 10 0.1 0.1 * dcut exsg y 0 10 -50 0.7 0.7 endblock * ---------------------------------------------------------------------------- Block EHMS is sHower Max Strip * Material POLYSTYREN Material Cpolystyren Isvol=1 Attribute EHMS seen=1 colo=2 serial=cut ! red Shape TRD1 dx1=0 dx2=emxg_Sbase/2 dy=len/2 dz=emxg_Sapex/2 Call GSTPAR (ag_imed,'CUTGAM',0.00008) Call GSTPAR (ag_imed,'CUTELE',0.001) Call GSTPAR (ag_imed,'BCUTE',0.0001) * define Birks law parameters Call GSTPAR (ag_imed,'BIRK1',1.) Call GSTPAR (ag_imed,'BIRK2',0.0130) Call GSTPAR (ag_imed,'BIRK3',9.6E-6) * HITS EHMS Birk:0:(0,10) * xx:16:SH(-250,250) yy:16:(-250,250) zz:16:(-350,350), * px:16:(-100,100) py:16:(-100,100) pz:16:(-100,100), * Slen:16:(0,1.e4) Tof:16:(0,1.e-6) Step:16:(0,100), * none:16: Eloss:0:(0,10) * Endblock * ---------------------------------------------------------------------------- Block EXGT is the G10 layer in the Shower Max * * G10 is about 60% SiO2 and 40% epoxy Component Si A=28.08 Z=14 W=0.6*1*28./60. Component O A=16 Z=8 W=0.6*2*16./60. Component C A=12 Z=6 W=0.4*8*12./174. Component H A=1 Z=1 W=0.4*14*1./174. Component O A=16 Z=8 W=0.4*4*16./174. Mixture g10 Dens=1.7 Attribute EXGT seen=1 colo=7 Shape TUBS dz=emxg_F4/2, rmin=(section-diff)*Tan_Low-1.526, rmax=(section+msecwd-diff)*Tan_Upp, phi1=emcs_PhiMin/emcs_Nsupsec, phi2=emcs_PhiMax/emcs_Nsupsec Call GSTPAR (ag_imed,'CUTGAM',0.00001) Call GSTPAR (ag_imed,'CUTELE',0.00001) EndBlock * ---------------------------------------------------------------------------- * ECAL nice views: dcut ecvo x 1 10 -5 .5 .1 * draw emdi 105 0 160 2 13 .2 .1 * draw emdi 120 180 150 1 14 .12 .12 * --------------------------------------------------------------------------- end
ecalgeo.g geometry file (Jason Webb edits, g23)
c***************************************************************************** Module ECALGEO is the EM EndCap Calorimeter GEOmetry c-- Created 26 jan 1996 Author Rashid Mehdiyev c-- c Version 1.1, W.J. Llope c - changed sensitive medium names... c c Version 2.0, R.R. Mehdiyev 16.04.97 c - Support walls included c - intercell and intermodule gaps width updated c - G10 layers inserted c Version 2.1, R.R. Mehdiyev 23.04.97 c - Shower Max Detector geometry added c - Variable eta grid step size introduced c Version 2.2, R.R. Mehdiyev 03.12.97 c - Eta grid corrected c - Several changes in volumes dimensions c - Material changes in SMD c c Version 3.0, O. Rogachevsky 28.11.99 c - New proposal for calorimeter SN 0401 c c Version 4.1, O.Akio 3 Jan 01 c - Include forward pion detectors c c Version 5.0, O. Rogachevsky 20.11.01 c - FPD is eliminated in this version c - More closed to proposal description c of calorimeter and SMD structure c c***************************************************************************** +CDE,AGECOM,GCONST,GCUNIT. * Content EAGA,EALP,ECAL,ECHC,ECVO,ECGH,EFLP,EHMS, ELED,EMGT,EMOD,EPER,EPSB,ERAD,ERCM,ERSM, ESHM,ESEC,ESCI,ESGH,ESPL,ESSP,EMSS,ETAR, EXGT,EXSG,EXPS,EFLS,EBLS Structure EMCG { Version, int Onoff, int fillMode} Structure EMCS { Version,Type,zorg,zend,EtaMin,EtaMax, PhiMin,PhiMax,Offset, Nsupsec,Nsector,Nsection,Nslices, Front,AlinCell,Frplast,Bkplast,PbPlate,LamPlate, BckPlate,Hub,Rmshift,SMShift,GapPlt,GapCel, GapSMD,SMDcentr,TieRod(2),Bckfrnt,GapHalf,Cover, Rtie,slop} Structure EETR { Type,Etagr,Phigr,Neta,EtaBin(13)} Structure ESEC { Isect, FPlmat, Cell, Scint, Nlayer, deltaz, Jiggle(18) } Structure EMXG {Version,Sapex,Sbase,Rin,Rout,F4} Structure EXSE {Jsect,Zshift,Sectype(6)} Structure ESMD {Version, front_layer, back_layer, spacer_layer, base, apex } Integer I_section,J_section,Ie,is,isec,istrip,Nstr,Type,ii,jj, cut,fsect,lsect,ihalf,filled,i,j,k,i_sector Real center,Plate,Cell,G10,halfi, tan_low,tan_upp,Tanf,RBot,Rtop,Deta,etax,sq2,sq3, dup,dd,d2,d3,rshift,dphi,radiator Real maxcnt,msecwd,mxgten,curr,Secwid,Section, curcl,EtaTop,EtaBot,zwidth,zslice,Gap,megatile, xleft,xright,yleft,yright,current, rth,length,p,xc,yc,xx,yy,rdel,dxy,ddn,ddup Real myPhi Integer N Parameter (N=12) Tanf(etax) = tan(2*atan(exp(-etax))) c-------------------------------------------------------------------------------- c Data c c FillMode =1 only 2-5 sectors (in the first half) filled with scintillators c FillMode =2 all sectors filled (still only one half of one side) c FillMode =3 both halves (ie all 12 sectors are filled) c c OnOff =0 Do not build geometry c OnOff =1 Build West Endcap c OnOff =2 Build East Endcap (disabled) c OnOff =3 Build Both Endcaps (east disabled) c c Note: Fill EMCG ! EM EndCAp Calorimeter basic data Version = 5.0 ! Geometry version OnOff = 3 ! Configurations 0-no, 1-west 2-east 3-both FillMode = 3 ! sectors fill mode c-- Fill EMCS ! EM Endcap Calorimeter geometry Version = 1 ! Versioning Type = 1 ! =1 endcap, =2 fpd edcap prototype ZOrg = 268.763 ! calorimeter origin in z ZEnd = 310.007 ! Calorimeter end in z EtaMin = 1.086 ! upper feducial eta cut EtaMax = 2.0, ! lower feducial eta cut PhiMin = -90 ! Min phi PhiMax = 90 ! Max phi Offset = 0.0 ! offset in x Nsupsec = 6 ! Number of azimuthal supersectors Nsector = 30 ! Number of azimutal sectors (Phi granularity) Nslices = 5 ! number of phi slices in supersector Nsection = 4 ! Number of readout sections Front = 0.953 ! thickness of the front AL plates AlinCell = 0.02 ! Aluminim plate in cell Frplast = 0.015 ! Front plastic in megatile Bkplast = 0.155 ! Fiber routing guides and back plastic Pbplate = 0.457 ! Lead radiator thickness LamPlate = 0.05 ! Laminated SS plate thickness BckPlate = 3.175 ! Back SS plate thickness Hub = 3.81 ! thickness of EndCap hub Rmshift = 2.121 ! radial shift of module smshift = 0.12 ! radial shift of steel support walls GapPlt = 0.3/2 ! HALF of the inter-plate gap in phi GapCel = 0.03/2 ! HALF of the radial inter-cell gap GapSMD = 3.400 ! space for SMD detector << version 2 -- 3.600 >> SMDcentr = 279.542 ! SMD position TieRod = {160.,195} ! Radial position of tie rods Bckfrnt = 306.832 ! Backplate front Z GapHalf = 0.4 ! 1/2 Gap between halves of endcap wheel Cover = 0.075 ! Cover of wheel half Rtie = 1.0425 ! Radius of tie rod Slop = 0.1400 ! Added to cell containing radiator 6 (formerly hardcoded in geom) c-- Fill EMCS ! EM Endcap Calorimeter geometry Version = 2 ! Versioning Type = 1 ! =1 endcap, =2 fpd edcap prototype ZOrg = 268.763 ! calorimeter origin in z ZEnd = 310.007 ! Calorimeter end in z EtaMin = 1.086 ! upper feducial eta cut EtaMax = 2.0, ! lower feducial eta cut PhiMin = -90 ! Min phi PhiMax = 90 ! Max phi Offset = 0.0 ! offset in x Nsupsec = 6 ! Number of azimuthal supersectors Nsector = 30 ! Number of azimutal sectors (Phi granularity) Nslices = 5 ! number of phi slices in supersector Nsection = 4 ! Number of readout sections Front = 0.953 ! thickness of the front AL plates AlinCell = 0.02 ! Aluminim plate in cell Frplast = 0.015 ! Front plastic in megatile Bkplast = 0.155 ! Fiber routing guides and back plastic Pbplate = 0.457 ! Lead radiator thickness LamPlate = 0.05 ! Laminated SS plate thickness BckPlate = 3.175 ! Back SS plate thickness Hub = 3.81 ! thickness of EndCap hub Rmshift = 2.121 ! radial shift of module smshift = 0.12 ! radial shift of steel support walls GapPlt = 0.3/2 ! HALF of the inter-plate gap in phi GapCel = 0.03/2 ! HALF of the radial inter-cell gap GapSMD = 3.600 ! space for SMD detector (* from master_geom_bmp.xls *) SMDcentr = 279.542 ! SMD position TieRod = {160.,195} ! Radial position of tie rods Bckfrnt = 306.832 ! Backplate front Z GapHalf = 0.4 ! 1/2 Gap between halves of endcap wheel Cover = 0.075 ! Cover of wheel half Rtie = 0.75 ! Radius of tie rod Slop = 0.0000 ! Added to cell containing radiator 6 (formerly hardcoded in geom) c-- c--------------------------------------------------------------------------- c-- c-- Supporting documentation: c-- http://drupal.star.bnl.gov/STAR/system/files/SMD_module_stack.pdf c-- Fill ESMD ! shower maximum detector information Version = 1 ! versioning information front_layer = 0.161 ! thickness of front layer back_layer = 0.210 ! thickness of back layer base = 1.0 ! base of the SMD strip apex = 0.7 ! apex of the SMD strip spacer_layer = 1.2 ! spacer layer c-- Fill EETR ! Eta and Phi grid values Type = 1 ! =1 endcap, =2 fpd EtaGr = 1.0536 ! eta_top/eta_bot tower granularity PhiGr = 0.0981747 ! Phi granularity (radians) NEta = 12 ! Eta granularity EtaBin = {2.0,1.9008,1.8065,1.7168,1.6317,1.5507,1.4738, 1.4007,1.3312,1.2651,1.2023,1.1427,1.086}! Eta rapidities c-- c--------------------------------------------------------------------------- c-- Fill ESEC ! Preshower 1 / Radiator 1 ISect = 1 ! Section number Nlayer = 1 ! Number of Sci layers along z Cell = 1.505 ! Cell full width in z Scint = 0.475 ! Sci layer thickness (4.75mm Bicron) deltaz = -0.014 ! Amount to shift section in z to align with as-built numbers Jiggle = {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} ! Degrees to shift EPER in each layer c-- c-- Note: Jiggle allows one to shift each megatile by Jiggle(i) degrees, where c-- i indicates the layer within the section of the calorimeter. This feature c-- has only been crudely tested... i.e. it compiles and creates a reasonable c-- set of pictures, but I have not verified that every scintillator shows up... c-- There could be volume conflicts and this would need to be checked. --JW c-- Fill ESEC ! Preshower 2 / Radiator 2 ISect = 2 ! Section number Nlayer = 1 ! Number of Sci layers along z Cell = 1.505 ! Cell full width in z Scint = 0.475 ! Sci layer thickness (4.75mm Bicron) deltaz = -0.0182 ! Amount to shift section in z to align with as-built numbers Jiggle = {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} ! Degrees to shift EPER in each layer c-- Fill ESEC ! Megatiles 3-6 / Radiators 3-5 ISect = 3 ! Section number Nlayer = 4 ! Number of Sci layers along z Cell = 1.405 ! Cell full width in z Scint = 0.4 ! Sci layer thickness deltaz = -0.0145 ! Amount to shift section in z to align with as-built numbers Jiggle = {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} ! Degrees to shift EPER in each layer c-- Fill ESEC ! Megatiles 7-23 / Radiators 6-23 ISect = 4 ! Section Nlayer = 18 ! Number of layers along z Cell = 1.405 ! Cell full width in z Scint = 0.4 ! Sci layer thickness deltaz = +0.0336 ! Amount to shift section in z to align with as-built numbers Jiggle = {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} ! Degrees to shift EPER in each layer c-- Fill ESEC ! Postshower ISect = 5 ! Section Nlayer = 1 ! Number of layers along z Cell = 1.505 ! Cell full width in z Scint = 0.5 ! Sci layer thickness (5.0mm Kurarary) deltaz = +0.036 ! Amount to shift section in z to align with as-built numbers Jiggle = {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} ! Degrees to shift EPER in each layer c-- c---------------------------------------------------------------------------- c-- Fill EMXG ! EM Endcap SMD basic data Version = 1 ! Geometry version Sapex = 0.7 ! Scintillator strip apex Sbase = 1.0 ! Scintillator strip base Rin = 77.41 ! inner radius of SMD plane Rout = 213.922 ! outer radius of SMD plane F4 = .15 ! F4 thickness c-- c---------------------------------------------------------------------------- c-- Fill EXSE ! First SMD section JSect = 1 ! Section number Zshift = -1.215 ! Section width sectype = {4,1,0,2,1,0} ! 1-V,2-U,3-cutV,4-cutU c-- Fill EXSE ! Second SMD section JSect = 2 ! Section number Zshift = 0. ! Section width sectype = {0,2,1,0,2,3} ! 1-V,2-U,3-cutV,4-cutU c-- Fill EXSE ! Third SMD section JSect = 3 ! Section number Zshift = 1.215 ! Section width sectype = {1,0,2,1,0,2} ! 1-V,2-U,3-cutV,4-cutU c-- c---------------------------------------------------------------------------- c-- Materials c-- c-- PVC used in the SMD spacer layers c-- Component H A=1 Z=1 W=3.0*1.0/62.453 Component C A=12 Z=6 W=2.0*12.0/62.453 Component Cl A=35.453 Z=17 W=1.0*35.453/62.453 Mixture PVC_Spacer Dens=1.390*(1.20/1.00) c-- c-- Lead alloy used in the radiators c-- Component Sn A=118.710 Z=50 W=0.014 Component Ca A=40.0780 Z=20 W=0.00075 Component Al A=26.9815 Z=13 W=0.0003 Component Pb A=207.190 Z=82 W=0.98495 Mixture PbAlloy DENS=11.35 c-- c-- Stainless Steel used in various places c-- Component Cr A=51.9960 Z=24 W=0.19 Component Ni A=58.6934 Z=28 W=0.09 Component Fe A=55.8450 Z=26 W=0.72 Mixture Steel DENS=8.03 c-- c-- Aluminized mylar. According to information which I dug up on a google c-- search, this is typically mylar coated with a thin (1000 angstrom) layer c-- of aluminium on each side. c-- c-- http://www.eljentechnology.com/datasheets/EJ590-B10HH%20data%20sheet.pdf c-- Component Mylar A=12.875 Z=6.4580 w=0.999 Component Al A=26.980 Z=13.000 w=0.001 Mixture AlMylar dens=1.390 c-- c-- G10 Epoxy used in various places c-- Component Si A=28.08 Z=14 W=0.6*1*28./60. Component O A=16 Z=8 W=0.6*2*16./60. Component C A=12 Z=6 W=0.4*8*12./174. Component H A=1 Z=1 W=0.4*14*1./174. Component O A=16 Z=8 W=0.4*4*16./174. Mixture G10 Dens=1.7 c-- c-- Fibreglass cloth used in SMD stackup. I googled this one too... a self- c-- described expert quotes typical densities and percent by volume c-- http://en.allexperts.com/q/Composite-Materials-2430/fiberglass-1.htm c-- c-- glass fiber: 2.6 g/cm3 (17.6%) resin: 1.3 g/cm3 (82.4%) c-- c-- Fiberglass density = 1.529 g/cm3 c-- c-- I will assume that G10 epoxy is close enough to the typical resins c-- used, at least in terms of chemical composition. Then c-- Component G10 A=18.017 Z=9.013 W=1.3*0.824/(1.3*0.824+2.6*0.176) Component Si A=28.08 Z=14 W=2.6*0.176/(1.3*0.824+2.6*0.176)*28.08/60.08 Component O A=16 Z=8 W=2.6*0.176/(1.3*0.824+2.6*0.176)*32.00/60.08 Mixture Fiberglass dens=1.53 c-- c-- c---------------------------------------------------------------------------- c-- Select versions of various geometry data c-- Use EMCG Use EMCS Version=2 Use EETR c-- c---------------------------------------------------------------------------- c-- Calculate frequently used quantities c-- sq3 = sqrt(3.) ! 1/tan(30deg) = sq3 sq2 = sqrt(2.) c-- c-- center = (emcs_zorg+emcs_zend)/2 ! center of the calorimeter tan_upp = tanf(emcs_etamin) ! think this is angle pointing to top of calo tan_low = tanf(emcs_etamax) ! think this is angle pointing to bot of calo rth = sqrt(1. + tan_low*tan_low) ! ?? rshift = emcs_hub * rth ! ?? dup = emcs_rmshift*tan_upp ! dd = emcs_rmshift*rth ! d2 = rshift + dd ! radiator = emcs_pbplate + 2*emcs_lamplate ! thickness of radiator assembly dphi = (emcs_phimax-emcs_phimin)/emcs_nsector ! single endcap sector c-- c---------------------------------------------------------------------------- c---------------------------------------------------------------------------- c-- BEGIN Prin1 emcg_version ('ecalgeo version: ',F4.2) c-- IF (emcg_OnOff>0) THEN c-- c-- Build the EEMC geometry for one half wheel c-- Create ECAL c-- c-- Position the two halves. Bottom half installed in 2003, top c-- half in 2004... so we allow logic to allow for the time c-- evolution of the calorimeter c-- c-- c-- West Endcap c-- IF (emcg_OnOff==1 | emcg_OnOff==3) THEN Position ECAL in CAVE z=+center ENDIF IF (section > emcs_zend) THEN Prin1 section, emcs_zend (' ECALGEO error: sum of sections exceeds maximum ',2F12.4) ENDIF IF (emcg_OnOff==2 ) THEN Prin1 ('East Endcap has been removed from the geometry' ) ENDIF c-- EndIF! emcg_OnOff c-- Prin1 ('ECALGEO finished') c-- c-- END c---------------------------------------------------------------------------- c----------------------------------------------------------------- Block ECAL -- c-- Block ECAL is one EMC EndCap wheel c-- c-- The EEMC is built from two 180 degree half-wheels tilted at an angle c-- with respect to zero in the STAR reference frame. This block is serves c-- as a logical volume which creates the two half wheels. c-- c-- Creates: c-- + EAGA c-- Material Air Attribute ECAL seen=0 colo=7 ! lightblue c-- Shape CONE dz=(emcs_zend-emcs_zorg)/2, rmn1=emcs_zorg*tan_low-d2, rmn2=emcs_zend*tan_low-d2, rmx1=emcs_zorg*tan_upp+dup, rmx2=emcs_zend*tan_upp+dup c-- c-- DO ihalf=1,2 c-- filled = 1 halfi = -105 + (ihalf-1)*180 if (ihalf=2 & emcg_FillMode<3) filled = 0 c-- Create and Position EAGA AlphaZ=halfi c-- ENDDO c-- EndBlock c----------------------------------------------------------------- Block EAGA -- c-- Block EAGA IS HALF OF WHEEL AIR VOLUME FOR THE ENDCAP MODULE c-- c-- The eemc is divided into two halves. one half installed for 2003 run, c-- second half added for 2004 and beyond. the eaga block represents one c-- of these half-wheels. it is an air volume which will be filled in c-- with additional detector components. c-- c-- Creates: c-- + EMSS -- steel support block c-- + ECGH -- air gap between the two halves c-- C-- Material AIR Attribute EAGA seen=0 colo=1 serial=FILLED ! BLACK C-- Shape CONS dz=(emcs_zend-emcs_zorg)/2, rmn1=emcs_zorg*tan_low-d2 rmn2=emcs_zend*tan_low-d2, rmx1=emcs_zorg*tan_upp+dup rmx2=emcs_zend*tan_upp+dup, phi1=emcs_phimin phi2=emcs_phimax c-- c-- IF ( FILLED .EQ. 1 ) THEN c-- Create AND Position EMSS konly='MANY' c-- curr = emcs_zorg curcl = emcs_zend c-- Create AND Position ECGH alphaz=90 kOnly='ONLY' c-- ENDIF c-- EndBlock c----------------------------------------------------------------- Block EMSS -- c-- Block EMSS is the steel support of the endcap module c-- c-- Creates: c-- + EFLP -- ALUMINIUM FRONT PLATE c-- + ECVO -- VOLUMES TO CONTAIN RADIATORS AND MEGATILES c-- + ESHM -- SHOWER MAX DETECTOR VOLUME c-- + ESSP -- STAINLESS STEEL BACKPLATE c-- + ERCM -- STAINLESS STEEL TIE-RODS PENETRATING ECVO c-- c-- Material Steel c-- Attribute EMSS seen=1 colo=1 ! BLACK Shape CONS dz=(emcs_zend-emcs_zorg)/2, rmn1=emcs_zorg*tan_low-d2 rmn2=emcs_zend*tan_low-d2, rmx1=emcs_zorg*tan_upp+dup rmx2=emcs_zend*tan_upp+dup, phi1=emcs_phimin phi2=emcs_phimax c-- c-- Aluminium front plate C-- zslice = emcs_zorg zwidth = emcs_front c-- Prin1 zslice+zwidth/2 (' Front Al plate centered at: ', F12.4 ) c-- Create AND Position EFLP z=zslice-center+zwidth/2 zslice = zslice + zwidth C-- Prin1 zslice (' FIRST CALORIMETER STARTS AT: ',F12.4) c-- c-- Preshower 1, preshower 2, and calorimeter tiles up to c-- megatile number six. c-- fsect = 1 ! first section lsect = 3 ! last section c-- zwidth = emcs_smdcentr - emcs_gapsmd/2 - zslice ! width of current slice c-- Prin1 zslice+zwidth/2 ('Sections 1-3 positioned at: ', F12.4 ) c-- Create AND Position ECVO z=zslice-center+zwidth/2 c-- zwidth = emcs_gapsmd zslice = emcs_smdcentr - emcs_gapsmd/2 c-- Prin1 section, zslice (' 1st calorimeter ends, smd starts at: ',2f10.5) Prin1 zwidth (' smd width = ',f10.5 ) c-- Prin1 zslice+zwidth/2 ('SMD section centered at: ', F12.4 ) c-- Do not kill neighbors Create AND Position ESHM z=zslice-center+zwidth/2 kOnly='MANY' zslice = zslice + zwidth c-- Prin1 zslice (' SMD ends at: ',f10.5) c-- c-- fsect = 4 ! first section lsect = 5 ! last section c-- c-- Calculate the width of the last two calorimeter sections c-- zwidth = 0 DO i_section = fsect,lsect c-- USE ESEC isect=i_section zwidth = zwidth + esec_cell*esec_nlayer c-- ENDDO c-- c-- ============================================================= c-- c-- Total width will be between the back plate and the current c-- position... this effectively turns the geometry into an c-- accordian... whatever was defined earlier will compress c-- / expand this section. so correcting the smd gap will c-- result in some small, sub-mm shifts of radiators and c-- megatiles... one would like to actually place these c-- into their absolute positions. c-- c-- ============================================================== c-- zwidth = emcs_bckfrnt - zslice c-- Prin1 zslice+zwidth/2 ('Sections 4-5 positioned at: ', F12.4 ) c-- Create AND Position ECVO z=zslice-center+zwidth/2 c-- zslice = emcs_bckfrnt c-- Prin1 section,zslice (' 2nd calorimeter ends, back plate starts at: ',2f10.5) c-- zwidth = emcs_bckplate c-- Create AND Position ESSP z=zslice-center+zwidth/2 c-- zslice = zslice + zwidth c-- Prin1 zslice ('EEMC Al backplate ends at: ',F12.4 ) c-- c-- Done with the calorimeter stackup. now go back and cut through the c-- calorimeter stack with the tie rods c-- c-- slice width will be full calorimeter depth zwidth = emcs_zend-emcs_zorg c-- Create ERCM c-- DO i = 1,2 ! two tie rods along DO j = 1,5 ! each gap between sectors (5 gaps) xx = emcs_phimin + j*30 yy = xx*degrad xc = cos(yy)*emcs_tierod(i) yc = sin(yy)*emcs_tierod(i) Position ERCM z=0 x=xc y=yc ENDDO ENDDO c-- c-- Now add in projective steel bars which form part of the support c-- structure of the eemc c-- rth = emcs_zorg*tan_upp+dup + 2.5/2 xc = (emcs_zend - emcs_zorg)*tan_upp length = .5*(emcs_zend + emcs_zorg)*tan_upp + dup + 2.5/2 yc = emcs_zend-emcs_zorg p = atan(xc/yc)/degrad c-- Create EPSB DO i = 1,6 c-- xx = -75 + (i-1)*30 yy = xx*degrad xc = cos(yy)*length yc = sin(yy)*length c-- Position EPSB X=XC Y=YC ALPHAZ=XX c-- ENDDO c-- EndBlock c----------------------------------------------------------------- Block ECVO -- c-- Block ECVO is one of endcap volume with megatiles and radiators c-- c-- CreateS: c-- + EMOD -- Responsible for creating esec which, in a glorious example c-- of spaghetti code, turns around and creates esec, which is c-- responsible for creating the radiators before and after the c-- smd layers. C-- Material AIR Attribute ECVO seen=1 colo=3 ! GREEN Shape CONS dz=zwidth/2, rmn1=zslice*tan_low-dd, rmn2=(zslice+zwidth)*tan_low-dd, rmx1=zslice*tan_upp+dup, rmx2=(zslice+zwidth)*tan_upp+dup c-- c-- Loop over the SIX SECTORS in the current half-wheel. determine c-- whether the sector is filled or not, and create the "module". c-- By "module", we really mean endcap sector. (Lots of code in the c-- EEMC borrows from the barrel, and so barrel modlues get mapped c-- to EEMC sectors). c-- DO i_sector = 1,6 c-- IF (1 < I_SECTOR < 6 | EMCG_FILLMODE > 1) THEN filled = 1 ELSE filled = 0 ENDIF c-- d3 = 75 - (i_sector-1)*30 Create AND Position EMOD alphaz=d3 ncopy=i_sector c-- ENDDO c-- EndBlock c----------------------------------------------------------------- Block ESHM -- c-- Block ESHM is the shower max section c-- c-- CreateS: c-- + ESPL -- SHOWER MAXIMUM DETECTOR PLANES c-- + ERSM -- TIE RODS W/IN THE SHOWER MAXIMUM DETECTOR c-- Material AIR Attribute ESHM seen=1 colo=4 ! BLUE c-- Shape CONS dz=zwidth/2, rmn1=(zslice*tan_low)-dd, rmn2=(zslice+zwidth)*tan_low-dd, rmx1=(zslice)*tan_upp+dup, rmx2=(zslice+zwidth)*tan_upp+dup, phi1=emcs_phimin phi2=emcs_phimax c-- USE EMXG c-- maxcnt = emcs_smdcentr Prin1 zslice, section, center (' === z start for smd,section: ',3f12.4) c-- c-- Loop over the three possible locations for the smd planes and c-- create them. note that code w/in espl will decide which of c-- 5 types of smd planes are created... u, v, cutu,cutv or spacer. c-- DO j_section = 1,3 c-- USE EXSE jsect=j_section c-- current = exse_zshift secwid = emxg_sapex + 2.*emxg_f4 section = maxcnt + exse_zshift c-- Prin1 j_section,current,section,secwid (' layer, z, width : ',i3,3f12.4) c-- rbot=section*tan_low rtop=section*tan_upp c-- Prin1 j_section,rbot,rtop (' layer, rbot,rtop : ',i3,2f12.4) c-- Prin1 j_section, center+current (' smd layer=',I1,' z=',F12.4 ) c-- Do not kill neighbors Create and Position ESPL z=current kOnly='MANY' c-- ENDDO c-- c-- Add in the tie rods which penetrate the SMD layers c-- Create ERSM c-- DO i = 1,2 DO j = 1,5 xx = emcs_phimin + j*30 yy = xx*degrad xc = cos(yy)*emcs_tierod(i) yc = sin(yy)*emcs_tierod(i) Position ERSM Z=0 X=XC Y=YC END DO END DO C-- EndBlock c----------------------------------------------------------------- Block ECGH -- c-- Block ECGH is air gap between endcap half wheels c-- c-- Creates: c-- + ECHC -- THE STAINLESS STEEL COVER FOR 1/2 OF THE EEMC. c-- Material AIR Medium standard Attribute ECGH seen=0 colo=7 ! LIGHTBLUE Shape TRD1 dz=(emcs_zend-emcs_zorg)/2, dy =(emcs_gaphalf+emcs_cover)/2, dx1=emcs_zorg*tan_upp+dup, dx2=emcs_zend*tan_upp+dup c-- c-- rth = emcs_gaphalf + emcs_cover xx=curr*tan_low-d2 xleft = sqrt(xx*xx - rth*rth) yy=curr*tan_upp+dup xright = sqrt(yy*yy - rth*rth) secwid = yy - xx xx=curcl*tan_low-d2 yleft = sqrt(xx*xx - rth*rth) yy=curcl*tan_upp+dup yright = sqrt(yy*yy - rth*rth) zwidth = yy - xx xx=(xleft+xright)/2 yy=(yleft + yright)/2 xc = yy - xx length = (xx+yy)/2 yc = curcl - curr p = atan(xc/yc)/degrad rth = -(emcs_gaphalf + emcs_cover)/2 c-- Create ECHC c-- Position ECHC X=+LENGTH Y=RTH Position ECHC X=-LENGTH Y=RTH ALPHAZ=180 c-- EndBlock c----------------------------------------------------------------- Block ECHC -- c-- Block ECHC is steel endcap half cover c-- Material steel Attribute ECHC seen=1 colo=1 ! BLACK c-- Shape TRAP dz=(curcl-curr)/2, thet=p, bl1=secwid/2, tl1=secwid/2, bl2=zwidth/2, tl2=zwidth/2, h1=emcs_cover/2, h2=emcs_cover/2, phi=0, alp1=0, alp2=0 c-- EndBlock c----------------------------------------------------------------- Block ESSP -- c-- Block ESSP is stainless steel back plate c-- Material steel Attribute ESSP seen=1 colo=6 fill=1 Shape CONS dz=emcs_bckplate/2, rmn1=zslice*tan_low-dd, rmn2=(zslice+zwidth)*tan_low-dd, rmx1=zslice*tan_upp+dup, rmx2=(zslice+zwidth)*tan_upp+dup, phi1=emcs_phimin, phi2=emcs_phimax c-- EndBlock c----------------------------------------------------------------- Block EPSB -- c-- Block EPSB IS A PROJECTILE STAINLESS STEEL BAR C-- Material Steel Attribute EPSB seen=1 colo=6 FILL=1 Shape TRAP dz=(emcs_zend-emcs_zorg)/2, thet=p, bl1=2.5/2, tl1=2.5/2, bl2=2.5/2, tl2=2.5/2, h1=2.0/2, h2=2.0/2, phi=0, alp1=0, alp2=0 c-- c-- EndBlock c----------------------------------------------------------------- Block ERCM -- c-- Block ERCM is stainless steel tie rod in calorimeter sections c-- Material Steel Attribute ERSM seen=1 colo=6 FILL=1 c-- Shape TUBE dz=zwidth/2, rmin=0, rmax=emcs_rtie c-- c-- Looks like the tie rods are meant to engage the 1.525 cm diameter holes c-- piercing the ears of the smd spacer... 1.5 cm may be a better approximation c-- here. c-- c-- http://drupal.star.bnl.gov/star/system/files/smd_spacer_drawings.pdf c-- EndBlock c----------------------------------------------------------------- Block ERSM -- c-- Block ERSM is stainless steel tie rod in shower max c-- Material Steel Attribute ERSM seen=1 colo=6 FILL=1 c-- Shape TUBE dz=zwidth/2, rmin=0, rmax=emcs_rtie c-- c-- see comments above c-- EndBlock c----------------------------------------------------------------- Block EMOD -- c-- Block EMOD (fsect,lsect) IS ONE MODULE OF THE EM ENDCAP c-- c-- Arguements: (do be defined prior to the creation of this block) c-- c-- fsect -- first section to create c-- lsect -- last section to create c-- Attribute EMOD seen=1 colo=3 serial=FILLED ! GREEN Material Air Shape CONS dz=zwidth/2, phi1=emcs_phimin/emcs_nsupsec, phi2=emcs_phimax/emcs_nsupsec, rmn1=zslice*tan_low-dd, rmn2=(zslice+zwidth)*tan_low-dd, rmx1=zslice*tan_upp+dup, rmx2=(zslice+zwidth)*tan_upp+dup c-- c-- Running parameter 'section' contains the position of the current section c-- it should not be modified in daughters, use 'current' variable instead. c-- secwid is used in all 'cons' daughters to define dimensions. c-- section = zslice curr = zslice + zwidth/2 c-- c-- DO i_section = fsect, lsect USE ESEC isect=i_section c-- secwid = esec_cell*esec_nlayer c-- c-- Section 3 precedes the smd. section 5 is the post shower. in c-- both cases these sections end with a scintillator layer and no c-- radiator. c-- IF (I_SECTION = 3 | I_SECTION = 5) THEN secwid = secwid - radiator ELSE IF (I_SECTION = 4) THEN ! add one more radiator secwid = secwid - esec_cell + radiator ENDIF c-- Prin1 i_section, section-curr+secwid/2 ('+ ECVO isection=',I1,' zcenter=', F12.4) c-- Create AND Position ESEC z=section-curr+secwid/2 c-- section = section + secwid c-- ENDDO! Loop over sections c-- EndBlock c----------------------------------------------------------------- Block ESEC -- c-- Block ESEC is a single em section Material AIR Medium standard Attribute ESEC seen=1 colo=1 serial=filled lsty=2 c-- Shape CONS dz=secwid/2, rmn1=(section)*tan_low-dd, rmn2=(section+secwid)*tan_low-dd, rmx1=(section)*tan_upp+dup, rmx2=(section+secwid)*tan_upp+dup c-- length = -secwid/2 current = section c-- megatile = esec_scint+emcs_alincell+emcs_frplast+emcs_bkplast c-- gap = esec_cell - radiator - megatile Prin2 i_section,section (' ESEC:i_section,section',i3,f12.4) c-- c-- Loop over all layers in this section c-- DO is = 1,esec_nlayer c-- c-- Define actual cell thickness: cell = esec_cell plate = radiator c-- IF (is=nint(esec_nlayer) & (i_section = 3 | i_section = 5)) THEN c-- cell = megatile + gap plate=0 c-- ELSE IF (i_section = 4 & is = 1) THEN ! RADIATOR ONLY c-- cell = radiator c-- ENDIF c-- Prin2 i_section,is,length,cell,current (' esec:i_section,is,length,cell,current ',2i3,3f12.4) C-- C-- This handles the special case in the section after the smd. c-- this section begins with a lead radiator. the previous section c-- ended with a plastic scintillator c-- IF (i_section = 4 & is = 1) THEN ! radiator only c-- c$$$ cell = radiator + .14 cell = radiator + emcs_slop ! ^^^^ probably the fiber router layer... but is this needed here? c-- Prin1 is, current + cell/2+esec_deltaz ( ' + ESEC radiator ilayer=',I2,' z=',F12.4 ) Create AND Position ERAD z=length+(cell)/2+esec_deltaz c-- length = length + cell current = current + cell c-- c-- All other cases are standard radiator followed by scintillator c-- ELSE c-- cell = megatile IF (FILLED = 1) THEN c-- Create AND Position EMGT z=length+(gap+cell)/2+esec_deltaz c-- xx = current + (gap+cell)/2+esec_deltaz prin2 i_section,is,xx (' mega i_section,is ',2i3,f10.4) Prin1 is, xx (' + ESEC megatile ilayer=',I2,' z=',F12.4) c-- ENDIF c-- length = length + cell + gap current = current + cell + gap c-- IF (PLATE>0) THEN c-- cell = radiator Prin1 is, current + cell/2+esec_deltaz ( ' + ESEC radiator ilayer=',I2,' z=',F12.4 ) Create AND Position ERAD z=length+cell/2+esec_deltaz c-- length = length + cell current = current + cell c-- ENDIF c-- ENDIF c-- ENDDO c-- c-- EndBlock c----------------------------------------------------------------- Block EMGT -- c-- Block EMGT is a 30 degree megatile c-- Material Air Medium Standard Attribute EMGT seen=1 colo=1 lsty=2 c-- Shape CONS dz=megatile/2, rmn1=(current)*tan_low-dd, rmn2=(current+megatile)*tan_low-dd, rmx1=(current)*tan_upp+dup, rmx2=(current+megatile)*tan_upp+dup c-- c-- DO isec=1,nint(emcs_nslices) c-- myPhi = (emcs_nslices/2-isec+0.5)*dphi + esec_jiggle(is) c-- Create AND Position EPER alphaz=myPhi c-- END DO c-- EndBlock c----------------------------------------------------------------- Block EPER -- c-- Block EPER is a 5 degree slice of a 30 degree megatile (subsector) c-- c-- Creates: c-- + ETAR -- The pseudo-rapidity divivisions in the megatiles c-- Material Polystyren Attribute EPER seen=1 colo=1 lsty=1 c-- c-- c-- Shape CONS dz=megatile/2, phi1=emcs_phimin/emcs_nsector, phi2=emcs_phimax/emcs_nsector, rmn1=(current)*tan_low-dd, rmn2=(current+megatile)*tan_low-dd, rmx1=(current)*tan_upp+dup, rmx2=(current+megatile)*tan_upp+dup c-- curcl = current+megatile/2 DO ie = 1, nint(eetr_neta) c-- etabot = eetr_etabin(ie) etatop = eetr_etabin(ie+1) rbot=(curcl)*tanf(etabot) rtop=min((curcl)*tanf(etatop), ((current)*tan_upp+dup)) c-- check rbot<rtop c-- xx=tan(pi*emcs_phimax/180.0/emcs_nsector) yy=cos(pi*emcs_phimax/180.0/emcs_nsector) Create and Position ETAR x=(rbot+rtop)/2 ort=yzx prin2 ie,etatop,etabot,rbot,rtop (' EPER : ie,etatop,etabot,rbot,rtop ',i3,4f12.4) c-- ENDDO c-- EndBlock c----------------------------------------------------------------- Block ETAR -- c-- c-- ETAR is a single cell of scintillator, including fiber router, plastic, c-- etc... c-- c-- local z is radially outward in star c-- local y is the thickness of the layer c-- Block ETAR is a single calorimeter cell, containing scintillator, fiber router, etc... c-- Material POLYSTYREN Attribute ETAR seen=1 colo=4 lsty=1 ! BLUE c-- Shape TRD1 dy=megatile/2 dz=(rtop-rbot)/2, dx1=rbot*xx-emcs_gapcel/yy, dx2=rtop*xx-emcs_gapcel/yy c-- Create AND Position EALP y=(-megatile+emcs_alincell)/2 g10 = esec_scint Create AND Position ESCI y=(-megatile+g10)/2+emcs_alincell _ +emcs_frplast c-- EndBlock c----------------------------------------------------------------- Block ESCI -- c-- Block ESCI is the active scintillator (polystyrene) layer c-- c-- Obtain the definition of polystyrene on this line, next line clones Material Polystyren Material Ecal_scint isvol=1 Medium Ecal_active isvol=1 c-- Attribute ESCI seen=1 colo=7 fill=0 lsty=1 ! LIGHTBLUE c-- local z goes along the radius, y is the thickness Shape TRD1 dy=esec_scint/2, dz=(rtop-rbot)/2-emcs_gapcel c-- c-- Call ecal_set_cuts( ag_imed, 'detector' ) c-- c-- HITS ESCI BIRK:0:(0,10) c-- c-- EndBlock c----------------------------------------------------------------- Block ERAD -- c-- Block ERAD is the lead radiator with stainless steel cladding c-- c-- Creates: c-- + ELED -- the business end of the calorimeter... c-- Material STEEL c-- Attribute ERAD seen=1 colo=6 fill=1 lsty=1 ! VIOLET Shape CONS dz=radiator/2, rmn1=(current)*tan_low-dd, rmn2=(current+cell)*tan_low-dd, rmx1=(current)*tan_upp+dup, rmx2=(current+radiator)*tan_upp+dup c-- Create AND Position ELED c-- EndBlock c------------------------------------------------------------------------- c----------------------------------------------------------------- Block ELED -- c-- Block ELED is a lead absorber plate c-- c-- Material PbAlloy Medium Ecal_lead Attribute ELED seen=1 colo=4 fill=1 lsty=1 c-- Shape TUBS dz=emcs_pbplate/2, rmin=(current)*tan_low, rmax=(current+emcs_pbplate)*tan_upp, c-- Call ecal_set_cuts( ag_imed, 'radiator' ) c-- EndBlock c-- c----------------------------------------------------------------------------- c----------------------------------------------------------------- Block EFLP -- c-- Block EFLP is the aluminum (aluminium) front plate of the endcap c-- Material ALUMINIUM Attribute EFLP seen=1 colo=3 fill=1 lsty=1 ! GREEN Shape CONS dz=emcs_front/2, rmn1=68.813 rmn2=68.813, rmx1=(zslice)*tan_upp+dup, rmx2=(zslice+zwidth)*tan_upp+dup, phi1=emcs_phimin phi2=emcs_phimax c-- EndBlock c----------------------------------------------------------------------------- c----------------------------------------------------------------- Block EALP -- c-- Block EALP is the thin aluminium plate in calorimeter cell c-- c-- Material Aluminium Attribute EALP seen=1 colo=1 lsty=1 c-- c-- Shape TRD1 dy=emcs_alincell/2 dz=(rtop-rbot)/2 c-- c-- Thin aluminium plate in each calorimeter cell. The energy-loss c-- fluctuations are restricted in this thin material. c-- CALL GsTPar (AG_IMED,'CUTGAM',0.00001) CALL GsTPar (AG_IMED,'CUTELE',0.00001) CALL GsTPar (AG_IMED,'LOSS',1.) CALL GsTPar (AG_IMED,'STRA',1.) c-- EndBlock c----------------------------------------------------------------- Block ESPL -- c-- Block ESPL is the logical volume containing an SMD plane c-- Material Air Attribute ESPL seen=1 colo=4 lsty=4 Shape TUBS dz=emcs_gapsmd/3/2, rmin=section*tan_low-1.526, rmax=(section-secwid/2)*tan_upp+dup, phi1=emcs_phimin phi2=emcs_phimax c-- USE EMXG version=1 msecwd = (emxg_sapex+emxg_f4)/2 c-- ^^^^^^ what is this used for? --jw c-- looks like the g10 layer which we are retiring c-- c-- loop over the six sectors in an endcap half wheel c-- DO isec=1,6 cut=1 d3 = 75 - (isec-1)*30 c-- IF (exse_sectype(isec)=0|(emcg_fillmode=1&(isec=6|isec=1))) THEN cut = 0 c -- come back and build spacers -- ElseIF (exse_sectype(isec) = 1) then ! v c-- Create and Position EXSG alphaz=d3 ncopy=isec kOnly='MANY' c-- ElseIF (exse_sectype(isec) = 2) then ! u c-- Create and Position EXSG alphaz=d3 ort=x-y-z ncopy=isec kOnly='MANY' c-- ElseIF (exse_sectype(isec) = 3) then ! cut v c-- cut=2 Create and Position EXSG alphaz=d3 ncopy=isec kOnly='MANY' c-- ElseIF (exse_sectype(isec) = 4) then ! cut u c-- cut=2 Create and Position EXSG alphaz=d3 ort=x-y-z ncopy=isec kOnly='MANY' c-- EndIF c-- EndDO! loop over six sectors in eemc half wheel c-- c-- repeat the loop and add in the spacer layers c-- DO isec=1,6 d3=75 - (isec-1)*30 IF (exse_sectype(isec)=0|(emcg_fillmode=1&(isec=6|isec=1))) then cut = 0 c-- Do not kill neighbors Create and Position EXSG alphaz=d3 ncopy=isec kOnly='MANY' c ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ c potential side effect... may screw up the mapping c of the smd strips into the tables? c EndIF EndDO c-- EndBlock c----------------------------------------------------------------- Block EXSG -- c-- Block EXSG Is another logical volume... this one acutally creates the planes c-- c-- Creates: c-- + EHMS -- shower max strips c-- + EFLS -- front cover for SMD planes c-- + EBLS -- back cover for SMD planes c-- Attribute EXSG seen=1 colo=7 serial=cut lsty=3 ! MEH Material Air c$$$ Medium TMED_EXSG stemax=0.01 Shape TUBS dz=emcs_gapsmd/3/2, rmin=section*tan_low-1.526, rmax=(section-secwid/2)*tan_upp+dup, phi1=emcs_phimin/emcs_nsupsec-5, phi2=emcs_phimax/emcs_nsupsec+5 c-- rbot = emxg_rin rtop = emxg_rout c-- c-- Code to handle smd spacers c-- IF ( cut .eq. 0 ) THEN Create and Position EXPS kONLY='MANY' ENDIF c-- c-- Code to handle smd planes c-- IF (cut > 0) THEN c-- c-- setup which plane we are utilizing c-- IF (cut = 1) THEN nstr = 288 ELSE nstr = 285 ENDIF c-- c-- loop over all smd strips and place them w/in this smd plane c-- DO istrip = 1,nstr c-- Call ecal_get_strip( section, cut, istrip, xc, yc, length ) c-- IF (mod(istrip,2) != 0 ) THEN Create and Position EHMS x=xc y=yc alphaz=-45 kOnly='ONLY' Create and Position EBLS x=xc y=yc z=(+esmd_apex/2+esmd_back_layer/2) alphaz=-45 kOnly='ONLY' ELSE Create and Position EHMS x=xc y=yc alphaz=-45 ort=x-y-z kOnly='ONLY' Create and Position EFLS x=xc y=yc z=(-esmd_apex/2-esmd_front_layer/2) alphaz=-45 ort=x-y-z kOnly='ONLY' ENDIF c-- Prin1 istrip, xc, yc, length ( 'SMD Plane: strip=',I3,' xc=',F5.1,' yc=,'F5.1,' length=',F5.1 ) c-- ENDDO c-- ENDIF c-- c-- * dcut exsg z 0 0 10 0.1 0.1 * dcut exsg y 0 10 -50 0.7 0.7 c-- EndBlock c-- c-- c----------------------------------------------------------------------------- c----------------------------------------------------------------- Block EHMS -- c-- Block EHMS defines the triangular SMD strips c-- Material Ecal_scint Medium Ecal_active isvol=1 Attribute EHMS seen=1 colo=2 serial=cut lsty=1 ! red c-- Shape TRD1 dx1=0 dx2=emxg_Sbase/2 dy=length/2 dz=emxg_Sapex/2 c-- HITS EHMS Birk:0:(0,10) c-- Endblock! EHMS c----------------------------------------------------------------------------- c--- c-- Several thin layers of material are applied to the front and back of the c-- SMD planes to provide structural support. We combine these layers into c-- a single effective volume, which is affixed to the base of the SMD c-- strips. As with the SMD strips, z along the depth, y is length c-- c-- http://drupal.star.bnl.gov/STAR/system/files/SMD_module_stack.pdf c-- c-- 1.19 mm G10 c-- 0.25 mm Fiberglass and epoxy c-- 0.17 mm Aluminized mylar c-- c-- Weight in mixture by mass = (depth)*(Area) c-- c-- Weighted density is given by sum (density)_i * (depth)_i / sum (depth)_i c-- c----------------------------------------------------------------- Block EFLS -- c-- Block EFLS is the layer of material on the front of the SMD planes c-- c-- Component G10 A=18.017 Z=9.013 w=1.19*1.700/(1.19*1.700+0.25*1.530+0.17*1.390) Component Fiberglass A=19.103 Z=9.549 w=0.25*1.530/(1.19*1.700+0.25*1.530+0.17*1.390) Component AlMylar A=12.889 Z=6.465 w=0.17*1.390/(1.19*1.700+0.25*1.530+0.17*1.390) Mixture EFLS dens=(1.19*1.7+0.25*1.53+0.17*1.39)/(1.19+0.25+0.17) Attribute EFLS seen=1 colo=22 lsty=1 Shape TRD1 dz=esmd_front_layer/2 dy=length/2 dx1=esmd_base/2 dx2=esmd_base/2 c-- EndBlock! EFLS c-- c-- see link above for documentation c-- c-- 0.10 mm aluminized mylar c-- 0.25 mm fiberglass and epoxy c-- 1.50 mm WLS fiber router layer (polystyrene) c-- 0.25 mm aluminum c-- c----------------------------------------------------------------- Block EBLS -- c-- Block EBLS is the layer of material on the back of the SMD planes c-- Component AlMylar A=12.889 Z=6.465 w=0.10*1.390/(0.10*1.390+0.25*1.530+1.50*1.032+0.25*2.699) Component Fiberglass A=19.103 Z=9.549 w=0.25*1.530/(0.10*1.390+0.25*1.530+1.50*1.032+0.25*2.699) Component Polystyren A=11.154 Z=5.615 w=1.50*1.032/(0.10*1.390+0.25*1.530+1.50*1.032+0.25*2.699) Component Al A=28.08 Z=14.00 w=0.25*2.699/(0.10*1.390+0.25*1.530+1.50*1.032+0.25*2.699) Mixture EBLS dens=(0.10*1.390+0.25*1.530+1.50*1.032+0.25*2.699)/(0.10+0.25+1.50+0.25) c-- Attribute EFLS seen=1 colo=22 lsty=1 Shape TRD1 dz=esmd_back_layer/2 dy=length/2 dx1=esmd_base/2 dx2=esmd_base/2 c-- EndBlock! EFLS c----------------------------------------------------------------- Block EXPS -- c-- Block EXPS is the plastic spacer in the shower maximum section c-- c-- Simple implementation of the spacer in the shwoer maximum detector. c-- This implmentation neglects the ears and the source tube. c-- c-- n.b. There may be a side effect in the way this gets created... c-- it could overwrite SMD strips which extend into this plane. c-- Probably need to go with a different approach here. c-- c-- Scanned Drawings: c-- + http://drupal.star.bnl.gov/STAR/system/files/SMD_spacer_drawings.pdf c-- c-- thickness is 1.2 cm, as given by detail B and C... but I do not want c-- to do alot of complicated recoding of the geometry. So I am limiting c-- it to be the same width as a normal SMD volume. c-- Material PVC_Spacer Attribute EXPS seen=1 colo=6 lsty=1 lwid=2 c-- c-- Spacer layers are extended by +/- 5 degrees into the adjacent sectors. c-- The kONLY='Many' option at creation time should mean that conflicts c-- in volume will be resolved in favor of the SMD strips. c-- Shape TUBS dz=esmd_apex/2, rmin=(section)*Tan_Low-1.526, rmax=(section+msecwd)*Tan_Upp, phi1=emcs_PhiMin/emcs_Nsupsec, phi2=emcs_PhiMax/emcs_Nsupsec c-- EndBlock c-- END c----------------------------------------------------------------- End Module -- c------------------------------------------------------------------------------ c-- Helper subroutines and functions c------------------------------------------------------------------------------ c-- c-- Subroutine ecal_set_cuts(id, medium) c-- c-- id -- integer ID idetifying the current tracking medium c-- medium -- character switch selecting the type of cuts to be c-- used in this tracking volumne c-- c------------------------------------------------------------------------------ Subroutine ecal_set_cuts(id,medium) c-- Implicit NONE Integer id Character medium*(*) c-- Integer radiator, megatile, detector Save radiator, megatile, detector c-- IF ( medium == 'print' ) THEN c-- Write (*,400) radiator Write (*,401) megatile Write (*,402) detector c-- Call GpTMed( +radiator ) Call GpTMed( -megatile ) Call GpTMed( -detector ) c-- Return c-- ENDIF c-- 400 Format('radiator cuts set for ag_imed=',I3) 401 Format('megatile cuts set for ag_imed=',I3) 402 Format('detector cuts set for ag_imed=',I3) c-- c-- c-- Setup common cuts for neutrons, hadrons and muons c-- Call GsTPar (id,'CUTNEU',0.001) Call GsTPar (id,'CUTHAD',0.001) Call GsTPar (id,'CUTMUO',0.001) c-- IF ( medium == 'radiator' ) THEN Call GsTPar (id,'CUTGAM',0.00008) Call GsTPar (id,'CUTELE',0.001) Call GsTPar (id,'BCUTE' ,0.0001) radiator = id C-- c-- ELSEIF ( medium == 'megatile' ) THEN Call GsTPar (id,'CUTGAM',0.00008) Call GsTPar (id,'CUTELE',0.001) Call GsTPar (id,'BCUTE' ,0.0001) megatile = id c-- c-- ELSEIF ( medium == 'detector' ) THEN Call GsTPar (id,'CUTGAM',0.00008) Call GsTPar (id,'CUTELE',0.001) Call GsTPar (id,'BCUTE' ,0.0001) c-- Call GsTPar (id,'BIRK1',1.) Call GsTPar (id,'BIRK2',0.0130) Call GsTPar (id,'BIRK3',9.6E-6) detector = id c-- c-- ELSE Call GsTPar (id,'CUTGAM',0.00008) Call GsTPar (id,'CUTELE',0.001) Call GsTPar (id,'BCUTE' ,0.0001) Write(*,300) 300 Format('Warning: unknown medium[',A20,'] in ecal_set_cuts') c-- c-- ENDIF c-- Return End c----------------------------------------------------------------------- c----------------------------------------------------------------------- c-- c-- Subroutine ecal_get_strip( section, cut, istrip, xcenter, ycenter, length ) c-- in in in out out out Implicit NONE c-- Real section Integer cut ! 0=no plane 1=normal plane 2=cut plane Integer istrip ! strip index Real xcenter ! output Real ycenter ! output Real length ! output c-- Integer nstrips Real rdel ! shift in radius (?) Real rth Real ddn, ddup Real megatile, p c-- Real xleft, yleft, xright, yright Real dxy, xx, yy Real sqrt2, sqrt3 c-- c-- SMD data copied from data structures above c-- Real base, apex Data base, apex / 1.0, 0.7/ !cm c-- Real Rbot, Rtop Data Rbot, Rtop / 77.41, 213.922 / c-- Real EtaMin, EtaMax Data EtaMin, EtaMax / 1.086, 2.000 / c-- Real tan_theta_min, tan_theta_max c-- Real tanf, eta tanf(eta) = tan(2*atan(exp(-eta))) c-- tan_theta_min = tanf( EtaMax ) tan_theta_max = tanf( EtaMin ) c-- IF (cut = 1) THEN rdel = 3.938 nstrips = 288 ELSE rdel = -.475 nstrips = 285 ENDIF c-- xcenter=0. ycenter=0. length=0. c-- IF ( cut = 0 ) THEN RETURN ENDIF c-- sqrt2 = sqrt(2.0) sqrt3 = sqrt(3.0) c-- rth = .53*rdel ! .53 --- tentatavily jcw-- wtf? ddn = sqrt(3.0)*1.713 + rdel ddup = .5*1.846 + 1.713 megatile = base + .01 c-- p = .5*(istrip-1)*megatile + 41.3655 IF (p <= (.5*rbot*sqrt3 + rth)) THEN dxy = 1.9375*sqrt2 xleft = .5*sqrt2*p*(sqrt3 + 1.) - dxy yleft = .5*sqrt2*p*(sqrt3 - 1.) - dxy yright = .5*sqrt2*(sqrt( rbot*rbot - p*p) - p) xright = sqrt2*p + yright ELSEIF ((.5*rbot*sqrt3 + rth) < p <= (.5*rtop + 1.5)) THEN dxy = 1.9375*sqrt2 xleft = .5*sqrt2*p*(sqrt3 + 1.) - dxy yleft = .5*sqrt2*p*(sqrt3 - 1.) - dxy dxy = rdel*sqrt2/sqrt3 yright = .5*sqrt2*p*(1.- 1./sqrt3) xright = sqrt2*p - yright - dxy yright = -yright - dxy ELSEIF (p > (.5*rtop +1.5)) THEN yleft = (sqrt(rtop*rtop - p*p) - p)/sqrt2 xleft = sqrt2*p + yleft dxy = rdel*sqrt2/sqrt3 yright = .5*sqrt2*p*(1.- 1./sqrt3) xright = sqrt2*p - yright - dxy yright = -yright - dxy dxy = 0. c-- IF ((.5*sqrt3*160.- ddn) < p <= (.5*sqrt3*160.+ ddup) ) THEN xcenter = .5*(sqrt3*160.+1.846) ycenter = xcenter - .5*sqrt3*1.713 IF (p > ycenter) THEN dxy = .5*sqrt2*(2/sqrt3*rdel + .5*sqrt3*1.846 +_ sqrt(1.713*1.713 - (p-xcenter)*(p-xcenter))) ELSE dxy = sqrt2/sqrt3*(p - .5*sqrt3* 160. + ddn) ENDIF ELSEIF ((.5*sqrt3*195.- ddn) < p <= (.5*sqrt3*195. + ddup) ) THEN xcenter = .5*(sqrt3*195.+1.846) ycenter = xcenter - .5*sqrt3*1.713 IF (p > ycenter) THEN dxy = .5*sqrt2*(2/sqrt3*rdel + .5*sqrt3*1.846 +_ sqrt(1.713*1.713 - (p-xcenter)*(p-xcenter))) ELSE dxy = sqrt2/sqrt3*(p - .5*sqrt3*195. + ddn) ENDIF ENDIF xright = xright + dxy yright = yright + dxy ENDIF dxy = section*tan_theta_max - rtop xcenter = .5*(xright+xleft) + dxy ycenter = .5*(yright+yleft) xx = .5*sqrt2*(xleft+yleft) yy = .5*sqrt2*(xright+yright) length = xx-yy c-- c-- Return c-- End! Subroutine smd_strip c-- * ---------------------------------------------------------------------------- * ECAL nice views: dcut ecvo x 1 10 -5 .5 .1 * draw emdi 105 0 160 2 13 .2 .1 * draw emdi 120 180 150 1 14 .12 .12 * --------------------------------------------------------------------------- c-- examples of HITS * HITS EHMS Birk:0:(0,10) * xx:16:SH(-250,250) yy:16:(-250,250) zz:16:(-350,350), * px:16:(-100,100) py:16:(-100,100) pz:16:(-100,100), * Slen:16:(0,1.e4) Tof:16:(0,1.e-6) Step:16:(0,100), * none:16: Eloss:0:(0,10) *
Monte-Carlo setup:
Cuts for shower shapes:
Single particle kinematic cuts: pt=7-8GeV, eta=1.2-1.4
All shapes are normalized to 1 at peak (central strip)
Added layer definition from Jason file:
Some comments:
Figure 1: Sampling fraction vs. thrown energy
Figure 3: Sampling fraction vs. thrown energy (left), 2x1/3x3 energy ratio (right)
See legend for details
Figure 4: Shower shapes. See legend for details
Pre-shower bins:
Ep1/Ep2 is the energy deposited in the 1st/2nd EEMC pre-shower layer.
For a single particle MC it is a sum over
all pre-shower tiles in the EEMC with energy of 3 sigma above pedestal.
For eta-meson from pp2006 data the sum is over 3x3 tower patch
Monte-Carlo setup:
Added layer definition from Jason file:
Geometry configurations and notations (shown in the center of the plot):
cross section of 1st SMD plane labeled with "SUV" ordering
Note: u-v ordering scheme can be found here (Fig. 9-11)
Figure 1: Average number of SMD u-strip fired vs. thrown photon's (x,y)
Figure 2:Average number of SMD v-strip fired vs. thrown photon's (x,y)
Monte-Carlo setup:
Geometry configurations and notations (shown in the center of the plot):
Figure 2: Total energy distribution
Figure 3: Shower shapes (left) and shape ratios (right) for 0 < pre-shower1 < 4MeV
For the previous study click here
Monte-Carlo setup:
Geometry configurations and notations (shown in the center of the plot):
Figure 1: Average energy in SMD-u plane vs. position of the thrown photon
SMD v (left) and u (right) sampling fraction (E_smd/E_thrown) vs. E_thrown
Figure 2: Sampling fraction (E_tower^total/E_thrown) vs. position of the thrown photon
Sampling fraction (E_tower^total/E_thrown) vs. E_thrown
Figure 3: Number of towers above threshold vs. position of the thrown photon
Number of towers above threshold vs. E_thrown
Figure 4: (left) Pre-shower1 and (right) Pre-shower2 sampling fraction vs. E_thrown
Figure 5: (left) High tower sampling fraction and (right) residual energy, [E_tot-E_3x3]/E_thrown, vs. E_thrown
Monte-Carlo setup:
Geometry configurations and notations (shown in the center of the plot):
Figure 1: number of post-shower tiles
Figure 2: number of pre-1-shower tiles
Figure 3: number of pre-2-shower tiles
Figure 4: number of towers
Figure 5: Average pre-shower1 energy
Figure 6: Average pre-shower2 energy
Figure 7: Average number of SMD-u strips
Figure 8: Average number of SMD-v strips
Figure 9: Average post-shower energy
Figure 10: Sampling fraction 1x1 vs. thrown energy
Figure 11: Sampling fraction 2x1 vs. thrown energy
Figure 12: Sampling fraction 3x3 vs. thrown energy
Figure 13: Sampling fraction (total energy) vs. thrown energy
Figure 14: Sampling fraction 1x1
Figure 15: Sampling fraction 2x1
Figure 16: Sampling fraction 3x3
Monte-Carlo setup:
Geometry configurations and notations (shown in the center of the plot):
Figure 1: Average number of SMD-u strips
Figure 2: Average number of SMD-v strips
Figure 3: distribution of 1x1 sampling fraction
Figure 4: distribution of 2x1 sampling fraction
Figure 5: distribution of 3x3 sampling fraction
Figure 6: 1x1 sampling fraction vs. thrown energy
Monte-Carlo setup:
Geometry configurations and notations (shown in the center of the plot):
Figure 1: Sampling fraction 1x1
Figure 2: Sampling fraction 2x1
Figure 3: Sampling fraction 3x3
Figure 4: Sampling fraction total energy
Figure 5: Sampling fraction pre1-shower
Figure 6: Sampling fraction pre2-shower
Figure 7: Sampling fraction smd-u
Figure 8: Sampling fraction smd-v
Figure 9: Sampling fraction post-shower
Figure 10: Sampling fraction 1x1 vs. thrown energy
Figure 11: Sampling fraction 2x1 vs. thrown energy
Figure 12: Sampling fraction 3x3 vs. thrown energy
Figure 13: Sampling fraction (tatal energy) vs. thrown energy
FYI: Alice blog on ELED block study
Monte-Carlo setup:
Geometry configurations and notations (shown in the center of the plot):
Figure 1: Sampling fraction 1x1 (up-left), 2x1 (up-right), 3x3 (low-left), total energy (low-right)
Figure 2: Sampling fraction pre1 (up-left), pre2 (up-right), SMD-u (low-left), post (low-right)
Figure 3: Shower shapes (left) and shower shape ratio (right)
Monte-Carlo setup:
Geometry configurations and notations (shown in the center of the plot):
Figure 1: Distribution of the sampling fraction (total energy in EEMC)
Figure 2: Sampling fraction (total energy in EEMC) vs. thrown energy
Figure 3: Sampling fraction (total energy in EEMC) vs. position of the thrown photon
Monte-Carlo setup:
Geometry configurations and notations:
data base settings (same settings in bfc.C (Jan's trick) and in my MuDst reader):
dbMk->SetFlavor("sim","bemcPed");
dbMk->SetFlavor("Wbose","bemcCalib");
dbMk->SetFlavor("sim","bemcGain");
dbMk->SetFlavor("sim","bemcStatus");
dbMk->SetFlavor("sim","bprsPed");
dbMk->SetFlavor("Wbose","bprsCalib");
dbMk->SetFlavor("sim","bprsGain");
dbMk->SetFlavor("sim","bprsStatus");
dbMk->SetFlavor("sim","bsmdePed");
dbMk->SetFlavor("Wbose","bsmdeCalib");
dbMk->SetFlavor("sim","bsmdeGain");
dbMk->SetFlavor("sim","bsmdeStatus");
dbMk->SetFlavor("sim","bsmdpPed");
dbMk->SetFlavor("Wbose","bsmdpCalib");
dbMk->SetFlavor("sim","bsmdpGain");
dbMk->SetFlavor("sim","bsmdpStatus");
Note: for BEMC ideal pedSigma set to 0, so effectively
there is no effect when I apply 3-sigma threshold above pedestal.
Figure 1: E_reco/E_thrown distribution.
E_reco is the total energy in the BEMC towers from mMuDstMaker->muDst()->muEmcCollection()
E_thrown energy of the thrown photon from tne GEant record
No cut (yet) applied to exclude otliers in the average
Outliers in E_reco/E_thrown
Figure 2: Average E_reco/E_thrown vs. thrown photon eta (left) and phi (right)
Average is taken over a slice in eta or phi (no gaussian fits)
Figure 3: Average E_reco/E_thrown vs. thrown position (eta and phi)
Left: without LOW_EM option; right: with LOW_EM option
No cut applied to exclude otliers
Monte-Carlo setup:
Figure 1: Sampling fraction (total energy in EEMC)
Figure 2: Sampling fraction (total energy in EEMC)
black: same black as in Fig. 1, upper plots
red: EEMC geometry with Material PbAlloy isvol=0
(modification suggested by Jason in this post)
Monte-Carlo setup:
Geometry configurations
Figure 1: Tower sampling fraction distribution
Figure 2: Tower sampling fraction vs. thrown energy
Figure 3: Tower sampling fraction vs. position of the thrown photon
Figure 4: Pre1, pre2, post and SMD sampling fraction distribution
Figure 5: Pre1, pre2, post and SMD sampling fraction vs. thrown energy
Figure 6: SMD-v shower shapes
Figure 7: SMD-v shower shape ratios
Figure 8: Number of SMD-u strips
Figure 9: Number of SMD-v strips
Figure 10: Energy ractio of 2x1 to 3x3 cluster vs. gamma-jet data
Figure 11: Pre-shower1 energy
Figure 12: Pre-shower2 energy
Figure 13: Post-shower energy
Figure 14: SMD-v energy
Figure 15: Number of towers
Figure 16: Tower Sampling fraction: LOW_EM option and pre-shower migration
Monte-Carlo setup:
Geometry configurations and notations:
data base settings (same settings in bfc.C (Jan's trick) and in my MuDst reader):
dbMk->SetFlavor("sim","bemcPed");
dbMk->SetFlavor("Wbose","bemcCalib");
dbMk->SetFlavor("sim","bemcGain");
dbMk->SetFlavor("sim","bemcStatus");
Note: for BEMC ideal pedSigma set to 0, so effectively
there is no effect when I apply 3-sigma threshold above pedestal.
Figure 1: Sampling fraction (0.07*E_reco/E_thrown) distribution: average vs. gaussian fit
E_reco is the total energy in the BEMC towers from mMuDstMaker->muDst()->muEmcCollection()
E_thrown energy of the thrown photon from tne GEant record
The difference between fit and using average values is < 0.7%
Figure 2: Otliers vs. eta and phi: (left) no energy reconstrycted, (right) s.f. < 55%
Most outlier are at eta = 0, -1, +1
Figure 3: Sampling fraction (0.07*E_reco/E_thrown) distribution
Effect of LOW_EM cuts
Figure 4: Sampling fraction vs. thrown photon eta (left) and phi (right)
Average is taken over a slice in eta or phi with cut on outliers (events with s.f. < 5.5% rejected)
Figure 5: Sampling fraction vs. thrown position (eta and phi)
Average is taken over a slice in eta or phi with cut on outliers (events with s.f. < 5.5% rejected)
Figure 6: (left) Single tower sampling fraction
and (right) energy ratio of 1x1 cluster to the total BEMC energy
Not much of the effect from LOW_EM cuts on the 1x1 clustering. Need to look at other (2x1, 2x2 clusters)
Monte-Carlo setup:
Geometry configurations
Figure 1: Sampling fraction of various EEMC layers vs. thrown photon energy:
(a) tower s.f.; (b) tower s.f. distribution; (c) pre-shower1; (d) pre-shower2; (e) SMD, (f) post-shower
Figure 2: (left) Shower shapes and (right) shower shape ratios
Monte-Carlo setup:
Geometry configurations
Monte-Carlo setup:
data base settings (same settings in bfc.C (Jan's trick) and in my MuDst reader):
dbMk->SetFlavor("sim","bemcPed");
dbMk->SetFlavor("Wbose","bemcCalib");
dbMk->SetFlavor("sim","bemcGain");
dbMk->SetFlavor("sim","bemcStatus");
Note: for BEMC ideal pedSigma set to 0, so effectively
there is no effect when I apply 3-sigma threshold above pedestal.
Figure 1: Rapidity cuts study (no eta cuts, no cuts on otliers in this figure)
Figure 2: Sampling fraction (0.07*E_reco/E_thrown) distribution
E_reco is the total energy in the BEMC towers from mMuDstMaker->muDst()->muEmcCollection()
E_thrown energy of the thrown photon from tne Geant record
Cuts: |eta| < 0.97 && |eta|>0.01 && s.f. > 0.055
s.f. distribution on the log scale
Monte-Carlo setup:
Geometry configurations
Figure 1: (left) time/event distribution, (right) average time for the particle type
Conclusion: for single particle Monte-Carlo required time in starsim
with LOW_EM option is ~ 2.6 times higher.
Monte-Carlo setup:
Geometry configurations
Figure 1: EEMC sampling fraction (left) distribution (right) vs. thrown photon energy (1.2 < eta < 1.9; no pt cuts)
Figure 2: EEMC sampling fraction (left) distribution (right) vs. thrown photon energy (1.2 < eta < 1.9; pt > 7GeV cut)
Figure 5: Shower shape ratios (v plane)
Figure 6: Shower shape ratios (u plane)
Figure 7: Pre-shower migration (1.2 < eta < 1.9; no pt cuts)
Monte-Carlo setup:
data base settings (same settings in bfc.C (Jan's trick) and in my MuDst reader):
dbMk->SetFlavor("sim","bemcPed");
dbMk->SetFlavor("Wbose","bemcCalib");
dbMk->SetFlavor("sim","bemcGain");
dbMk->SetFlavor("sim","bemcStatus");
Note: for BEMC ideal pedSigma set to 0, so effectively
there is no effect when I apply 3-sigma threshold above pedestal.
Figure 1: Energy sampling of various cluster in the Barrel EMC
E_reco is the total energy in the BEMC towers from mMuDstMaker->muDst()->muEmcCollection()
eta_thrown - rapidity of the thrown photon from the Geant record
Cuts: |eta| < 0.97 && |eta|>0.01 && total energy s.f. > 0.055
Figure 2: Various cluster energy ratios
Conclusions/dicsussion at the emc2 hypernew
http://www.star.bnl.gov/HyperNews-star/get/emc2/3369.html
http://www.star.bnl.gov/HyperNews-star/get/emc2/3375.html
NoCuts: Default STAR geometry EM cuts
Endcap EMC setup is quite non-uniform
(all cuts are set via "Call GSTPAR (ag_imed,'CutName', Value)":
CUTGAM = 0.00001
CUTELE = 0.00001
CUTGAM = 0.00008
CUTELE = 0.001
BCUTE = 0.0001
CUTNEU = 0.001
CUTHAD = 0.001
CUTMUO = 0.001
c-- Define Birks law parameters
BIRK1 = 1.
BIRK2 = 0.013
BIRK3 = 9.6E-6
CUTGAM = 0.00008
CUTELE = 0.001
BCUTE = 0.0001
CUTNEU = 0.001
CUTHAD = 0.001
CUTMUO = 0.001
CUTGAM = 0.00001
CUTELE = 0.00001
LOSS = 1.
STRA = 1.
CUTGAM = 0.00008
CUTELE = 0.001
BCUTE = 0.0001
c-- Define Birks law parameters
BIRK1 = 1.
BIRK2 = 0.0130
BIRK3 = 9.6E-6
CUTGAM = 0.0001
CUTELE = 0.0001
BCUTE = 0.0001
BCUTM = 0.0001
DCUTE = 0.0001
DCUTM = 0.0001
CUTGAM = 0.00001
CUTELE = 0.00001
BCUTE = 0.00001
BCUTM = 0.00001
DCUTE = 0.0001
DCUTM = 0.00001
CUTGAM = 0.00001
CUTELE = 0.00001
BCUTE = 0.00001
BCUTM = 0.00001
DCUTE = 0.00001
DCUTM = 0.00001
Figure 1: Endcap EMC sampling fraction for different cluster sizes:
1x1, 2x1, 3x3, and total energy in the EEMC
Lower right plot shows total s.f. vs. photon thrown energy
Conclusions/dicsussion at the emc2 hypernew:
http://www.star.bnl.gov/HyperNews-star/get/emc2/3374.html
List of LOW_EM cuts and defaults
Pythia QCD Monte-Carlo:
Figure 1: QCD Total (GEANT/GSTAR+bfc) timing (seconds/event)
Figure 2: QCD GEANT/GSTAR timing (seconds/event)
Figure 3: QCD bfc.C timing (seconds/event)
EEMC single photons Monte-Carlo
Figure 4: EEMC single photon Total (GEANT/GSTAR+bfc) timing (seconds/event)
Figure 5: EEMC single photon GEANT/GSTAR timing (seconds/event)
Figure 1: (left) Endcap EMC sampling fraction (total calorimeter energy), (right) SMD-u sampling fraction
Red: (previous) ecalgeo-v6.1 with global LOW_EM option
(Note: same points as in this post, Fig. 1 lower left, label y6:LOW_EM)
Black: (new) ecalgeo-v6.2 (embedded LOW_EM cuts), no global LOW_EM option
Figure 2: Pre-shower migrations
There is only a few events with pre1>4MeV with new simulations: potential problem with TPC geometry?
Results: Update for the previous tests of EMC v6.2 geometry after fixing TPC/EEMC overlap
Figure 1: Endcap EMC sampling fraction: total calorimeter energy, pre1-, pre2-, post- shower layers, and SMD-u energy
Red: (previous) ecalgeo-v6.1 with global LOW_EM option
(Note: same points as in this post, Fig. 1 lower left, label y6:LOW_EM)
Black: (new) ecalgeo-v6.2 (embedded LOW_EM cuts), no global LOW_EM option
Figure 2: Pre-shower migrations
Change in TPC geometry seems to introduce a reasonable (small) change in pre-shower migration
* Update version of the previous simulation
request from December 18, 2008 (see Ref. [1])
Understanding effects of trigger, material budget differences,
and throughout comparison between 2006 and 2009 data
requires to have dedicated Monte-Carlo
data samples with both y2006 and y2009 geometries.
We request to produce the following set of
Monte-Carlo samples for the photon-jet analysis:
Dedicated (gamma filtered, Refs. [2-5]) data sample
for Pythia pp@200GeV prompt photon processes
with y2006 STAR geometry configuration
and partonic pt range 2-25GeV.
Simulations configured with:
LOW_EM option in starsim (Ref. [6]).
Low cuts on electromagnetic processes in GSTAR
y2006h geometry tag, which includes
latest Endcap EMC (v6.1) and TPC (v4) geometry fixes.
Pythia 6.4 CDF Tune A or Perugia tunes (6.4.22)?
Dedicated (gamma filtered, Refs. [2-5]) data sample
for Pythia pp@200GeV hard QCD processes
with y2006 STAR geometry configuration
and partonic pt range 2-25GeV.
Same simulation setup as for the sample S1.
Pythia pp@200GeV prompt photon and hard QCD
processes with y2009 STAR geometry configuration
and partonic pt range 2-25GeV.
Same simulation setup as for the sample S1
but with y2009a geometry tag.
S4: 3rd priority
Pythia pp@500GeV prompt photon and hard QCD
processes with y2009 STAR geometry configuration
and partonic pt range 2-25GeV.
Same simulation setup as for the sample S1
but with y2009a geometry tag.
Below I provide some estimates of CPU and disk space
which are required to produce the data samples listed above.
These estimates are based on the previous (private)
production of the MC gamma-filtered events with y2006
geometry which was done at MIT computer cluster
by Michael Betancourt (Ref. [2,4-5]):
Pythia pp@200GeV prompt photon simulations
with ~7 pb^-1 luminosity:
~60 days running time on a single CPU
~17Gb of disk space to store MuDst/geant files
Number of (filtered) events:
~ 30K for pt range 6-9GeV
~ 15K for pt range 9-15GeV
Pythia pp@200 QCD hard process simulations
with (at least) 1 pb^-1 luminosity:
~ 620 days running on a single CPU
(less than a week on a cluster with 100 CPUs)
~ 150Gb of disk space to store MuDst/geant files
Number of (filtered) events:
~ 650K for pt range 6-9GeV
~ 300K for pt range 9-15GeV
Notes on the estimates:
Enabling LOW_EM option in GSTAR increases
the time estimates by ~40% (Ref. [7]).
Additional production of jet trees will
require a disk space on the order of < 2%
of the total size of the MuDst/geant files.
Additional production of gamma trees will also
require a disk space on the order of a few percents
of the total size of the MuDst/geant files.
Previous simulation request (Date: 2008, Dec 18):
http://www.star.bnl.gov/HyperNews-star/protected/get/starspin/3596.html
Michael's document on
"Targeted MC procedure for the gamma-jet program at STAR":
http://drupal.star.bnl.gov/STAR/system/files/20080729_gammaFilter_by_MichaelBetancourt.pdf
simulations with filtering readiness:
http://www.star.bnl.gov/HyperNews-star/protected/get/starsimu/387/1/1/2/1/1/2/3/1.html
Filtered photon production with y2006 geometry:
http://www.star.bnl.gov/HyperNews-star/protected/get/phana/256.html
More details on statistics needed and disk space estimates:
http://www.star.bnl.gov/HyperNews-star/protected/get/phana/297.html
LOW_EM option in GSTAR:
http://www.star.bnl.gov/HyperNews-star/protected/get/phana/371.html
Time estimates with and without LOW_EM option:
Geometry configurations:
Note: results are with CVS before "15Deg rotated volume" bug being fixed
Figure 1:Pre-shower migration: y2006h (red - CVS:2009/12/17) vs. y2006h (black - CVS:2009/12/29)
Figure 2: Pre-shower migration: y2006h (red) vs. y2009a (black) all with CVS:2009/12/29
Geometry configurations:
STAR geometry includes the latest "15Deg rotated volume" bug bug fix
Figure 1: EEMC sampling fraction
(left) vs. thrown photon energy (with 1.2 < eta < 1.9 cut)
(right) vs. thrown photon eta
Figure 3: Shower shapes (u plane)
Figure 4: Shower shape ratios (u plane)
Figure 5: Pre-shower migration (1.2 < eta < 1.9)
Figure 6: Average pre-shower1 energy vs. thown photon position in EEMC
(left) y2009a with emc_10KeV
(right) y2006h with emc_10KeV
Click here for results before phi cuts
Geometry configurations:
Figure 1: Average pre-shower1 energy vs. thown photon position in EEMC
with cuts on TPC sector boundaries: cos(12*(phi-Pi/6.)) < -0.65 (similar plot before phi cuts)
(left) y2009a with emc_10KeV
(right) y2006h with emc_10KeV
Figure 2: Pre-shower 1 sampling fraction (E_pre1/E_thrown) vs. thrown eta
Figure 3: EEMC sampling fraction
(left) vs. thrown photon energy (with 1.2 < eta < 1.9 cut)
(right) vs. thrown photon eta
All plost from second (with vertex distribution) test W-sample from Lidia/Jason.
generated files are from /star/rcf/test/Wprod_test2/
The previous sample with fixed (zero) vertex can be found was announced here:
http://www.star.bnl.gov/HyperNews-star/protected/get/starsimu/435.html
Figure 1: Electron from W decay (a) eta, (b) phi, (c) pt and (d) energy distributions
from geant record (no kinematic cuts)
Figure 2: Reconstructed vs. geant vertex (Cuts: abs(geant_eta_electron) < 1)
(left) difference, (right) ratio
Figure 3:
(left) Correlation between thrown and reconsructed energy: abs(geant_eta_electron) < 1
(right) ratio of the reconsructed to thrown energy (Bemc_Etow > 25)
Reconstructed energy is the total energy in all Barrel towers
The follwoing DB tables are used to read MuDst (dbMk->SetDateTime(20090325,0)):
StEmcSimulatorMaker:INFO - loaded a new bemcPed table with beginTime 2009-03-24 22:16:13 and endTime 2009-03-26 06:03:44
StEmcSimulatorMaker:INFO - loaded a new bemcStatus table with beginTime 2009-03-24 02:16:58 and endTime 2009-03-26 04:07:02
StEmcSimulatorMaker:INFO - loaded a new bemcCalib table with beginTime 2008-12-15 00:00:02 and endTime 2037-12-31 12:00:00
StEmcSimulatorMaker:INFO - loaded a new bemcGain table with beginTime 1999-01-01 00:08:00 and endTime 2037-12-31 12:00:00
StEmcSimulatorMaker:INFO - loaded a new bprsPed table with beginTime 2008-03-04 10:30:56 and endTime 2037-12-31 12:00:00
StEmcSimulatorMaker:INFO - loaded a new bprsStatus table with beginTime 2008-12-15 00:00:00 and endTime 2037-12-31 12:00:00
StEmcSimulatorMaker:INFO - loaded a new bprsCalib table with beginTime 1999-01-01 00:10:00 and endTime 2037-12-31 12:00:00
StEmcSimulatorMaker:INFO - loaded a new bprsGain table with beginTime 1999-01-01 00:08:00 and endTime 2037-12-31 12:00:00
StEmcSimulatorMaker:INFO - loaded a new bsmdePed table with beginTime 2009-03-24 15:42:29 and endTime 2009-03-25 11:24:55
StEmcSimulatorMaker:INFO - loaded a new bsmdeStatus table with beginTime 2009-03-24 15:42:29 and endTime 2009-03-25 11:24:55
StEmcSimulatorMaker:INFO - loaded a new bsmdeCalib table with beginTime 2002-11-14 00:01:00 and endTime 2037-12-31 12:00:00
StEmcSimulatorMaker:INFO - loaded a new bsmdeGain table with beginTime 1999-01-01 00:08:00 and endTime 2037-12-31 12:00:00
StEmcSimulatorMaker:INFO - loaded a new bsmdpPed table with beginTime 2009-03-24 15:42:29 and endTime 2009-03-25 11:24:55
StEmcSimulatorMaker:INFO - loaded a new bsmdpStatus table with beginTime 2009-03-24 15:42:29 and endTime 2009-03-25 11:24:55
StEmcSimulatorMaker:INFO - loaded a new bsmdpCalib table with beginTime 2002-11-14 00:01:00 and endTime 2037-12-31 12:00:00
StEmcSimulatorMaker:INFO - loaded a new bsmdpGain table with beginTime 1999-01-01 00:08:00 and endTime 2037-12-31 12:00:00
StEmcSimulatorMaker:INFO - loaded a new bemcTriggerStatus table with beginTime 2009-03-23 07:50:04 and endTime 2009-04-01 18:10:03
StEmcSimulatorMaker:INFO - loaded a new bemcTriggerPed table with beginTime 2009-03-20 04:11:43 and endTime 2009-03-30 20:00:05
StEmcSimulatorMaker:INFO - loaded a new bemcTriggerLUT table with beginTime 2009-03-23 07:50:04 and endTime 2009-04-03 22:08:11
http://drupal.star.bnl.gov/STAR/node/16704
QA of the test W-sample from Lidia/Jason.
generated MuDst are from /star/simu/jwebb/01-11-2010-w-test-production/
QA plots for the previous pass can be found here
Two channels being analyzed:
Cuts: |geant_eta_lepton| < 1
Discussions can be found here:
http://www.star.bnl.gov/HyperNews-star/protected/get/starsimu/440.html
Figure 1: (left) Reconstructed vertex z distribution
(right) reconstructed minus geant z-vertex
Figure 2: E2x2/E_geant energy ratio
Black: positron from W+, mean value= 0.972973;
Red - electron from W- mean value = 0.969773
Figure 3: E1x1/E_geant (highest tower) energy ratio
Black: positron from W+, mean value= 0.815287;
Red - electron from W- mean value = 0.812098
Figure 4: Lepton E2x2/E_geant energy ratio
Parameter | black: positron from W+ | red: electron from W- |
gaus-Constant | 1.60709e+01 , err=3.08565e+00 | 1.56834e+01 , err=4.71967e+00 |
gaus-Mean | 9.85514e-01 , err=4.94309e-03 | 9.86118e-01 , err=5.43577e-03 |
gaus-Sigma | 3.15205e-02 , err=3.73952e-03 | 2.52009e-02 , err=6.57793e-03 |
Hist-Mean | 0.972973 | 0.969773 |
Figure 5: Lepton E3x3/E_geant energy ratio
Parameter | black: positron from W+ | red: electron from W- |
gaus-Constant | 1.48719e+01 , err=2.82186e+00 | 1.35741e+01 , err=3.36776e+00 |
gaus-Mean | 9.89924e-01 , err=5.72959e-03 | 9.83056e-01 , err=6.28736e-03 |
gaus-Sigma | 3.37758e-02 , err=4.24983e-03 | 3.00597e-02 , err=6.06841e-03 |
Hist-Mean | 0.975662 | 0.974163 |
QA of the test W-sample from Lidia/Jason.
generated MuDst are from /star/data08/users/starreco/recowtest/
QA plots for the previous pass 2 can be found here
QA plots for the previous pass 1 can be found here
Two channels being analyzed:
Cuts: |geant_eta_lepton| < 1
Discussions can be found here:
http://www.star.bnl.gov/HyperNews-star/protected/get/starsimu/443.html
Figure 1: Reconstructed minus geant z-vertex
Figure 2: Lepton E2x2/E_geant energy ratio
Parameter | black: positron from W+ | red: electron from W- |
gaus-Constant | 6.24023e+01 , err=3.46979e+00 | 4.73536e+01 , err=3.16029e+00 |
gaus-Mean | 9.79982e-01 , err=1.69854e-03 | 9.79787e-01 , err=1.68813e-03 |
gaus-Sigma | 3.52892e-02 , err=1.40963e-03 | 3.15336e-02 , err=1.40759e-03 |
Hist-Mean | 0.972122 | 0.975073 |
Figure 3: Lepton E3x3/E_geant energy ratio
Parameter | black: positron from W+ | red: electron from W- |
gaus-Constant | 6.33596e+01 , err=3.58862e+00 | 4.72335e+01 , err=3.19552e+00 |
gaus-Mean | 9.83287e-01 , err=1.72276e-03 | 9.83632e-01 , err=1.67661e-03 |
gaus-Sigma | 3.45514e-02 , err=1.48019e-03 | 3.05224e-02 , err=1.38944e-03 |
Hist-Mean | 0.974372 | 0.977858 |
Click here for previous study before TPC typo fix
Geometry configurations:
Figure 1: Pre-shower migration (1.2 < eta < 1.9)
Geometry configurations:
Figure 2: Pre-shower migration (1.2 < eta < 1.9): y2006h vs. y2009a
W test sample from Lidia/Jason. MuDst's from /star/data08/users/starreco/recowtest/
Two channels being analyzed:
Figure 1: Lepton yield vs. rapidity (no cuts)
Figure 2: Lepton yield vs. pt and energy
(left) no rapidity cuts
(right) |lepton_eta| < 1
All plots below with |lepton_eta| < 1
Skewed gaussian fits: [const]*exp(-0.5*((x-[mean])/([sigma]*(1+[skewness]*(x-[mean]))))**2)
Figure 3: Lepton E1x1/E_geant energy ratio
Simulations: official pp 500GeV pythia W production
Two channels being analyzed:
Figure 1: Lepton yield vs. energy
Figure 2: Lepton (left) E1x1/E_thrown and (right) E2x2/E_thrown energy ratio
Skewed gaussian fits: [const]*exp(-0.5*((x-[mean])/([sigma]*(1+[skewness]*(x-[mean]))))**2)
Figure 3: Endcap EMC lepton E3x3/E_thrown energy ratio
Figure 4: Endcap 2x2 sampling fraction (s.f.) vs. thrown lepton (left) energy and (right) eta
S.f. is defined as an average E_2x2/E_thrown for E_2x2/E_thrown>0.8
Figure 5: Endcap 3x3 sampling fraction (s.f.) vs. thrown lepton (left) energy and (right) eta
S.f. is defined as an average E_3x3/E_thrown for E_3x3/E_thrown>0.8
Figure 6: Lepton yield vs. energy
Figure 7: Lepton (left) E1x1/E_thrown and (right) E2x2/E_thrown energy ratio
Figure 8: Barrel EMC lepton E3x3/E_thrown energy ratio
Figure 9: Barrel 2x2 s.f. vs. thrown lepton (left) energy and (right) eta
S.f. is defined as an average E_2x2/E_thrown for E_2x2/E_thrown>0.8
Figure 10: Barrel 3x3 s.f. vs. thrown lepton (left) energy and (right) eta
S.f. is defined as an average E_3x3/E_thrown for E_3x3/E_thrown>0.8
Pythia gamma-jet | Pythia QCD 2->2 processes |
14 f + fbar -> g + gamma | 11 f + f' -> f + f' (QCD) |
18 f + fbar -> gamma + gamma | 12 f + fbar -> f' + fbar' |
29 f + g -> f + gamma | 13 f + fbar -> g + g |
114 g + g -> gamma + gamma | 28 f + g -> f + g |
115 g + g -> g + gamma | 53 g + g -> f + fbar |
68 g + g -> g + g |
Number of generated events (100events/job) |
||||||
Parton pt range (GeV) | 2-3 | 3-4 | 4-6 | 6-9 | 9-15 | 15-25 |
Pythia gamma-jet | 50K | 50K | 50K | 50K | 50K | 50K |
Pythia QCD 2->2 processes | 100K | 100K | 50K | 50K | 50K | 50K |
Filter parameter | Value | Notes |
mConeRadius | 0.24 | |
mSeedThreshold | 2.5 | Cluster seed energy threshold |
mClusterThreshold | 3.7 | Cluster Et threshold |
mEtaLow | 0.9 | EEMC acceptance |
mEtaHigh | 2.1 | EEMC acceptance |
mSmearEnergy | 0 | Disabled |
mThrowTracks | 0 | Disabled |
mCalDepth | 279.5 | ZDC SMD depth |
mMinPartEnergy | 1e-05 | Disabled by mThrowTracks=0 |
mHadronScale | 0.4 | Downscale factor for hadron energy |
mFilterMode | 0 | Accepting all events |
Figure 1: Pythia Eemc gamma filter QA:
(left) False rejection, (right) fraction of accepted events
QCD and gamma-jet data samples are described here
Pythia filter configuration
StEemcGammaFilter:: running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events
StEemcGammaFilter:: mConeRadius 0.22 mSeedThreshold 2.1 mClusterThreshold 3.25 mEtaLow 0.95 mEtaHigh 2.1
StEemcGammaFilter:: mCalDepth 279.5 mMinPartEnergy 1e-05 mHadronScale 0.4 mFilterMode 0 mPrintLevel 0
BFC filter configuration
StChain:INFO - Init() : Seed energy threshold = 2.8 GeV
StChain:INFO - Init() : Cluster eT threshold = 4.2 GeV
StChain:INFO - Init() : Maximum vertex = +/- 120 cm
StChain:INFO - Init() : Running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events in BFC
Figure 1: Fraction of accepted events
Figure 2: False rejection (Y-axis scale is 10^-3)
Figure 3: Fraction of accepted events (relative to triggered events)
Click here for discussion and results with spread=0.05/gain=0.95
QCD and gamma-jet data samples are described here
Resultys without gain shift can be found here
(Note: ignore parton pt=25-35GeV for the gamma-jet sample since all jobs failed)
StEemcGammaFilter:: running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events
StEemcGammaFilter:: mConeRadius 0.22 mSeedThreshold 2.1 mClusterThreshold 3.25 mEtaLow 0.95 mEtaHigh 2.1
StEemcGammaFilter:: mCalDepth 279.5 mMinPartEnergy 1e-05 mHadronScale 0.4 mFilterMode 0 mPrintLevel 0
StChain:INFO - Init() : Seed energy threshold = 2.8 GeV
StChain:INFO - Init() : Cluster eT threshold = 4.2 GeV
StChain:INFO - Init() : Maximum vertex = +/- 120 cm
StChain:INFO - Init() : Running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events in BFC
Figure 1: Fraction of accepted events
Accept rate: fract. of generated events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.0023 | 0.06264 | 0.00148 |
pt=3-4 | 0.0242285 | 0.250601 | 0.0126854 |
pt=4-6 | 0.103111 | 0.427535 | 0.0571313 |
pt=6-9 | 0.16828 | 0.48368 | 0.13918 |
pt=9-15 | 0.1692 | 0.50118 | 0.1619 |
pt=15-25 | 0.12708 | 0.42904 | 0.11786 |
pt=25-35 | 0.05702 | 0.24854 | 0.0509 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 3.003e-05 | 0.00426426 | 2.002e-05 |
pt=3-4 | 0.0001001 | 0.0122923 | 1.001e-05 |
pt=4-6 | 0.00078 | 0.03166 | 0.00014 |
pt=6-9 | 0.00622 | 0.10538 | 0.00216 |
pt=9-15 | 0.02822 | 0.27666 | 0.01022 |
pt=15-25 | 0.07568 | 0.4405 | 0.03086 |
pt=25-35 | 0.0761 | 0.35556 | 0.04116 |
Figure 2: False rejection (Y-axis scale is 10^-3)
False reject: fract. of generated events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 2e-05 | 0 | 0 |
pt=3-4 | 2.00401e-05 | 0 | 0 |
pt=4-6 | 8.08081e-05 | 0 | 0 |
pt=6-9 | 6e-05 | 4e-05 | 0 |
pt=9-15 | 0.0002 | 0.00018 | 0 |
pt=15-25 | 0.0001 | 4e-05 | 0 |
pt=25-35 | 0.00018 | 2e-05 | 0 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0 | 0 | 0 |
pt=3-4 | 0 | 0 | 0 |
pt=4-6 | 0 | 0 | 0 |
pt=6-9 | 4e-05 | 6e-05 | 0 |
pt=9-15 | 4e-05 | 0.00026 | 0 |
pt=15-25 | 0.00016 | 0.00018 | 0 |
pt=25-35 | 4e-05 | 4e-05 | 0 |
Figure 3: Fraction of accepted events (relative to triggered events)
Figure 4: False rejection relative to triggered events
Figure 5: Fraction of accepted events relative to Pythia filter accepted events
Accept rate: fract. of Pythia-filtered events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.0363985 | 1 | 0.0220307 |
pt=3-4 | 0.0966813 | 1 | 0.0501399 |
pt=4-6 | 0.241081 | 1 | 0.133488 |
pt=6-9 | 0.347461 | 1 | 0.287587 |
pt=9-15 | 0.336286 | 1 | 0.322639 |
pt=15-25 | 0.29573 | 1 | 0.274613 |
pt=25-35 | 0.228776 | 1 | 0.204635 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.00704225 | 1 | 0.00234742 |
pt=3-4 | 0.00488599 | 1 | 0.000814332 |
pt=4-6 | 0.0214782 | 1 | 0.00442198 |
pt=6-9 | 0.053141 | 1 | 0.0191687 |
pt=9-15 | 0.0965806 | 1 | 0.0356394 |
pt=15-25 | 0.16958 | 1 | 0.0695573 |
pt=25-35 | 0.213185 | 1 | 0.115592 |
Figure 6: False rejection relative to Pythia filter accepted events
False reject: fract. of Pythia-filtered events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.000319285 | 0 | 0 |
pt=3-4 | 7.9968e-05 | 0 | 0 |
pt=4-6 | 0.000189009 | 0 | 0 |
pt=6-9 | 0.000124049 | 0 | 0 |
pt=9-15 | 0.000399058 | 0 | 0 |
pt=15-25 | 0.000233079 | 0 | 0 |
pt=25-35 | 0.000724229 | 0 | 0 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0 | 0 | 0 |
pt=3-4 | 0 | 0 | 0 |
pt=4-6 | 0 | 0 | 0 |
pt=6-9 | 0.000379579 | 0 | 0 |
pt=9-15 | 0.000144582 | 0 | 0 |
pt=15-25 | 0.000363224 | 0 | 0 |
pt=25-35 | 0.000112499 | 0 | 0 |
QCD and gamma-jet data samples are described here
Resultys without gain spread can be found here
(Note: ignore parton pt=25-35GeV for the gamma-jet sample since all jobs failed)
void StEEmcSlowMaker::setTowerGainSpread(Float_t s, Float_t mTowerGainMean)
{
LOG_INFO << "setTowerGainSpread(): gain spread: " << s << "; gain mean value: " << mTowerGainMean << endm;
// initialize tower gain factors to 1
for ( Int_t sec=0;sec<kEEmcNumSectors;sec++ )
for ( Int_t sub=0;sub<kEEmcNumSubSectors;sub++ )
for ( Int_t eta=0;eta<kEEmcNumEtas;eta++ )
{
// mTowerGainFact[sec][sub][eta]=1.0;
Float_t f = -1.0E9;
while ( f <= -1. || f >= 1.0 )
f = gRandom->Gaus(0., s);
mTowerGainFact[sec][sub][eta] = mTowerGainMean + f;
}
}
StEemcGammaFilter:: running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events
StEemcGammaFilter:: mConeRadius 0.22 mSeedThreshold 2.1 mClusterThreshold 3.25 mEtaLow 0.95 mEtaHigh 2.1
StEemcGammaFilter:: mCalDepth 279.5 mMinPartEnergy 1e-05 mHadronScale 0.4 mFilterMode 0 mPrintLevel 0
StChain:INFO - Init() : Seed energy threshold = 2.8 GeV
StChain:INFO - Init() : Cluster eT threshold = 4.2 GeV
StChain:INFO - Init() : Maximum vertex = +/- 120 cm
StChain:INFO - Init() : Running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events in BFC
Figure 1: Fraction of accepted events
Figure 2: False rejection (Y-axis scale is 10^-3)
Figure 3: Fraction of accepted events (relative to triggered events)
Prompt photons (gamma-jets) | 2->2 QCD | ||
id | Process | id | Process |
14 | f + fbar -> g + gamma | 11 | f + f' -> f + f' (QCD) |
18 | f + fbar -> gamma + gamma | 12 | f + fbar -> f' + fbar' |
29 | f + g -> f + gamma | 13 | f + fbar -> g + g |
114 | g + g -> gamma + gamma | 28 | f + g -> f + g |
115 | g + g -> g + gamma | 53 | g + g -> f + fbar |
68 | g + g -> g + g |
Number of generated events (100events/job) |
|||||||
Parton pt range (GeV) | 2-3 | 3-4 | 4-6 | 6-9 | 9-15 | 15-25 | 25-35 |
gamma-jets | 50K | 50K | 50K | 50K | 50K | 50K | 50K |
2->2 QCD processes | 100K | 100K | 50K | 50K | 50K | 50K | 50K |
StRoot/StMCFilter/StEemcGammaFilter.cxx
StRoot/StMCFilter/StEemcGammaFilter.h
Filter parameter | Value | Notes |
mConeRadius | 0.22 | |
mSeedThreshold | 2.6 | Cluster seed energy threshold (GeV) |
mClusterThreshold | 3.6 | Cluster Et threshold (GeV) |
mEtaLow | 0.95 | EEMC acceptance |
mEtaHigh | 2.1 | EEMC acceptance |
mMaxVertex | 120.0 | Vertex z cut (cm) |
mCalDepth | 279.5 | EEMC SMD depth (cm) |
mMinPartEnergy | 1e-05 | Ignore track with minim energy (GeV) |
mHadronScale | 0.4 | Downscale factor for hadron energy |
mFilterMode | 0 / 1 | 0=Accept all events; 1=reject events |
StRoot/StFilterMaker/StEemcGammaFilterMaker.cxx
StRoot/StFilterMaker/StEemcGammaFilterMaker.h
Filter parameter | Value | Notes |
mSeedEnergyThreshold | 3.4 | Cluter seed energy threshold (GeV) |
mClusterEtThreshold | 4.5 | Cluster Et threshold (GeV) |
mEemcSamplingFraction | 0.05 | Assume 5% sampling fraction for EEMC |
mMaxVertex | 120.0 | Vertex z cut (cm) |
mFilterMode | 0 / 1 | 0=Accept all events; 1=reject events |
Filter parameter | Value | Notes |
ConeRadius | 0.7 | |
ClusterEtThreshold | 5.5 | (GeV) |
SeedEnergyThreshold | 4.2 | (GeV) |
ClusterEnergyThreshold | 5.5 | (GeV) |
(for a moment private version) of StEEmcSlowMaker.cxx
with modified setTowerGainSpread(Float_t s, Float_t mTowerGainMean)
Filter parameter | Value | Notes |
mTowerGainMean | 1.05 | Overall +5% gain shift |
GainSpread | 0 | No gain spread |
QCD and gamma-jet data samples and filter configurtions are given here
Note: for this study I have used ideal EEMC gains (no gain shift/spread)
Note on trigger effect intepretation:
There is no requirement for the Pythia gamma-jet sample to have direct gamma
headed to the EEMC, only requirement is to have a gamma candidate in the EEMC,
so the away side jet may also contribute.
Figure 1: pt distribution of the gamma candidates
for Pythia/Bfc level filter and triggered events
Event cuts: at least one gamma candidate, |v_z| <120
Left: Pythia gamma-jet MC; (right) 2->2 Pythia QCD
Lower plots: fraction of accepted gamma candidates by filter/trigger
No parton pt weights (= ignore bumps in pt distribution for gamma-jet sample)
Figure 2: Rapidity distribution of the gamma candidates (Same conditions as in Fig. 1)
Figure 3: pt distribution of false rejection for Pythia/Bfc filters
Candidate cuts: at least one gamma candidate, l2gamm-trigger=fired, |v_z| <120
Most of false rejection (~ 1-3% for QCD) is for gamma candidates with pt < 8GeV
Request last updated on Jul 21, 2010
Total resources estimate for QCD with 1/pb and prompt-photon with 10/pb suimulations:
partonic pt |
QCD |
prompt photon |
2-3 | 0 | 30K |
3-4 | 0 | 36K |
4-6 | 130K | 76K |
6-9 | 240K | 40K |
9-15 | 150K | 10K |
15-35 | 23K | 1K |
Note: These and all other studies are linked from here
StEemcGammaFilterMaker.cxx
StEemcGammaFilterMaker.h
eemcGammaFilterMakerParams.idl
Original disk space estimate (see spreadsheed linked above for the latest estimates):
http://www.star.bnl.gov/HyperNews-star/protected/get/starspin/3982.html
------------------------ REQUEST DRAFT BELOW ----------------------------------------
Event generator | Pythia |
Extra options |
Additional libraries required for Eemc-gamma Pythia-level filter gexec $ROOTSYS/lib/libCint.so Select prompt photon Pythhia processes: MSUB (14)=1 Select QCD 2->2 Pythhia processes: MSUB (11) = 1 Perugia0 Pythia tune: |
Vertex Z, cm | -120 < Vertex < 120 |
Gaussian sigma in X,Y,Z if applicable |
x/y spread use 0 |
Vertex offset: x, mm | Run 6: 0.0cm Run 9: 0.3cm (note: values in cm) |
Vertex offset: y, mm | Run 6: -0.3cm (note: values in cm) Run 9: 0.0cm |
Φ (phi), radian | 0 < Φ < 6.29 |
η (eta) | Default (include Barrel, Endcap, BBC) |
Pt bin, GeV | See list above for QCD and g-jet samples |
Macro file | Pythia gamma-filter code:
StEemcGammaFilter.cxx StEemcGammaFilterMaker.cxx Private bfc: /star/u/seluzhen/star/spin/MCgammaFilter/scripts/bfc.C |
See this post from Alice for QCD sample rates
QCD and gamma-jet data samples are described here (filter parameters are listed below)
StEemcGammaFilter:: running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events
StEemcGammaFilter:: mConeRadius 0.22 mSeedThreshold 2.6 mClusterThreshold 3.6 mEtaLow 0.95 mEtaHigh 2.1 mMaxVertex 120
StEemcGammaFilter:: mCalDepth 279.5 mMinPartEnergy 1e-05 mHadronScale 1 mFilterMode 0 mPrintLevel 1
StChain:INFO - Init() : Using gamma filter on the EEMC
StChain:INFO - Init() : EEMC Sampling Fraction = 0.05
StChain:INFO - Init() : Seed energy threshold = 3.4 GeV
StChain:INFO - Init() : Cluster eT threshold = 4.5 GeV
StChain:INFO - Init() : Maximum vertex = +/- 120 cm
StChain:INFO - Init() : Running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events in BFC
BFC:INFO - setTowerGainSpread(): gain spread: 0; gain mean value: 1.1
Figure 1: Fraction of accepted events
Accept rate: fract. of generated events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.00646 | 0.09532 | 0.00656 |
pt=3-4 | 0.03042 | 0.2401 | 0.02772 |
pt=4-6 | 0.09438 | 0.42552 | 0.07568 |
pt=6-9 | 0.165984 | 0.54004 | 0.149137 |
pt=9-15 | 0.167329 | 0.559137 | 0.162972 |
pt=15-25 | 0.12486 | 0.45662 | 0.11744 |
pt=25-35 | 0.0562525 | 0.269499 | 0.0536273 |
Figure 2: False rejection (Y-axis scale is 10^-3)
False reject: fract. of generated events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 6e-05 | 0 | 0 |
pt=3-4 | 0.00016 | 6e-05 | 0 |
pt=4-6 | 0.0003 | 8e-05 | 0 |
pt=6-9 | 0.000261044 | 6.0241e-05 | 0 |
pt=9-15 | 0.000220884 | 6.0241e-05 | 0 |
pt=15-25 | 0.00028 | 0.00012 | 0 |
pt=25-35 | 0.000280561 | 0.000140281 | 0 |
Figure 3: Fraction of accepted events relative to Pythia filter accepted events
Accept rate: fract. of Pythia-filtered events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.0677717 | 1 | 0.0612673 |
pt=3-4 | 0.126697 | 1 | 0.105623 |
pt=4-6 | 0.221799 | 1 | 0.16991 |
pt=6-9 | 0.307318 | 1 | 0.26809 |
pt=9-15 | 0.299264 | 1 | 0.281882 |
pt=15-25 | 0.273444 | 1 | 0.244317 |
pt=25-35 | 0.20873 | 1 | 0.181217 |
Figure 4: False rejection relative to Pythia filter accepted events
False reject: fract. of Pythia-filtered events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.000629459 | 0 | 0 |
pt=3-4 | 0.000416493 | 0 | 0 |
pt=4-6 | 0.000517014 | 0 | 0 |
pt=6-9 | 0.00037183 | 0 | 0 |
pt=9-15 | 0.000287305 | 0 | 0 |
pt=15-25 | 0.000350401 | 0 | 0 |
pt=25-35 | 0.000520524 | 0 | 0 |
See this post from Alice for QCD sample rates with slightly lower thresholds
QCD and gamma-jet data samples are described here (filter parameters are listed below)
StEemcGammaFilter:: running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events
StEemcGammaFilter:: mConeRadius 0.22 mSeedThreshold 2.4 mClusterThreshold 3.3 mEtaLow 0.95 mEtaHigh 2.1 mMaxVertex 120
StEemcGammaFilter:: mCalDepth 279.5 mMinPartEnergy 1e-05 mHadronScale 1 mFilterMode 0 mPrintLevel 1
StChain:INFO - Init() : Using gamma filter on the EEMC
StChain:INFO - Init() : EEMC Sampling Fraction = 0.05
StChain:INFO - Init() : Seed energy threshold = 2.8 GeV
StChain:INFO - Init() : Cluster eT threshold = 3.8 GeV
StChain:INFO - Init() : Maximum vertex = +/- 120 cm
StChain:INFO - Init() : Running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events in BFC
BFC:INFO - setTowerGainSpread(): gain spread: 0; gain mean value: 1.1
Figure 1: Fraction of accepted events
Accept rate: fract. of generated events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.01732 | 0.1343 | 0.00628 |
pt=3-4 | 0.05818 | 0.3001 | 0.0261 |
pt=4-6 | 0.1317 | 0.46492 | 0.07864 |
pt=6-9 | 0.17804 | 0.56314 | 0.15092 |
pt=9-15 | 0.17226 | 0.57516 | 0.15964 |
pt=15-25 | 0.13356 | 0.46894 | 0.1179 |
pt=25-35 | 0.062 | 0.28546 | 0.05482 |
Figure 2: False rejection (Y-axis scale is 10^-3)
False reject: fract. of generated events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 2e-05 | 2e-05 | 0 |
pt=3-4 | 6e-05 | 6e-05 | 0 |
pt=4-6 | 6e-05 | 4e-05 | 0 |
pt=6-9 | 0.0001 | 6e-05 | 0 |
pt=9-15 | 2e-05 | 2e-05 | 0 |
pt=15-25 | 2e-05 | 0 | 0 |
pt=25-35 | 2e-05 | 2e-05 | 0 |
Figure 3: Fraction of accepted events relative to Pythia filter accepted events
Accept rate: fract. of Pythia-filtered events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.128816 | 1 | 0.0415488 |
pt=3-4 | 0.193735 | 1 | 0.0808397 |
pt=4-6 | 0.283232 | 1 | 0.161877 |
pt=6-9 | 0.316049 | 1 | 0.260291 |
pt=9-15 | 0.29943 | 1 | 0.26876 |
pt=15-25 | 0.284813 | 1 | 0.240415 |
pt=25-35 | 0.217053 | 1 | 0.175156 |
Figure 4: False rejection relative to Pythia filter accepted events
False reject: fract. of Pythia-filtered events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0 | 0 | 0 |
pt=3-4 | 0 | 0 | 0 |
pt=4-6 | 4.30182e-05 | 0 | 0 |
pt=6-9 | 7.10303e-05 | 0 | 0 |
pt=9-15 | 0 | 0 | 0 |
pt=15-25 | 4.26494e-05 | 0 | 0 |
pt=25-35 | 0 | 0 | 0 |
Data sample used:
Pythia prompt photon Monte-Carlo (partonic pt bins are combined without weights)
Common event cuts:
reconstruct at least one gamma candidate, |v_z| <120, !=0 l2e-gamma-trigger=fired
Figure 1:
Figure 2: Same as Fig. 1 vs. gamma candidate energy
Figure 3: Same as Fig. 1 vs. gamma candidate pseudo-rapidity
Related inks:
Number of generated events per partnic pt bin:
gamma-jet: 25K
QCD(2-4): 50K
QCD(4-55): 25K
StEemcGammaFilter:: running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events
StEemcGammaFilter:: mConeRadius 0.22 mSeedThreshold 3.8 mClusterThreshold 5 mEtaLow 0.95 mEtaHigh 2.1 mMaxVertex 120
StEemcGammaFilter:: mCalDepth 279.5 mMinPartEnergy 1e-05 mHadronScale 1 mFilterMode 0 mPrintLevel 1
StChain:INFO - Init() : Using gamma filter on the EEMC
StChain:INFO - Init() : EEMC Sampling Fraction = 0.05
StChain:INFO - Init() : Seed energy threshold = 3.8 GeV
StChain:INFO - Init() : Cluster eT threshold = 5 GeV
StChain:INFO - Init() : Maximum vertex = +/- 120 cm
StChain:INFO - Init() : Running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events in BFC
BFC:INFO - setTowerGainSpread(): gain spread: 0; gain mean value: 1.1
runSimuGammaTreeMaker():: GammaMaker config: ConeRadius 0.7 ClusterEtThreshold 5.5 SeedEnergyThreshold 4.2 ClusterEnergyThreshold 5.5 BsmdRange 0.05237 EsmdR ange 20
StEEmcA2EMaker *EEanalysis = new StEEmcA2EMaker("mEEanalysis");
EEanalysis->threshold(3.0, 0); // tower threshold (ped+N sigma)
EEanalysis->threshold(3.0, 1); // pre1 threshold
EEanalysis->threshold(3.0, 2); // pre2 threshold
EEanalysis->threshold(3.0, 3); // post threshold
EEanalysis->threshold(3.0, 4); // smdu threshold
EEanalysis->threshold(3.0, 5); // smdv threshold
emulate L2E-gamma trigger for Run 2006 [eemc-http-mb-l2gamma:: id 137641]
Trigger conditions:
cluster Et (2x2) = 5.2GeV
seed Et = 3.7GeV
Figure 1: Fraction of accepted events
Accept rate: fract. of generated events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.00288 | 0.01472 | 0.00616 |
pt=3-4 | 0.01504 | 0.06192 | 0.02576 |
pt=4-6 | 0.06824 | 0.22112 | 0.07548 |
pt=6-9 | 0.15848 | 0.45836 | 0.15016 |
pt=9-15 | 0.1584 | 0.50416 | 0.15812 |
pt=15-25 | 0.12112 | 0.42076 | 0.11916 |
pt=25-55 | 0.05356 | 0.2292 | 0.0538 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 2e-05 | 0.00258 | 6e-05 |
pt=3-4 | 6e-05 | 0.00854 | 0.00022 |
pt=4-6 | 0.00072 | 0.03492 | 0.00076 |
pt=6-9 | 0.00564 | 0.144 | 0.00496 |
pt=9-15 | 0.0242 | 0.36036 | 0.0186 |
pt=15-25 | 0.07368 | 0.47592 | 0.05008 |
pt=25-55 | 0.0684553 | 0.323374 | 0.0557724 |
Figure 2: False rejection (Y-axis scale is 10^-3)
False reject: fract. of generated events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.0002 | 0.00012 | 0 |
pt=3-4 | 0.0002 | 0.00056 | 0 |
pt=4-6 | 0.00096 | 0.00132 | 0 |
pt=6-9 | 0.0006 | 0.00032 | 0 |
pt=9-15 | 0.0002 | 4e-05 | 0 |
pt=15-25 | 4e-05 | 0 | 0 |
pt=25-55 | 8e-05 | 8e-05 | 0 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0 | 0 | 0 |
pt=3-4 | 0 | 0 | 0 |
pt=4-6 | 0 | 0 | 0 |
pt=6-9 | 0.00012 | 0 | 0 |
pt=9-15 | 8e-05 | 8e-05 | 0 |
pt=15-25 | 0.00016 | 4e-05 | 0 |
pt=25-55 | 0.000203252 | 0 | 0 |
Figure 3: Fraction of accepted events relative to Pythia filter accepted events
Accept rate: fract. of Pythia-filtered events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.17663 | 1 | 0.171196 |
pt=3-4 | 0.215762 | 1 | 0.197028 |
pt=4-6 | 0.291787 | 1 | 0.259407 |
pt=6-9 | 0.344096 | 1 | 0.313814 |
pt=9-15 | 0.314107 | 1 | 0.301254 |
pt=15-25 | 0.28786 | 1 | 0.269798 |
pt=25-55 | 0.233333 | 1 | 0.211693 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.00775194 | 1 | 0 |
pt=3-4 | 0.00702576 | 1 | 0.00936768 |
pt=4-6 | 0.0183276 | 1 | 0.0160367 |
pt=6-9 | 0.0386111 | 1 | 0.0294444 |
pt=9-15 | 0.0667111 | 1 | 0.048618 |
pt=15-25 | 0.154816 | 1 | 0.102706 |
pt=25-55 | 0.211691 | 1 | 0.163545 |
Figure 4: False rejection relative to Pythia filter accepted events
False reject: fract. of Pythia-filtered events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.0108696 | 0 | 0 |
pt=3-4 | 0.00258398 | 0 | 0 |
pt=4-6 | 0.00325615 | 0 | 0 |
pt=6-9 | 0.00113448 | 0 | 0 |
pt=9-15 | 0.00031736 | 0 | 0 |
pt=15-25 | 9.50661e-05 | 0 | 0 |
pt=25-55 | 0.00017452 | 0 | 0 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0 | 0 | 0 |
pt=3-4 | 0 | 0 | 0 |
pt=4-6 | 0 | 0 | 0 |
pt=6-9 | 0.000833333 | 0 | 0 |
pt=9-15 | 0.000222 | 0 | 0 |
pt=15-25 | 0.000252143 | 0 | 0 |
pt=25-55 | 0.000628536 | 0 | 0 |
Figure 5: False rejection relative to trigger accepted events
False reject: fract. of triggered events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.623377 | 0.558442 | 0 |
pt=3-4 | 0.517081 | 0.464286 | 0 |
pt=4-6 | 0.240594 | 0.192369 | 0 |
pt=6-9 | 0.0348961 | 0.0167821 | 0 |
pt=9-15 | 0.0111308 | 0.00151783 | 0 |
pt=15-25 | 0.00872776 | 0.00134273 | 0 |
pt=25-55 | 0.00966543 | 0.00148699 | 0 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.333333 | 0.333333 | 0 |
pt=3-4 | 0.363636 | 0.181818 | 0 |
pt=4-6 | 0.631579 | 0.263158 | 0 |
pt=6-9 | 0.282258 | 0.0887097 | 0 |
pt=9-15 | 0.202151 | 0.0301075 | 0 |
pt=15-25 | 0.0686901 | 0.000798722 | 0 |
pt=25-55 | 0.0291545 | 0.000728863 | 0 |
Related inks:
Number of generated events per partnic pt bin:
gamma-jet: 25K
QCD(2-4): 50K
QCD(4-55): 25K
StEemcGammaFilter:: running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events
StEemcGammaFilter:: mConeRadius 0.22 mSeedThreshold 3.8 mClusterThreshold 5 mEtaLow 0.95 mEtaHigh 2.1 mMaxVertex 120
StEemcGammaFilter:: mCalDepth 279.5 mMinPartEnergy 1e-05 mHadronScale 1 mFilterMode 0 mPrintLevel 1
StChain:INFO - Init() : Using gamma filter on the EEMC
StChain:INFO - Init() : EEMC Sampling Fraction = 0.05
StChain:INFO - Init() : Seed energy threshold = 3.8 GeV
StChain:INFO - Init() : Cluster eT threshold = 5 GeV
StChain:INFO - Init() : Maximum vertex = +/- 120 cm
StChain:INFO - Init() : Running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events in BFC
BFC:INFO - setTowerGainSpread(): gain spread: 0; gain mean value: 1.1
runSimuGammaTreeMaker():: GammaMaker config: ConeRadius 0.7 ClusterEtThreshold 5.5 SeedEnergyThreshold 4.2 ClusterEnergyThreshold 5.5 BsmdRange 0.05237 EsmdR ange 20
StEEmcA2EMaker *EEanalysis = new StEEmcA2EMaker("mEEanalysis");
EEanalysis->threshold(3.0, 0); // tower threshold (ped+N sigma)
EEanalysis->threshold(3.0, 1); // pre1 threshold
EEanalysis->threshold(3.0, 2); // pre2 threshold
EEanalysis->threshold(3.0, 3); // post threshold
EEanalysis->threshold(3.0, 4); // smdu threshold
EEanalysis->threshold(3.0, 5); // smdv threshold
emulate L2E-gamma trigger for Run 2006 [eemc-http-mb-l2gamma:: id 137641]
Trigger conditions:
cluster Et (2x2) = 5.2GeV
seed Et = 3.7GeV
Definition: offline selected events are events which satisfy to the following conditions:
Figure 1a:
(upper plots) Gamma candidate yields vs. candidate pt (all partonic pt bins, no pt weights)
(lower plots) False rejection: histograms in the upper panel scaled by L2E-gamma-trigger yield (blue histogram)
Figure 1b: Same ad Fig. 1a with zoom into low pt region
Figure 2: Same ad Fig. 1b for partonic pt=2-3
Figure 3: Same ad Fig. 1b for partonic pt=3-4
Figure 4: Same ad Fig. 1b for partonic pt=4-6
Figure 5: Same ad Fig. 1b for partonic pt=6-9
Figure 6: Same ad Fig. 1b for partonic pt=9-15
Related inks:
Figure 1: BFC filter processing time for accepted events
Note an extra peaks around 23/33/43 seconds for the QCD sample
(they also present but less pronounced in gamma-jet sample)
I found that these are processing times needed for the first accepted by filter events
(not always the time for the first processed event and depends on filter acceptance rate).
Processing is much longer due to time needed to initiaize additional stuff in bfc makers
and it is ignored in the total cpu time estimate
Figure 1b:
1st row: starsim time per partonic pt bin
2nd row: bfc time for accepted events per partonic pt bin
3rd row: bfc time for rejected events per partonic pt bin
Average starsim/bfc timing (ignoring times in Fig. 1 with more that 18 seconds):
Gamma-jets bfc:acc starsim bfc:rej
pt=25-55 6.49765 20.2376 0.139911
pt=15-25 4.04562 11.8268 0.095903
pt=9-15 4.84475 11.4816 0.112344
pt=6-9 6.19909 13.0528 0.143109
pt=4-6 4.86546 9.8856 0.114983
pt=3-4 5.07415 10.404 0.12363
pt=2-3 4.04254 9.04627 0.0995413
QCD bfc:acc starsim bfc:rej
pt=25-55 6.18626 14.9944 0.13752
pt=15-25 6.20077 12.9668 0.126722
pt=9-15 6.848 13.7706 0.140625
pt=6-9 5.29513 10.3708 0.110363
pt=4-6 6.29547 11.5318 0.127077
pt=3-4 4.45859 10.1538 0.0986285
pt=2-3 5.26187 13.9151 0.114372
Related inks:
Pythia filter bug details:
bug in Pythia Filter StEemcGammaFilter.cxx:
double scale = (mCalDepth-v[2]) / p[2];
for(unsigned int j = 0; j < 3; ++j) p[j] = p[j] * scale + v[j];
Should be "abs(p[2])" in the "scale" factor.
Otherwise this will transfer all - Eta -> Eta,
and such tracks will pass the consequent Endcap rapidity cut:
if(detectorV.Eta() < mEtaLow || detectorV.Eta() > mEtaHigh) continue;
what will increase Pythia filter accept rate by a factor of 2.
Number of generated events per partnic pt bin:
Note: not every jib finished due to RCF scheduler upgrade
gamma-jet: 25K
QCD(2-4): 50K
QCD(4-55): 25K
StEemcGammaFilter:: running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events
StEemcGammaFilter:: mConeRadius 0.22 mSeedThreshold 3.8 mClusterThreshold 5 mEtaLow 0.95 mEtaHigh 2.1 mMaxVertex 120
StEemcGammaFilter:: mCalDepth 279.5 mMinPartEnergy 1e-05 mHadronScale 1 mFilterMode 0 mPrintLevel 1
StChain:INFO - Init() : Using gamma filter on the EEMC
StChain:INFO - Init() : EEMC Sampling Fraction = 0.05
StChain:INFO - Init() : Seed energy threshold = 3.3 GeV
StChain:INFO - Init() : Cluster eT threshold = 4.5 GeV
StChain:INFO - Init() : Maximum vertex = +/- 120 cm
StChain:INFO - Init() : Running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events in BFC
BFC:INFO - setTowerGainSpread(): gain spread: 0; gain mean value: 1.1
runSimuGammaTreeMaker():: GammaMaker config: ConeRadius 0.7 ClusterEtThreshold 5.5 SeedEnergyThreshold 4.2 ClusterEnergyThreshold 5.5 BsmdRange 0.05237 EsmdR ange 20
StEEmcA2EMaker *EEanalysis = new StEEmcA2EMaker("mEEanalysis");
EEanalysis->threshold(3.0, 0); // tower threshold (ped+N sigma)
EEanalysis->threshold(3.0, 1); // pre1 threshold
EEanalysis->threshold(3.0, 2); // pre2 threshold
EEanalysis->threshold(3.0, 3); // post threshold
EEanalysis->threshold(3.0, 4); // smdu threshold
EEanalysis->threshold(3.0, 5); // smdv threshold
emulate L2E-gamma trigger for Run 2006 [eemc-http-mb-l2gamma:: id 137641]
Trigger conditions:
cluster Et (2x2) = 5.2GeV
seed Et = 3.7GeV
Figure 1: Fraction of accepted events
Accept rate: fract. of generated events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.00772455 | 0.00820359 | 0.00646707 |
pt=3-4 | 0.0276027 | 0.0311644 | 0.024726 |
pt=4-6 | 0.0924862 | 0.0980663 | 0.0743646 |
pt=6-9 | 0.165708 | 0.217554 | 0.149013 |
pt=9-15 | 0.167815 | 0.258319 | 0.162353 |
pt=15-25 | 0.123 | 0.215667 | 0.117083 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.000107527 | 0.000430108 | 0.000107527 |
pt=3-4 | 0.000117647 | 0.00358824 | 5.88235e-05 |
pt=4-6 | 0.00115385 | 0.0146154 | 0.000576923 |
pt=6-9 | 0.00932927 | 0.06 | 0.00530488 |
pt=9-15 | 0.0325 | 0.178846 | 0.0173077 |
pt=15-25 | 0.0860331 | 0.253802 | 0.0510331 |
False reject: fract. of generated events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0 | 0.000359281 | 0 |
pt=3-4 | 0 | 0.000616438 | 0 |
pt=4-6 | 0.000165746 | 0.00436464 | 0 |
pt=6-9 | 0.000128755 | 0.00270386 | 0 |
pt=9-15 | 0 | 0.000210084 | 0 |
pt=15-25 | 0.00025 | 0.00025 | 0 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0 | 0 | 0 |
pt=3-4 | 0 | 0 | 0 |
pt=4-6 | 0 | 0 | 0 |
pt=6-9 | 0 | 0.000121951 | 0 |
pt=9-15 | 0 | 0 | 0 |
pt=15-25 | 4.13223e-05 | 0.000123967 | 0 |
Accept rate: fract. of Pythia-filtered events | |||
GammaJet | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.518248 | 1 | 0.49635 |
pt=3-4 | 0.505495 | 1 | 0.525275 |
pt=4-6 | 0.663662 | 1 | 0.614648 |
pt=6-9 | 0.703492 | 1 | 0.64707 |
pt=9-15 | 0.645576 | 1 | 0.605563 |
pt=15-25 | 0.568006 | 1 | 0.510433 |
QCD | |||
pt bin | Bfc Filter | Pythia Filter | L2gamma Trigger |
pt=2-3 | 0.02857 | 1 | 0 |
pt=3-4 | 0.05161 | 1 | 0 |
pt=4-6 | 0.0526316 | 1 | 0.0394737 |
pt=6-9 | 0.126016 | 1 | 0.0731707 |
pt=9-15 | 0.173118 | 1 | 0.0935484 |
pt=15-25 | 0.334419 | 1 | 0.194074 |
Description can be found here
Jet tree branches
General configuration
Triggers
pp@200GeV
addTrigger(127611); //HTTP
137611
5
127821 //HTTP-fast
137821
137822
127212 //HT2
137213
127501 //JP0
137501
127622 //JP0-etot
137622
127221 //JP1
137221
137222
137585 //bemc-jp2
127641 // eemc-http-mb-l2gamma
137641 // eemc-http-mb-l2gamma
6 // eemc-http-mb-l2gamma
Analysis cuts
StppAnaPars* anapars = new StppAnaPars();
anapars->setFlagMin(0);
anapars->setNhits(12);
anapars->setCutPtMin(0.2);
anapars->setAbsEtaMax(2.5);
anapars->setJetPtMin(3.5);
anapars->setJetEtaMax(100.0);
anapars->setJetEtaMin(0);
anapars->setJetNmin(0);
Cone finder configuration
StConePars* cpars = new StConePars();
cpars->setGridSpacing(105, -3.0, 3.0, 120,-TMath::Pi(),TMath::Pi());
cpars->setConeRadius(0.7);
cpars->setSeedEtMin(0.5);
cpars->setAssocEtMin(0.1);
cpars->setSplitFraction(0.5);
cpars->setPerformMinimization(true);
cpars->setAddMidpoints(true);
cpars->setRequireStableMidpoints(true);
cpars->setDoSplitMerge(true);
cpars->setDebug(false);
jetMaker->addAnalyzer(anapars, cpars, bet4pMaker, "ConeJets12");
anapars->setNhits(5);
jetMaker->addAnalyzer(anapars, cpars, bet4pMaker, "ConeJets5");
Disk space required
needs to be updated
Jet tree branches
General configuration
Triggers
pp@200GeV
240410 // JP1 // lum: 0.246
240411 // JP1 // lum: 4.045
240650 // L2JetHigh // lum: 3.745
240651 // L2JetHigh // lum: 1.811
240652 // L2JetHigh // lum: 19.769
240620 // L2BGamma // lum: 23.004
240630 // L2EGamma // lum: 3.969
240631 // L2EGamma // lum: 21.592
240013 // BBCMB-Cat2 (luminosity monitor)
240113 // BBCMB-Cat2 (luminosity monitor)
240123 // BBCMB-Cat2 (luminosity monitor)
240223 // BBCMB-Cat2 (luminosity monitor)
pp@500GeV
230410 // JP1 // lum: 0.198
230411 // JP2 // lum: 8.089
230630 // L2EGamma // lum: 3.347
230013 // BBCMB-Cat2 (luminosity monitor)
Analysis cuts
StppAnaPars* anapars = new StppAnaPars;
anapars->setFlagMin(0); // track->flag() > 0
anapars->setCutPtMin(0.2); // track->pt() > 0.2
anapars->setAbsEtaMax(2.5); // abs(track->eta()) < 2.5
anapars->setJetPtMin(5.0);
anapars->setJetEtaMax(100.0);
anapars->setJetEtaMin(0);
anapars->setJetNmin(0);
Cone finder configuration
StConePars* cpars = new StConePars;
cpars->setGridSpacing(105,-3.
cpars->setSeedEtMin(0.5);
cpars->setAssocEtMin(0.1);
cpars->setSplitFraction(0.5);
cpars->setPerformMinimization(
cpars->setAddMidpoints(true);
cpars->
cpars->setDoSplitMerge(true);
cpars->setDebug(false);
Disk space required
1Tb (see links at the top of the page for mode details)
Comments:
Figure 1: Reconstructed gamma-jet candidate yield vs. photon candidate pt in the endcap
(di-jet events found with the jet finder) Prompt photon filtered Monte-Carlo, partonic pt 3-25 GeV
(a)
(b) Same as (a) on a log scale
Figure 2: Same as Fig. 1 for QCD two processes filtered Monte-Carlo, partonic pt 6-9 GeV
(a)
Same on a log scale
(b) Same as (a) on a log scale
1.4M events, 6.8 CPU years, 0.29Tb disk space
parton pt, GeV | Pythia acc | bfc acc wrt. Pythia | Total filter's acc | Sigma, pb | lumi, 1/pb | Number of filtered events to generate | Total CPU time, days | disk space, Gb | starsim CPU, sec | bfc CPU, sec | Total Starsim CPU time, days | Total bfc CPU time, days | bfc acc |
g-jets | |||||||||||||
2-3 | 0.00820 | 0.2663 | 0.00218 | 1304000 | 10.0 | 28491 | 14.60576 | 4.45 | 10.72 | 4.0 | 13.270 | 1.34 | 0.00288 |
3-4 | 0.03116 | 0.3787 | 0.01180 | 293300 | 10.0 | 34611 | 14.85782 | 5.63 | 12.19 | 4.9 | 12.901 | 1.96 | 0.01504 |
4-6 | 0.09807 | 0.5521 | 0.05414 | 126300 | 10.0 | 68382 | 20.99942 | 11.34 | 12.04 | 4.7 | 17.254 | 3.75 | 0.06824 |
6-9 | 0.21755 | 0.6688 | 0.14550 | 26090 | 10.0 | 37961 | 7.79574 | 6.48 | 9.56 | 3.4 | 6.280 | 1.52 | 0.15848 |
9-15 | 0.25832 | 0.6274 | 0.16207 | 4675 | 10.0 | 7577 | 1.95231 | 1.31 | 11.56 | 3.8 | 1.616 | 0.34 | 0.15840 |
15-25 | 0.21567 | 0.5394 | 0.11633 | 326 | 10.0 | 379 | 0.13531 | 0.07 | 14.34 | 4.2 | 0.117 | 0.02 | 0.12112 |
totals: | 1754691 | 177401 | 60.3 | 29.29 | |||||||||
0.18 | 0.16533 | years | |||||||||||
QCD | |||||||||||||
2-3 | 0.00043 | 0.0185 | 0.00001 | 8226000000 | 0.1 | 6545 | 68.81525 | 1.30 | 16.62 | 9.9 | 68.064 | 0.75 | 0.00002 |
3-4 | 0.00359 | 0.0268 | 0.00010 | 1295000000 | 0.2 | 24907 | 140.98015 | 5.32 | 12.88 | 8.3 | 138.594 | 2.39 | 0.00006 |
4-6 | 0.01462 | 0.0450 | 0.00066 | 440300000 | 1.0 | 289582 | 925.73023 | 57.50 | 12.07 | 7.9 | 899.343 | 26.39 | 0.00072 |
6-9 | 0.06000 | 0.0744 | 0.00446 | 57830000 | 2.0 | 516306 | 915.77947 | 111.13 | 10.94 | 6.2 | 878.663 | 37.12 | 0.00564 |
9-15 | 0.17885 | 0.1354 | 0.02422 | 7629000 | 2.0 | 369484 | 360.48698 | 77.18 | 10.72 | 5.1 | 338.666 | 21.82 | 0.02420 |
15-25 | 0.25380 | 0.2754 | 0.06990 | 381900 | 1.0 | 26694 | 17.99424 | 5.57 | 14.43 | 5.9 | 16.185 | 1.81 | 0.07368 |
totals: | 10027140900 | 1233518 | 2429.78632 | 258.01 | |||||||||
1.23 | 6.65695 | years | |||||||||||
number of events, x 10e6 | CPU years | disk space, Gb | total time with 50 CPU, weeks | total time with 100 CPU, weeks | |||||||||
1.41 | 6.8 | 287.3 | 7.1 | 3.6 |
2M events, 6.9 CPU years, 0.41Tb disk space
parton pt, GeV | Pythia acc | bfc acc wrt. Pythia | Total filter's acc | Sigma, pb | lumi, 1/pb | Number of filtered events to generate | Total CPU time, days | disk space, Gb | starsim CPU, sec | bfc CPU, sec | Total Starsim CPU time, days | Total bfc CPU time, days | bfc acc |
g-jets | |||||||||||||
2-3 | 0.00820 | 0.51825 | 0.00425 | 1304000 | 10.0 | 55439 | 15.74249 | 8.66 | 10.72 | 3.9 | 13.270 | 2.47 | 0.00772 |
3-4 | 0.03116 | 0.50550 | 0.01575 | 293300 | 10.0 | 46205 | 15.47012 | 7.52 | 12.19 | 4.8 | 12.901 | 2.57 | 0.02760 |
4-6 | 0.09807 | 0.66366 | 0.06508 | 126300 | 10.0 | 82200 | 21.71983 | 13.64 | 12.04 | 4.7 | 17.254 | 4.47 | 0.09249 |
6-9 | 0.21755 | 0.70349 | 0.15305 | 26090 | 10.0 | 39930 | 7.87117 | 6.82 | 9.56 | 3.4 | 6.280 | 1.59 | 0.16571 |
9-15 | 0.25832 | 0.64558 | 0.16676 | 4675 | 10.0 | 7796 | 1.96162 | 1.35 | 11.56 | 3.8 | 1.616 | 0.35 | 0.16782 |
15-25 | 0.21567 | 0.56801 | 0.12250 | 326 | 10.0 | 399 | 0.13625 | 0.07 | 14.34 | 4.2 | 0.117 | 0.02 | 0.123 |
totals: | 1754691 | 231970 | 62.9 | 38.05 | |||||||||
0.23 | 0.17233 | years | |||||||||||
QCD | |||||||||||||
2-3 | 0.00043 | 0.02857 | 0.00001 | 8226000000 | 0.1 | 10108 | 68.99113 | 2.01 | 16.62 | 7.9 | 68.064 | 0.93 | 0.00011 |
3-4 | 0.00359 | 0.05161 | 0.00019 | 1295000000 | 0.2 | 47964 | 142.14305 | 10.25 | 12.88 | 6.4 | 138.594 | 3.55 | 0.00012 |
4-6 | 0.01462 | 0.05263 | 0.00077 | 440300000 | 1.0 | 338693 | 928.66220 | 67.25 | 12.07 | 7.5 | 899.343 | 29.32 | 0.00115 |
6-9 | 0.06000 | 0.12602 | 0.00756 | 57830000 | 2.0 | 874501 | 935.22936 | 188.22 | 10.94 | 5.6 | 878.663 | 56.57 | 0.00933 |
9-15 | 0.17885 | 0.17312 | 0.03096 | 7629000 | 2.0 | 472410 | 365.62683 | 98.68 | 10.72 | 4.9 | 338.666 | 26.96 | 0.0325 |
15-25 | 0.25380 | 0.33442 | 0.08488 | 381900 | 1.0 | 32414 | 18.35070 | 6.77 | 14.43 | 5.8 | 16.185 | 2.17 | 0.08603 |
totals: | 10027140900 | 1776090 | 2459.00326 | 373.18 | |||||||||
1.78 | 6.73700 | years | |||||||||||
number of events, x 10e6 | CPU years | disk space, Gb | total time with 50 CPU, weeks | total time with 100 CPU, weeks | |||||||||
2.01 | 6.9 | 411.2 | 7.2 | 3.6 |
1.4M events, 18.3 CPU years, 0.29Tb disk space
parton pt, GeV | Pythia acc | bfc acc wrt. Pythia | Total filter's acc | Sigma, pb | lumi, 1/pb | Number of filtered events to generate | Total CPU time, days | disk space, Gb | starsim CPU, sec | bfc CPU, sec | bfc reject CPU / event | Total Starsim CPU time, days | Total bfc CPU time, days | Bfc accept CPU / event |
g-jets | ||||||||||||||
2-3 | 0.00820 | 0.2663 | 0.00218 | 1304000 | 10.0 | 28491 | 41.33076 | 4.45 | 10.72 | 85.1 | 20 | 13.270 | 28.06 | 30.00 |
3-4 | 0.03116 | 0.3787 | 0.01180 | 293300 | 10.0 | 34611 | 38.06518 | 5.63 | 12.19 | 62.8 | 20 | 12.901 | 25.16 | 30.00 |
4-6 | 0.09807 | 0.5521 | 0.05414 | 126300 | 10.0 | 68382 | 53.83970 | 11.34 | 12.04 | 46.2 | 20 | 17.254 | 36.59 | 30.00 |
6-9 | 0.21755 | 0.6688 | 0.14550 | 26090 | 10.0 | 37961 | 23.81285 | 6.48 | 9.56 | 39.9 | 20 | 6.280 | 17.53 | 30.00 |
9-15 | 0.25832 | 0.6274 | 0.16207 | 4675 | 10.0 | 7577 | 5.28863 | 1.31 | 11.56 | 41.9 | 20 | 1.616 | 3.67 | 30.00 |
15-25 | 0.21567 | 0.5394 | 0.11633 | 326 | 10.0 | 379 | 0.32331 | 0.07 | 14.34 | 47.1 | 20 | 0.117 | 0.21 | 30.00 |
totals: | 1754691 | 177401 | 162.7 | 29.29 | ||||||||||
0.18 | 0.44565 | years | ||||||||||||
QCD | ||||||||||||||
2-3 | 0.00043 | 0.0185 | 0.00001 | 8226000000 | 0.1 | 6545 | 150.72171 | 1.30 | 16.62 | 1091.1 | 20 | 68.064 | 82.66 | 30.00 |
3-4 | 0.00359 | 0.0268 | 0.00010 | 1295000000 | 0.2 | 24907 | 356.60524 | 5.32 | 12.88 | 756.3 | 20 | 138.594 | 218.01 | 30.00 |
4-6 | 0.01462 | 0.0450 | 0.00066 | 440300000 | 1.0 | 289582 | 2422.48046 | 57.50 | 12.07 | 454.4 | 20 | 899.343 | 1523.14 | 30.00 |
6-9 | 0.06000 | 0.0744 | 0.00446 | 57830000 | 2.0 | 516306 | 2544.80915 | 111.13 | 10.94 | 278.8 | 20 | 878.663 | 1666.15 | 30.00 |
9-15 | 0.17885 | 0.1354 | 0.02422 | 7629000 | 2.0 | 369484 | 1013.10425 | 77.18 | 10.72 | 157.7 | 20 | 338.666 | 674.44 | 30.00 |
15-25 | 0.25380 | 0.2754 | 0.06990 | 381900 | 1.0 | 26694 | 41.71136 | 5.57 | 14.43 | 82.6 | 20 | 16.185 | 25.53 | 30.00 |
totals: | 10027140900 | 1233518 | 6529.43217 | 258.01 | ||||||||||
1.23 | 17.88886 | years | ||||||||||||
number of events, x 10e6 | CPU years | disk space, Gb | total time with 50 CPU, weeks | total time with 100 CPU, weeks | ||||||||||
1.41 | 18.3 | 287.3 | 19.1 | 9.6 |
Figure 1: Reconstructed photon candidate pt, pt_gamma (no cut on pt_gamma, pt_jet > 5GeV)
Figure 2: Partonic pt distribution (pt_gamma>7GeV, pt_jet > 5GeV)
Figure 3: Estimate of the contribution from low partonic pt,
only QCD-TuneA MC are shown (pt_gamma>7GeV, pt_jet > 5GeV)
Black line: Exponential fit to partonic pt distribution in 4-7GeV range
(pt_gamma>7GeV cut for the photon candidate)
Red line: Exponential fit extrapolated to the partonic pt range below 4GeV.
Ratio of the area under the red line (integral pt=0-4geV)
to the area under the green line (integral pt=4-35GeV) is 0.0028.
I would propose we drop both of the lowest parton pt bins,
i.e. pt=2-3 and pt=3-4 (Inherited error for pt_gamma>7GeV < 0.3%)
and instead use our CPU time to produce more
statistics in the 4-35 partonic pt range.
There is a small difference between CDF-Tune-A and
Perugia0 tunes partonic pt distributions
even for the prompt photon Monte-Carlo.
Figure 1: Reconstructed photon candidate pt, pt_gamma (no cut on pt_gamma, pt_jet > 5GeV)
Figure 2: Partonic pt distribution (no cut on pt_gamma, pt_jet > 5GeV)
Figure 3: Partonic pt distribution (pt_gamma>7GeV, pt_jet > 5GeV)
Figure 4: Away side jet pt (pt_gamma>7GeV, pt_jet > 5GeV)
Figure 5: Reconstructed z vertex (pt_gamma>7GeV, pt_jet > 5GeV)
Figure 6: Partonic pt distribution for Pythia CDF-Tune-A QCD simulations (pt_gamma>7GeV, pt_jet > 5GeV)
Estimate of the contribution from low partonic pt:
Black line: Exponential fit to partonic pt distribution in 4-7GeV range
Red line: Exponential fit extrapolated to the partonic pt range below 4GeV.
Ratio of the area under the red line (integral over pt=0-4GeV)
to the area under the green line (integral over pt=4-35GeV) is 0.0028 (<0.3%)
Simulations with Perugia0 tune has a higher yield than that from CDF-Tune-A simulations
Shapes vs. partonic pt are different for Perugia0 and CDF-TuneA simulations
Shapes vs. reconstructed variables are similar for Perugia0 and CDF-TuneA simulations
(based on Fig. 6) I would propose we drop both of the lowest parton pt bins,
i.e. pt=2-3 and pt=3-4 (Inherited error for pt_gamma>7GeV < 0.3%)
and instead use CPU time to produce more statistics in the 4-35 partonic pt range.
More discussion at phana hyper news:
http://www.star.bnl.gov/
Figure 7a: Photon candidate yield vs. rapidity (pt_gamma>7GeV, pt_jet > 5GeV)
Left: pt_gamma>7GeV; right: zoom into eta < 1 region
Figure 7b: yield vs. jet1 momentum (pt_gamma>7GeV, pt_jet > 5GeV)
Figure 7c: eta yield without pt_gamma cut
Yields ratio for eta <0.95 to the total yield is ~ 1.7% (1004/58766 = 0.0171)
Figure 8: Photon candidate yield vs. rapidity (pt_gamma>7GeV, pt_jet > 5GeV)
Note: trigger condition is not applied in simulations yet
but at high pt the data to Pythia CDF-Tune-A ratio is about 1.28 (at 9GeV: 3200/2500),
what is consistent with an additional 25% scaling factor
used for CIPANP 2009 presentation (see slide 6)
Figure 1: Reconstructed photon candidate pt, pt_gamma (no cut on pt_gamma, pt_jet > 5GeV)
Figure 2: Same as Fig. 1 with L2e-gamma condition simulated in Monte-Carlo
Figure 3: Same as Fig. 1, added distribution for photon pt from geant record (prompt photon MC only)
Figure 4: raw jet pt from jet trees: QCD pt=6-9
upper plot: mit0043 M. Betancourt simulations (MIT Simulation Productions)
bottom plot: new filtered MC
Figure 1:
Yields vs. thrown photon pt
left: Yields with (red) and without (black) L2e-gamma trigger condition
right: Yield ratio (with/without trigger)
Figure 2: Same as Fig. 1 vs. thrown eta
Figure 3: Same as Fig. 1 vs. thrown energy
Figure 4: Same as Fig. 1 vs. total reconstructed transverse energy
Figure 5: Same as Fig. 1 vs. reconstructed high tower energy
Figure 6: Same as Fig. 1 vs. reconstructed energy of the 2x1 tower cluster
Figure 7: Same as Fig. 1 vs. reconstructed energy of the 3x3 tower cluster
Figure 1: Reconstructed photon candidate pt (no pt_gamma cut, pt_jet > 5GeV)
L2e-gamma condition simulated in Monte-Carlo
Figure 2: Yield ratios (no pt_gamma cut, pt_jet > 5GeV)
Black: data[pp2006] / QCD[Perigia0]
Green: QCD[Perigia0] / QCD[CDF-Tune-A]
Red: g-jet[Perigia0] / g-jet[CDF-Tune-A]
Figure 3: Vertex z distribution (pt_gamma>7GeV, pt_jet > 5GeV)
Figure 4: Simulation yield vs. partonic pt (no pt_gamma cut, pt_jet > 5GeV)
Figure 1: Trigger effect vs. reconstructed photon candidate pt (3x3 patch) (no pt_gamma cut, pt_jet > 5GeV)
Dashed lines: Pythia Tune A, solid lines Pythia Perugia0 tune
Figure 2: Trigger effect vs. simulated direct photon pt (no pt_gamma cut, pt_jet > 5GeV)
Figure 3: Trigger effect vs. simulated direct photon eta (no pt_gamma cut, pt_jet > 5GeV)
Figure 4: Trigger effect vs. reconstructed vertex z (no pt_gamma cut, pt_jet > 5GeV)
Figure 5: Trigger effect vs. reconstructed vertex z (with additional pt_gamma >7GeV, pt_jet > 5GeV)
Figure 6: Trigger effect vs. 2x2 cluster Et (no pt_gamma cut, pt_jet > 5GeV)
Figure 7: Trigger effect vs. 1x1 cluster (high tower) Et (no pt_gamma cut, pt_jet > 5GeV)
Real and simulated trigger decisions:
Data samples:
Notations in the table:
sample | Total | BBC=1 | EEMC=1 | L2=1 | L2=1 EEMC=0 | L2=1 BBC=0 | L2=0 BBC=1 | L2=0 EEMC=1 |
pp2006, st_physics | ||||||||
(counts) | 3396 | 3306 | 568 | 549 | 5 | 2 | 2759 | 24 |
(%) | 1.0000 | 0.9735 | 0.1673 | 0.1617 | 0.0015 | 0.0006 | 0.8124 | 0.0071 |
gamma-jets (3-25GeV) | ||||||||
(counts) | 147 | 119 | 127 | 122 | 3 | 24 | 21 | 8 |
(%) | 1 | 0.80952 | 0.86395 | 0.82993 | 0.020 | 0.16327 | 0.14286 | 0.054 |
QCD (6-9GeV) | ||||||||
(counts) | 45 | 38 | 19 | 19 | 1 | 4 | 23 | 1 |
(%) | 1 | 0.84444 | 0.42222 | 0.42222 | 0.022 | 0.08889 | 0.51111 | 0.022 |
simu vs. real triggers | data-EEMC=1 | data-L2=1 | L2=1 data-L2=0 | L2=0 data-L2=1 | Trig=1 data-L2=0 | Trig=0 data-L2=1 | EEMC=0 data-EEMC=1 | EEMC=1 data-EEMC=0 |
572 | 548 | 7 | 6 | 0 | 6 | 0 | 4 | |
0.1673 | 0.1617 | 0.0021 | 0.0018 | 0.0000 | 0.0018 | 0.0000 | 0.0012 | |
Related inks:
Number of generated events per partnic pt bin (pt binsa are: 2-3, 3-4, 4-6, 6-9, 9-15, 15-35):
gamma-jets (2-4): 25K/bin
gamma-jets (4-35): 12.5K/bin
QCD(2-4): 50K/bin
QCD(4-35): 25K/bin
StEemcGammaFilter:: running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events
StEemcGammaFilter:: mConeRadius 0.22 mSeedThreshold 3.8 mClusterThreshold 5 mEtaLow 0.95 mEtaHigh 2.1 mMaxVertex 120
StEemcGammaFilter:: mCalDepth 279.5 mMinPartEnergy 1e-05 mHadronScale 1 mFilterMode 0 mPrintLevel 1
StChain:INFO - Init() : Using gamma filter on the EEMC
StChain:INFO - Init() : EEMC Sampling Fraction = 0.05
StChain:INFO - Init() : Seed energy threshold = 3.8 GeV
StChain:INFO - Init() : Cluster eT threshold = 5 GeV
StChain:INFO - Init() : Maximum vertex = +/- 120 cm
StChain:INFO - Init() : Running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events in BFC
BFC:INFO - setTowerGainSpread(): gain spread: 0; gain mean value: 1 (Fig. 1 only)
BFC:INFO - setTowerGainSpread(): gain spread: 0; gain mean value: 1.1 (Fig. 2 and below)
runSimuGammaTreeMaker():: GammaMaker config: ConeRadius 0.7 ClusterEtThreshold 5.5 SeedEnergyThreshold 4.2 ClusterEnergyThreshold 5.5 BsmdRange 0.05237 EsmdR ange 20
StEEmcA2EMaker *EEanalysis = new StEEmcA2EMaker("mEEanalysis");
EEanalysis->threshold(3.0, 0); // tower threshold (ped+N sigma)
EEanalysis->threshold(3.0, 1); // pre1 threshold
EEanalysis->threshold(3.0, 2); // pre2 threshold
EEanalysis->threshold(3.0, 3); // post threshold
EEanalysis->threshold(3.0, 4); // smdu threshold
EEanalysis->threshold(3.0, 5); // smdv threshold
(Includes all recent fixes to trigger emulator configuration/software)
emulated L2E-gamma trigger for Run 2006 [eemc-http-mb-l2gamma:: id 137641]
Trigger conditions:
cluster Et (3x3) = 5.2GeV
seed Et = 3.7GeV
Definition: offline selected events are events which satisfy to the following conditions:
Figure 1:
(upper plots) Gamma candidate yields vs. candidate pt (all partonic pt bins, no pt weights)
(lower plots) False rejection [histograms in the upper panel scaled by L2E-gamma-trigger yield (shown in blue)]
No gain shifts in StEEmcSlowMaker
Note: statistics without gain shifts is smaller because ~10-20% jobs died at RCF
Figure 2: Same as Fig. 1, but with +10% (1.1) gain shifts in StEEmcSlowMaker.
Figure 3: Same as Fig. 2 vs. candidate eta (with +10% (1.1) gain shifts in StEEmcSlowMaker).
Figure 4: Same as Fig. 2 vs. candidate azimuthal angle (with +10% (1.1) gain shifts in StEEmcSlowMaker).
Figure 5: Same as Fig. 2 vs. energy (with +10% (1.1) gain shifts in StEEmcSlowMaker).
Related inks:
Number of generated events per partnic pt bin (pt binsa are: 2-3, 3-4, 4-6, 6-9, 9-15, 15-35):
gamma-jets (2-4): 25K/bin
gamma-jets (4-35): 12.5K/bin
QCD(2-4): 50K/bin
QCD(4-35): 25K/bin
StEemcGammaFilter:: running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events
StEemcGammaFilter:: mConeRadius 0.22 mSeedThreshold 3.8 mClusterThreshold 5 mEtaLow 0.95 mEtaHigh 2.1 mMaxVertex 120
StEemcGammaFilter:: mCalDepth 279.5 mMinPartEnergy 1e-05 mHadronScale 1 mFilterMode 0 mPrintLevel 1
StChain:INFO - Init() : Using gamma filter on the EEMC
StChain:INFO - Init() : EEMC Sampling Fraction = 0.05
StChain:INFO - Init() : Seed energy threshold = 3.8 GeV
StChain:INFO - Init() : Cluster eT threshold = 5 GeV
StChain:INFO - Init() : Maximum vertex = +/- 120 cm
StChain:INFO - Init() : Running the TEST mode (accepting all events). Set mFilterMode=1 to actually reject events in BFC
Figure 1: Error for gains from MIP study minus ideal
Data digitized from Scott's presentation at 2008 Calibartion workshop
BFC:INFO - setTowerGainSpread(): gain spread: 0.1; gain mean value: 1.05 (Fig. 1,3 only)
BFC:INFO - setTowerGainSpread(): gain spread: 0.1; gain mean value: 0.95 (Fig. 2,4 and below)
runSimuGammaTreeMaker():: GammaMaker config: ConeRadius 0.7 ClusterEtThreshold 5.5 SeedEnergyThreshold 4.2 ClusterEnergyThreshold 5.5 BsmdRange 0.05237 EsmdR ange 20
StEEmcA2EMaker *EEanalysis = new StEEmcA2EMaker("mEEanalysis");
EEanalysis->threshold(3.0, 0); // tower threshold (ped+N sigma)
EEanalysis->threshold(3.0, 1); // pre1 threshold
EEanalysis->threshold(3.0, 2); // pre2 threshold
EEanalysis->threshold(3.0, 3); // post threshold
EEanalysis->threshold(3.0, 4); // smdu threshold
EEanalysis->threshold(3.0, 5); // smdv threshold
(Includes all recent fixes to trigger emulator configuration/software)
emulated L2E-gamma trigger for Run 2006 [eemc-http-mb-l2gamma:: id 137641]
Trigger conditions:
cluster Et (3x3) = 5.2GeV
seed Et = 3.7GeV
Definition: offline selected events are events which satisfy to the following conditions:
Figure 2:
(upper plots) Gamma candidate yields vs. candidate pt (all partonic pt bins, no pt weights)
(lower plots) False rejection [histograms in the upper panel scaled by L2E-gamma-trigger yield (shown in blue)]
StEEmcSlowMaker configured with +5% (scale factor=1.05) gain shifts and 0.1 sigma
Previous plots: 125K events per pt-bin, 250K/pt-bin
(figure below combines previous statisitcs + 18K for partonic pt=6-9 and pt=9-15 GeV bins)
Figure 2b: Filter bias per partonic pt bin (QCD simulations only)
Figure 3: Same as Fig. 1 with gain shift=0.95 and sigma=0.1
Figure 4: Same as Fig. 1 vs. candidate eta with gain shift=1.05 and sigma=0.1
Figure 5: Same as Fig. 1 vs. candidate eta with gain shift=0.95, sigma=0.1
parton pt, GeV | Pythia acc | bfc acc wrt. Pythia | Total filter's acc | Sigma, pb | lumi, 1/pb | Number of filtered events to generate | Total CPU time, days | disk space, Gb |
Number of |
g-jets | |||||||||
2-3 | 0.00870 | 0.2663 | 0.00232 | 1280000 | 10.0 | 29659 | 18.75 | 4.63 | 111360 |
3-4 | 0.03300 | 0.3787 | 0.01250 | 290000 | 10.0 | 36237 | 15.38 | 5.90 | 95700 |
4-6 | 0.10920 | 0.5521 | 0.06029 | 126700 | 10.0 | 76387 | 25.66 | 12.67 | 138356 |
6-9 | 0.22320 | 0.6688 | 0.14928 | 26860 | 10.0 | 40096 | 10.74 | 6.85 | 59952 |
9-15 | 0.25360 | 0.6274 | 0.15911 | 4636 | 10.0 | 7376 | 2.17 | 1.28 | 11757 |
15-35 | 0.21360 | 0.5394 | 0.11522 | 347 | 10.0 | 399 | 0.17 | 0.07 | 740 |
totals: | 1728543 | 190154 | 72.9 | 31.40 | 417865 | ||||
0.19 | 0.2 | years | |||||||
QCD | |||||||||
2-3 | 0.00067 | 0.0185 | 0.00001 | 8089000000 | 0.0 | 0 | 0.00 | ||
3-4 | 0.00298 | 0.0268 | 0.00008 | 1302000000 | 0.0 | 0 | 0.00 | ||
4-6 | 0.01312 | 0.0240 | 0.00031 | 413600000 | 2.0 | 260469 | 1428.35 | 51.72 | 10852864 |
6-9 | 0.06140 | 0.0640 | 0.00393 | 60620000 | 2.0 | 476425 | 1023.1 | 102.54 | 7444136 |
9-15 | 0.17692 | 0.1120 | 0.01982 | 7733000 | 2.0 | 306459 | 440.74 | 64.02 | 2736245 |
15-35 | 0.25480 | 0.2260 | 0.05758 | 404300 | 2.0 | 46563 | 34.53 | 9.72 | 206031 |
totals: | 9873357300 | 1089916 | 2926.72 | 228.00 | 21239276 | ||||
1.09 | 8.02 | years | |||||||
QCD |
number of events, x 10e6 | CPU years | disk space, Gb | total time with 50 CPU, weeks | total time with 100 CPU, weeks | ||||
1 | .74 | 4.2 | 145.4 | 4.4 | 2.2 | ||||
2 |
1.28 | 8.2 | 259.4 | 8.6 | 4.3 |
Figure 1: Timing tests for BFC and Pythia gamma-filters (in seconds)
Submitted run-6 photon-jet simulation request for spin physics
Request last updated on Aug 19, 2010
Total resources estimate for QCD with 1/pb and prompt-photon with 10/pb suimulations:
partonic pt |
QCD | prompt photon | ||
total | Pythia | total | Pythia | |
2-3 | 0 | 0 | 30K | 110K |
3-4 | 0 | 0 | 36K | 95K |
4-6 | 130K | 5.5M | 76K | 140K |
6-9 | 240K | 3.7M | 40K | 60K |
9-15 | 150K | 1.4M | 10K | 12K |
15-35 | 23K | 100K | 1K | 3K |
Note: These and all other studies are linked from here
StEemcGammaFilterMaker.cxx
StEemcGammaFilterMaker.h
eemcGammaFilterMakerParams.idl
See this study for more details and plots
Request an equal fraction (10%) for each of the 10 timestamps below:
sdt20060516.152000 (GMT during run 7136022)
sdt20060518.073700 (GMT during run 7138010)
sdt20060520.142000 (GMT during run 7140024)
sdt20060521.052000 (GMT during run 7141011)
sdt20060522.124500 (GMT during run 7142029)
sdt20060523.204400 (GMT during run 7143044)
sdt20060525.114000 (GMT during run 7145023)
sdt20060526.114000 (GMT during run 7146020)
sdt20060528.144500 (GMT during run 7148028)
sdt20060602.071500 (GMT during run 7153015)
------------------------ REQUEST DETAILS BELOW ----------------------------------------
Request ID | |
Priority: EC | 0 |
Priority: pwg | High |
Status | New |
Physics Working Group | Spin |
Requested by | Photon group for SPIN PWG |
Contact email(s) | ilya.selyuzhenkov@gmail.com, bridgeman@hep.anl.gov |
Contact phone(s) | |
PWG email(s) | starspin-hn@www.star.bnl.gov |
Assigned Deputy: | Not assigned |
Assigned Helper: | Not assigned |
Endcap photon-jets request
Request type: | Event generator simulation, with filtering |
Number of events | See list for each partonic pt bins |
Magnetic Field |
Full-Field |
Collision Type |
pp@200GeV |
Centrality | ---- SELECT CENTRALITY ---- |
BFC tags |
trs fss y2006h Idst IAna l0 tpcI fcf ftpc Tree logger ITTF Sti VFPPV bbcSim tofsim tags emcY2 EEfs evout -dstout IdTruth geantout big fzin MiniMcMk eemcDb beamLine clearmem |
Production | ---- SELECT PRODUCTION TAG ---- |
Geometry: simu | y2006h |
Geometry: reco | y2006h |
Library | use library with approved filter code checked in |
Vertex option |
Leave vertex to be reconstructed vertex, and use VFPPVnoCTB with beamline |
Pileup option | No |
Detector Set |
TPC, ETOW, BTOW, BSMD, ESMD, BPRS, EPRE1, EPRE2, EPOST, TOF, BBC, SVT, SSD |
Event generator | Pythia |
Extra options |
Additional libraries required for Eemc-gamma Pythia-level filter gexec $ROOTSYS/lib/libCint.so Prompt photon Pythia processes: QCD 2->2 Pythia processes: Pro-pT0 Pythia tune: |
Vertex Z, cm | -120 < Vertex < 120 |
Gaussian sigma in X,Y,Z if applicable |
0, 0, 55 200 GeV |
Vertex offset: x, mm | 0.0cm |
Vertex offset: y, mm | -0.3cm |
Φ (phi), radian | 0 < Φ < 6.29 |
η (eta) | Default (include Barrel, Endcap, BBC) |
Pt bin, GeV | See list above for QCD and g-jet samples |
Macro file | Pythia gamma-filter code:
StEemcGammaFilter.cxx StEemcGammaFilterMaker.cxx Private bfc: /star/u/seluzhen/star/spin/MCgammaFilter/scripts/bfc.C |
Ran full Pythia+GSTAR simulation and require at least one
reconstucred EEMC photon candidate in the gamma Maker.
Figure 1:
Left: Reconstructed photon candidate transverse momentum (no normalization factor applied)
Right: ratio of Pro-Pt0/Perugia0 simulations (solid Line: "a+b*x" fit to ratio)
Event selections: require at least one reconstucred EEMC photon candidate
Figure 2:
Same as in Fig. 1 with different event selection criteria:
L2E-gamma, |v_z| < 120cm, at least one EEMC gamma candidate
pytune(320) Perugia 0
P. Skands, Perugia MPI workshop October 2008
and T. Sjostrand & P. Skands, hep-ph/0408302
CR by M. Sandhoff & P. Skands, in hep-ph/0604120
LEP parameters tuned by Professor
pytune(329) Pro-pT0
See T. Sjostrand & P. Skands, hep-ph/0408302
and M. Sandhoff & P. Skands, in hep-ph/0604120
LEP/Tevatron parameters tuned by Professor
Red text indicates the parameter which are different between tunes
Parameter | Perugia 0 | Pro-pT0 | Parameter description |
MSTP(51) | 7 | 7 | PDF set |
MSTP(52) | 1 | 1 | PDF set internal (=1) or pdflib (=2) |
MSTP(64) | 3 | 2 | ISR alphaS type |
PARP(64) | 1.0000 | 1.3000 | ISR renormalization scale prefactor |
MSTP(67) | 2 | 2 | ISR coherence option for 1st emission |
PARP(67) | 1.0000 | 4.0000 | ISR Q2max factor |
MSTP(68) | 3 | 3 | ISR phase space choice & ME corrections (Note: MSTP(68) is not explicitly (re-)set by PYTUNE) |
MSTP(70) | 2 | 2 | ISR IR regularization scheme |
MSTP(72) | 1 | 0 | ISR scheme for FSR off ISR |
PARP(71) | 2.0000 | 2.0000 | FSR Q2max factor for non-s-channel procs |
PARJ(81) | 0.2570 | 0.2570 | FSR Lambda_QCD scale |
PARJ(82) | 0.8000 | 0.8000 | FSR IR cutoff |
MSTP(81) | 21 | 21 | UE model |
PARP(82) | 2.0000 | 1.8500 | UE IR cutoff at reference ecm (Note: PARP(82) replaces PARP(62).) |
PARP(89) | 1800.0000 | 1800.0000 | UE IR cutoff reference ecm |
PARP(90) | 0.2600 | 0.2200 | UE IR cutoff ecm scaling power |
MSTP(82) | 5 | 5 | UE hadron transverse mass distribution |
PARP(83) | 1.7000 | 1.8000 | UE mass distribution parameter |
MSTP(88) | 0 | 0 | BR composite scheme |
MSTP(89) | 1 | 1 | BR colour scheme |
PARP(79) | 2.0000 | 1.1800 | BR composite x enhancement |
PARP(80) | 0.0500 | 0.0100 | BR breakup suppression |
MSTP(91) | 1 | 1 | BR primordial kT distribution |
PARP(91) | 2.0000 | 2.0000 | BR primordial kT width <|kT|> |
PARP(93) | 10.0000 | 7.0000 | BR primordial kT UV cutoff |
MSTP(95) | 6 | 6 | FSI colour (re-)connection model |
PARP(78) | 0.3300 | 0.1700 | FSI colour reconnection strength |
PARP(77) | 0.9000 | 0.0000 | FSI colour reco high-pT dampening streng |
MSTJ(11) | 5 | 5 | HAD choice of fragmentation function(s) |
PARJ(21) | 0.3130 | 0.3130 | HAD fragmentation pT |
PARJ(41) | 0.4900 | 0.4900 | HAD string parameter a |
PARJ(42) | 1.2000 | 1.2000 | HAD string parameter b |
PARJ(46) | 1.0000 | 1.0000 | HAD Lund(=0)-Bowler(=1) rQ (rc) |
PARJ(47) | 1.0000 | 1.0000 | HAD Lund(=0)-Bowler(=1) rb |
Figure 1a: Reconstructed photon candidate pt (L2e-gamma condition simulated in Monte-Carlo)
Figure 1b: Same as Fig. 1 on a linear scale and zoom into low pt
Figure 2: QCD Monte-Carlo yield to pp2006 data ratio
Figure 3: Prompt photon Monte-Carlo yield to pp2006 data ratio
Figure 4: Simulation yield vs. partonic pt (on a linear scale)
Generate Monte-Carlo events for
10 different timestamps and 10% of statistics each:
sdt20060516.152000 (GMT during run 7136022)
sdt20060518.073700 (GMT during run 7138010)
sdt20060520.142000 (GMT durign run 7140024)
sdt20060521.052000 (GMT during run 7141011)
sdt20060522.124500 (GMT during run 7142029)
sdt20060523.204400 (GMT during run 7143044)
sdt20060525.114000 (GMT during run 7145023)
sdt20060526.114000 (GMT during run 7146020)
sdt20060528.144500 (GMT during run 7148028)
sdt20060602.071500 (GMT during run 7153015)
(from http://www.star.bnl.gov/HyperNews-star/protected/get/phana/481.html)
sdt20060512.043500 (GMT during run 7132005)
sdt20060513.064000 (GMT during run 7133011)
sdt20060514.090000 (GMT during run 7134015)
sdt20060516.152000 (GMT during run 7136022)
sdt20060518.073700 (GMT during run 7138010)
sdt20060520.142000 (GMT durign run 7140024)
sdt20060521.052000 (GMT during run 7141011)
sdt20060522.124500 (GMT during run 7142029)
sdt20060523.204400 (GMT during run 7143044)
sdt20060525.114000 (GMT during run 7145023)
sdt20060526.114000 (GMT during run 7146020)
sdt20060528.144500 (GMT during run 7148028)
sdt20060602.071500 (GMT during run 7153015)
sdt20060604.191200 (GMT during run 7155043)
Figure 1: Number of events from Run 6 golden runs
which fired L2e-gamma trigger (trigger id 137641 and 127641)
(using jet trees regenerated in new format by Wayne/Renee)
7132005: 0
7133011: 0
7134015: 10474
7136022: 171217
7138010: 221567
7140024: 62826
7141011: 174207
7142029: 187048
7143044: 189752
7145023: 142799
7146020: 133758
7148028: 181269
7153015: 145129
7155043: 89428
Figure 1: Reconstructed photon candidate pt (L2e-gamma condition simulated in Monte-Carlo)
Figure 3: Thrown photon pt (from Geant record, prompt photon sample only)
Figure 1: Reconstructed photon candidate pt
Figure 2: Reconstructed away side jet pt
Figure 3: z vertex distribution
Figure 4: 3x3 tower cluster energy
Figure 5: 2x1 tower cluster energy
Figure 6: Reconstructed photon candidate (detector) rapidity
Figure 1: Cluster energy ratio: 2x1/2x2
Figure 2: Cluster energy ratio: 2x1/3x3
Figure 3: Cluster energy ratio: 2x2/3x3
Figure 4: Cluster energy ratio: 2x1/E(R=0.7)
Figure 1: 3x3 tower cluster energy
Figure 2: 25 central SMD u-strip energy
Figure 3: 3x3 pre-shower1 cluster energy
Figure 1: 3x3 tower cluster energy to jet R=0.7 energy ratio
Left: Official production (Pro-Pt0), Right: Pro-Pt0 (Ilya private production)
Figure 2: 3x3 tower cluster energy to jet R=0.7 energy ratio - Perugia0 (Ilya private production)
Figure 3: 3x3 tower cluster energy to jet R=0.7 energy ratio - CDF Tune A (Ilya private production)
Figure 4: 3x3 tower cluster with jet thresholds energy to jet R=0.7 energy ratio - Official production (Pro-Pt0)
Year 2010
Year 2009
StEemcGammaFilter maker is the Pythia level EEMC gamma filter
StEemcGammaFilterMaker maker is the BFC level Endcap gamma filter
STAR Jet finder code and the new (Pibero's) jet tree format description
StEemcDstMaker is the maker which copies the Eemc detector response and TPC tracks
from MuDst into the StEemcDstEvent tree
StGammaJetMaker is the maker which reads jet, skim, and EemcDst trees simultaneously
and generates an StGammaJetEvent tree of gamma-jet candidate
StGammaJetAna is the maker which runs the shower shape and sided residual analyses.
As result it generates the StGammaJetAnaEvent tree
(StGammaJetAnaEvent is an event container which stores the gamma-jet sided residual info)
StGammaJetDraw is the maker which applies final analysis cuts and generates histograms
Signal to background optimization with multi-variant analysis:
macros to run TMVA analysis (LDA, neural network MLP, etc)
Macros to run various makers
2009/2010 GEANT geometry file update summary (ecalgeo v6.0):
Final updates (ecalgeo v6.2):
See also:
Anylysis flow chart:
starsim (Kumac) -> fzd.gz
bfc.C (fzd) -> MuDst.root / geant.root
JetFinder (MuDst) -> jet.root / skim.root
EEmcDstMaker (MuDst) -> eemc.root
GammaJetMaker (jet/skim) -> dijet.root
GammaJetAnaMaker (dijet/eemc) -> ana.root
GammaJetDrawMaker (ana) -> draw.root / mlp.root
Main directory for Ilya's private directory files at RCF IUCF disk:
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC
fzd.gz, geant.root, and MuDst.root are in files/ subdirectory
logs (MuDst.log.gz, sim.log.gz) in logs/ subdirectory
Prompt photons (partonic pt range 3-25, single bin):
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100630/GammaJet_pt3_25_pytune100
QCD (partonic pt range 4-35, bins: 4-6, 6-9, 9-15, 15-35):
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100630/QCD_pt4_6_pytune100
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100630/QCD_pt6_9_pytune100
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100630/QCD_pt9_15_pytune100
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100630/QCD_pt15_35_pytune100
fzd.gz, geant.root, and MuDst.root are in files/ subdirectory
logs (MuDst.log.gz, sim.log.gz) in logs/ subdirectory
Prompt photons (partonic pt range 3-25, single bin):
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100630/GammaJet_pt3_25_pytune320
QCD (partonic pt range 4-35, bins: 4-6, 6-9, 9-15, 15-35):
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100630/QCD_pt15_35_pytune320
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100630/QCD_pt4_6_pytune320
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100630/QCD_pt6_9_pytune320_1
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100630/QCD_pt6_9_pytune320_2
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100630/QCD_pt9_15_pytune320
fzd.gz, geant.root, and MuDst.root are in files/ subdirectory
logs (MuDst.log.gz, sim.log.gz) in logs/ subdirectory
Prompt photons (partonic pt range 3-25, single bin):
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100727/GammaJet_pt3_25_pytune329
QCD (partonic pt range 4-35, bins: 4-6, 6-9, 9-15, 15-35):
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100727/QCD_pt4_6_pytune329
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100727/QCD_pt6_9_pytune329
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100727/QCD_pt9_15_pytune329
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/20100727/QCD_pt15_35_pytune329
trees (ana, dijet, draw, eemc, gamma, geant, jet, mlp, MuDst, skim) are in:
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/pp200/pythia6_423/
logs for:
ana, dijet, draw, eemc, gamma, jet, mlp, skim:
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/prodlog/trees/
MuDst and geant:
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/prodlog/P10ii/log/trs/
Prompt photons (partonic pt range 2-35, bins: 2-3, 3-4, 4-6, 6-9, 9-15, 15-35):
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/pp200/pythia6_423/pt_2-3gev/eemcgammafilt100_gamma
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/pp200/pythia6_423/pt_3-4gev/eemcgammafilt100_gamma
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/pp200/pythia6_423/pt_4-6gev/eemcgammafilt100_gamma
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/pp200/pythia6_423/pt_6-9gev/eemcgammafilt100_gamma
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/pp200/pythia6_423/pt_9-15gev/eemcgammafilt100_gamma
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/pp200/pythia6_423/pt_15-35gev/eemcgammafilt100_gamma
QCD (partonic pt range 4-35, bins: 4-6, 6-9, 9-15, 15-35):
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/pp200/pythia6_423/pt_4-6gev/eemcgammafilt100_qcd
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/pp200/pythia6_423/pt_6-9gev/eemcgammafilt100_qcd
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/pp200/pythia6_423/pt_9-15gev/eemcgammafilt100_qcd
/star/institutions/iucf/IlyaSelyuzhenkov/gammaFilterMC/official/pp200/pythia6_423/pt_15-35gev/eemcgammafilt100_qcd
/star/institutions/iucf/IlyaSelyuzhenkov/jetTrees/2006/ppProductionLong/
/star/institutions/anl/Run6GammaTrees/log/
/star/institutions/anl/Run6GammaTrees/root/
Examples of different kumac files:
TObjArray* HList=new TObjArray;
StTriggerSimuMaker *simuTrig = new StTriggerSimuMaker("StarTrigSimu");
simuTrig->setHList(HList);
simuTrig->setMC(true); // must be before individual detectors, to be passed
simuTrig->useBbc();
simuTrig->useBemc();
simuTrig->useEemc(0);
simuTrig->bemc->setConfig(StBemcTriggerSimu::kOffline);
StGenericL2Emulator* simL2Mk = new StL2_2006EmulatorMaker;
assert(simL2Mk);
simL2Mk->setSetupPath("/afs/rhic.bnl.gov/star/users/kocolosk/public/StarTrigSimuSetup/");
simL2Mk->setOutPath("/star/institutions/iucf/IlyaSelyuzhenkov/data/MCFilter/StGenericL2Emulator_log/");
simuTrig->useL2(simL2Mk);
macros to run various makers for the gamma-jet analysis:
Macros to run various makers:
Run 9 bfc options with EEMC slow and fast simulators (EEfs EEss):
"trs,fss,Idst,IAna,l0,tpcI,fcf,ftpc,Tree,logger,ITTF,Sti,MakeEvent,McEvent,
geant,evout,IdTruth,tags,bbcSim,tofsim,emcY2,EEfs,EEss,
GeantOut,big,-dstout,fzin,-MiniMcMk,beamLine,clearmem,eemcDB,VFPPVnoCTB"
Run 6 bfc options with EEMC slow and fast simulators (EEfs EEss):
"trs fss y2006h Idst IAna l0 tpcI fcf ftpc Tree logger
ITTF Sti VFPPV bbcSim tofsim tags emcY2 EEfs EEss evout
-dstout IdTruth geantout big fzin MiniMcMk clearmem eemcDb beamLine sdt20060523"
Run 6 bfc options with EEMC gamma filter in the chain (FiltEemcGamma):
"FiltEemcGamma trs fss y2006h Idst IAna l0 tpcI fcf ftpc Tree logger
ITTF Sti VFPPV bbcSim tofsim tags emcY2 EEfs EEss evout
-dstout IdTruth geantout big fzin MiniMcMk clearmem eemcDb beamLine sdt20060523"
Note:
need to use a special macro RunEemcGammaFilterBfc.C
to run FiltEemcGamma with bfc
Official scheduler documentation
Schedule template file examples:
Catalog request to get official Gamma filtered Monte-Carlo files:
get_file_list.pl -distinct -keys 'path,filename' -cond 'production=P10ii,path~pt_4-6gev/eemcgammafilt100_qcd/y2006h,filetype=MC_reco_MuDst,storage=nfs'
or
get_file_list.pl -distinct -keys 'path,filename' -cond 'production=P10ii,runnumber=2000010060,filetype=MC_reco_MuDst,storage=nfs
where run number = 2000000000 + 10060
StEemcDstMaker is Eemc dst event container (similar to the gamma maker code structure).
Creates root tree from MuDst which stores the relevant information
for the photon-jet analysis
StEemcGammaFilter is the Pythia level EEMC gamma filter.
The code is available at STAR/cvs: StEemcGammaFilter.h / StEemcGammaFilter.cxx
Basic algo description:
Algo parameters:
mConeRadius - eta-phi cluster cone radius
mSeedThreshold - seed track threshold
mClusterThreshold - track cluster threshold
mEtaLow - lowerst rapidity cut
mEtaHigh - highest rapidity cut
mMaxVertex - vertex cut
Other parameters:
mCalDepth - calorimeter depth at which tracks are extrapolated
mMinPartEnergy - minimum particle energyto be included in the cluster
mHadronScale - down scale factor for hadrons (be careful when playing with this) No scaling by default
mFilterMode - filter mode: 0 - test mode (no event rejection), 1 - filter reject events
mPrintLevel - print level (0 - no output, 1 or 2 print some logs)
StEemcGammaFilterMaker big full chain (BFC) Endcap gamma filter
Code is accessible in CVS/STRoot: StEemcGammaFilterMaker.h / StEemcGammaFilterMaker.cxx
Parameter can be stored in the data base (see eemcGammaFilterMakerParams.idl file),
but this is not enabled in the current implementation.
Basic idea of StEemcGammaFilterMaker algo:
Available parameters to vary:
Seed energy threshold (mSeedEnergyThreshold, GeV)
Cluster eT threshold (mClusterEtThreshold GeV)
Maximum z vertex (mMaxVertex, cm)
Macro to run StEemcGammaFilterMaker with BFC
(fixes the problem of loading StJetSkimEvent library):
StGammaJetAna is the main maker which actually do the shower shape analysis.
StGammaJetAna.h / StGammaJetAna.cxx
StRoot/StGammaJetAna/StGammaJetAna:
StGammaJetAnaEvent is an event container which stores the information
on gamma-jet candidates, output from shower shape fits and sided residual analysis
Also it has an information from the crude pi0 (multi-photon event) finder
StGammaJetDraw - applying analsyis cuts
(such as photon isolation, photon and jet pt cuts, etc)
and generate pre-shower sorted histograms
StRoot/StGammaJetDraw/StGammaJetDraw:
StGammaJetEvent - container for the gamma-jet candidate events
(stores the information on selected di-jets from the jet finder and Eemdc Dst trees).
StGammaJetMaker read jet, skim, and EemcDst trees and select/write gamma-jet tree.
Photon-jet reconstruction software documentation
Year 2010
Year 2009
Year 2008
Figure 1:. Gamma candidate pt distributions for a three different data samples:
Note: Same algorithm has been used to analyse Monte-Carlo and real data events
Figure 2: Sided residual and sample gamma-jet candidate (EEMC response)
proposed modification ot the title/abstract
Get l2 software
Currently copied from ~rcorliss/l2/official-2009a
Compile
# cd onlineL2
# make lib
# make
Run
# m 5000
Convert "bin" file format to root file:
# ./binH2rootH-exe out/run9.l2eemcGamma.hist.bin out/run9.l2eemcGamma.hist.root
Create ps file with plots from root file with plotl2eemcGamma.C macro:
# root -b -q 'plotl2eemcGamma.C("out/run9.l2eemcGamma.hist.root","run9.l2eemcGamma.ps")'
# ps2pdf run9.l2eemcGamma.ps run9.l2eemcGamma.pdf
Sample pdf plots:
pythia_pT7-9_rcf1225.eve_.bin-348k
pythia500_QCD_pt10_Filter20Bemc_LT10invpb
Documentation for Relative Luminosity Analysis at STAR:
Tai Sakuma
The dijet cross sections were measured using a data sample of 5.4 pb-1 in proton-proton collisions at 200 GeV. The cross sections were measured at the mid-rapidity |η| ≤ 0.8 as a function of dijet mass Mjj.
The dijet cross sections were estimated with the formula:
J is the dijet yields at the detector level. C is the correction factors which correct the dijet yields to the hadron level. The correction factors C are estimated from the MC events as bin-by-bin ratios of the dijet yields at the detector level and at the hadron level. ΔMjjΔη3Δη4 normalizes the cross sections to per unit space volume.
The major systematic uncertainty was due to the uncertainty on the jet energy scale (JES). Because the Mjj dependence is steeply decreasing, the uncertainty of the cross section is very sensitive to systematic uncertainty on the JES.
The figures show the preliminary results of the dijet cross section measurements. The measured dijet cross sections are well described by the theory. This indicates that measured ALL as well can be interpreted in the same theory and suggests ways to constrain the polarized gluon distributions from dijet ALL.
Please, visit this site for the detail: http://people.physics.tamu.edu/sakuma/star/jets/c100923_dijets/s0000_index_001/prelim.php
Tai Sakuma
The longitudinal double spin asymmetry ALL of the dijet production in polarized proton-proton collisions at 200 GeV at the mid-rapidity |η| ≤ 0.8 was measured. ALL was measured as a function of the dijet invariant mass Mjj.
The ALL was measured as the ratios of the spin sorted dijet yields with the corrections for the relative luminosity and polarizations:
Four false asymmetries, which should vanish, were measured for a systematic check of the data. Two single spin asymmetries and two wrong-sign spin asymmetries were consistent with zero within the statistical uncertainties.
The largest systematic uncertainty is the trigger bias, which is the uncertainty in the changes of ALL from the parton level to the detector level. This was evaluated using the MC events with several polarized parton distributions which are compatible with the current experimental data: DSSV, GRSV std, and the GRSV series with ΔG from -0.45 to 0.3. In this evaluation, in order to calculate ALL with the unpolarized event generator Pythia, the MC events were wighted by the products of the spin asymmetries of the parton distributions and parton-level cross sections.
The result is consistent with a theoretical prediction based on the DSSV polarized parton distributions, which indicates the dijet ALL will be a promising channel to constrain the polarized gluon distribution when we collect more statistics.
Please, visit this site for the detail: http://people.physics.tamu.edu/sakuma/star/jets/c100926_dijets_asym/s0000_index_001/prelim.php
Tai Sakuma
We measured the inclusive jet cross section in proton-proton collisions at 200 GeV using data collected with the STAR detector during RHIC Run-6. The jet cross section is an essential quantity to test the predictive power of Quantum Chromodynamics (QCD). We have made several improvements since the previous measurement from STAR [PRL 97 (2006) 252001]; the data size increased from 0.3 pb-1 to 5.4 pb-1; while the previous measurement used the Time Projection Chamber (TPC) and only the west side of the Barrel Electromagnetic Calorimeter (BEMC), which corresponds to the acceptance of 0 ≤ η ≤ 1, this measurement used the TPC and both sides of the BEMC (-1 ≤ η ≤ 1).
Jets are sprays of particles which are moving approximately in the same direction from the collision point. We used the mid-point cone jet-finding algorithm with the cone radius 0.7 to define jets. Jets can be defined at three different levels: the parton level, the hadron level, and the detector level. The parton-level jets are outgoing partons of the hard interactions. The hadron-level jets are composed of products of hadronization and particle decay of the outgoing partons. They are predominantly hadrons, but may contain leptons and photons as well. The detector-level jets are detector responses to the hadron-level jets. They are made of energy deposited in BEMC towers and charged tracks reconstructed in the TPC.
We estimated the hadron-level jet yields from the detector-level jet yields by inverting the response of the detector using a MC simulation. Consequently, the results have a tendency to be biased toward the predictions of the MC simulation. To minimize this bias, we used MC events which desciribe the data well.
The results are in agreement with next-to-leading-order (NLO) perturbative QCD predictions which include corrections for non-perturbative effects. This agreement is evidence that the measured inclusive jet ALL [PRL 97 (2006) 252001] [PRL 100 (2008) 232003] can be interpreted in the framework of the QCD factorization. Furthermore, having a theoretical model that well describes the inclusive jet production is a crucial step toward dijet measurements.
There is a poster about the preliminary results.
A full size pdf file can be found at (pdf).
Please, visit this site for the detail: http://people.physics.tamu.edu/sakuma/star/jets/c100826_inclusive_jets/s0000_index_001/prelim.php
Originally, the MC samples generated for the inclusive jet analyses were used for the di-jet analyses. However it turns out that these samples were not sufficient for the di-jet analyses especially for unfolding the cross sections for the 2005 di-jets. To generate sufficient MC samples with available computing resources, MC generations were designed to generate events only in the region of the phase space where the di-jet events in the STAR acceptance come from.
These are the distributions of pseudorapidity and scattering angle for the original MC samples. The left plots of each image is for all the generated events and the right plots are for the dijet events.
Significant portion of the dijet events come from only the regions inside the red boxes.
The new MC samples were generated only in those regions of the phase space from which most dijet events come.
The most of the MC production jobs that the spin PWG requested for the di-jet analysis didn't finish successfully
Patch for a bug in PYTHIA6
This page explains how to run the patched PYHIA 6 as the event generator for starsim. The starsim has a mechanism where a user can choose a specific version of Pythia to use at run time.This feature will be used.
This tar ball contains the source files for the patched PYTHIA 6.205 and 6.4.10 in the form that fits to starsim.
Build the shared objects with the following commands.
tai@rcas6007% stardev
tai@rcas6007% tar xvfz patched_pythia_for_starsim.1.0.0.tar.gz
tai@rcas6007% cons
Two shared objects should be built in the directory $MINE_LIB.
These are loadable modules for starsim which contain the patched PYTHIA 6.205 and 6.4.10, respectively.
This is a smple kumac file load the shared object pythia_6410t.so and generated one hundred events.
tai@rcas6007% starsim
******************************************************
* Starting starsim NwGEANT= 20000000 NwPAW= 2000000 *
**********************pid= 22383**********************
******************************************************
* *
* W E L C O M E to starsim *
* *
* Version INITIAL 16 November 2006 *
* *
******************************************************
Workstation type (?=HELP) <CR>=1 : 0
Version 1.29/04 of HIGZ started
1***** GEANT Version 3.21/08 Released on 230697
0***** Correction Cradle Version 0.0800
***** RZMAKE. OLD RZ format selected for RZDOC
starsim > exec sample.kumac
You should be able to find the output my_pythia_file.fz if the MC production is successful.
If you have a question or comment, send email to sakuma@bnl.gov or add comment to this page.
This patch is included in PYTHIA from PYTHIA 6.412. You don't need to apply this patch if you are using PYTHIA 6.412 or newer.
If you need the patch for a different version of PYTHIA, email sakuma@bnl.gov.
At the end of the year 2006, The spin PWG requested the MC productions with uncommon kinematical cuts for the measurement of
the 2005 di-jet cross sections in pp collisions.
The most of the MC production jobs didn't finish successfully.
The failure is due to a bug in PYTHIA 6. This page provides a patch for the bug.
If you want to run the patched PYTHIA as the event generator for starsim, the instruction can be found at "How to run the patched PYTHIA 6 in starsim."
PYTHIA 6 has options to generate events only a specific region of the phase space. You can specify the region in terms of various variables such as pT, y, cos(theta), s, t, u, x1, x2, and other kinematical variables. With some sets of the values for the cuts, PYTHIA 6 behaves improperly especially when cuts are applied on both pT and cos(theta) simultaneously. This is a main program that can reproduce the improper behavior.
This main.f should be able to reproduce the bug for any version of PYTHIA between 6.2 and 6.4.11. From the version 6.4.12, this patch is included in PYTHIA.
You can compile and run for yourself with the following commands.
f77 main.f pythia-6.4.11.f
./a.out
PYTHIA 6 can be found at the following websites.
With the main.f, PYTHIA will try to generate one thousand events of the pp collisions at 200 GeV in the following region of the phase space.
With the main.f, the cross section does not converge and sometime
becomes negative.
And you will also constantly get the warning like
Warning: negative cross-section fraction -2.262E+01 in event 140
ISUB = 28; Point of violation:
tau = 2.930E-02, y* = 3.735E-01, cthe = -0.5988706, tau' = 0.000E+00
and
Advisory warning: maximum violated by 1.505E+01 in event 243
XSEC(68,1) increased to 1.631E-01
Then, PYTHIA will gradually slow down in generating events and won't make
it to generate one thousand events within an hour on an average PC.
These are the patches for the bug for PYHIA 6.4.11 and 6.205.
You can apply these patches, for example, in this way.
patch pythia-6.4.11.f < pythia-6.4.11-t.diff
I reported the bug and sent my patch to Torbjörn Sjöstrand, the author of PYTHIA. He responded "Thanks a lot for your input. Yes, you are right, this is a
possibility we missed so far. Will try to have your fix inserted for the next subversion. ... In retrospect the number of kinematics options grew to a level
where not all possible combinations were sufficiently tested".
In another email, I asked him if my patch is safe to use for serious physics study. Torbjörn Sjöstrand said
"So far as I can see the patch should be safe and not have any
undesirable consequences, but I could not give any 100%
guarantees".
The patch that I actually sent to the author is simpler than ones in the previous section.
In the patches in the previous section, I also modified the title logo such that it indicates that the program is modified.
I compared the cross sections computed with the original PYTHIA and the patched PYTHIA. I got a consistent result. I'll write the detail later.
I figured out how to implement this patch in starsim.
How to run the patched PYTHIA 6 in starsim
Neutral pion analysis
Proposed Title: "Double longitudinal spin asyymetry and cross sectrion for inclusive neutral pion production at midrapidity in polarized proton collisions at Sqrt(s) = 200GeV"
PAs: Alan Hoffman, Joe Seele, Bernd Surrow, ...
Target Journal: PRD - Rapid Communication
Abstract:
Figures:
The first two figures are obvious: the cross section plot and the A_LL plot. The third is less so. I offer a number of options below.
1)
Caption 1. Cross section for inclusive \pi^0 production. a) The unpolarized cross section vs. P_T. The cross section points are plotted along with NLO pQCD predictions made using DSS and KKP fragmentation functions. b) Statistical and systematic uncertainties for the cross section measurement. c) Comparison of measured values to theoretical predictions. Predictionsa re shown for three different fragmetnation scales to give an idea of theoretical uncertainty.
2)
Caption 2. The longitudinal double spin asymmetry, A_LL, vs. P_T for inclusive \pi^0 prodution. The error bars are purely statistical. The systmatic uncertainty is represented by the shaded band beneath the points. The measurement is compared to a number of NLO pQCD predictions for different input values of \Delta G.
3) Option 1
Caption: Comparison between Data and Simulation for energy asymmetry Z_gg = |E1 - E2|/(E1 + E2). (Ed. Note: The nice thing about this plot is that it would not require too much supporting explanation in the text. Readers would know what it means. "Monte Carlo" could be changed to "Pythia + Geant" to be more specific.)
3) Option 2
Caption: Left: Two photon invariant mass distribution for data (black points) and various simulation components. Right: Same data distribution compared to combined simulation. (Ed. Note: This plot would require us to describe the whole mass-peak simulation scheme, which may be outside the scope of the paper.)
3) Option 3
Some combination of these two plots showing the A_LL points and then the P-values associated with various pQCD predictions. This would follow the example set by the jet group.
Summary and Conclusions:
Supporting Documentation:
Click on the link to download my slides for the PWG meeting.
My initial attempt at pinpointing the causes of the 'floating' pion mass examined, as possible causes, the fit function, an artificial increase in the opening angle, and the BEMC energy resolution. Preliminary findings indicate that the both the opening angle and the BEMC resolution play a part in the phenomena, however the resolution seems to be the dominant factor in these pt ranges (5.2 - 16).
I also compared the effect in Data and MC using a full QCD (pythia + geant) MC sample, filtered for high-pt pions. As can be seen in the link below, the mean mass position and peak widths are comprable in data and MC. The floating mass problem is readily reproduced in this MC sample.
On the pages listed below I'm going to try to keep track of the work towards measuring the cross section for inclusive pion production in pp collisions from run 6. I'll try to keep the posts in chronological order, so posts near the bottom are more recent than posts near the top.
The plot below shows the total errors, statistical and systematic, for the cross section measurement. The inner tick marks on the error bars represent the statistical errors. The outer ticks represent the statistical and point-to-point systematic errors added in quadrature. The grey band shows the systematic error from the BEMC gain calibration uncertainty, which we have agreed to separate from the others (as it cannot be meaningfully added in quadrature to the other uncertainties).
Goal:
To calculate the systematic uncertainty on the cross section due to the BEMC calibration uncertainty.
Justification:
Clearly, the BEMC energy scale is of vital importance to this measurement. The energies measured by the BEMC are used to calculate many of physics level quantities (photon energy, pion pt, pion mass, Zgg) that directly enter into the determination of the cross section. Since the calibration of the BEMC is not (and indeed could not be) perfect, some level of uncertainty will be propagated to the cross section. This page will try to explain how this uncertainty is calculated and the results of those calculations.
Method:
Recently, the MIT grad students (lead by Matt Walker) calculated the gain calibration uncertainty for the BEMC towers. The results of this study can be found in this paper. For run 6, it was determined that the BEMC gain calibration uncertainty was 1.6% (in the interest of a conservative preliminary estimate I have gone with 2%). In the analysis chain, the BEMC gains are applied early, in the stage where pion candidate trees are built from the MuDSTs. So if we are to measure the effect of a gain shift, we must do so at this level. To calculate the systematic uncertainty, I recalculated the cross section from the MuDSTs with the BEMC gain tables shifted by plus or minus 2%. I recreated every step of the analysis from creating pion trees to recreating MC samples, calculating raw yields and correction factors, all with shifted gain tables. Then, I took the ratio of new cross section to old cross section for both shifts. I fit these ratios after the first two bins, which are not indicative of the overall uncertainty. I used these fits to estimate the systematic for all bins. The final results of these calculation can be found below.
Plots:
1) All three cross secton plots on the same graph (black = nominal, red = -2%, blue = +2%)
2) The relative error for the plus and minus 2% scenarios.
Discussion:
This method of estimating the systematic has its drawbacks, chief among which is its maximum-extent nature. The error calculated by taking the "worst case scenario," which we are doing here, yields a worst case scenario systematic. This is in contrast to other systmatics (see here) which are true one-sigma errors of a gaussian error distribution. Gaussian errors can be added in quadrature to give a combined error (in theory, the stastical error and any gaussian systematics can be combined in this manner as wel.) Maximum extent errors cannont be combinded in quadrature with gaussian one-sigma errors (despite the tendency of previous analyzers to do exactly this.) Thus we are left with separate sources of systematics as shown below. Furthermore, clearly this method accurately estimates the uncertainty for low pt points. Consider, for example, the +2% gain shift. This shift increases the reconstructed energies of the towers, and ought to increase the number of pion candidates in the lower bins. However, trigger thresholds are based on the nominal energy values not the increased energy values. Since we cannot 'go back in time' and include events that would have fired the trigger had the gains been shifted 2% high, the data will be missing some fraction of events that it should include. I'm not explaining myself very well here. Let me say it this way: we can correct for thing like acceptence and trigger efficiency because we are missing events and pions that we know (from simulation) that we are missing. However, we cannot correct for events and candidates that we don't know we're missing. Events that would have fired a gain shifted trigger, but didn't fire the nominal trigger are of the second type. We only have one data set, we can't correct for the number of events we didn't know we missed.
All this being said, this is the best way we have currently for estimating the BEMC energy scale uncertainty using the available computing resources, and it is the method I will use for this result.
Objective:
Show that, for an important set of kinematic variable distributions, the full QCD 2->2 Pythia MC sample matches the data. This justifies using this MC sample to calculate 'true' distributions and hence correction factors. All plots below contain information from all candidates, that is, all diphoton pairs that pass the cuts below.
Details:
Data (always black points) Vs. T2_platinum MC (always red) (see here)
Cuts:
Plots:
1a)
The above plot shows the Zgg distribution ((E1 - E2)/(E1 + E2)) for data (black) and (MC). The MC is normalized to the data (total integral.) Despite what the title says this plot is not vs. pt, it is integrated over all values of pt.
1b)
The above left shows Data/MC for Zgg between 0 and 1. The results have been fit to a flat line and the results of that fit are seen in the box above. The above right shows the histogram projection of the Data/MC and that has been fit to a guasian; the results of that fit are shown.
2a)
The above plot shows the particle eta for data pions (black) and MC pions (red). The MC is normalized to the data (total integral.) As you can see, there is a small discrepancy between the two histograms at negative values of particle eta. This could be a symptom of only using one status table for the MC while the data uses a number of status tables in towers and SMD.
2b)
The above left plot shows Data/MC for particle eta, which is fit to a flat line. The Y axis on this plot has been truncated at 2.5 to show the relevant region (-1,1). the outer limits of this plot have points with values greater than 4. The above right shows a profile histogram of the left plot fit to a gaussian. Note again that some entries are lost to the far right on this plot.
3)
The above plot shows detector eta for data (black) and MC (red). Again we see a slight discrepancy at negative values of eta.
3b)
The above left shows Data/MC for detector eta, and this has been fit to a flat line. Again note that the Y axis has been truncated to show detail in the relevant range. The above right shows a profile histogram of the left plot and has been fit to a guassian.
4)
The above plot shows the raw yields (not background subtracted) for data (black) and MC (red) where raw yield is the number of inclusive counts passing all cuts with .08 < inv mass < .25 and Zgg < 0.7. There is a clear 'turn on' curve near the trigger threshold, and the MC follows the data very nicely. For more information about the individual mass peaks see here.
Conclusions:
The Monte Carlo sample clearly recreates the data in the above distributions. There are slight discrepancies in the eta distributions, but they shouldn't preclude using this sample to calculate correction factors for the cross section measurement.
Attached is the presentation I gave at the collaboration meeting in late March. It was decided that before releasing a preliminary result, we would have to calculate the BEMC gain calibration uncertainty for 2006. A group of us at MIT created a plan for estimating this uncertainty (see here) and are currently working on implementing this plan as can be seen in Adam's blog post here:
http://drupal.star.bnl.gov/STAR/blog-entry/kocolosk/2009/apr/06/calib-uncertainty-update.
We hope to have a final estimate of this uncertainty by early next week. In that case, I can hopefully calculate the uncertainty in the cross section by the spin pwg meeting on 4/23. If this can be done, I will present the results then and ask to release the preliminary result for DIS 2009. If we cannot calculate a gain calibration systematic by 4/23, obviously we will not be asking to release the preliminary result.
Below you will find comparisons of the Run 6 cross section with recent Phenix results and the STAR Run 5 final result. The lower panel is the statistical error on the Run 6 points. Uncertainties for the other plots are not included. Plot 1 shows a comparison between run 6 and the Phenix result as published in PRD. Plot 2 shows a comparison between run 6 and the Run 5 final result from STAR, and plot three 3 shows all three results together. As requested, I included the errors for both run 5 and 6 results. The error bars on the cross section points are a quadrature sum of all errors (stat and sys) for the results.
Objective:
Explore the pt-dependent mean mass position in data and MC and perhaps draw some conclusions about the quality of our simulations.
Details:
Data Vs T2 platinum MC (see here for explanations)
Bins in Pt {5.5, 6., 6.75, 7.5, 8.25, 9.25, 11., 13., 16., 21.}
Cuts:
Plots:
1)
The above plot shows data (black) Vs. MC (red) for Zgg for my 9 pt bins. The MC plots are normalized to the data so that the total number of entries is equal in both distributions.
2)
Apologies for the poor labeling. The above left plot shows the mean mass per Pt for data (black) and MC (red). These means are calculated by fitting the mass spectra to a gaussian between .1 and .2 GeV/c^2. (see here for more) In addition to the cuts listed at the top of page, I make a Zgg < .7 cut and an | particle eta | < .7 cut on all pion candidates. The PDG mass of the pi0 is shown in blue. The above right plot shows the ratio of Data/MC for the mean masses, again as a function of Pt. This plot is fit to a flat line and the fit parameters are shown.
Conclusions:
The most basic conclusion we can draw is that the simulation is recreating the floating mass peak quite well. The data is never more than 3% higher or lower than the simulation and a flat-line fit is really darn close to one. Couple this with the Zgg comparison and I think we can say that we are simulating the EMC (and SMD) response correctly, at least as it concerns reconstructing neural pions between 5 - 20 GeV/c. Of particular interest is the Zgg comparisons at relatively higher Pt, as then the distance between the two reconstructed photons is smaller than the size of one tower, and we rely on the SMD to correctly identify the daughter photons.
At the PWG meeting a few weeks ago, people expressed concerns about the high-mass tail from the pion peak that, for higher PT bins, is underestimated by the pion peak simulation. This is shown (in the most egregious case) below (see especially, the left-hand plot between .2 and .5):
It is clear, at least at high-pt that the aggregate MC model does not fully reproduce this 'bleeding edge'. Naturally the question arises of how sensitive the cross section measurement is to this tail. One way to probe the sensitivity is to vary the invariant mass cut around the peak position. For the preliminary result, I used a 3 sigma cut calculated by fitting the mass peak to a gaussian. I can also calculate the cross section using a 2 sigma and 4 sigma cut. These cuts are shown below...
This plot shows a closeup of the pion peak for each of the 9 bins, with vertical lines showing the three different mass windows. For most bins, the 2 sigma cut completely excludes the tails and the 4 sigma cut includes a large portion of the tails.
I can then compare the different windows to the nominal window and the smaller (larger) windows.
Bin | % diff 4 sig | % diff 2 sig |
1 | 2.4 | 1.4 |
2 | 1.6 | 0.5 |
3 | 3.3 | 1.7 |
4 | 6.2 | 3.0 |
5 | 5.6 | 4.5 |
6 | 10.6 | 4.8 |
7 | 10.3 | 5.3 |
8 | 13.5 | 2.3 |
9 | 10.1 | 0.62 |
The largest % difference is 13.5%, in the 8th bin. For the most part the higher pt bins can be off by ~10% for a large mass window.
Goal:
To test the stability of the cross section measurement to changes in the analysis cuts and, if necessary, assign a systematic uncertainty for cut variations.
Justification:
At many points in the measurements I make cuts on the data. For example, I place a maximum Zgg cut of 0.7 on all pion candidates. These cuts are motivated by our understanding of the detector and underlying physics, but the specific location of each cut is somewhat arbitrary. The cuts could move by some small amount and still be well-motivated. The measurement should be relatively stable with respect to changing analysis cuts. To test this, I take the three most important cuts, Zgg, inv. mass window, and z vertex, and vary them by some small amount in either direction. I then repeat the analysis from start to finish to discern the effect (if any) these cut changes have on the final cross section. The procedure is similar to that used to test the BEMC energy scale systematic (seen here)
Plots:
Instead of showing the cross section measurement for each individual cut change, I will plot the results in what I hope is a more illuminating way. Below is nine plots, each one representing a Pt bin in my analysis. The Pt range in GeV/c is shown in the upper right hand corner. Plotted on each canvas are the (Delta Sigma)/(Sigma) points for each of the cut variations (see key below.) Also note the solid lines indicating the statistical error of the nominal cross section measurement in that bin.
KEY:
point x position Cut Change
2 Invariant Mass Window of plus/minus 4sigma (nominal is 3sigma)
3 Zgg - 10%
4 Z vertex cut + 10%
7 Invariant Mass Window of plus/minus 2sigma (nominal is 3sigma)
8 Zgg cut - 10%
9 Z vertex - 10%
Broadly speaking, the points on the left side of the dashed-dotted line at 5.5 are cut changes that ought to increase raw yield and cuts on the right side ought to decrease raw yield. Of course an increase (decrease) in raw yield does not always translate into an increase (decrease) in cross section because the raw yields are corrected. Note that for most bins the effect for all cut changes is small (on the same order as the statistical uncertainty.) Other systematics (BEMC energy scale and yield extraction) dominate the uncertainty.
Data and MC comparison for pion mass peak position..
The left side shows the individual mass peak positions for Data (black) and MC (red). The MC points trend a touch higher than the data point. On the right is (Data-MC)/MC. The right side plot is fit to a pol0, the value of the fit is shown to be -1.01%.
For the cross section analysis I am using a number of Monte Carlo samples along with one data set. The details of each of these sets can be found below:
Pion enhanced, QCD 2->2 sample (full event): aka "T2 Platinum":
This MC sample was produced at Tier 2 by Mike Betancourt for me. It consists of ~200,000 events in each of following partonic pt bins {5-7, 7-9, 9-11, 11-15, 15-25, 25-35} GeV. The events were pre-filtered at the pythia level so every event contains a pythia-level pion with the following kinematic cuts: Pt > 4 GeV, -1.2 < particle eta < 1.2. The code to generate the trees lives on /star/u/ahoffman/T2_maker and is complied in SL08c. The MuDsts and .geant files are archived at HPSS. The trees themselves (600 files) live on /star/institutions/mit/ahoffman/Pi0Analysis/T2_platinum/Trees/. The following parameters were set in the analysis macro:
emcSim->setCalibSpread(kBarrelEmcTowerId,0.15);
emcSim->setCalibOffset(kBarrelEmcTowerId,0.);
emcSim->setCalibSpread(kBarrelSmdEtaStripId,0.25);
emcSim->setCalibOffset(kBarrelSmdEtaStripId,0.0);
emcSim->setMaximumAdc(kBarrelSmdEtaStripId,700);
emcSim->setMaximumAdcSpread(kBarrelSmdEtaStripId,70);
emcSim->setCalibSpread(kBarrelSmdPhiStripId,0.25);
emcSim->setCalibOffset(kBarrelSmdPhiStripId,0.0);
emcSim->setMaximumAdc(kBarrelSmdPhiStripId,700);
emcSim->setMaximumAdcSpread(kBarrelSmdPhiStripId,70);
As of now, only events which pass the software trigger conditions for trigger 137611 (HTTP L2gamma) or 117001 (mb) are saved. These events are weighted properly using Mike B's custom weight calculator for his filtered events. That code can be found /star/u/ahoffman/BetanWeightCalc/
Single Particle Monte Carlo Sets
I have three separate single particle MC samples, single pion, single eta, and single gamma. These were produced using the code located at /star/u/ahoffman/SingleParticle_platinum/. The starsim, bfc, and treemaking code is all there. The .MuDsts and .geant files that result from the bfc jobs are run through a treemaker similar to that for the full pythia monte carlo. These samples are used to estimate the background shapes in in the diphoton invariant mass spectrum. The single gamma sample, for example, is used to model the 'low mass' background, as pion candidates are found from split clusters. The following cuts were set in the macro:
emcSim->setCalibSpread(kBarrelEmcTowerId,0.15);
emcSim->setCalibOffset(kBarrelEmcTowerId,0.);
emcSim->setCalibSpread(kBarrelSmdEtaStripId,0.25);
emcSim->setCalibOffset(kBarrelSmdEtaStripId,0.0);
emcSim->setMaximumAdc(kBarrelSmdEtaStripId,700);
emcSim->setMaximumAdcSpread(kBarrelSmdEtaStripId,70);
emcSim->setCalibSpread(kBarrelSmdPhiStripId,0.25);
emcSim->setCalibOffset(kBarrelSmdPhiStripId,0.0);
emcSim->setMaximumAdc(kBarrelSmdPhiStripId,700);
emcSim->setMaximumAdcSpread(kBarrelSmdPhiStripId,70);
One important difference to note is that these events are not held to the simulated trigger standard. Instead, I only choose events (offline) that have pion candidates with Pt above the trigger threshold. Essentially this assumes that the trigger efficiency is perfect for such events. Obviously this is not true, but in my analysis these samples are used primarily to estimate the background line shapes. The single pion events are not weighted. The other two samples are weighted according to the funcional form given by the PHENIX cross section measurements.
Data
This analysis is only concerned with run 6 data, and only data that satisfies the HTTP L2gamma trigger (online and software.) I restrict myself to good runs between 7139017 and 7143025, as it is the longest period of run 6 with relatively stable tower and SMD status tables. Parts of the barrell are missing in this run range, and this will be accounted for in a geometric acceptance correction, but I believe that the stability of the status tables is more important that having a 100% live detector. Using a stable run range will cut down on the systematic error of the measurement which, given previous measurements, will be larger than the statistical error. The data was produced by Murad using my StSkimPionMaker (which can be found in StSpinPool) as part of the SpinAnalysisChain. The output trees are located at /star/institutions/mit/ahoffman/Pi0Analysis/Murads_Production_2_08/. The following parameters were made in the macro:
As of now, only events which pass either HTTP L2gamma (online and software) or MB triggers are saved. Only the L2g triggered events are used in the analysis. All other cuts are made offline and will be listed in individual analysis sections to follow.
Mixed Event Background:
I should note that I also make use of a 'mixed event' sample that is made by taking photons from different (real data) events and mixing them to form pion candidates. This sample is used to model the combinatoric background as described here.
Details
Data Vs. T2 Platinum (see here)
Cuts:
Bins:
9 pt bins, with boundries {5.5, 6., 6.75, 7.5, 8.25, 9.25, 11., 13., 16., 21.}
plots:
All MC plots are normalized. They are scaled to match the number of counts in the data between M = .08 and M = .25 GeV/c^2 (the nominal signal region.)
The above plots shows the data/mc comparison for the first four bins (the bin number is in the upper right corner.) The MC peak position and width track relatively well to the data. In the data, there is an excess of 'low mass' background events. This is expected as the MC is filtered for high pt pion events and thus the background will be artificially suppressed compared to the signal.
The above plot shows the last five bins along with the total comparison for all bins (lower right)
The Data (black) and MC (red) are fit to separate gaussians between .1 and .2 GeV/c^2. The mean masses for each are plotted below. Apologies for the lack of axis labels. The x-axis is pion pt and the y-axis is mean mass of that pt bin. The errors on the points are the errors on the fits. I would take the last bin with a grain of salt considering the stats.
The blue line is the pdg mean mass of the pion. As you can see, the MC tracks the data very well, recreating the rising mass peak.
Ok, now we're cooking. Most of the ingredients are in place. We have our background subtracted raw yields. We have our generalized correction factor to account for inefficiencies in trigger, reconstruction, etc. Now, it's time to take a first look at a cross section. At a high level, we'll be starting with the raw yields, and applying a number of corrections for geometrical acceptance, efficiencies, etc. to recreate the true distribution. The formula for the invariant differential cross section:
Where:
Pt = Average Pt in a bin (as an aside, all points are plotted at this value)
Nraw = background subtracted raw yields
delta_pt = bin width in pt
delta_eta = 1.4 (= size of pseudorapidity range -.7 to .7)
Ctrig+reco = Trigger + Reconstruction Efficiency (Generalized) Correcton Factor
Gamma/Gamma = branching fraction for Pi0 -> gamma gamma (=98.8%)
L = Luminosity
After applying all of these corrections, we arrive at the cross-section below.
The a) panel shows the invariant cross section along with 2 NLO pQCD predictions (based on DSS and KKP FFs.) The b) panel shows the relative statistical errors on the cross section. Panel c) shows the (data-NLO)/NLO for both pQCD predictions as well as for predictions from DSS at two different factorization scales. The points are placed at the average Pt for a bin. As you can see on in panel c) the measured cross section agrees well with theory for both DSS and KKP FFs.
Goal:
Properly model the signal and background to the invariant mass plots using four single particle MC sets normalized to fit the data. Further, subtract out background contributions to arrive at a raw yield for each pt bin.
Details:
Data Vs. Single Particle MC (see here)
Cuts:
Bins:
9 pt bins, with boundries {5.5, 6., 6.5, 7., 7.75., 9., 11.5, 13.5, 16., 21.}
Plots:
1)
Above is a plot of the invariant mass distributions for the 9 pt bins used in this analysis. The black crosses represent the data (with errors.) The four colored histograms show the invariant mass distributions of pion candidates found in single pion MC (purple), Single photon MC (red), single eta MC (blue) and mixed-event MC (green). The four distributions are simultaneously fit to the data.
2)
The above plot shows a data/MC comparison, where the red MC curve is the sum of the four single particle curves shown in plot 1. As you can see (especially in bins 3-7) the single particle MC seems to be underestimating the width of the pion peak, especially on the high mass side. The MC peak is too narrow. I think this can be explained by two effects. First, I am overestimating the energy precision of the towers and SMDs. The width of the mass peak is directly related to the energy resolution of the towers and SMD. I think this is telling us that the simulated resolution is too precise. Also, there is the issue of jet background, which is not present in these simulations and would tend to add small amounts of energy to each photon (thus increasing the mass and the pt of the pion candidate.)
Conclusions:
Obviously this MC parameterization is not quite good enough to compare to the data. I want to go back and remake the MC distributions with more smearing in the energy resolution, and perhaps with a small pt-dependent term to simulate the jet background.
Following up from this post concerning the modeling of the invariant mass distribution using different monte carlo samples for the signal and three sources of background, I respun through the modeling algorithm with an added smearing to the masses. The procedure is outlined below.
Goal:
Properly model the signal and background to the invariant mass plots using four single particle MC sets normalized to fit the data. Further, subtract out background contributions to arrive at a raw yield for each pt bin. Details: Data Vs. Single Particle MC (see here) Cuts: Bins: 9 pt bins, with boundries {5.5, 6., 6.5, 7., 7.75., 9., 11.5, 13.5, 16., 21.} Smear: The mass and of the single pions are smeared by sampling from a pt dependent normal distribution of the form N(1.005*Pt,.04). Mass = smear*smear*old_mass. This is supposed to mimic not only the detector resolution, but also the artificial increase in photon energy resultant from excess jet background at higher Pt. Obviously this is not the correct way to do this sort of smearing; it should be done at the BEMC level in the simulation, but this is a rapid way to test out assumption that smearing will better recreate the mass peak. Plots: 1) Above is a plot of the invariant mass distributions for the 9 pt bins used in this analysis. The black crosses represent the data (with errors.) The four colored histograms show the invariant mass distributions of pion candidates found in single pion MC (purple), Single photon MC (red), single eta MC (blue) and mixed-event MC (green). The four distributions are simultaneously fit to the data. 2)
The above plot shows a data/MC comparison, where the red MC curve is the sum of the four single particle curves shown in plot 1. As you can see (especially in bins 3-7) the single particle MC much better recreates the mass peak with the smearing. It is not perfect, but compared to the original test, at least by eye, it looks better. Conclusions: I think this test supports the conclusions that the BEMC response for single pion simulation was too precise originally. Extra Pt dependent smearing should be added into the BEMC tower response.
As noted here and here, the pion peak is difficult to model using single-particle MC. In single particle studies, the pion inv mass peak is reconstructed to narrow. Instead of trying to manipulate the single particle MC to conform to the data (using smearing techniques) I decided instead to model the pion peak using identified pions from the filtered pythia MC sample, where identified in this context means the reconstructed pion is less than .01 (in eta-phi space) away from a thrown pythia pion. As seen here, the mean and width of the peaks from the filtered pythia set match the data extremely well.
Goal:
Properly model the signal and background to the invariant mass plots using single particle MC background shapes and identified pion peak shapes from filtered pythia MC normalized to fit the data. Further, to subtract out the background on a bin by bin basis to arrive at a raw yield for each pt bin.
Details:
Data Vs. Single Particle MC (see here) and Identified Pions from filtered pythia MC (see here)
Cuts:
Bins:
9 pt bins, with boundries {5.5, 6., 6.5, 7., 7.75., 9., 11.5, 13.5, 16., 21.}
Plots:
1)
Above is a plot of the invariant mass distributions for the 9 pt bins used in this analysis. The black crosses represent the data (with errors.) The four colored histograms show the invariant mass distributions of pion candidates found in identified pions from filtered pythia MC (purple,) Single photon MC (red,) single eta MC (blue,) and mixed-event MC (green.) The four distributions are simultaneously fit to the data.
2)
The above plot shows a data/MC comparison, where the red MC curve is the sum of the four single particle curves shown in plot 1. As you can see (especially in bins 3-7) the identified pion spectrum from filtered pythia MC much better recreates the mass peak than single particle (compare here.)
3)
The above plot shows the diphoton invariant mass spectrum for each of the 9 pt bins after the background shapes have been subtracted off. To calculate the background subtracted raw yields, these peaks are integrated from mean - 3sigma to mean +3sigma of a gaussian fit to the peak.
The proposed final version of the cross section plot would look like this.
The link below has the presentation for preliminary cross section result.
Now that I have my raw pion spectrum (see here) I need to proceed in transforming those raw counts into a cross section measurement. The first step in this process is calculating a correction factor that accounts for inefficiencies in the trigger and reconstruction algorithm. I will calculate this correction factor using the filtered, full-pythia MC sample. To first order the correction factor C = Nreco(Pt)/Ntrue(Pt) where Nreco = the number of pions found with our reconstruction algorithm and trigger, binned in Pt, after all cuts have been applied, and Ntrue is the true number of pions in the pythia record within the usable detector volume that should have fired the trigger. Note that C is not strictly a reconstruction efficiency. It represents a convolution of efficiencies in the reconstruction algorithm, trigger, acceptance, finite detector resolution, bin migration, merging and splitting effects.
Goal:
Calculate generalized correction factor.
Data Sets Used:
T2 Platinum MC (see here.) Previous studies (here and here) show that this MC sample very reasonably mimics the real data, especially within the pion mass peak.
Cuts:
Bins:
9 pt bins, with boundries {5.5, 6., 6.5, 7., 7.75., 9., 11.5, 13.5, 16., 21.}
Plots:
1)
The above plot shows the generalized correction factor Nreco(Pt)/Ntrue(Pt). Nreco is the number of reconstructed pions, where pions are found and reconstructed using the exact same procedure as is done for real data. The events in the MC sample are properly weighted.
We would like to check the applicability of a correction factor calculated similarly to the one above. To do this I split the filtered MC sample into two separate samples. One of these (MCd) I treat as data and the other (MCt) I treat as MC. I run the MCd sample through normal pion reconstruction and extract a raw yield spectrum. Then from the MCd sample I calculate a correction factor similar to the one above. I then apply the correction factor to the MCd raw yield distribution. The results are below.
The black squares are the raw yields of the 'data' set as a function of Pt. The red squares are the true pt distribution of pythia pions. The blue squares are the fully corrected yields obtained by applying the correction factor to the black points. As you can see, after applying the correction factor to the reconstructed 'data' the true distribution is obtained.
The collaboration has concerns about the SMD, and not without reason. They, they SMDs, have been notoriously hard to understand and model. And the SMD is central to my analysis so I need to be able to trust that I understand it. To this end, I am using a comparison of Zgg in Data and MC to claim that I understand the SMDs well enough. The SMDs are mainly used in my analysis to split the energy of tower clusters into single photons. Zgg is a measurement of this splitting. This effect is exaggerated at higher values of Pt, where the two photons from a single pion are most likely to fall in a single pion.
Below is nine plots of Data (black) Vs MC (red) for my 9 pt bins in my cross section analysis. The MC is normalized (over all pt bins) to the integral of the data.
As you can see, the data and MC line up very well within statistics. The last bin should be taken with multiple grains of salt considering the number of entries in the hists. This is the justification I offer for using simulated SMD response in calculating correction factors and background shapes to compare to the data.
Goal:
To calculate a combined systematic error for the yield extraction (i.e. background subtraction) and the correction factor, and to do so in a way that allows me to properly combine systematic uncertainties and statistical uncertaintiees in a meaningful way.
Method:
as shown here, my background-subtracted raw yields are calculated using what I call the jigsaw method. I model the background shapes using simulated data (both single particle and full pythia.) These shapes are simultaneously fit to the data and then subtracted from the data leaving a pure pion peak. This peak is integrated over to find the raw yeild in any particular bin. Obviously this method is succeptible to uncertainty, especially in the normailzation of the background shapes to the data. This normalization determines how many counts are subtracted from the data and has a direct influence on the final counts.
Previous analyses have taken a maximum-extent approach to this problem. The raw yields are calculated using some extreme scenario such as assuming no background at all or fitting the background to a polynomial. A major problem with this method is that these extreme scenarios are improbable. They sample only the largest outliers of whatever underlying distribution the background actually is. Further, these systematic uncertainties are then quoted as on equal footing with statistial uncertainties arising from gaussian processes and constituting 1 sigma errors. Thus, the systematics are vastly overestimated which leads to a large overall uncertainty and a weaker measurement. This problem is compounded when separate maximum extent errors are calculated for related variables (such as yield extraction and correction factor) and then added together in quadrature. We ought to be able to do better.
As stated above the end result of the Jigsaw method is a set of scaling parameters for each of the background shapes. The shapes are scaled by these parameters and then subtracted away. If the scaling parameters are wrong, the final yield will be wrong. Fortunately, the fitting procedure provides not only a scale for the shape but an uncertainty on that scale. So we know, how likely the scale is to be wrong. Instead of picking an outlying scenario (e.g. all scaling factors = 0) we can calculate the yields with a range of scaling factors sampled from an underlying gaussian probability distribution with a mean of the nominal scaling value and a width of the error on that scaling factor. By sampling enough points, we can build up a probability distribution for the measured point (which should also be gaussian) and take a 1 sigma error on that distribution. This error will not only be more accurate but will be on equal footing with the statistical error of the measured point.
Of course the final cross section value is a convolution of the background subtracted raw yields and the generalized correction factor. We need to vary the fitting paramaters for both at the same time to obtain an accurate estimation of the error on the final value. When we do this we get distributions for the final cross sections on a bin by bin basis. See below
Bins:
9 pt bins, with boundries {5.5, 6., 6.5, 7., 7.75., 9., 11.5, 13.5, 16., 21.}
Plots:
1)
The above shows the bin by bin cross section values after 10,000 iterations of the sampling procedure described above. The systematic error for yield extraction + correction factor can be taken to be the width/mean of the above gaussian fits.
The Bin by bin relative systematic errors are as follows
Bin Rel. Sys.
1 14.7%
2 8.2%
3 10.2%
4 9.6%
5 12.3%
6 11.6%
7 12.0%
8 13.2%
9 25.0%
previous measurements of the systematic uncertainties for these two contributions (when added in quadrature) yield an average systematic of ~20%. As you can see, this method produces substantially reduced uncertainties in most bins in a fashion that is (as I argue above) more robust than previous methods.
Here are my proceedings for DIS 2008
Here are the powerpoint and pdf versions of my slides for DNP.
Jet Pion Study
Procedure
In making the below plots, I employed the Spin Analysis Trees recently put together. I used all of the jets available, in all the jet triggers, assuming that the jets in the analysis tree are "physics" jets. I used pions from the L2-gamma and L2-gamma-test triggers. I used a run if it passed both my pion QA and Murad/Steve's Jet QA. That is, I used only those runs that were in both my golden run list and Jim Sowinski's golden run list.
First I look for any event with a pion found with -0.3 < Pion Eta < 0.3. I then loop over every jet in that event looking for any jet that is less then 0.7 away in Sqrt((delta Eta)2 + (delta phi)2). I look in such a limited Eta range for the pion so as to avoid any edge effects. I then make a histogram of the ratio of pion Pt to Jet Pt and take the mean value of that histogram. This mean value is plotted below.
Currently this includes pions only from BBC timebinds 7,8, and 9. But I will soon add timebin 6 as well.
Plots
The above plot shows the ratio of Pion Pt to Jet Pt as a function of the Pion's Pt. It looks like as Pt gets higher and higher the ratio tends towards a fixed value between 75% and 80%
This histogram shows the distance in eta and phi between pion and associated jets. As you can see the RMS in the Eta-plane (x axis) is 0.064 and the RMS in the Phi-plane (y axis) is 0.055, which corresponds to the values from run 5.
Update: 3/11/2008
All of my analysis leading up to the preliminary result uses one runlist which consist of the golden runlist from below plus about a dozen runs from the jet group's list. I added to my list any run that the jet group deemed good as long as the run log browser for that run didn't show any problems. the final runlist can be found here.
--------------------------------------------------------------------------------
Update: 6/19/2007
At the collaboration meeting in Berkeley some of out collaborators pointed out some flaws in my initial QA, most notably that I did not include BBC time bin #6. I have now redone my run QA and asymmetry calculations including this timebin. This results in a new 'golden' runlist which can be found below.
All pages below should be up to date.
--------------------------------------------------------------------------------
My first task is to determine a preliminary runlist over which I will run my analyses. Using Murad's jet QA as a guide (found here), I have looked at a number of different event criteria. At the moment, I am focusing on the second longitudinal period runs only. The data set is comprised of about 390 runs, with about 420,000 triggered events (including production and test L2-G triggers.) Each run number has an index (for easier plotting;) this index can be found here. I am also (for now) restricting myself to one trigger,:
Some book keeping stats for this running period
My results can be found on the pages below.
Preliminary Run List
As of 2/1/07 I have created a preliminary list of 'good' runs. If a run failed any of my QA tests for either HT trigger, I excluded it from this list. I tried to be as discriminating as possible for this list. I feel it will be easier to go back and add runs if they are later determined to be good. The preliminary list includes 302 runs, and can be seen by clicking below.
Furthermore, using the run log browser I have checked all of my excluded runs to see if there is an obvious reason why it shouldn't be included. Many of the runs did indeed have glaring reasons, but not all of the runs. A summary of this check can be found here.
Hi all-
My Spin 2008 talk and proceedings can be found below.
Update:
v2 reflects updates based on comments from SPIN pwg and others
The PDF for my slides is linked below.
Links for the 2006 Neutral Pion A_LL analysis
The numbered links below are in 'chronological' type order (i.e. more or less the order in which they should be looked at.) The 'dotted' links below the line are a side-effect in Drupal that lists all daughter pages in alphebetical order. They are the exact same as the numbered links and probably should just be ignored.
1. Run List QA
4. Cuts etc.
6. Invariant Mass Distribution
10. Sanity Checks
11. DIS Presentation
The measurement of ALL for inclusive neutral pion production is seen below along with statistical error bars and a systematic error band. This asymmetry was calculated using a class developed by Adam Kocoloski (see here for .cpp file and here for .h file.) Errors bars are statistical only and propagated by ROOT. The gray band below the points represents the systematic uncertainties as outlined here. The relative luminosities are calculated on a run by run basis from Tai's raw scalar counts. Each BBC timebin is treated seperately. The theory curves are GRSV predictions from 2005. These will change slightly for 2006.
Bin ALL (x10-2)
1 0.80 +/- 1.15
2 0.58 +/- 1.36
3 2.03 +/- 1.89
4 -0.84 +/- 3.06
Here I will detail the some general information about my analysis; topics that aren't substantial enough to warrant their own page but need to be documented. I will try to be as thorough as I can.
Data
Run 6 PP Long 2 Only.
Run Range: 7131043 - 7156040
Fill Range: 7847 - 7957
Days: 131 - 156 (May 11 - June 5, 2006)
HTTP L2gamma triggered data (IDs 5, 137611)
Trees using StSkimPionMaker (found in StRoot/StSpinPool/) and Murad's spin analysis chain macro
Trees located in /star/institutions/mit/ahoffman/Pi0Analysis/Murads_Production_1_08/
Cluster Finding Conditions
Detector Seed Add
BEMC 0.4 GeV 0.05 GeV
SMDe/p 0.4 GeV 0.005 GeV
Pion Finding Cuts
Event passes online and software trigger for L2gamma
Energy asymmetry (Zgg) <= 0.8
Charged track veto (no photon can have a charged track pointing to its tower)
BBC timebins 6,7,8,9 (in lieu of a z vertex cut)
At least one good SMD strip exists in each plane
-0.95 <= eta <= .95
Z vertex found
Pt Bins for ALL
All reconstructed pion candidates are separated by Pt into four bins:
5.20 - 6.75
6.75 - 8.25
8.25 - 10.5
10.5 - 16.0
Simulation
Full pythia (5 to 45 GeV/c in partonic Pt, weighted)
Single pion, photon, and eta simulations (2 - 25 GeV/c in particle Pt, unweighted)
EMC simulator settings:
15% Tower Spread
25% SMD Spread
SMD Max ADC: 700
SMD Max ADC spread: 70
(see this link for explanation of SMD Max ADC parameters)
Four representative timestamps used:
20060516, 062000 (40%)
20060525, 190000 (25%)
20060530, 113500 (25%)
20060603, 130500 (10%)
Full pythia trees located in /star/institutions/mit/ahoffman/Pi0Analysis/MC_Production_2_08/
Single particle trees located in /star/institutions/mit/ahoffman/Pi0Analysis/single_particle_simulations/
Below you will find a link to a draft my DIS 2008 presentation.
For my single particle Monte Carlo studies, I argued (here) that I needed to add a small amount of energy to each reconstructed photon to better match the data. This small addition of energy brings the simulation mass distributions into better alignment with the mass distributions in the data. I did not, however, subtract this small bit of energy from reconstructed (data) pions. This affects ALL in that pion counts will migrate to lower Pt bins and some will also exit the low end of the mass windown (or enter the high end.) So I calculated ALL after subtracting out the 'extra' energy from each photon. The plot below shows the original ALL measurement in black and the new measurement in red.
The values from both histograms are as follows:
Bin black (orig) red (new)
1 .0080 .0095
2 .0058 .0092
3 .0203 .0196
4 -.0084 -.0069
So things do not change too much. I'm not sure which way to go with this one. My gut tells me to leave the data alone (don't correct it) and assign a systematic to account for our lack of knowledge of the 'true' energy of the photons. The error would be the difference between the two plots, that is:
Bin Sys. Error (x10-3)
1 1.5
2 3.4
3 0.7
4 1.5
Using Werner's code I calculated A_LL for pi0 production over my eta range for 15 different integral values of Delta G. Below I plot the measured A_LL points and all of those curves.
I then calculated chi^2 for each of the curves. Below is the chi^2 vs. integral delta g.
The red line shoes minimum chi^2 + 1. For my points, GRSV-Std exhibits the lowest chi^2, but GRSV-Min is close. My data indicates a small positive integral value of delta g in the measured x range.
The two-photon invariant mass distribution can be roughly broken up into four pieces, seen below*.
Fig. 1
The black histogram is the invariant mass of all pion candidates (photon pairs) with pt in the given range. I simulate each of the four pieces in a slightly different way. My goal is to understand each individual piece of the puzzle and then to add all of them together to recreate the mass distribution. This will ensure that I properly understand the backgrounds and other systematic errors associated with each piece. To understand how I simulate each piece, click on the links below.
1. Pion Peak
2. Eta Peak
Once all of the four pieces are properly simulated they are combined to best fit the data. The individual shapes of are not changed but the overall amplitude of each piece is varied until the chisquared for the fit is minimized. Below are plots for the individual bins. Each plot contains four subplots that show, clockwise from upper left, the four individual peices properly normalized but not added; the four pieces added together and compared to data (in black); the ratio of data/simulatio histogramed for the bin; and a data simulation comparison with error bars on both plots.
Bin 1: 5.2 - 6.75 GeV/c
Bin 2: 6.75 - 8.25 GeV/c
Bin 3: 8.25 - 10.5
Bin 4: 10.5 - 16.0
Below there is a table containing the normalization factors for each of the pieces for each of the bins as well as the total integrated counts from each of the four pieces (rounded to the nearest whole count.)
bin | low norm. | low integral | pion norm. | pion integral | eta norm. | eta integral | mixed norm. | mixed integral |
1 | 121.3 | 9727 | 146.4 | 75103 | 20.91 | 5290 | 0.723 | 44580 |
2 | 77.34 | 4467 | 77.81 | 51783 | 20.86 | 6175 | 0.658 | 34471 |
3 | 40.13 | 3899 | 29.41 | 23687 | 12.93 | 6581 | 1.02 | 18630 |
4 | 5.373 | 1464 | 5.225 | 8532 | 2.693 | 3054 | 0.521 | 6276 |
Table 2 below contains, for each source of background, the total number of counts in the mass window and the background fraction [background/(signal+background)].
Bin | Low Counts | Low B.F (%) | Eta Counts | Eta B.F (%) | Mixed Counts | Mixed B.F (%) |
1 | 2899 | 3.60 | 1212 | 1.50 | 4708 | 5.84 |
2 | 2205 | 3.96 | 917 | 1.65 | 3318 | 5.96 |
3 | 2661 | 9.29 | 633 | 2.21 | 1507 | 5.26 |
4 | 858 | 8.56 | 170 | 1.70 | 591 | 5.89 |
* Note: An astute observer might notice that the histogram in the top figure, for hPtBin2, does not exactly match the hPtBin2 histogram from the middle of the page (Bin 2.) The histogram from the middle of the page (Bin 2) is the correct one. Fig. 1 includes eta from [-1,1] and thus there are more total counts; it is shown only for modeling purposes.
The last piece of the invariant mass distribution is the combinatoric background. This is the result of combining two non-daughter photons into a pion candidate. Since each photon in an event is mixed with each other photon in an attempt to find true pions, we will find many of these combinatoric candidates. Below is a slide from a recent presentation describing the source of this background and how it is modeled.
---------------------------------------
-------------------------------------------
As it says above we take photons from different events, rotate them so as to line up the jet axes from the two events, and then combine them to pion candidates. We can then run the regular pion finder over the events and plot out the mass distribution from these candidates. The result can be seen below.
These distributions will be later combined with the other pieces and normalized to the data. For those who are interested in the errors on these plots please see below.
I treat the eta peak in a similar way as the pion peak. I throw single etas, flat in Pt from 2 - 25, and reconstruct the two-photon invariant mass distribution for the results. The thrown etas are weighed according to the PHENIX cross-section as outlined here. The mass distributions for the four pt bins can be seen below. (I apologize for the poor labeling, the x-axis is Mass [GeV/c^2] and the y-axis is counts.) Don't worry about the scale (y-axis.) That is a consequence of the weighting. The absolute scale will later be set by normalizing to the data.
These plots will later be combined with other simulations and normalized to the data. The shape will not change. For those interested in the errors, that can be seen below.
The low mass background is the result of single photons being artifically split by the detector (specifically the SMD.) The SMD fails in it's clustering algorithm and one photon is reconstructed as two, which, by definition, comprises a pion candidate. These will show up with smaller invariant masses than true pions. Below is a slide from a recent presentation that explaines this in more detail and with pictures.
----------------------------------
----------------------------------
We can reproduce this background by looking at singly thrown photons and trying to find those that are artificially split by the clustering algorithm. Indeed when we do this, we find that a small fraction (sub 1%) do indeed get split. We can then plot the invariant mass of these pion candidats. The results can be seen below. (x-axis is mass in GeV/c^2.)
These mass distributions will later be combined with other pieces and normalized to the data. For those interested in the errors on these histograms please see below.
To study the pion peak section of the invariant mass distribution I looked at single pion simulations. The pions were thrown with pt from 2 - 25 GeV/c flat and were reconstructed using the cuts and parameters described in the cuts, etc. page. The mass of each reconstructed pion is corrected by adding a small amount of energy to each photon (as outlined here.) After this correction the peak of the reconstructed mass distribution is aligned with the peak of the data. The mass distributions from the four bins can be seen below.
Later, these peaks will be normalized, along with the other pieces, to the data. However, the shape will not change.
If you are interested in seeing the errors on the above plots, I reproduce those below.
I am using the final polarization numbers from run 6, released by A. Bazilevsky to the spin group on December 4, 2007. The files can be found below.
The two-photon invariant mass is given (in the lab frame) by
M = Sqrt(2E1E2(1 - Cos(theta)))
where E1 and E2 are the energies of the two photons and theta is the angle between those photons. For every real photon we should measure ~135 MeV, the rest mass of the pi0. Of course, the detectors have finite resolution and there is some uncertainty in our measurement of each of the three quantities above, so we should end up measuring some spread around 135 MeV.
But it is not that simple. We do not see a simple spread around the true pion mass. Instead, we see some pt dependence in the mean reconstructed mass.
The above left plot shows the two-photon invariant mass distribution separated into 1 GeV bins. The pion peak region (between ~.1 and .2 GeV) has been fit with a gaussian. The mean of each of those gaussians has been plotted in the above right as a function of Pt. Obviously the mean mass is increasing with Pt. This effect is not particularly well understood. It's possible that the higher the Pt of the pion, the closer together the two photons will be in the detector and the more likely it is that some of the energy from one photon will get shifted to the other photon in reconstruction. This artificially increases the opening angle and thus artificially increases the invariant mass. Which is essentially to say that this is a detector effect and should be reproducible in simulation. Indeed...
The above plot overlays (in red) the exact same measurement made with full-pythia monte carlo. The same behavior is exhibited in the simulation. Linear fits to the data and MC yield very similar results...
-- M = 0.1134 + 0.0034*Pt (data)
-- M = 0.1159 + 0.0032*Pt (simulation)
If we repeat this study using single-particle simulations, however, we find some thing slightly different.
-- M = 0.1045 + 0.0033*Pt
So even in single-particle simulation we still see the characteristic rise in mean reconstructed mass. (This is consistent with the detector-effect explanation, which would be present in single-particle simulation.) However, the offset (intercept) of the linear fit is different. These reconstructed pions are 'missing' ~11 MeV. This is probably the effect of jet background, where other 'stuff' in a jet get mixed in with the two decay photons and slightly boost their energies, leading to an overall increase in measured mass.
The upshot of this study is that we need to correct any single-particle simulations by adding a slight amount of extra energy to each photon.
For my relative luminosity calculations I use Tai's relative luminosity file that was released on June 14th, 2007.
I read this using the StTamuRelLum class, which, given a run number and BBC timebin, reads in the raw scalar values for each spinbit. Each event is assigned raw scalar counts for each spinbit and every event from the same run with the same timebin should have the same scalar counts assigned. When it comes time to calculate my asymmetry, the relative luminosity is calculated from these scalar counts.
Below you will find the runlist I used for all of the studies leading up to a preliminary result. For a more detailed look at how I arrived at this runlist please see my run QA page.
Below there are links to various 'sanity' type checks that I have performed to make sure that certain quantities behave as they should
The nominal mass window was chosen 'by eye' to maximize the number of pion candidates extracted while minimizing the backgrounds (see yield extraction page.) I wanted to check to see how this choice of mass window would affect the measurement of ALL. To this end, ALL was calculated for two other mass windows, one narrower than the nominal window (.12 - .2 GeV) and one wider than the nominal window (.01 - .3 Gev). The results are plotted below where the nominal window points are in black, the narrow window points are in blue and the wide window points are in red. There is no evidence to indicate anything more than statistical fluctuations. No systematic error is assigned for this effect.
After some discussion in the spin pwg meeting and on the spin list, it appears I have been vastly overestimating my eta systematic as I was not properly weighing my thrown single etas. I reanalyzed my single eta MC sample using weights and I found that the background contribution from etas underneath my pion peak is negligible. Thus I will not assign a systematic error eta background. The details of the analysis are as follows. First I needed to assign weights to the single etas in my simulation. I calculated these weights based on the published cross section of PP -> eta + X by the PHENIX collaboration (nucl-ex 06110066.) These points are plotted below. Of course, the PHENIX cross section on reaches to Pt = 11 GeV/c and my measurement reaches to 16 GeV/c. So I need to extrapolate from the PHENIX points out to higher points in Pt. To do this I fit the PHENIX data to a function of the form Y = A*(1 + (Pt)/(Po))^-n. The function, with the parameters A = 19.38, P0 = 1.832 and n = 10.63, well describes the available data.
I then caluclate the (properly weighted) two-photon invariant mass distribution and calculate the number of etas underneath the pion peak. The eta mass distributions are normalized to the data along with the other simulations. As expected, this background fraction falls to ~zero. More specifically, there was less than ten counts in the signal reigon for all four Pt bins. Even considering a large background asymmetry (~20%) this becomes a negligable addition to the total systematic error. The plots below show the normalized eta mass peaks (in blue) along with the data (in black.) As you can see, the blue peaks do not reach into the signal reigion.
Unfortunately, the statistics are not as good, as I have weighted-out many of the counts. I think that the stats are good enough to show that Etas do not contribute to the background at any significant level. For the final result I think I would want to spend more time studying both single particle etas and etas from full pythia.
I should also note that for this study, I did not have to 'correct' the mass of these etas by adding a slight amount of energy to each photon. At first I did do this correction and found that the mass peaks wound up not lining up with the data, When I removed the correction, I found the peaks to better represent the data.
In summary: I will no longer be assigning a systematic from eta contamination, as the background fraction is of order 0.01% and any effect the would have on the asymmetry would be negligible.
The plots below show the single spin asymmetries (SSA) for the blue and yellow beams, as a function of run index. These histograms are then fit with flat lines. The SSA's are consistent with zero.
We need to worry about a number of systematic effects that may change our measurement of ALL. These effects can be broadly separated into two groups: backgrounds and non backgrounds. The table below summarizes these systematic errors. A detailed explanation of each effect can be found by clicking on the name of the effect in the table.
Systematic Effect | value {binwise} (x10-3) |
Low Mass Background | {1.0; 1.1; 3.8; 1.0} |
Combinatoric Background | {1.0; 0.86; 1.6; .03} |
Photon energy Uncertainty | {1.5; 3.4; 0.7; 1.5} |
Non Longitudinal Components* | 0.94 |
Relative Luminosity* | 0.03 |
Total** | {2.3; 3.8; 4.3; 2.0} |
* These numbers were taken from the Jet Group
** Quadrature sum of all systematic errors
At the moment I am calculating the systematic error on ALL from the presence of Etas in the signal reigon using theoretical predictions to estimate ALLeta. The study below is an attempt to see how things would change if I instead calculated this systematic from the measured ALLeta. Perhaps, also, this would be a good place to flesh out some of my original motivation for using theory predictions.
First order of buisness is getting ALLeta. Since this was done in a quick and dirty fashion, I have simply taken all of my pion candidates from my pion analysis and moved my mass window from the nominal pion cuts to a new window for etas. For the first three bins this window is .45 GeV/c2 < mass < .65 GeV/c2 and for the fourth bin this is .5 GeV/c2 < mass < .7 GeV/c2. Here is a plot of ALLeta, I apologize for the poor labeling.
I guess my first reason for not wanting to use this method is that, unlike the other forms of background, the Etas A_LL ought to be Pt dependent. So I would need to calculate the systematic on a bin-by-bin basis, and now I start to get confused because the errors on these points are so large. Should I use the nominal values? Nominal values plus one sigma? I'm not sure.
For this study I made the decison to use ALLtrue as the values, where ALLtrue is calculated from the above ALL using the following formula:
ALLM = (ALLT + C*ALLBkgd)/(1 + C)
Remembering that a large portion the counts in the Eta mass window are from the combinatoric background. I then calculate the background fraction or comtamination factor for this background (sorry I don't have a good plot for this) and get the following values
Bin Bkg fraction
1 77.2%
2 60.9%
3 44.6%
4 32.6%
Plugging and chugging, I get the following values for ALLtrue:
Bin ALLT
1 .0298
2 .0289
3 -.0081
4 .175
Using these values of ALL to calculate the systematic on ALLpion I get the following values:
Bin Delta_ALLpion (x10^-3)
1 .33
2 .38
3 .63
4 3.1
Carl was right that these values would not be too significant compared to the quad. sum of the other systematics, except for final bin which becomes the dominant systematic. In the end, I would not be opposed to using these values for my systematic *if* the people think that they tell a more consistent story or are easier to justify/explain than using the theory curves. (i.e. if they represent a more accurate description of the systematic.)
For the combinatoric background systematic we first estimate the background contribution (or contamination factor) to the signal reigon. That is we integrate our simulated background to discern the precentage of the signal yield that is due to background counts. The plots below show, for each of the four bins, the background fraction underneath the singal peak. The background (simulation) is in green and the signal (data) is in black and the background that falls in the signal reigon is filled-in with green.
The background fractions for the bins are
Bin 1: 6.1%
Bin 2: 6.1%
Bin 3: 5.7%
Bin 4: 6.2%
Then I consider how much this background fraction could affect my measured asymmetry. So I need to meausre the asymmetry in the high-mass reigon. I do this, taking the mass window to be 1.2 to 2.0 GeV/c2. I do not expect this asymmetry to be Pt-dependant, so I fit the asymmetry with a flat line and take this to be the asymmetry of the background, regardless of Pt. The plot below shows this asymmetry and fit.
Finally, I calculate the systematic error Delta_ALL = ALLTrue - ALLMeasured where:
ALLM = (ALLT + C*ALLBkgd)/(1 + C)
And C is the background fraction. This yields in the end as a systematic error (x10-3):
Bin 1: 1.0
Bin 2: 0.9
Bin 3: 1.6
Bin 4: 0.03
For the eta background systematic we first estimate the background contribution (or contamination factor) to the signal reigon. That is we integrate our simulated background to discern the precentage of the signal yield that is due to background counts. The plots below show, for each of the four bins, the background fraction underneath the singal peak. The background (simulation) is in blue and the signal (data) is in black and the background that falls in the signal reigon is filled-in with. Below that is the same four plots but blown up to show the contamination.
Here we blow up these plots
The background fractions for the bins are
Bin 1: 1.50%
Bin 2: 1.65%
Bin 3: 2.21%
Bin 4: 1.70%
Then I consider how much this background fraction could affect my measured asymmetry. So I need to measure the asymmetry in the etas. So instead of measuring the asymmetry in the etas I will use a theoretic prediction for ALL. From GRSV standard and GRSV min I approximate that the size of ALL in my Pt range to be between 2 - 4%.
I stole this plot from C. Aidala's presentation at DNP in Fall 2007. Since GRSV-Max is ruled out by the 2006 jet result I restrict myself only to min, standard and zero. For a conservative estimate on the systematic, I should pick, for each Pt bin, the theory curve that maximizes the distance between the measured and theoretical asymmetries. Unfortunately, at this time I do not have predictions for Pt above 8, so I must extrapolate from this plot to higher bins. For the first two bins this maximum distance would correspond to GRSV standard (ALLbg ~ 0.02). For the third bin, this would correspond to GRSV = 0 (ALLbg ~ 0.). For the fourth bin (which has a negative measured asymmetry) I extrapolate GRSV standard to ~4% and use this as my background ALL.
Systematic (x10-3)
Bin 1: 0.18
Bin 2: 0.23
Bin 3: 0.43
Bin 4: 0.82
For the low mass background systematic we first estimate the background contribution (or contamination factor) to the signal reigon. That is we integrate our simulated background to discern the precentage of the signal yield that is due to background counts. The plots below show, for each of the four bins, the background fraction underneath the singal peak. The background (simulation) is in red and the signal (data) is in black and the background that falls in the signal reigon is filled-in with red.
The background fractions for the bins are
Bin 1: 3.5%
Bin 2: 4.2%
Bin 3: 9.3%
Bin 4: 8.3%
Then I consider how much this background fraction could affect my measured asymmetry. So I need to meausre the asymmetry in the low-mass reigon. I do this, taking the mass window to be 0 to 0.7 GeV/c2. I do not expect this asymmetry to be Pt-dependant, so I fit the asymmetry with a flat line and take this to be the asymmetry of the background, regardless of Pt. The plot below shows this asymmetry and fit.
Finally, I calculate the systematic error Delta_ALL = ALLTrue - ALLMeasured where:
ALLM = (ALLT + C*ALLBkgd)/(1 + C)
And C is the background fraction. This yields in the end as a systematic error (x10-3):
Bin 1: 1.0
Bin 2: 1.1
Bin 3: 3.7
Bin 4: 1.1
After all the pion candidates have been found and all the cuts applied, we need to extract the number of pions in each bin (in each spin state for ALL.) To do this we simply count the number of pion candidates in a nominal mass window. I chose the mass window to try to maximize the signal region and cut out as much background as possible. For the first three Pt bins, this window is from .08 - .25 GeV/c2 and in the last bin the window is from .1 - .3 GeV/c2. The window for the last Pt bin is shifted mostly to cut out more of the low mass background and to capture more pions with higher than average reconstructed mass. The windows can be seen below for bins 2 and 4.
These Pt bins are broken down by spin state, and the individual yields are reported below.
Bin | uu | du | ud | dd | Total |
1 | 20209 | 20088 | 19961 | 20231 | 80489 |
2 | 14088 | 14057 | 13645 | 13825 | 55615 |
3 | 7224 | 7080 | 7107 | 7204 | 28615 |
4 | 2505 | 2470 | 2552 | 2491 | 10018 |
Calibration
I am trying to calibrate the BEMC using neutral pions. As of now I am only using the L2 Gamma trigger for the second longitudinal running period, although I plan on incorporating the transverse data as well since the calibration should be the same for the two running periods. The procedure, so far, is listed below. Items 1 - 4 have been done for the long2 data set and are not difficult. Items 5+ I have not done yet, nor am I certain if they are the correct way to proceed.
1. Find all pion candidates using Frank's finder.
2. Calculate the mass for each di-photon pair.
3. Find the tower struck by each photon in the candidate and fill that tower's histogram with the invariant mass of the pion candidate. Note that if the two photons strike two different towers, both towers are filled with the mass of one pion.
4. Fit the towers with a gaussian + linear function and extract the location of the peak (see below.)
* * *
5. Using the mass peaks, calculation a correction factor for each tower, and apply this correction factor to the tower response (gains? I'm not sure.)
6. Repeat until desired level of precision is reached.
Plots
Good Tower:
Poor Statistics (Hope to improve w/ Transverse):
Poor Fit:
Spiked Fit (Chi^2 = 60/32 if you can't read it.)
A .pdf with all 4800 towers, and their fits can be found here. It is about 50 MB.
Along with the spin sorted yields and the polarization, the relative luminosity is important piece of the spin asymmetries and is measured by BBC and ZDC. The relative luminosity is primarily determined from the BBC data. The systematic uncertainty is determined from the comparison between BBC and ZDC.
here are some presentations from the run 8 trigger planning.
Collect documentation on run 9 here.
Goals
Statement of priorities for run
CAD projections for run 9
BTOW calibration thread and pages
Early polarimeter commisioning see links in March 5 pwg meeting.
Link to magnet cooldown.
JP threshold ADC->GeV and initial guesses link
500 GeV trigger list
500 GeV run ends ~noon on Monday April 13 2009. FOM collected 1.4pb-1 vs 2.5pb-1 goal (email).
First overnights at 200 GeV April 18 and 19.
Report on run to convenors 4/21/09
5/27/09 STAR magnet field reversed from direction previously.
Phil Pile planning meeting postings
Jamies trigger summary
Green = complete Red = currently critical
Run 9 500 GeV Commission plan (start of draft) Not necessarily time ordered
or prioritized
Establish collisions
Develop Minbias trigger
BBC
TCU
DSMs
BBC as lumi and polarimeter
Commission and test scalers
Look for analyzing power - need > 30%? pol
FMS triggers and commissioning
EMC commissioning
Need minbias trigger to start - pol irrelevant
Timing Scan
Need stable beam background conditions - 2nd half of store?
Guess 4 hrs? scan both at same time
need EEMC and BEMC experts available
1 day min. to produce and check
Requires fast offline production of data on short time scale
HV adjustments and calibrations
Needs timing scan complete and set
Need minbias trigger - "low" backgrounds
1hr of beam - 3 succesive days
day of analysis of each run
Need calo experts and analyzers
Polarimetry commissioning in addition to BBC
ZDC -
signals into DAQ/trg
establish trigger
5-10M events with P>25%
min 1 day of analysis - try to analyze from trigger data
Suggest optimized trigger
Longer run after seeing analysis of first data (~1 day)
Needs detector and analysis experts
VPD
signals into DAQ/trg
signals at scalers
runs parasiticaly
Time to have answer few shifts of beam over few days?
Needs detector and analysis experts
Commission high level calo triggers
Needs calibration steps done
set thresholds based on rate scans - needs 1/2 a store
check for an mask hot towers at L0 and L2
monitor and analyze for a day
check L2 algos
confirm all ready to go
need L2 experts, calo experts
Criteria to switch to longitudinal
Some polarimeter working well enough to measure transverse components
Sufficient data to evaluate alternate polarimeters
Priorities? Time ordering? What can go in parallel? What could
but is prevented from going in parallel due to overlap of people?
Carl has prepared a trigger description for 200 GeV.
The beam polarization of the proton beams is measured with a set of polarimeters at IP12.
Carbon polarimeters: fast measurement several times during a RHIC fill, two devices per beam
Hydron jet polarimeter: absolute polarization measurement with a polarized atomic hydrogen jet, for normalization of carbon devices
Detailed information on polarimetry and results are available from the RHIC spin webpage: wiki.bnl.gov/rhicspin/Polarimetry
Summary of results for the experiments: wiki.bnl.gov/rhicspin/Results
Details for the 2005 RHIC run (Run 5)
(Archived into Drupal from MIT servers in August 2008. Original analysis by Julie Millane and Bernd Surrow.)
*_polarization_new_spread.txt
Fill#, Time (CNI), Days (Days since 01/01/04) using Time (CNI), Time (CDEV), Year, Month, Day, Hour, Minute, Seconds, X90, err. X90, X45, err. X45, X, err. X, Y, err. Y, A (Analyzing power), err. A, P (Polarization), err. P, Energy (RHIC beam energy), RHIC P bit (RHIC CNI polarization status), CNI bit (RHIC CNI polarimeter status word)
*_fill_average.txt
Fill#, X, err. X, P (Polarization), err. P
*_polarization.txt
Fill#,x90,err-x90,x45,err-x45,x,err-x,ana,anae,beam energy,month,day,year,hour,minute,second, polarization, err-Polarization
*_summary.txt
timestamp, RunID, Fill#, x90, err x90, x45, err x45, x , err x, y, err y, analyzing powers, err analyzing powers, beam energy, cni starttimes, statuss, statusstrings, raw cni_starttimes, starttimes (slightly different from before), polarization, polarization error, date, time, check
Check: 99 - ok, != 99, not ok, not found in other data files
Polarization as a function of time
X-asymmetry as a function of time
X-asymmetry (flattop/injection)
Ratio of flattop/injection
Yellow X-asym time dependence for a given fill
Blue X-asym time dependence for a given fill
Yellow Polarization time dependence for a given fill
Blue Polarization time dependence for a given fill
Fill dependence
Analyzing Power
Analyzing power as function of time
Details for the 2006 RHIC run (Run 6)
(Archived into Drupal from MIT servers in August 2008. Original analysis by Julie Millane and Bernd Surrow.)
polarization as a function of time: February/March: Yellow Blue April: Yellow Blue May: Yellow Blue
X-asymmetry as a function of time: February/March: Yellow Blue April: Yellow Blue May: Yellow Blue June: Yellow Blue
Yellow/Blue X-asymmetry (flattop/injection):
Yellow X-asym time dependence for a given fill
Blue X-asym time dependence for a given fill Yellow Polarization time dependence for a given fill Blue Polarization time dependence for a given fill
Analyzing power as function of time Yellow Blue
The linked data files include the following information.
month, day, year, hour, minute, second,fill,runid,timestamp,x , errx,pol, errpol, energy, statusA, statusB,x90, errx90, x45, errx45,y, erry, ana, errana,cni_time, raw_time,starttime,stoptime,flagA
flagA: 99 - ok, != 99, not ok, not found in other dat files
runid, x, errx, polarization, err polarization
The statusB number refers to the following lines
The error calculation for the tables is
Charged pion analysis
Here's a fragmentation study looking at the ratio of reconstructed charged pion p_{T} and the event partonic p_{T} in PYTHIA. Cuts are
Error bars are just the errors on the mean partonic p_{T} in each reconstructed pion p_{T} bin. Next step is to look at the jet simulations to come up with a plot that is more directly comparable to a real data measurement.
This is a study of 2005 data conducted in March 2006. Ported to Drupal from MIT Athena in October 2007
Goal: Quantify the relationship between the z-vertex position and the bbc timebin for each event.
Procedure: Plot z-vertex as a function of trigger and bbc timebin. Also, plot distributions of bbc timebins for each run to examine stability. Exclude runs<=6119039 as a result. Fit each vertex distribution with a gaussian and extract mean, sigma. Plots are linked at the bottom of the page. See in particular page 8 of run_plots.pdf, which shows the change from 8 bit to 4 bit onlineTimeDifference values.
Timebin 12 had zero counts for each trigger. Summaries of the means and sigmas:
m | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
mb | 101.7 | 124.1 | 56.3 | 22.72 | -7.835 | -38.89 | -80.48 | -135.6 | - |
ht1 | 81.09 | 111.8 | 50.75 | 16.88 | -13.49 | -44.57 | -89.36 | -182.8 | - |
ht2 | 79.86 | 107.2 | 48.93 | 15.76 | -14.27 | -45.17 | -89.76 | -176.7 | - |
jp1 | 101.3 | 139.3 | 54.8 | 17.68 | -12.95 | -44.05 | -92.4 | -176 | - |
jp2 | 99.49 | 128.5 | 51.58 | 15.77 | -14.29 | -45.5 | -94.1 | -192.2 | - |
s | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
mb | 68.85 | 67.48 | 40.4 | 34.26 | 33.31 | 35.91 | 49.32 | 76.29 | - |
ht1 | 68.99 | 70.9 | 43.06 | 34.71 | 32.49 | 34.86 | 47.42 | 79.98 | - |
ht2 | 67.64 | 70.13 | 43.06 | 34.76 | 32.55 | 34.98 | 47.26 | 78.22 | - |
jp1 | 76.49 | 79.85 | 45.44 | 35.6 | 32.56 | 35.34 | 49.69 | 78.1 | - |
jp2 | 76.18 | 78.01 | 45.73 | 35.79 | 32.87 | 35.68 | 49.37 | 81.21 | - |
Conclusions: Hank started the timebin lookup table on day 119, so this explains the continuous distributions from earlier runs. In theory one could just use integer division by 32 to get binned results before this date, but it would be good to make sure that no other changes were made; e.g., it looks like the distributions are also tighter before day 119. Examining the vertex distributions of the different timebins suggests that using timebins {6,7,8,9} corresponds roughly to a 60 cm vertex cut. A given timebin in this range has a resolution of 30-45 cm.
These histograms plot the fraction of reconstructed charged pions in each pion pT bin arising from gg, qg, and qq scattering. I use the following cuts:
I analyzed Pythia samples from the P05ih production in partonic pT bins 3_4 through 55_65 (excluded minbias and 2_3). The samples were weighted according to partonic x-sections and numbers of events seen and then combined. StEmcTriggerMaker provided simulations of the HT1 (96201), HT2 (96211), JP1 (96221), and JP2 (96233) triggers. Here are the results. The solid lines are MB and are identical in each plot, while the dashed lines are the yields from events passing a particular software trigger. Each image is linked to a full-resolution copy:
Outdated or obsolete studies are archived here
Motivation:
The charged pion A_LL analysis selects pions from events triggered by the EMC. This analysis attempts to estimate the systematic bias introduced by that selection.
Conditions:
Plots:
Conclusion:
The BBC trigger has a negligible effect on the asymmetries, affirming its use as a "minimum-bias" trigger. The EMC triggers introduce a positive bias of as much as 1.0% in both asymmetries. The positive bias is more consistent in JP2; the HT2 asymmetries are all over the map.
This is a study of 2005 data conducted in March 2006. Ported to Drupal from MIT Athena in October 2007
eL_asymmetries.pdf
phi_asymmetries.pdf
I also increment 20 separate histograms with (asymmetry/error) for each fill and then fit the resulting distribution with a Gaussian. Ideally the mean of this Gaussian should be centered at zero and the width should be exactly 1. The results are in asymSummaryPlot.pdf
Finally, a summary of single-spin asymmetries integrated over all data. 2-sigma effects are highlighted in bold:
+ | MB | HT1 | HT2 | JP1 | JP2 |
Y | 0.0691 +/- 0.0775 | 0.0069 +/- 0.0092 | -0.0038 +/- 0.0126 | 0.0086 +/- 0.0104 | 0.0116 +/- 0.0069 |
B | -0.0809 +/- 0.0777 | -0.0019 +/- 0.0092 | -0.0218 +/- 0.0126 | 0.0067 +/- 0.0104 | -0.0076 +/- 0.0069 |
- | MB | HT1 | HT2 | JP1 | JP2 |
Y | -0.0206 +/- 0.0767 | -0.0193 +/- 0.0092 | -0.0158 +/- 0.0130 | -0.0035 +/- 0.0101 | 0.0061 +/- 0.0070 |
B | 0.0034 +/- 0.0769 | -0.0021 +/- 0.0092 | 0.0006 +/- 0.0130 | -0.0164 +/-0.0101 | -0.0147 +/- 0.0070 |
This is a study of 2005 data conducted in May 2006. Ported to Drupal from MIT Athena in October 2007
Hi jetters. Mike asked me to plot the charged track / pion asymmetries in a little more detail. The structure is the same as before; each column is a trigger, and the four rows are pi+/Yellow, pi+/Blue, pi-/Yellow, pi-/Blue. I've split up the high pt pion sample (2< pT < 12 GeV) and plotted single-spin asymmetries for timebins 7,8, and 9 separately versus pT and phi. The plots and summaries are linked at the bottom of the page.
2 sigma effects are highlighted in yellow, 3 sigma in red. There are no 3 sigma asymmetries in the separate samples, although pi-/B/JP1 is 3 sigma above zero in the combined sample. Here's a table of all effects over 2 sigma:
timebin
|
charge
|
trig
|
asym |
effect
|
8
|
+
|
HT1
|
Y |
+2.2
|
9
|
+
|
JP1
|
B | +2.07 |
9 | - | JP1 | B | +2.45 |
7-9 | - | JP1 | B | +3.15 |
If you compare these results with the ones I had posted back in March (First Look at Single-spin Asymmetries), you'll notice the asymmetries have moved around a bit for the combined sample. The dominant effect there was the restriction to the new version of Jim's golden run list. The list I had been using before had at least two runs with spotty timebin info for board 5; see e.g.,
http://www.star.bnl.gov/HyperNews-star/protected/get/jetfinding/355/1/1/1.html
and ensuing discussion. I'm in the process of plotting asymmetries for charged track below 2 GeV in 200 MeV pT bins and will post those results here when I have them.
Summary:
I associated charged pions from JP2 events with the jets that were found in these events. If a jet satisfied a set of cuts (including the geometric cut to exclude non-trigger jets), I calculated a deltaR from this jet for each pion in my sample. Then I split up my sample into near-side and away-side pions and calculate an asymmetry for both samples.
Jet cuts:
Note: all plots are pi- on the left and pi+ on the right
This first set of plots shows eta(pion)-eta(jet) on the x axis and phi(pion)-phi(jet) on the y axis. You can see the intense circle around (0,0) from pions inside the jet cone radius as well as the regions around the top and bottom of the plots from the away-side jet:
Next I calculate deltaR = sqrt(deta*deta + dphi*dphi) for both samples. Again you can see the sharp cutoff at deltaR=0.4 from the jetfinder:
Asymmetries
My original asymmetries for JP2 without requiring a jet in the event:
After requiring a jet in the event I get
Now look at the asymmetry for near-side pions, defined by a cone of deltaR<0.4:
And similarly the asymmetries for away-side pions, defined by deltaR>1.5:
Conclusions: No showstoppers. The statistics for away-side pions are only about a factor of 2 worse than the stats for near-side (I can post the exact numbers later). The asymmetries are basically in agreement with each other, although the first bin for pi+ and the second bin for pi- do show 1 sigma differences between near-side and away-side.
The goal of this analysis is to estimate the contribution to A_LL from particles that aren't charged pions but nevertheless make it into my analysis sample. So far I have calculated A_LL using a different dE/dx window that should pick out mostly protons and kaons, and I've estimated the fraction of particles inside my dE/dx window that are not pions by using a multi-Gaussian fit in each pt bin. I've assumed that this fraction is not spin-dependent.
pi- is on the left, pi+ on the right. Each row is a pt bin corresponding to the binning of my asymmetry measurement. The red Gaussian corresponds to pions, green is protons and kaons, blue is electrons. So far I've let all nine parameters float. I tried fixing the mean and width of the pion Gaussian at 0. and 1., respectively, but that made for a worse overall fit. So far, the fit results for the first two bins seem OK.
2 < pt < 4:I extracted the the integral of each curve from -1..2 and got the following fractional contributions to the total integral in this band:
pi- bin | pion | p/K | electron |
2-4 | 0.91 | 0.09 | 0.01 |
4-6 | 0.92 | 0.05 | 0.03 |
6-8 | 0.78 | 0.07 | 0.15 |
8-10 | 0.53 | 0.46 | 0.01 |
pi+ bin | pion | p/K | electron |
2-4 | 0.90 | 0.09 | 0.01 |
4-6 | 0.91 | 0.06 | 0.03 |
6-8 | 0.68 | 0.06 | 0.26 |
8-10 | 0.88 | 0.05 | 0.08 |
I repeated my A_LL analysis changing the dE/dx window to [-inf,-1] to select a good sample of protons and kaons. The A_LL I calculate for a combined MB || JP1 || JP2 trigger (ignore the theory curves) is
For comparison, the A_LL result for the pion sample looks like
I know it looks like I must have the p/K plots switched, but I rechecked my work and everything was done correctly. Anyway, since p/K is the dominant background the next step is to use this as the A_LL for the background and use the final contamination estimates from the fits to get a systematic on the pion measurement
I've included an Excel spreadsheet with currently assigned systematic errors as an attachment.
Select a trigger and charge combination to view QA summary plots. Each point on a plot is a mean value of that quantity for the given run, while the error is sqrt(nentries).
get_file_list.pl -distinct -keys 'orda(runnumber)' -cond 'production=P06ie,trgsetupname=ppProductionLong,sanity=1,tpc=1' -limit 0
This query yields 406 runs (3 with emc=0) which I process with star-submit-template. I'm using Murad's production of StJetSkimEvents to get all event-level info, so my chain is brutally simple: just StMuDSTMaker and a simple set of track quality cuts, viz.
/home/kocolosk/analysis/run6/may03
Once I've got these trees back at MIT I merge them with the jetSkimEvent trees using an index on (run,event) (see Common Analysis Trees). I also apply some more stringent cuts:
BJP1 (hardware & software & geometric) requirement, only use pions with dR > 1.5
fill yellow blue like unlike
7847 0.7681 0.4152 0.8136 0.2513
7850 0.0743 1.4901 1.1202 -0.9843
7851 -0.5521 -1.5695 -1.5313 0.7059
7852 -0.5546 -1.1228 -1.1148 0.4334
7853 -0.8047 2.7533 1.3496 -2.5720
7855 -0.1095 -1.0144 -0.7683 0.6419
7856 0.6243 -0.6925 -0.0455 0.9280
7858 1.3109 1.9636 2.3779 -0.4507
7863 0.6637 1.3537 1.3883 -0.4979
7864 0.2973 -0.8424 -0.3922 0.7972
7871 -1.7681 0.6963 -0.7669 -1.7202
7872 -1.4830 -0.4183 -1.2917 -0.7713
7883 0.7329 -0.4249 0.2105 0.8539
7886 0.4131 0.7406 0.8332 -0.2265
7887 0.8142 1.0339 1.3192 -0.1441
7896 -0.3938 -0.2628 -0.4542 -0.0927
7901 0.3990 0.0513 0.3428 0.2471
7908 -0.1043 -0.2753 -0.2721 0.1245
7909 0.2401 -1.4131 -0.8252 1.2060
7911 -1.8391 1.9288 0.0727 -2.6732
7913 -0.0822 0.7613 0.4930 -0.5827
7916 -0.3658 -1.9129 -1.5979 1.0991
7918 -1.1823 -0.9377 -1.5543 -0.1821
7921 -0.7642 1.2557 0.3598 -1.4019
7922 1.8057 0.0540 1.2658 1.2471
7926 -0.5481 -2.1827 -1.8897 1.1854
7944 0.0950 0.4734 0.4049 -0.2722
7949 -0.1770 0.6205 0.3156 -0.5489
7951 -0.2755 -0.0891 -0.2622 -0.1306
7952 2.2435 1.6046 2.8193 0.4314
7954 -1.2534 -0.5687 -1.2512 -0.4838
7957 -0.6056 -2.1501 -1.8931 1.1112
fill yellow blue like unlike
7847 -0.6434 2.3161 1.1484 -2.1363
7850 1.8693 -0.0728 1.2844 1.3589
7851 -1.2476 -1.4218 -1.9278 0.1198
7852 0.4635 -0.7461 -0.1245 0.9018
7853 0.2474 3.4829 2.6019 -2.3402
7855 0.6099 -0.3582 0.1694 0.7191
7856 -0.3472 -0.0663 -0.3147 -0.2412
7858 0.5772 0.0588 0.4406 0.3577
7863 1.2914 0.4583 1.2065 0.6182
7864 0.9606 -0.4055 0.3951 0.9624
7871 -1.6101 -0.2726 -1.3459 -0.9187
7872 0.5035 0.3827 0.6093 0.0966
7883 -0.7030 0.1324 -0.3950 -0.6150
7886 1.9632 1.2030 2.2793 0.5283
7887 1.1916 1.1695 1.7115 0.0042
7896 1.0944 -1.5376 -0.3071 1.8997
7901 -1.1326 -0.1455 -0.9498 -0.6828
7908 -0.1445 0.6122 0.3287 -0.5444
7909 -1.5394 -0.4124 -1.3598 -0.8080
7911 -2.4637 0.5309 -1.3758 -2.1097
7913 1.4852 -1.7004 -0.1439 2.2214
7916 1.3170 -1.4964 -0.1252 2.0055
7918 -0.0600 -2.4808 -1.8464 1.6679
7921 -0.6402 1.6446 0.6993 -1.5745
7922 -1.7100 -1.8694 -2.4555 0.1048
7926 -0.8854 -1.8649 -1.8962 0.7077
7944 0.7047 -0.3786 0.2404 0.7810
7949 -1.1675 0.2958 -0.6320 -0.9979
7951 -1.6275 0.5100 -0.7990 -1.4975
7952 1.3279 1.7884 2.2557 -0.3194
7954 -0.0209 -0.7787 -0.5861 0.5011
7957 2.2026 -1.9116 0.2045 2.9721
fill yellow blue like unlike
6988 2.8954 3.3548 4.2810 -0.3045
6990 -1.1356 0.0822 -0.7347 -0.8748
6992 2.2104 0.3517 1.9057 1.2493
6994 -0.3457 0.3976 0.0759 -0.6364
6995 0.0236 0.1136 0.1058 -0.0989
6997 0.6616 2.4959 2.2008 -1.2739
6998 -0.0607 0.5594 0.3556 -0.4868
7001 -0.2676 0.5874 0.2397 -0.6092
7002 -1.0157 -1.8627 -2.0789 0.4709
7032 -10.7190 9.6297 -0.9199 -13.3990
7034 2.6986 -1.2420 1.0235 2.7046
7035 -5.9795 5.8657 -0.0851 -8.3401
7048 -0.0177 -1.8298 -1.3617 1.2361
7049 -0.6182 -0.6846 -0.9274 0.0772
7051 1.2298 1.6795 2.1185 -0.3414
7055 0.7022 2.1289 2.0639 -1.0710
7064 -0.4975 1.9746 1.0530 -1.8834
7067 -2.7525 1.7490 -0.6884 -3.2186
7068 0.5999 -2.3405 -1.2244 2.1034
7069 1.6100 1.1541 1.9830 0.3217
7070 -0.0836 0.6656 0.4473 -0.4897
7072 0.1926 -0.7871 -0.3990 0.6684
7075 0.8745 -2.6544 -1.3421 2.4330
7079 0.1552 -1.5263 -1.0723 1.2324
7085 -0.0897 -0.2026 -0.2088 0.0906
7087 1.9237 0.4959 1.6501 1.0719
7088 0.3847 -0.4083 -0.0174 0.5569
7092 2.0581 -0.5933 1.0121 1.9479
7102 0.8406 0.3069 0.7570 0.5024
7103 -0.3106 -1.2057 -1.0763 0.6761
7110 2.6473 -0.2804 1.6718 2.0768
7112 1.5189 0.6019 1.4554 0.7426
7114 1.6817 0.9240 1.7917 0.5391
7118 -1.7624 0.7710 -0.5612 -1.6619
7120 -0.7654 0.2761 -0.2967 -0.7026
7122 0.0848 -0.6810 -0.3646 0.5913
7123 -1.6676 1.3976 -0.0291 -2.0208
7124 1.3759 -0.2691 0.6933 1.2215
7125 1.8810 -0.1630 1.1017 1.5199
7127 0.1055 1.6688 1.1933 -1.1824
7131 -0.1858 -0.0352 -0.2407 -0.1477
7133 0.8733 0.4679 1.0256 0.3223
7134 0.6636 -0.6857 -0.0360 0.9213
7151 -0.3299 -0.6315 -0.7004 0.2166
7153 -2.5741 -1.5110 -3.2579 -0.8339
7161 -0.9482 -0.8973 -1.2234 -0.1557
7162 -1.4261 -0.0548 -1.0450 -0.9047
7164 -0.2787 0.3688 0.1438 -0.5959
7165 0.1723 -1.3462 -0.7982 1.0477
7166 0.3072 2.2635 1.8098 -1.2695
7172 -0.6414 1.0035 0.2382 -1.1475
7237 0.8140 -1.9210 -0.7821 1.9362
7238 0.9147 0.1583 0.7514 0.5303
7249 0.8511 0.0570 0.6455 0.5322
7250 1.6782 -1.6771 0.1037 2.3099
7253 1.2592 0.8287 1.5859 0.2875
7255 -0.1376 0.1269 0.0300 -0.1948
7265 -2.7099 -1.0899 -2.5877 -1.2855
7266 -0.1283 0.7634 0.4338 -0.6211
7269 0.4862 -1.4204 -0.6823 1.3197
7270 -0.3694 -1.4968 -1.3117 0.7702
7271 2.1860 0.7501 2.0633 1.0176
7272 2.2742 -2.2593 0.0511 3.1922
7274 0.3692 1.9398 1.7348 -1.1304
7276 -1.9901 0.5043 -1.0389 -1.7776
7278 0.7444 -0.9791 -0.1687 1.2300
7279 -2.3442 0.9652 -0.9159 -2.3637
7300 -0.8765 1.6118 0.6363 -1.8350
7301 0.8553 -0.2668 0.3570 0.7616
7302 1.0808 -0.0070 0.7584 0.7798
7303 -0.7486 0.1757 -0.3854 -0.6549
7304 -0.7711 0.2501 -0.3825 -0.6815
7305 0.8851 0.7527 1.1938 0.0802
7308 -0.8466 0.7225 -0.0718 -1.1143
7311 0.2896 1.3780 1.1925 -0.7556
7317 -0.8703 -0.0998 -0.6921 -0.5361
7320 -1.3928 -2.0561 -2.4636 0.4663
7325 -0.9948 1.1141 0.0747 -1.5080
7327 -1.6448 0.1399 -1.0593 -1.2770
fill yellow blue like unlike
6988 1.5237 0.3259 1.3166 0.8438
6990 1.1388 -0.4585 0.5317 1.0481
6992 2.7809 1.8496 3.2777 0.6367
6994 0.4036 -0.0709 0.2152 0.3816
6995 0.0284 0.7506 0.5669 -0.5518
6997 -1.2708 1.5377 0.1390 -1.9290
6998 -0.2966 0.4639 0.1302 -0.4701
7001 0.8019 -0.9775 -0.1193 1.2528
7002 1.0862 -0.8451 0.1595 1.3065
7032 -7.2733 5.8628 -1.0782 -8.7338
7034 2.4731 -0.8650 1.1370 2.2900
7035 -5.7211 3.9134 -1.2690 -6.7932
7048 -0.9821 0.5199 -0.2484 -0.9325
7049 -2.4413 -1.6901 -2.8984 -0.5287
7051 0.1898 0.2886 0.3473 -0.0752
7055 2.4241 0.6951 2.2625 1.1398
7064 2.2608 -0.4958 1.2645 1.7928
7067 -0.9410 -0.7594 -1.1653 -0.2053
7068 0.2002 -0.1126 0.0601 0.2288
7069 0.6342 0.4304 0.7885 0.1599
7070 -1.2299 2.9297 1.2261 -2.8784
7072 -0.7843 1.6628 0.5990 -1.7002
7075 2.3895 -0.4305 1.3059 1.9201
7079 2.1971 -1.5796 0.3723 2.6978
7085 1.3459 -0.2317 0.7799 1.1367
7087 0.5258 0.2137 0.5551 0.1279
7088 -0.1856 -0.1438 -0.2435 -0.1064
7092 1.2742 -0.2971 0.6764 1.1774
7102 -0.1788 0.7376 0.3437 -0.5362
7103 -0.8089 0.0366 -0.5355 -0.6171
7110 2.6260 0.2961 2.0858 1.6233
7112 1.9199 -0.0349 1.3241 1.3657
7114 1.8546 0.6690 1.6611 0.8189
7118 -1.4017 0.8334 -0.4454 -1.6526
7120 -0.4001 -0.8129 -0.8129 0.3250
7122 0.5141 -0.2102 0.3512 0.6298
7123 -1.3042 1.8959 0.5395 -2.1551
7124 3.9571 0.3816 2.8666 2.6861
7125 -1.3947 0.3251 -0.8597 -1.3188
7127 2.2501 -0.6104 0.9831 2.1725
7131 -0.9200 -0.6472 -1.1191 -0.2102
7133 -1.1714 1.5062 0.0760 -1.9908
7134 0.6319 -1.4622 -0.6012 1.5632
7151 0.5372 -1.7916 -0.9108 1.6296
7153 -1.2329 0.7181 -0.3432 -1.3650
7161 1.3848 0.0689 1.0066 0.8943
7162 -2.3956 0.6038 -1.3699 -2.1493
7164 0.3508 1.6100 1.3783 -0.8174
7165 1.4134 -0.7712 0.4739 1.5248
7166 -0.3523 2.1152 1.2432 -1.6452
7172 -0.1923 3.1633 2.1209 -2.3379
7237 1.5778 -1.1650 0.2675 1.9640
7238 1.4628 3.2685 3.4046 -1.2492
7249 0.4261 0.1171 0.3816 0.2054
7250 1.2336 -1.0578 0.2506 1.5672
7253 0.6686 -1.3123 -0.3461 1.3663
7255 0.4010 0.1360 0.3899 0.1899
7265 0.1921 -1.1813 -0.6969 0.9601
7266 -0.6051 -0.5478 -0.8301 -0.0250
7269 0.1734 -0.5571 -0.2799 0.5063
7270 0.8825 -0.1983 0.4846 0.7612
7271 0.4453 -0.5304 -0.0492 0.6870
7272 -0.0131 -0.0176 -0.1003 0.0666
7274 2.5228 -0.2154 1.7141 1.8915
7276 -1.2212 2.1062 0.6034 -2.3542
7278 0.3318 0.0408 0.2745 0.1836
7279 -0.5121 -1.0690 -1.0773 0.3939
7300 -1.6321 0.7300 -0.6380 -1.6637
7301 -0.3916 -1.4341 -1.3355 0.7032
7302 1.4687 -1.3287 0.0978 1.9877
7303 0.4977 0.8000 0.8904 -0.2186
7304 -1.3292 -1.5037 -2.0497 0.1612
7305 0.2956 1.9077 1.6151 -1.1684
7308 -0.9212 -1.6537 -1.8057 0.5161
7311 0.0845 -1.0962 -0.7150 0.8359
7317 -2.3657 -0.6376 -2.1734 -1.1486
7320 -2.8559 1.1114 -1.2439 -2.7725
7325 0.3738 0.4026 0.5462 -0.0209
7327 -0.0750 -1.3466 -1.0211 0.8721
Update 2008-10-03: include the effect on A_{LL} from the uncertainty on the jet pT shift in the total point-to-point systematics.
Comparison to models obtained by sampling a_{LL} and parton distribution functions at the kinematics specified by the PYTHIA event:
Asymmetries are plotted versus the ratio of pion p_{T} and the p_{T} of the trigger jet.
Error bars on each histogram take multi-particle correlations into account when multiple pions from an event fall into the same bin. Here is the Δϕ distribution obtained from the data and compared to Monte Carlo:
Systematic uncertainties are dominated by the bias in the subprocess mixture introduced by the application of the jetpatch trigger. Uncertainty in the asymmetry of the PID background also contributes in the two highest z
bins. The full bin-by-bin systematic uncertainties are
π- = {9.1, 8.1, 6.1, 11.1} E-3
π+ = {14.8, 11.0, 6.6, 14.8} E-3
π- = {9.6, 9.5, 17.1, 14.9} E-3
π+ = {15.3, 13.0, 17.3, 21.8} E-3
I initially tried to estimate the bias from the JP trigger by applying the Method of Asymmetry Weights to PYTHIA. The next three plots show the Monte Carlo asymmetries after applying a) the minbias trigger, b) the jetpatch trigger, and c) the difference between a) and b):
a)
b)
c)
As you can see, the bias from this naïve approach is huge. It turns out that a significant source of the asymmetry differences is the fact that each of these bins integrates over a wide range in jet pT, and the mean jet pT in each bin is very different for MB and JP triggers:
We decided to factor out this difference in mean pT by reweighting the minbias Monte Carlo. This reweighting allows the trigger bias systematic to focus on the changes in subprocess mixture introduced by the application of the trigger. Here’s the polynomial used to do the reweighting:
Here are the reweighted minbias asymmetries and the difference between them and the jetpatch asymmetries:
The final bias numbers assigned using GRSV-STD are 6-15 E-3.
I calculate the background in my PID window using separate triple-Gaussian fits for π- (8.6%) and π+ (9.2%), but I assume a 10% background in the final systematic to account for errors in this fit:
Then I shift to a sideband [-∞, -2] and calculate an A_{LL}:
The relation between measured A_{LL} and the “true” background-free charged pion A_{LL} is
so the systematic uncertainty we assign is given by
and is ~9 E-3 in the highest bin, 1.5-4 E-3 elsewhere.
I used the corrections to measured jet pT that Dave Staszak determined by comparing PYTHIA and GEANT jets link to correct my measured jet pTs before calculating z
. The specific equation is
p_{T,true} = 1.538 + 0.8439*p_{T,meas} - 0.001691*p_{T,meas}**2
There is some uncertainty on the size of these shifts from a variety of sources; I took combined uncertainties from the 2006 preliminary jet result (table at http://cyclotron.tamu.edu/star/2005n06Jets/PRDweb/ currently lists the preliminary uncertainties). The dotted lines plot the 1σ uncertainties on the size of the jet pT shift:
Next I used those 1σ pT shift curves to recalculate A_{LL} versus z
. The filled markers use the nominal pT shifts. The open markers to the left plot the case when the size of the shift is large (that is, the 1σ corrected jet pT is lower lower than the nominal case, which causes some migration from nominally higher z
into the given bin). The open markers to the right plot the case where the shift is small (corrected jet pT closer to measured).
In short: low markers represent migration from lower z
, high markers represent migration from higher z
.
No assignment of systematic at the moment. If I were to assign a systematic based on the average difference between the nominal and min/max for each bin I’d get
I assign a systematic based on the average difference between the nominal and low/high for each bin; this ends up being 3-16 E-3.
Murad’s detailed documentation
A pT-independent systematic uncertainty of 9.4 E-4 is assigned.
Analysis of beam polarization vectors leads to tan(θB)tan(θY)cos(ΦB-ΦY) = 0.0102
. I calculated an Aσ from transverse running:
The small size of the non-longitudinal beam components mean that even the Aσ in the case of π- leads to a negligible systematic on A_{LL}. A pT- and charge-dependent systematic of 1.4-7.3 E-4 is assigned.
The following are summary results (val ± err and χ2) from straight-line fits to single-spin asymmetries versus fill:
π- | val ± err | χ2 (37 d.o.f.) |
Y | -4.8 ± 3.0 | 63.74 |
B | 0.8 ± 3.1 | 34.46 |
L | 6.7 ± 7.4 | 46.21 |
U | 9.9 ± 7.5 | 52.51 |
π+ | val ± err | χ2 (37 d.o.f.) |
Y | -1.2 ± 2.9 | 53.65 |
B | 0.5 ± 3.0 | 43.45 |
L | 3.2 ± 7.2 | 55.03 |
U | 2.0 ± 7.3 | 41.72 |
There’s a hint of an excess of uu and/or ud counts for π-, but no systematic is assigned.
Primary authors: Salvatore Fazio, Dmitri Smirnov, and Elke C. Aschenauer
When protons accelerated by RHIC collide at the Z and W bosons can be produced and their decay products measured at STAR. In this analysis we measure the asymmetry of the W (and Z) bosons produced in pp collisions with the spin of the protons perpendicular to the beam (transverse polarization). During the 2011 run STAR has collected such data for the first time. The bosons cannot be detected directly but their kinematics can be reconstructed by detecting the decay products. The Z bosons can be easily reconstructed in the di-electron channel. However, the reconstruction of the W's decaying into a eνe pair is challenging due to the undetected neutrino. The W has never before been reconstructed with the STAR detector. This analysis is the first attempt to reconstruct the kinematics of the W bosons at STAR.
The latest version of the analysis note is available from File:Vbasym.pdf
The code for this analysis can be pulled from a CVS repository as:
cvs co -P -d WeakBosonTSSA offline/paper/psn0624
alternatively the code can be cecked from a github repository at https://github.com/plexoos/vbasym as:
$git clone git@github.com:plexoos/vbasym.git
The code heavily depends on the STAR libraries. It is verified to compile on the STAR cluster with the STAR environment. Before you can build and run the program, all the enviroment variables must be properly set. Please refer to the README file within the code's main directory or to the analysis note for more information on how to do it.
To compile the code one can do:
$cd vbasym $starver SL12c $cons $make stana $make vbana
The make command will produce standalone executables stana and vbana.
First one needs to reconstruct jets with stana as
$./stana -f filelist.lis -j
If the jet files are in the current directory one can run the analysis code as
$./stana -f filelist.lis
There is a job template available for running jobs on the farm. We use the following script to submit jobs
$./scripts/submit_jobs.sh
to check out transversely polarised pp2pp runs for the 2011 data taking year:
$get_file_list.pl -keys 'path,filename' -cond 'path!~long,filename~st_W,production=P11id,filetype=daq_reco_mudst,storage=hpss ' -limit 0 -delim '/'
The root file with the tree can be navigated after loading the appropriate libraries:
gROOT->LoadMacro("$STAR/StRoot/StMuDSTMaker/COMMON/macros/loadSharedLibraries.C"); loadSharedLibraries(); gSystem->Load(".sl53_gcc432/lib/libutils.so"); gSystem->Load(".sl53_gcc432/lib/libStVecBosAna.so"); TFile *_file0 = TFile::Open("R1210603X_test.Wtree.root")
Available at DIS 2014 preliminaries
Available at 2017 projections plots
Available at Paper Proposal page
The current version of the analysis note is available here
A collection of the latest results for the asymmetry including blue and yellow beam asymmetries extracted separately, asymmetries from the geometry and luminosity effects, asymmetries calculated from the decay lepton and all the sin(phi) modulations fits can be downloaded here
Results can also be easily accessed via a web interface at the following page:
http://www.star.bnl.gov/~fazio/vbasym/webview/
This page should give
-location
-documentation of branches
-example code (MC/Data)
-Jet algorithms
-Trigger Bias studies (can be links to specific analysis)
-
Progress of 2009 data analysis for W measurement
runs 10076136,152,153,154,161, only W-stream
Fig 1. Raw EMC spectra for BHT3 thr=30 & L2W >13 GeV, day 76
Fig 2. Z-vertex for good tracks
Fig 3. Frequency of towers with ET>5 GeV, 66 runs from days 76-81. All input BHT3 events are considered. Ideal gains are used. Note, Z-scale does not start form zero to visualize low-gain towers. Nominally there are 4 hot masked towers + 3 towers have bad pedestals. Y-axis is aligned with West TPC sectors, counting 0-11.
Fig 4. Seed tower distribution for 2x2 cluster ET within range. Only events accepted by L2W (cluster ET>13 GeV) are considered. Ideal gains are used. The same 66 runs from days 76-81 as in fig 3.
Daq files with W events were reco w/ BFC "pp2009a ITTF BEmcChkStat QAalltrigs btofDat Corr3 beamLine -VFMinuit VFPPVnoCTB -dstout -evout"
Event cuts:
Fig 1, day 76, runs 10076136,152,153,154,161
Fig 2, day 85, runs 10085132,133,136
Fig 3, day 86, ~20 runs , only L2W triggered events, bottom plots show only tracks with PT>1.0 GeV
att 1) all W-events for ~300K from days 76-89
att 2) one fill from day 83, 34K W-events, I think BPRS peds were not subtracted for some runs, page 7
att 3) half of fill in day 90, 6K W-events
This is working document for 2011 W AL analysis
The human-QA of 2011 W data was performed using criteria described here and the table of all pp-long 163 runs is in att A)
Among the 163 runs, there are 13 runs (list below) without MuDst files . The Integral luminosity of all the 163 runs is 10.01 1/pb and the integral luminosity of the 13 runs is 0.6 1/pb.
12101046
12101064
12102032
12102044
12102045
12104003
12104004
12104005
12104006
12104010
12105003
12107001
12107036
The automatic run QA, similar to that used for 2012 data has been performed.
This is Jamie's plots for Run 11 longitudinal: Luminosity and FOM
After the auto QA , 7 runs were rejected. The final run list with 143 run is in att B)
The requested events of Zerobias for every run is equal to all the requested events of run11 (12,000) assigned into every run according to their lumi weight . Attachment A) is the runlist with zerobias requested events. 2 runs (12103016 12107014) with too low request events were skipped.
The Library used is SL11d.
The BFC chain options:
DbV20110923 pp2011a btof mtddat fmsdat VFPPVnoCTB beamline -evout BEmcChkStat Corr4 OSpaceZ2 OGridLeak3D -hitfilt