-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Update of the Zmumu validation tool #25159
Update of the Zmumu validation tool #25159
Conversation
…ng the Y axis range and 2D plots
…ng the Y axis range and 2D plots
…ng the Y axis range and 2D plots
A new Pull Request was created by @cardinia for CMSSW_10_2_X. It involves the following packages: Alignment/OfflineValidation @tocheng, @monttj, @cmsbuild, @franzoni, @fgolf, @pohsun, @peruzzim, @lpernie can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
MuonAnalysis/MomentumScaleCalibration/test/Macros/RooFit/MultiHistoOverlapAll_Base.C
Outdated
Show resolved
Hide resolved
@@ -220,15 +235,15 @@ void splitOptionRecursive(string rawoption, vector<string>& splitoptions, char d | |||
} | |||
|
|||
void getCustomRanges(TString type, TString resonance, int iP, float minmax_plot[2]); | |||
void MultiHistoOverlapAll_Base_one(string files, string labels, string colors, string linestyles, string markerstyles, TString directory, TString resonance, TString type, bool switchONfit); | |||
void MultiHistoOverlapAll_Base_one(string files, string labels, string colors, string linestyles, string markerstyles, TString directory, TString resonance, TString type, bool switchONfit, bool AutoSetRange, float CustomMinY, float CustomMaxY); |
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'd suggest to set default values to the arguments added making sure they work as expected when they were not there. In that way, previously written code that uses this class will still work :)
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.
Dear Andres,
I assigned a default value in the function definition, so I cannot assign it also in the function declaration. I could assign the default value in the function declaration and remove it from the function definition though, is that what you were suggesting?
Thanks in advance,
Andrea
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 could assign the default value in the function declaration and remove it from the function definition though, is that what you were suggesting?
Not exactly. But that's a good idea.
Also, please make sure your commit description offers an explanation of the change you're applying and make sure it is unique. Right now I see you have three different commits with the same description. It is better to avoid 'Merge' commits, check git rebase
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.
Thank you very much for the tip, I'll implement the change.
As for the commits I'll try to be more careful next time when preparing a pull request, thanks for the information.
MuonAnalysis/MomentumScaleCalibration/test/Macros/RooFit/MultiHistoOverlapAll_Y1S.C
Outdated
Show resolved
Hide resolved
MuonAnalysis/MomentumScaleCalibration/test/Macros/RooFit/MultiHistoOverlapAll_Z.C
Outdated
Show resolved
Hide resolved
MuonAnalysis/MomentumScaleCalibration/test/Macros/RooFit/MultiHistoOverlapAll_Base.C
Outdated
Show resolved
Hide resolved
if(value>zMax)zMax=value; | ||
} | ||
} | ||
maxDist=fabs(zMax-Mass); |
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.
@cardinia you are using here a variable zMax
which is defined out of this scope (in the if(type=="mean"){
clause)
How is this supposed to work?
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.
Dear Marco,
I am sorry but I do not understand what you mean: the zMax and zMin variables are defined within the scope of the condition regarding the type of the histogram, and the scope of that condition ends at line 415.
I defined the variables in that scope since they are necessary only to fix the z axis range when working with the average of the mass distribution and not the standard deviation.
Can you be more specific regarding the issue you noticed?
Thanks in advance,
Andrea
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.
Hi Andrea, I counted the parentheses wrong -my bad.
Still I am wondering about the blank stripe you showed in the middle of the sigma distribution during the meeting (see also comment at line https://github.com/cms-sw/cmssw/pull/25159/files/88635fbdd021ffe44198e59bc13b66a59ecca03f#diff-b7a5bcf180f203de7abd9bb4d084e665R370).
In the case of the sigma which rangeuser is applied? None?
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.
Hi Marco,
no range is set for the sigma distribution, the plots are identical to what you would observe in the BiasCheck.root file drawing the histograms with the colz option.
I'm investigating the code in CompareBiasZValidation.cc [1] to try and understand what causes the problem, as of now I did not find anything weird...
Anyway I put the comment you underlined in the code as a reminder that there is still work to be done, then I decided to make the pull request anyway given that some features can already be used in the framework.
Cheers,
Andrea
…m/cardinia/cmssw into from-CMSSW_10_2_X_2018-11-08-1100
@cardinia sorry, but is this the backport of which PR? Please provide a master version of this development |
@fabiocos sorry, my bad. I accidentally made the PR to this branch instead of the master. I'm now trying to make the rebase to then create a proper PR to the master version, however I'm having some difficulties in doing so. Should I close this PR and open a new one or is it possible to change the branch destination of this commit? |
The pull request to the master branch has now been made (#25220). This pull request can either be used for backporting or closed entirely. |
@cardinia well it is up to you and Alignment people to say whether this is needed in 10_3_X for HI activities or not... |
Am I wrong or is this backport to 10.2 rather than 10.3? I don't think this is useful in 10.3, while it might in 10.2 where the analysis of 2018 pp data is still ongoing, in case a new release is built |
please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+1 |
merge utilities for alignment studies |
backport #25220 |
@connorpa
Implemented features:
2D plots Mass vs EtaPhi of muon (plus or minus)
Plotting options regarding the Y axis range in 1D histograms
Features presented in:
https://indico.cern.ch/event/768246/#72-latest-developments-of-vali
https://indico.cern.ch/event/688851/#sc-28-2-improvement-of-z-valid