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
Weighted histogram differs from numpy unless the data is explicity copied. #51
Comments
Thanks for reporting this, this definitely seems like a bug! I'm going to be able to address this in the next few weeks but if anyone has a chance to investigate and open a pull request, I'll happily review it! |
Glancing at the code, I think the issue is that we currently assume all arrays have the same memory layout since we use a single |
I found the issue, PR forthcoming |
@LucasCampos - could you check whether things work fine with the latest developer version? |
Hey! Thanks for suck a quick reponse. I can confirm that the new code works locally as well!
|
@LucasCampos - thanks! I'll make a new release. |
First, thanks for the great library. I suspect I am hitting a memory issue. Unless I explictly copy the arrays before passing them to histogram2D, the results differ from numpy. So far, I only saw this happen when I am using the weighted version of the 2Dhistogram. Code and output follows
with output
The data file necessary to run the code is attached. Due to github restrictions, I had to zip it first.
data.npz.zip
The text was updated successfully, but these errors were encountered: