-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: Move ParticleData
from Fatras to Core
#2233
refactor: Move ParticleData
from Fatras to Core
#2233
Conversation
Should we discuss this interactively in the meeting? |
This is maybe somehow related to #2230, so we could discuss this together |
try make everything |
|
Ah thats sad... Hmm so one possibility would be to provide a |
right that would be an option. I think that could be a separate effort to poly fill a few common functions which limit us in our |
Codecov Report
@@ Coverage Diff @@
## main #2233 +/- ##
=======================================
Coverage ? 49.26%
=======================================
Files ? 449
Lines ? 25398
Branches ? 11721
=======================================
Hits ? 12513
Misses ? 4553
Partials ? 8332
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
📊 Physics performance monitoring for 3bde52bSummary VertexingSeedingCKFAmbiguity resolutionTruth tracking (Kalman Filter)Truth tracking (GSF) |
hmmm physmon crashed but I don't see how this can be. rerunning. |
I would like to move `ParticleData` to `Core` so we have one central spot to get mass and charge for a PDG particle identifier. This can the be utilized in acts-project#2181
I would like to move
ParticleData
toCore
so we have one central spot to get mass and charge for a PDG particle identifier.This can the be utilized in #2181