Warning, /juggler/README.md is written in an unsupported language. File is not indexed.
0001 [TOC]
0002
0003 # Project Juggler
0004
0005 Concurrent event processor for NP experiments, based on the Gaudi framework.
0006
0007 Dependencies:
0008 - v5.x requires Gaudi v36+, ACTS v15.1+, DD4hep 1.17+, NPdet v1.0+ and eicd v1.1+
0009 - v4.x requires Gaudi v36+, ACTS v13+, DD4hep 1.17+, NPdet v1.0+ and eicd v1.1+
0010 - v3.6 requires Gaudi v36+, ACTS v13+, DD4hep 1.17+, NPdet v1.0.0 and eicd v0.9.0
0011 - v3.5 requires Gaudi v36+, ACTS v13+, DD4hep 1.17+, NPdet v0.9.0, eicd v0.8.0
0012 - v3.4 requires Gaudi v36+, ACTS v8.2+, DD4hep 1.17+, NPdet v0.9.0, eicd v0.8.0
0013 - v3.0 requires Gaudi v35+, ACTS v8.1+, DD4hep 1.17+, NPdet v0.7.0 eicd v0.5.0
0014 - v2.0 requires Gaudi v35+, ACTS v8.1+, DD4hep 1.17+ and eicd v0.2.0
0015 - v1.8 requires Gaudi v33-34, ACTS 8.1+, DD4hep 1.16.1+ and eicd v0.2.0
0016 - v1.5 requires Gaudi v33-34, ACTS 8.1 and DD4hep 1.16.1
0017
0018 Overview
0019 --------
0020
0021 ### Components
0022
0023 - [Juggler Base](@ref base)
0024 - [Digitization Algorithms](@ref digi)
0025 - [Hit Reconstruction Algorithms](@ref reco)
0026 - [Tracking Algorithms](@ref tracking)
0027 - [PID Algorithms](@ref pid)
0028
0029 ### Internal Units
0030
0031 The juggler internal units are (`GeV`, `mm`, `ns`, and `radians`).
0032
0033
0034 ### Running Juggler
0035
0036 Here is an example for topside
0037 ```
0038 ./scripts/run_topside.py -i inputevents.hepmc -o output_events.root -n 10
0039 ../where_ever/../juggler/build/run gaudirun.py options/example_reconstruction.py
0040 ```
0041
0042 # Outline of tracking and vertexing
0043
0044 ## The ACTS way of tracking
0045
0046 First, the geometry has to be constructed. Assuming this is already done, we describe the data processing.
0047
0048 ### Source Links and Measurements
0049
0050 ```
0051 Tracker Hit + Geometry --> Measurement
0052 Hit CellID + Surface --> Source Link
0053 ```
0054
0055 A `SourceLinker` is an algorithm that looks up the surface and maps it to the hit's `cellID`.
0056 Naturally the same algorithm outputs measurements which are also mapped to the hit and contain the position
0057 and sensor size information (via covariance matrix).
0058
0059
0060 ### Proto tracks
0061
0062 Both track finding and fitting will use the information contained in the source links and measurements.
0063 Track finding produces `proto tracks` or groupings of hits. Each proto track is simply a `std::vector<int>` storing the index of the
0064 hits associated with a track seed.
0065
0066 ### Initial Track parameters and Seeding
0067
0068 A Kalman filter needs a starting point and those are the `Initial Track Parameters`. These can be determined many different ways.
0069 Conceptually the process of determining these parameters begins with track seeding.
0070
0071
0072 ## Vertexing
0073
0074 WIP
0075
0076
0077
0078
0079
