Closed mpinkerton-oasis closed 3 years ago
Hi,
Am I correct in assuming that you are working on some kind of Linux distribution?
Thank you, Jovan.
Yes, ubuntu 18.04
Thanks for the report, we've been able to reproduce it. I hope we can fix it soon.
It seem the issue is python36 with numpy 1.17, you could downgrade to 1.16. I don't know exactly what the issue it, but it does seem like it's not vaex' fault.
Hi @maartenbreddels, thanks for looking into this. No problem for us to run with Numpy 1.16 for now.
This bug is still present for Python 3.9 on Linux with the latest Vaex (4.1.0) and Numpy (1.20.1) from pip. Downgrading to Numpy 1.16 is no longer a solution as Astropy requires Numpy>=1.17. As a workaround, it seems that setting percentages
to a list and putting the value you want in the 2nd or higher index calculates correctly.
e.g. This results in nan
p = df.percentile_approx(df.vals, percentage=0.001)
However, this results in [nan, 0.1637147]
p = df.percentile_approx(df.vals, percentage=[0.001, 0.001])
My magic numpy version is 1.19.5. But this is a numpy issue not a vaex or python issue.
You can verify by trying the np.percentile
function.
I am getting an error every time I run the percentile_approx function. Here is an example using the example data set, but I have seen the same error in all of my own test:
Here is my version information:
Python 3.6.8
vaex==2.0.2 vaex-arrow==0.3.5 vaex-astro==0.5.0 vaex-core==0.9.2 vaex-hdf5==0.5.4 vaex-server==0.2.1 vaex-viz==0.3.7