-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Move FitWithRooFit
out of bin
folder to make it available for DiMuonMassBiasClient
#42051
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
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42051/36030
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages:
@nothingface0, @emanueleusai, @tvami, @cmsbuild, @saumyaphor4252, @pmandrik, @syuvivida, @tjavaid, @micsucmed, @francescobrivio, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-493fb0/33337/summary.html Comparison SummarySummary:
|
@cms-sw/alca-l2 @cms-sw/dqm-l2 a kind ping on this one |
+1 |
+1
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Title says it all:
FitWithRooFit
class out ofAlignment/OfflineValidation/bin
such that there is a header file publicly available for other classes to use (commit c55d87c)DiMuonMassBiasClient
to use one of the models available inFitWithRooFit
, though the options is for now not active by default (commit 267ef5a)No changes expected.
PR validation:
scram b runtests use-ibeos
runs fine.Also I've privately run the tests configuration files in
DQMOffline/Alignment
to run on 2023C data and obtained the fits available here .If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Not a backport, possibly to be backported for 2023 data-taking