-
Notifications
You must be signed in to change notification settings - Fork 10
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
Fixing iss887 #919
Fixing iss887 #919
Conversation
… channels in 2021 in the IterateGainFactorDriver
…019SF_parameters_data.dat
Fix formatting.
Added new detector for the single pass running at 1.92GeV
Getting latest changes from master in iss887
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.
Code builds cleanly and all tests pass.
FEE cluster energy peaks at beam energies.
Please proceed.
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.
Let's see a talk on these changes at an Analysis/Reco meeting soon.
|
||
|
||
public void setBadChannels() { | ||
if (this.calibYear==2021) { |
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 don't think we should be hard coding bad channel lists like this. The database is the preferred solution for these sorts of things.
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.
This is a calibration driver, not used at all in reconstruction/analysis, so not sure it's such a big deal. There are gains in the database already which are appropriate for killing a channel in reconstruction and are already used for such. And, since this is reading a gains file during calibrations, they can/should be killed from there too, so we can probably just delete or at least ignore these hard-coded numbers.
|
||
public final class ClusterPositionCorrection2021 { | ||
// Parameterizations tested in MC using v3-fieldmap | ||
// Nov 2015 |
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.
We should use the database here rather than hard code numbers like this. Also, the code has a comment that these were tested on Nov 2015. I would like to see these tested them the 2021 beam energy and fieldmap.
ECAL 2021 energy calibration.