-
Notifications
You must be signed in to change notification settings - Fork 45
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
Modified .cpp file and adding the parameter section to the xml file #743
Modified .cpp file and adding the parameter section to the xml file #743
Conversation
for more information, see https://pre-commit.ci
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.
Why do you read all these variables first into double and then convert them to float?
a8a311d
to
efb1ebf
Compare
@wdconinc The number conversion part is addressed, please take one more look and approve the PR |
…' of github.com:eic/epic into 739-moving-hard-coded-pfrich-parameters-to-the-xml-file
fd570cf
to
c850e71
Compare
for more information, see https://pre-commit.ci
We see there is an overlap now, we are working on fixing it. |
@wdconinc @kkauder @RomanTkachenko-dev The overlap issue is resolved, please consider merging after the checks. |
Do we understand the failed checks? |
@wdconinc Hi Wouter, could you take a look a the auto-check result this time, the only thing that is not finished is the physics benchmark. Is this expected? |
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.
Defining constants is not the DD4hep way - those exist in a global namespace. Naming doesn't mention RICHEndcapN_
prefix. Let's merge this anyway.
…743) ### Briefly, what does this PR introduce? ### What kind of change does this PR introduce? - [ ] Bug fix (issue #__) - [ x] New feature (issue #__) - [ ] Documentation update - [ ] Other: __ ### Please check if this PR fulfills the following: - [ ] Tests for the changes have been added - [ ] Documentation has been added / updated - [ ] Changes have been communicated to collaborators ### Does this PR introduce breaking changes? What changes might users need to make to their code? No ### Does this PR change default behavior? Np --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Briefly, what does this PR introduce?
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
No
Does this PR change default behavior?
Np