Summary of “LArTPC Reconstruction Assessment and Requirements Workshops” Amir Farbin UTA
D Context a v Origins of the two contiguous workshops i d M a c F a • Reconstruction assessment workshop: r l a n e – Requested through the Fermilab PAC by the Long-Baseline • Link: https:// Neutrino Committee (LBNC) as a first step along a path of focusing community attention on automated reconstruction in indico.fnal.gov/ LAr TPCs conferenceDisplay.py? • Requirements workshop: confId=10394 – Community-led effort to collectively put together a shared goal of setting overall requirements for a LAr eco-system of software, hardware, and computing to guide work over the next few years • Prompted by LBNC – While strongly encouraged by the LBNC, bottoms up is a much better approach! • Two goals are tightly connected and the LBNC would like to • Actually 2 workshops PAC feedback on the SBN program from June 2015 see ownership of the outcomes by the community • Concerned about: • LBNC Mandate Expanded – Pace at which automated LAr reconstruction is developing, to LBN and SBN despite being absolutely crucial to the SBN and LBN programs – Slow progress in coordinating the analysis across the three • Primary organizer Ruth experiments, which is critical to the success of the SBN program and required for Stage 2 approval Pordes with – Very aggressive SBN schedule with little flexibility representatives from • Recommended that Fermilab continues: nearly all LArTPC – Monitoring progress on achieving automated event experiments… reconstruction – Providing relevant resources and expertise towards catalyzing this effort, since it is critical to quickly demonstrate the capabilities of the LArTPC technology.
D a v i d M a LBNC comments on DUNE Far Detector (FD) Task Force c F a r l a n e • Comments from Sept review • LArTPC Reco must meet – The LBNC notes that the 80% efficiency for automated assumptions made for DUNE reconstruction for quasi-elastic, resonant elastic scattering and reach. deep-inelastic scattering events is a key assumption in the projected physics reach of DUNE. Much progress in demonstrating this capability should be accomplished by the TF • Full Simulation and Automatic within the next 18 months. reconstruction for CD-2 – An important part of the FDTF planning would be to lay out a common understanding of the level of reconstruction • Need a thorough assessment sophistication needed at various stages during the 18 months and then beyond through the DUNE design phase leading up to for CD-2 CD-2 • A comprehensive summary of the current status of and future plans for further development of automated reconstruction – Timeline, milestones, deliverables and level of effort required for efforts: further development; – Basic physics information, such as event classes and – Linkages to hardware system development and experience with topologies, backgrounds for each experiment, performance neutrino and test beam data requirements, etc.; – Assessment of areas of commonality with other SBN or LBN – Current state-of-the-art, including quantified performance of the experiments; and reconstruction; – Assessment of resource limitations and impact of bringing additional targeted help, either from Fermilab or in cooperation – Leadership for the current effort and the level of effort across with other science collaborations. the collaboration; – Degree to which the effort relies on common software tools, such as analysis framework development, etc. and their further development;
Assessment Workshop
ArgoNeuT • Long list of accomplishments/ Tingjun Yang measurements: • Tracking, calorimetry, shower • ArgoNeuT was the first user of LArSoft after Brian reco, PID, … Rebel et al. started this project. • Example: Full Auto redo for inclusive CC x-section • Pioneered in development and validation of • 42%/59% off for neutrino/ simulation and reconstruction tools. antineutrino • Physics analyses done using LArSoft. • 5-10% Energy resolution • 1 degree angle resolution Topological Analysis 1 µ +Np • A first Topological analysis is developed by the ArgoNeuT experiment: 1 µ +Np (0 π ) - Sensitive to nuclear effects • Visual scanning for - Observation of back-to-back proton pairs PRD 90, 012008 (2014) some analyses • Analysis steps - automated reconstruction (muon angle and momentum) - visual scanning - hit selection Proton/angle/and/momentum - automated track and calorimetric reconstruction • Background (pion) removed
e C • The relatively small number of recorded CNGS neutrino interaction ICURUS . F A R events (~3000) allowed a semi automatic approach based on a pre- N E S E selection of events followed by a careful visual analysis of all physically interesting data; the reconstructed objects can be saved/modified • Highlighted the using a flexible ROOT-based I/O system • The developed software framework is based on: importance of a " Central package (fullreco) for data decoding, basic reconstruction powerful event " Qt-based event display (Qscan) for visualization/scanning and display + hand human interface scanning tool. " Event loop code (AnalysisLoop) for batch analyses and ROOT I/O " Higher-level analysis tools (Muon momentum by MCS, EM shower reconstruction, particle identification, 3D reconstruction…); • QScan Demo " Interface with FLUKA for analysis/visualization of simulated events; • Qscan is a qt-based tool for a fast visualization of events in the T600: " Interface with mySQL for access to DB; " the 2D projections associated to the wire planes are shown using a grey/color scale based on signal height/deposited energy; " the waveforms of wires and PMT signals can be displayed and fast Fourier transform tool available, useful for noise monitoring ~4.5 m ~7 GeV deposited energy 1.5m drift Typical ν µ CC event (Collection view) muon is ~13m long ICARUS_2015 Slide# : 9 Typical MIP signal in Coll .
T MicroBooNE r a MicroBooNE Commissioning c y U s h e r • Bringing complex detectors online for the first time is rarely a smooth process • Reminded us In particular, there are almost always surprises • that noise can • Two issues directly impacting reconstruction significantly Dead channels • increase data Tend to be in groups as opposed to the assumed isolated dead channels one might have studied in • developing algorithms volume… Noisy channels with several different signatures • “zig-zag” - high frequency tick-to-tick oscillations in randomly distributed short bursts • “correlated” - low frequency (~20 kHz) correlated across wires • “chirping” - transient issue, switching between “dead” and “live” with large baseline excursions • “high noise” - steady state very high rms noise - effectively dead channels for recon • Noise Run Event - Unfiltered • Redirection of reconstruction resources to address these issues Commissioning run data - Run 2728 Drift Time (ticks) Attacking noise issues by developing algorithms aimed at filtering out as much noise as possible • Conditions: 2 μ s shaping time, gain 14 mV/fc, 70 kV field Developing more sophisticated channel status information mechanism • Pattern recognition algorithms will need to be able to handle gaps with no information • Collection Plane 13 Drift Time (ticks) Middle Induction Plane Drift Time (ticks) First Induction Plane Wire Number
LArIAT f a V1751 data a LINING UP FRAGMENTS R V1740 data n e J MWPC data Clock reset at beginning of LArIAT supercycle • Reminded us the importance of timing across Apply clock Clock Time corrections different detectors…. RAW DATA STRUCTURE (Divide “spill” block into multiple “events,” where each event has a single trigger )
Pandora BNB ν μ CC RES μ , p, π 0 : Combined display ! Track particle: primary daughter of • Impressive neutrino performance… μ γ Shower particle: • Don’t forget Pandora primary daughter of Track particle: neutrino primary daughter of gives fully recoed neutrino p topologies in PFParticle. Shower particle: primary daughter of 3D neutrino neutrino interaction vertex γ Output to LArSoft: ! Parent Daughter(s) PFParticle PFParticle Two layers of ! ART associations ! PFParticle First layer: SpacePoint Cluster Track Vertex Seed (3D hit) (3D vertex position (3D vertex (3D trajectory) and direction) position) Second layer: Hit
Requirements
Organization • 4 x 4 Simultaneous sessions, each on one topic. • Participants rotate through all topics. • Roles assigned: • Leader • Scribe • Note taker • Document Editted live on Overleaf
Recommend
More recommend
