Particle Tracking Data: Bergen DTC Prototype

Dataset Description: Proton computing tomography is an imaging modality promising improved treatment planning for proton therapy. For this application, the Bergen pCT collaboration is developing a high granularity Digital Tracking Calorimeter (DTC), capable of measuring high multiplicities of particles in parallel [1]. In this dataset, we include various Monte Carlo (MC) simulations (generated using the Gate 9.2 simulation toolkit [2, 3] built upon Geant4 [4,5,6]) with different setups and phantom materials for evaluating and comparing particle reconstruction algorithms on the Bergen DTC. Files: We provide multiple simulations for different phantom geometries and simulation setups, each generated with a mono-energetic pencil beam (230 MeV, 2 sigma). The supplied files include a spot scanning dataset generated for a pediatric head phantom [7], spot scanning on water phantoms (100, 150 and 200 mm) as well as single beam spots for water phantoms of various thicknesses (0, 100, 150 and 200 mm): head_filtered_2k_spot.npz water_{100,150,200}_2k_spot.npz water_{100,150,200}_10k.npz no_phantom_10k.npz Columns: All above-mentioned simulation files contain MC simulated data of a single simulation run in tabular form, where each row represents a single particle hit inside the detector. Furthermore, each particle hit is parametrized by the following columns: posX, posY, posZ: Measured x, y, z position (in millimeter) of the particle hit relative to the simulation origin defined by the center of the phantom. edep: Amount of energy (in MeV) deposited by a particle while interacting with the sensitive area of the detector. eventID: Each primary is simulated in its own isolated "event" and gets an incremental ID. Everything that happens during the simulation of said primary is grouped under the same eventID. Events are simulated independent of each other. trackIDs are only unique within their respective event. trackID: A track describes a single particle throughout its entire lifetime in the simulation. In any given event, the first track (trackID = 1) is always associated with the primary particle. Every subsequently produced secondary particle has an incremental trackID. parentID: The parentID specifies the trackID in the current event that caused this track to exist. If the parentID is 0, the particle is a primary, i.e., generated by the particle beam. Otherwise, the row describes a secondary which was generated through interactions of a primary with the traversed matt