ProtoDUNE detector reconstruction stability Yongshun Zhou Aleena Rafique 1
Data Samples • Good beam run 5141-5844: (https://docs.google.com/spreadsheets/d/1O4o9_q8F-KynQltKDAfmco3e_s1eKItFkzZ4-g_Vls0/edit#gid=0) • Dataset name: np04_full-reconstructed_v07_08_00_unified_physics • • Cosmics run 5000-9000: • Runs tagged by “cosmics” during good beam runs (5000-5850) • Runs in the following dataset (np04_full-reconstructed_v07_08_00_05_cosmics) (http://samweb.fnal.gov:8480/sam/dune/api/definitions/name/np04_full-reconstructed_v07_08_00_05_cosmics/) • • 1 GeV/c beam+cosmics MCC11 is included in all plots Dataset name: jhugon_mcc11_pd_sp_reco_sce_1.0GeV • The same MC is used for both good beam run and cosmics run • 2
Data analysis • Module scripts are taken from MicroBooNE experiment • (https://microboone.fnal.gov/wp-content/uploads/MICROBOONE-NOTE-1013-PUB.pdf) • 10 reconstructed data files are chosen from each good beam run • Contain about 100 data events per file • The module gets the target mean/RMS over all events in each run à mean/RMS of a run for a given variable is plotted 3
Reconstructed quantities • Track related: • Optical flash related: • Number of tracks • Number of opflashes • Track length • Opflash peak amplitude • Track position • Opflash center (y/z) (begin/end, x/y/z positions) • Opflash width (y/z) v Comparison between pmtrack and pandoraTrack v Comparison between internal and external opflashes • Hit (linecluster hit) related: • Others: • Number of hits • Number of vertices (pmtarck/pandora) • Hit peak amplitude • Number of PFPs (pmtarck/pandora) • Hit charge • PandoraShower 4
Number of tracks Good Beam Run Notice : • A “sudden drop” as beam momentum is changed from 7GeV/c to 1 Gev/c • Average track number per event is slightly increasing during 1GeV/c beam runs • The actual pmtrack data diverges a lot from the pmtrack MC data. 5
Number of tracks Cosmics Run Notice : • Several “Vertical” lines. Caused by the wrong “cosmics” tags. • They are test runs with high trigger rate. • Relatively stable after around run 7500 (around 3/31/2019) 6
Track Length Good Beam Run Notice : In real data, PandoraTrack has longer tracks • than pmtrack In MC, pmtrack has longer tracks than • pandoratrack Overall stable • Length distribution of a single run analysis : run 5455 7
Track Length Cosmics Run Notice : • Similar pattern as in plots of number of tracks for cosmics run 8
Track X begin position Good Beam Y Run Z Overall Stable 9
Track X begin position Cosmics Run Y Overall stable except for the weird data points Z as corresponding to previous “vertical” lines. 10
Track X end position Good Beam Y Run Z Overall Stable 11
Track X end position Cosmics Run Y Overall stable except for the weird data points Z as corresponding to previous “vertical” lines. 12
Number of hits Good Beam Run Notice : • A similar drop from 7Gev/c to 1Gev/c • A similar increasing pattern in 1GeV/c region • Stable after around run 5429 (10/17/2018) 13
Number of hits Cosmics Run Notice : • Similar pattern as in plots of number of tracks for cosmics run 14
Hit peak amplitude Good Beam Run Notice : • Increasing pattern before run 5429 (10/17/2018); stable after that • In 6GeV/c beam runs, RMS is very unstable and big • V-plane data is the highest, while V- plane MC is the lowest 15
Hit peak amplitude Cosmics Run Notice : • Similar pattern as in plots of number of tracks for cosmics run 16
Hit charge Good Beam Run Notice : • Similar pattern as hit peak amplitude, which is reasonable • Seems like there is a gradual increase in hit charge overall • V-plane data is the highest, while V- plane MC is the lowest 17
Hit charge Cosmics Run Notice : • Similar pattern as in plots of number of tracks for cosmics run 18
Notice : Number of Opflashes • Int opflash data is unstable before run 5429 (10/17/2018), and stable after that Good Beam Run • Most optical flashes have high peak amplitude 19
Notice : Number of Opflashes (At the end of March 2019) Around run 7350-7500, flash data is abnormal; overall stable after that • Cosmics Run • Around 7350-7500, telescope test runs are wrongly tagged by “cosmics”. 20
Notice : Opflash peak amplitude Similar pattern as in plots of number of opflashes for good beam run • Good Beam Run External opflashes have much larger peak amplitude (notice the 10 3 ) • 21
Notice : Opflash peak amplitude Abnormal data around run 7350-7500 • Cosmics Run 22
Notice : Opflash y center Good Beam Run • Similar pattern as in the previous one for good beam run 23
Notice : Opflash y center Cosmics Run • Abnormal data around run 7350-7500 24
Notice : Opflash z center Good Beam Run • Similar pattern as in the previous one for good beam run 25
Notice : Opflash z center Cosmics Run • Abnormal data around run 7350-7500 26
Notice : Opflash width Similar pattern as in the previous one for good beam run • Good Beam Run External opflashes have larger width, which is reasonable • 27
Notice : Opflash width Abnormal data around run 7350-7500 • Cosmics Run 28
Number of vertices Good Beam Run Notice : • Similar pattern as number of tracks and hits for good beam run 29
Number of vertices Cosmics Run Notice : • Similar pattern as in plots of number of tracks for cosmics run 30
Number of PFPs Good Beam Run Notice : • Similar pattern as number of tracks and hits for good beam run 31
Number of PFPs Cosmics Run Notice : • Similar pattern as in plots of number of tracks for cosmics run 32
Number of showers Good Beam Run Notice : • Similar pattern as number of tracks and hits for good beam run • The number of showers is relatively large. 33
Number of showers Cosmics Run Notice : • Similar pattern as in plots of number of tracks for cosmics run 34
Shower length Good Beam Run Notice : • Overall stable • Slight decreasing pattern in RMS 35
Shower length Cosmics Run Notice : • Similar pattern as in plots of number of tracks for cosmics run 36
Summary and discussion Good beam run • Something should have happened after around run 5429, when beam momentum is changed from 1GeV/c to others. Data of hits, internal optical flashes, vertices, PFPs and showers all share a similar improvement in stability after that. • In Elog, we found that after run 5387, problems with CRT emerged. Several test runs were initiated without beam after that. Before run 5423, many software upgrades were also completed, and beam was back. • During 1GeV/c beam run, data of all mentioned also share a similar increasing pattern. • On 10/13/2018, the purity of liquid argon was relatively low (on average 2.7ms); it gradually changed back to 4.3ms on average on 10/17/2019. This could be a potential cause. • From 7GeV/c beam run to 1 GeV/c beam run, a sudden “drop” is noticed quite often, too. • Beam momentum change should be the main reason. • In Addition, before run 5213, which was before beam momentum change, high voltage of cathode plane changed from 180kV to 130kV. 37
Summary and discussion Cosmics run • Around run 7350-7500 (3/29/2019-3/31/2019), optical flash data was abnormal. • Runs around that range were telescope runs, causing optical flash data to be unstable; they should not be tagged as “cosmics”. • Several “vertical” lines are noticed in most plots. That’s around run 5751 (11/01/2018), run 5850 (11/12/2019) and run 6509 (01/22/2019). • In Elog, it turned out that these runs should all be test runs rather than cosmics runs; tagging is a little messed up. The “vertical” line in data was caused by CRT problem: trigger rate was too high. 38
Conclusions and to do • The detector stability script works well for checking the stability of ProtoDUNE-SP detector over runs • Some problems are detected, and potential reasons for unstable data can be checked via Elog • Some tags for the data file are messed up • We can further check MC for with other beam momentum, and compare them with the data • We can also look into other reconstruction algorithms, and check the stability for them Thanks! 39
Appendix—Single run analysis • Good beam run corresponding date • Data from all events in run 5455 included • Direct plot—no calculation of mean included • Variables included: • Track position (begin y, end y, begin z, end z) Vs. Track length • Internal optical flash center (y center, z center) Vs. flash peak amplitude 40
Good beam run corresponding date Run Range Corresponding Date Corresponding Beam Momentum 5141-5213 10/10/2018-10/12/2018 7 GeV/c 5216-5426 10/12/2018-10/19/2018 1 GeV/c 5429-5452 10/19/2018-10/23/2018 2 GeV/c 5455-5460 10/23/2018-10/24/2018 1 GeV/c 5461-5757 10/24/2018-11/01/2018 No Good Beam Run 5758-5776 11/01/2018-11/04/2018 6 GeV/c 5777-5797 11/04/2018-11/07/2018 3 GeV/c 5800-5824 11/07/2018-11/09/2018 Random 5825-5833 11/09/2018-11/10/2018 0.5 GeV/c 5834-5841 11/10/2018-11/11/2018 0.3 GeV/c 41
Recommend
More recommend
