Replies: 2 comments 7 replies
-
@reckoner are you on the latest version? I had a similar issue that went away recently (complicated slice on ~8ish dims) |
Beta Was this translation helpful? Give feedback.
-
Are you sure it's the same calculation? In boost-histogram, this is making a new histogram and computing the flow bins in the projections. In xarray, you are probably ignoring the flow bins. Even if you do include them, what xarray is doing is probably a little simpler, and it's not handling the axes. I think we avoid making an extra copy here in 1.2+, since the operations you are providing are all supported in a single fusion in Boost.Histogram (C++), but might be worth checking just to make sure. Note to self: I wonder if we can improve the conversion to xarray to include nice indices based on the axes, at least in hist... |
Beta Was this translation helpful? Give feedback.
-
I have a 13 dimensional dataset and I have noticed that although
h = bh.Histogram(...)
works beautifully, doingh.project(3,4)
is three of four times slower than doing the exact same calculation in Xarray,Am I doing something wrong here or is this to be expected? I tried on both a Windows and Linux Ubuntu backend. The result is exactly the same in both cases. It's just the
bh
is much slower.Beta Was this translation helpful? Give feedback.
All reactions