Difference between revisions of "FY2022 PID analysis"
From solidwiki
(Created page with "<pre> This is code and document for 2022 beamtest PID analysis Darren's PID code: ???? Spencer's traditional PID code: Pencil Beam code: TS3_Pencil_Beam_PID.ipynb Full Sim C...") |
|||
| Line 1: | Line 1: | ||
<pre> | <pre> | ||
| − | + | general software for FY2022 beamtest | |
| + | |||
| + | real data decoder https://github.com/JixieZhang/beamtest_hallc_decoder | ||
| + | real data decoder with maroc https://github.com/zhaozhiwen/beamtest_hallc_decoder | ||
| + | real data analysis ??? (Ye and Michael can add more) | ||
| + | sim and analysis https://github.com/JeffersonLab/solid_gemc/tree/master/prototype/ec_pro/HallC2022 | ||
| + | |||
| + | </pre> | ||
| + | |||
| + | <pre> | ||
| + | code and document for 2022 beamtest PID analysis | ||
Darren's PID code: | Darren's PID code: | ||
| − | + | (Zhiwen will add more details) | |
Spencer's traditional PID code: | Spencer's traditional PID code: | ||
| Line 13: | Line 23: | ||
Full Sim: ?? | Full Sim: ?? | ||
Background events: ?? | Background events: ?? | ||
| + | (Ye can add more) | ||
csv file location at /work/halla/solid/dwupton/Beamtest/ | csv file location at /work/halla/solid/dwupton/Beamtest/ | ||
| Line 30: | Line 41: | ||
=== how to merge background in sim ============ | === how to merge background in sim ============ | ||
| − | here is an example what | + | here is an example what Zhiwen think how to merge signal and background in sim |
// 1.assume beam current 15ua and 50ns time window. we have 15e-6/1.6e-19*50e-9=4.7e6 beam e- within 50ns time window | // 1.assume beam current 15ua and 50ns time window. we have 15e-6/1.6e-19*50e-9=4.7e6 beam e- within 50ns time window | ||
// 2.assume the background "beamontarget" sim file is from 1e10 e- with 10x actual target density and it has 1e5 number of events with hits in at least one detector. | // 2.assume the background "beamontarget" sim file is from 1e10 e- with 10x actual target density and it has 1e5 number of events with hits in at least one detector. | ||
Revision as of 14:14, 2 November 2023
general software for FY2022 beamtest real data decoder https://github.com/JixieZhang/beamtest_hallc_decoder real data decoder with maroc https://github.com/zhaozhiwen/beamtest_hallc_decoder real data analysis ??? (Ye and Michael can add more) sim and analysis https://github.com/JeffersonLab/solid_gemc/tree/master/prototype/ec_pro/HallC2022
code and document for 2022 beamtest PID analysis Darren's PID code: (Zhiwen will add more details) Spencer's traditional PID code: Pencil Beam code: TS3_Pencil_Beam_PID.ipynb Full Sim Code: Sim_Full_PID.ipynb solid gemc beamtest sim output file at /cache/halla/solid/sim/solid_gemc/ec_pro_JLAB_VERSION_2.5/pass1/18deg_reduce/ Pencil Beam: ?? Full Sim: ?? Background events: ?? (Ye can add more) csv file location at /work/halla/solid/dwupton/Beamtest/ Pencil Beam: Pencil_Beam/Sim_CSV/Sim_Pencil_AllEvents_TID1.csv Full Sim: Full_ML/Sim_CSV/FullSim_WithTracking.csv Full sim, extra pi-: Full_ML/Sim_CSV/pim_more_All_new.csv Background events: Full_ML/Sim_CSV/BeamOnTarget.csv Spencer Opatrny working dir and report /w/halla-scshelf2102/solid/sopatrny/Spencer_Summer_2023 https://solid.jlab.org/cgi-bin/public/ShowDocument?docid=496 Darren Upton's working dir and report /work/halla/solid/dwupton/Beamtest https://solid.jlab.org/cgi-bin/public/ShowDocument?docid=495 === how to merge background in sim ============ here is an example what Zhiwen think how to merge signal and background in sim // 1.assume beam current 15ua and 50ns time window. we have 15e-6/1.6e-19*50e-9=4.7e6 beam e- within 50ns time window // 2.assume the background "beamontarget" sim file is from 1e10 e- with 10x actual target density and it has 1e5 number of events with hits in at least one detector. // 3.beamontarget file has 1e10/4.7e6 = 2128 number of time window. // 4. for each signal particle in sim, we should add 1e5/10/2127=5 background event from beamontarget file randomly for every detector channel, then output in csv // 5.for GEM, we need to use 300ns time window. all other detector use 50ns. so GEM needs to add 6 time more background events for each signal event
