acts-project
docs: adding Fatras description
This PR adds the Fatras documentation consisting of
- Fatras simulation
- Digitisation
- Configuration
Codecov Report
Merging #1402 (faddc88) into main (91a1e87) will increase coverage by
1.00%. The diff coverage isn/a.
@@ Coverage Diff @@
## main #1402 +/- ##
==========================================
+ Coverage 48.59% 49.59% +1.00%
==========================================
Files 381 407 +26
Lines 20650 22600 +1950
Branches 9475 10305 +830
==========================================
+ Hits 10034 11208 +1174
- Misses 4064 4211 +147
- Partials 6552 7181 +629
| Impacted Files | Coverage Δ | |
|---|---|---|
| Core/src/Utilities/BinUtility.cpp | 50.00% <0.00%> (-50.00%) |
:arrow_down: |
| Core/include/Acts/Utilities/AnnealingUtility.hpp | 60.00% <0.00%> (-23.34%) |
:arrow_down: |
| ...e/include/Acts/Propagator/MultiStepperAborters.hpp | 65.38% <0.00%> (-20.33%) |
:arrow_down: |
| Core/src/TrackFitting/GsfUtils.cpp | 27.27% <0.00%> (-17.18%) |
:arrow_down: |
| Core/include/Acts/EventData/SourceLink.hpp | 84.61% <0.00%> (-15.39%) |
:arrow_down: |
| Core/src/Propagator/PropagatorError.cpp | 0.00% <0.00%> (-14.29%) |
:arrow_down: |
| Core/include/Acts/Propagator/Propagator.ipp | 38.88% <0.00%> (-13.62%) |
:arrow_down: |
| .../include/Acts/Propagator/MultiEigenStepperLoop.ipp | 31.25% <0.00%> (-12.87%) |
:arrow_down: |
| Core/src/TrackFinding/MeasurementSelector.cpp | 21.42% <0.00%> (-11.91%) |
:arrow_down: |
| Core/include/Acts/Utilities/Zip.hpp | 90.00% <0.00%> (-10.00%) |
:arrow_down: |
| ... and 185 more |
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
![codecov[bot] avatar](https://avatars.githubusercontent.com/in/254?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue/PR has been automatically marked as stale because it has not had recent activity. The stale label will be removed if any interaction occurs.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
@asalzburger I would suggest to bring this in in this state now, what do you think? Should we separate the unit test from this PR as @AJPfleger suggested or merge this directly?
This issue/PR has been automatically marked as stale because it has not had recent activity. The stale label will be removed if any interaction occurs.