-
Notifications
You must be signed in to change notification settings - Fork 52
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
Use configuration types as SSOT for defaults #833
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it. Just the m_
prefixes from my side... 🤔
fda2453
to
2bf58b7
Compare
This is another thing that might help the ITk track finding efficiency |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
As it stands, some of our default values for configuration parameters, e.g. those of the track finding, have defaults defined both in the configuration type as well as in the corresponding options type in the examples. This is confusing as @paradajzblond discovered today. In this commit, I remove the defaults defined in the examples code and treat the configuration type defaults as the single source of truth for default values.
2bf58b7
to
6fcc91c
Compare
|
As it stands, some of our default values for configuration parameters, e.g. those of the track finding, have defaults defined both in the configuration type as well as in the corresponding options type in the examples. This is confusing as @paradajzblond discovered today. In this commit, I remove the defaults defined in the examples code and treat the configuration type defaults as the single source of truth for default values.