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

Rory cluster #188

Open
wants to merge 70 commits into
base: master
Choose a base branch
from
Open

Rory cluster #188

wants to merge 70 commits into from

Conversation

rodwyer100
Copy link
Contributor

The most recent version of SvtRawDataAnaProcessor I was using. Furthermore the new Cluster processors

processors/config/roryClusterAna.py Outdated Show resolved Hide resolved
processors/config/roryClusterAna.py Outdated Show resolved Hide resolved
processors/config/roryClusterCompareAna.py Outdated Show resolved Hide resolved
processors/src/RoryClusterAnaProcessor.cxx Outdated Show resolved Hide resolved
processors/src/RoryClusterAnaProcessor.cxx Outdated Show resolved Hide resolved
processors/src/RoryClusterCompareAnaProcessor.cxx Outdated Show resolved Hide resolved
processors/src/SvtRawDataAnaProcessor.cxx Outdated Show resolved Hide resolved
processors/src/SvtRawDataAnaProcessor.cxx Outdated Show resolved Hide resolved
processors/src/SvtRawDataAnaProcessor.cxx Outdated Show resolved Hide resolved
processors/src/SvtRawDataAnaProcessor.cxx Outdated Show resolved Hide resolved
@sarahgaiser
Copy link
Collaborator

I will give this a second round of review once you are done cleaning up your code. Please remove all old/unused print statements and functions that are commented out and no longer needed. It would be great if you could also document your code. That means including a short statement about the purpose of a function or class, input and output of the function and general nice-to-know things about it. For classes, you usually also add short comments about the class attributes.
If you want to have a reference for including comments, you can refer to this.

@rodwyer100
Copy link
Contributor Author

Okay I changed the names to names Cam suggested, though I had to get a little creative as he already created a processor called 'TrackHitAnaProcessor" which I didn't know about. One is now called "TrackHitCompareAnaProcessor" while the other is "SVTClusterAnaProcessor" as it would have had the already used name; both of these were approved names for the object by Cam. I addressed the double usage of the for loop indexer and verified that it did not affect the operation of the processor as expected; I changed it anyways as it is confusing and potentially dangerous. I also addressed the hardcoded location of bad channels by putting it into a dat collection and I believe thats everything so far :)!

@sarahgaiser
Copy link
Collaborator

I have updated the formatting of your code. Can you check if everything builds and if the output is as expected? Once you got that done, I'll approve.

@rodwyer100
Copy link
Contributor Author

I got it so it compiles and does what it should do. Had to add some changes from RawSvtHitHistos.cxx in analysis to do it, but they ought to be minor.

Copy link
Collaborator

@sarahgaiser sarahgaiser left a comment

Choose a reason for hiding this comment

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

Looks good to me now!

Copy link
Collaborator

@cbravo135 cbravo135 left a comment

Choose a reason for hiding this comment

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

Remove scripts/AddIdentity.C

@@ -0,0 +1,18 @@
/**
Copy link
Collaborator

Choose a reason for hiding this comment

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

Remove this file, such an identifier already exists in the event header.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This identifier is used to identify separate reconstruction techniques. Is that in the event header?

Copy link
Collaborator

Choose a reason for hiding this comment

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

you could easily do what you want with the existing header, yes

Copy link
Collaborator

Choose a reason for hiding this comment

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

You just have to fill it correctly

Copy link
Collaborator

Choose a reason for hiding this comment

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

This file should be somewhere in analysis, not processors.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done, put in analysis/data

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

Successfully merging this pull request may close these issues.

3 participants