Projections after slicing including flow bins #384
-
I have a large-D histogram which I have sliced, and I've intentionally chosen one slice in "nbtag" which is empty.
That gives
As expected! Now I project down another level in nbtag:
Yep! Still what I want Now in njet
Not quite what I wanted, nor expected! I sliced the histogram afterall, but the flow from nbtag has been included back in I suppose, while the slice on njet is still applicable? So the question is, how can I do what I intended (e.g. project down to the njet/dataset axes, but still stick to the non-flow slice in nbtag from defining 'bkg')? If it's including 'flow' along this axis that had been sliced, what about other axes when I projected down from even higher dimensions? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Does |
Beta Was this translation helpful? Give feedback.
Does
bkg[0j:2j:sum, ...]
return the expected value (as opposed tobkg.project("njet", "dataset")
)?In general, I think the
project
function needs an option to decide whether or not to include flow bins.