Skip to content

Conversation

@guitargeek
Copy link
Contributor

In RooAbsCategoryLValue::setBin(), there is a check for passing a
named binning, because the function doesn't support named binnings.

However, if a binning with that name doesn't exist, it is fine to not
error out, because the default range is used.

This supports the fit in this forum post:
https://root-forum.cern.ch/t/roosimultaneous-and-roofftconvpdf/53606

There are also two additional commits with some code modernization as usual.

In `RooAbsCategoryLValue::setBin()`, there is a check for passing a
named binning, because the function doesn't support named binnings.

However, if a binning with that name doesn't exist, it is fine to not
error out, because the default range is used.
In particular, use less TString.
Also, use `nullptr` instead of `0` literal in `getBinningPtr()`.
@phsft-bot
Copy link

Starting build on ROOT-debian10-i386/soversion, ROOT-performance-centos8-multicore/cxx17, ROOT-ubuntu18.04/nortcxxmod, ROOT-ubuntu2004/python3, mac12/noimt, mac11/cxx14, windows10/cxx14
How to customize builds

Copy link
Member

@lmoneta lmoneta left a comment

Choose a reason for hiding this comment

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

LGTM!

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.

3 participants