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

Update of the Zmumu validation tool #25159

Merged

Conversation

cardinia
Copy link
Contributor

@cardinia cardinia commented Nov 8, 2018

@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

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 8, 2018

A new Pull Request was created by @cardinia for CMSSW_10_2_X.

It involves the following packages:

Alignment/OfflineValidation
MuonAnalysis/MomentumScaleCalibration

@tocheng, @monttj, @cmsbuild, @franzoni, @fgolf, @pohsun, @peruzzim, @lpernie can you please review it and eventually sign? Thanks.
@adewit, @tocheng, @argiro, @bellan, @tlampen, @mschrode, @mmusich this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@@ -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);
Copy link
Contributor

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 :)

Copy link
Contributor Author

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

Copy link
Contributor

@vargasa vargasa Nov 9, 2018

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

Copy link
Contributor Author

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.

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 9, 2018

Pull request #25159 was updated. @tocheng, @monttj, @cmsbuild, @franzoni, @fgolf, @pohsun, @peruzzim, @lpernie can you please check and sign again.

if(value>zMax)zMax=value;
}
}
maxDist=fabs(zMax-Mass);
Copy link
Contributor

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?

Copy link
Contributor Author

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

Copy link
Contributor

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?

Copy link
Contributor Author

@cardinia cardinia Nov 9, 2018

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

[1]https://github.com/cms-sw/cmssw/blob/02d4198c0b6615287fd88e9a8ff650aea994412e/MuonAnalysis/MomentumScaleCalibration/test/Macros/RooFit/CompareBiasZValidation.cc

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 9, 2018

Pull request #25159 was updated. @tocheng, @monttj, @cmsbuild, @franzoni, @fgolf, @pohsun, @peruzzim, @lpernie can you please check and sign again.

@fabiocos
Copy link
Contributor

@cardinia sorry, but is this the backport of which PR? Please provide a master version of this development

@cardinia
Copy link
Contributor Author

@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?

@cardinia
Copy link
Contributor Author

The pull request to the master branch has now been made (#25220). This pull request can either be used for backporting or closed entirely.
Sorry for the confusion.

@fabiocos
Copy link
Contributor

@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...

@mmusich
Copy link
Contributor

mmusich commented Nov 15, 2018

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

@fabiocos
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 24, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/31836/console Started: 2018/11/24 19:03

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-25159/31836/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 6 differences found in the comparisons
  • DQMHistoTests: Total files compared: 31
  • DQMHistoTests: Total histograms compared: 2986766
  • DQMHistoTests: Total failures: 2
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2986574
  • DQMHistoTests: Total skipped: 190
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 30 files compared)
  • Checked 129 log files, 14 edm output root files, 31 DQM output files

@pohsun
Copy link

pohsun commented Nov 25, 2018

+1

@fabiocos
Copy link
Contributor

+1

@fabiocos
Copy link
Contributor

merge

utilities for alignment studies

@cmsbuild cmsbuild merged commit 2ce2b3b into cms-sw:CMSSW_10_2_X Nov 26, 2018
@fabiocos
Copy link
Contributor

backport #25220

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

Successfully merging this pull request may close these issues.

6 participants