-
Notifications
You must be signed in to change notification settings - Fork 19
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
CuPy buffers error triggered from dask_awkward.from_parquet #472
Comments
Hmm, this is not a very helpful error message. It looks like we're treating if x:
...
else:
... as a boolean "NumPy" or "CuPy" rather than "not NumPy". I suspect we're seeing placeholders here, but they shouldn't be getting in to a kernel like this. Could you share the analysis excerpt too? |
The two lines at the bottom of the first code-block are all that's needed, I believe. The schema for this file, read via
Edit for posterity: setting optimize_graph=False in the compute removes this triggered error message, just like the error with the other schema in the iris-hep:servicex-join channel being discussed now |
A file with a perhaps ususual (or bad) parquet schema is triggering an awkward error when computed on via dask_awkward.from_parquet.
results in the following
(coffea: 2024.2.1 ak: 2.6.1 uproot: 5.2.2 hist: 2.7.2 dask-awkward: 2024.2.0 numpy: 1.26.4 numba: 0.59.0 trino: 0.327.0 as package versions)
When the equivalent is done via awkward.from_parquet, this computes without an error, but nevertheless it might belong properly there instead of dak.
The file can be found here:
https://drive.google.com/file/d/135ILkDokbHx4YehZuFSZ455hyRtBmfmE/view?usp=sharing
The text was updated successfully, but these errors were encountered: