-
Notifications
You must be signed in to change notification settings - Fork 82
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
Agnostic helix finder and correction of the charged pion lifetime #1210
Conversation
Will use it to create the filtered cosmics low dataset.
…luster small update for extracted position in EventDisplay
… the number 2 with a constexpr, replace some of the vectors with std::arrays
Changes to KinKal and CRV (PR1073) incorporated while still keeping the build e20-p047
@FNALbuild run build test |
⌛ The following tests have been triggered for d99670e: build (Build queue is empty) |
☀️ The build tests passed at d99670e.
N.B. These results were obtained from a build of this Pull Request at d99670e after being merged into the base branch at 07a76f5. For more information, please check the job page here. |
Once Production PR 316 is merged I will merge this PR. Note that a number of issues related to changes requested but not implemented in this PR have been added to Offline. It is expected that those will be dealt with promptly. |
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 agree that it's right to merge this and create issues to deal with any outstanding work.
📝 The HEAD of |
@FNALbuild run build test |
⌛ The following tests have been triggered for d99670e: build (Build queue is empty) |
Thanks a lot! |
☀️ The build tests passed at d99670e.
N.B. These results were obtained from a build of this Pull Request at d99670e after being merged into the base branch at f6fe4b1. For more information, please check the job page here. |
I cannot merge this PR until gaponenko removes his request for changes. If he doesn't wish to approve he can simply downgrade his review to a comment. |
Hi @brownd1978 , @kutschke Thank you very much. |
Hi Dave, I thought I already did that. My previous post on this PR #1210 (review) is a comment. I don't see what else I can do, as the options are "request changes", "comment" (which I did), or "approve". I already explained why I did not want to approve. |
Hi Andrei,
On Mon, May 6, 2024 at 10:22 AM Andrei Gaponenko ***@***.***> wrote:
I cannot merge this PR until gaponenko <https://github.com/gaponenko>
removes his request for changes. If he doesn't wish to approve he can
simply downgrade his review to a comment.
Hi Dave, I thought I already did that. My previous post on this PR #1210
(review)
<#1210 (review)>
is a comment. I don't see what else I can do, as the options are "request
changes", "comment" (which I did), or "approve". I already explained why I
did not want to approve.
How can I help to remove the "block" without doing the approval?
To supersede your previous review go to the PR select 'files changed' and
the select the green 'Review changes' button. From there you can change
your review to a comment, then 'submit review'
thanks, Dave
… —
Reply to this email directly, view it on GitHub
<#1210 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAH572226LBPXTJFA4DXMDZA636RAVCNFSM6AAAAABEJP7CI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJWGU2DCMJSG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
David Brown ***@***.***
Office Phone (510) 486-7261
Lawrence Berkeley National Lab
M/S 50R5008 (50-6026C) Berkeley, CA 94720
|
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.
Changing to a comment
Hi Andrei,
it turns out I'm wrong: simply commenting in the review response is not
enough to remove a 'changes requested' review. You must either approve the
PR, or dismiss your 'change request'.
sorry for the confusion.
Dave
…On Mon, May 6, 2024 at 1:17 PM Andrei Gaponenko ***@***.***> wrote:
***@***.**** commented on this pull request.
Changing to a comment
—
Reply to this email directly, view it on GitHub
<#1210 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAH572FULJV3GHB5ANWUEDZA7QNTAVCNFSM6AAAAABEJP7CI6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDANBRGYYDEMZSGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
David Brown ***@***.***
Office Phone (510) 486-7261
Lawrence Berkeley National Lab
M/S 50R5008 (50-6026C) Berkeley, CA 94720
|
Dave and I understand Andrei's objections to approving this PR and we are keeping them on the record. There is no practical way to satisfy Andrei's requests at this time so I will dismiss the review and proceed with the merge.
Dismissing Andrei's review indeed preserved the full history of his comments and requests for changes. You may need to hit the "Load more" button to see them. To the authors: @NamithaChitrazee @pavel1murat @matthewstortini @Hiigaran The issues #1250 and #1251 were created for you to follow up on issues raised during the review but not yet resolved. There is also work requested on the event generator that was removed from the review. |
This PR has the following main updates: