Skip to content
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

Feature/howard spillquality #109

Open
wants to merge 1 commit into
base: release_v09_20_06
Choose a base branch
from

Conversation

brucehoward-physics
Copy link
Contributor

Putting together PR for a couple of spill info updates to try to get things into the CAFs and in a way that we can also start to do beam quality cuts.

This goes along with SBNSoftware/sbncode#390 and as there see some info in doc-33224 slides 5-13.

IMPORTANT (!!) -- As with the other PR, I'm not sure if I should be making this PR against develop or v09_72_00_05 e.g. There seem to be a lot of commits present in the latter but not in develop as my changes are only the last commit...

… the spill quality for the spill that goes with a given event.
@brucehoward-physics brucehoward-physics changed the base branch from develop to release_v09_20_06 November 1, 2023 20:48
@brucehoward-physics
Copy link
Contributor Author

Per @PetrilloAtWork request to make things less confusing (even if we still have to figure out about the differences between this and develop) I've changed the base branch to be release_v09_20_06 which looking at my area's git log seemed to be what the tag I was working from pointed to.

Copy link
Member

@PetrilloAtWork PetrilloAtWork left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really don't know what to complain about this time.
Maybe the font?
I am forced to approve.

@PetrilloAtWork
Copy link
Member

For the release managers (@miquelnebot): I think that the content of this PR it targeted to be permanently in the release, i.e. to be merged in a develop and all future releases (@brucehoward-physics: confirm?). Also for @brucehoward-physics: is there a specific non-develop release you need this content in?

@jzettle
Copy link

jzettle commented May 13, 2024

Since I got an email from @PetrilloAtWork's comment I will also ask how this meshes with other similar PR's on this topic such as #123? That one is at least targeted to some version of SBN2023A and begs a similar question about what this is targeting and whether there is the intent (or there exists) a parallel request for develop

@brucehoward-physics
Copy link
Contributor Author

Should be available in develop already e0d9f69 -- let me know if this is not working or something!

I guess #123 for numi reprocessing tag probably makes this not needed any more here either?

(Note that this PR is from October 2023 😅)

@jzettle
Copy link

jzettle commented May 13, 2024

I have not tried, I use the excuse that these things are hard to keep track of and then I get an email from a comment here from a review I didn't actually do and wonder what happened

@miquelnebot
Copy link
Contributor

so, if aleready in develop e0d9f69
and will get to SBN2023A by #123
could this be closed @brucehoward-physics ?
also a followup on SBNSoftware/sbncode#390 would be needed too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Open pull requests
Development

Successfully merging this pull request may close these issues.

4 participants