I’m having a problem with using rebinned TProfile3D’s. After rebinning, attempting to draw throws a bad_alloc and GetBinContent returns 0 for every bin. This happens when using the Rebin3D method as well as RebinX, RebinY, and RebinZ methods. What am I missing here?
Yes as Wile said we need something showing the problem. A small reproducer (macro) we can run. Can you also tell on which kind of platform you are running ?
We are fixing the -inf bins problem now. The macro that produced this was actually filling those values.
But we didn’t expect that the infinite bin contents would cause a crash like this. I didn’t mention it before, but using RebinY(10) instead of RebinY(5) doesn’t lead to a crash, which makes me think it’s something more subtle than corrupted data.
This standalone macro shows unintuitive behavior of the rebinning method in a TProfile3D. Even the average of the bins in a row changes with rebinning. Am I misunderstanding what the Rebin methods are supposed to do or is this a bug?
This looks like a bug to me. The bins in the rebinned histogram don’t match what is expected from the histogram before rebinning. Can someone please comment on the simple standalone macro above, and decide if this is a ROOT bug or an implementation error ? I don’t @moneta or anybody commented on this. Thanks in advance.