Now that dask-awkward is starting to mature alongside awkward2, we should make sure fastjet functions with dask-awkward in a relatively seamless way.
This means, at least to me, that calling fastjet functions on dask-awkward inputs should yield the expected output in that case (a dask-awkward graph layer) rather than requiring that requiring the user to call map_partitions.
Now that dask-awkward is starting to mature alongside awkward2, we should make sure fastjet functions with dask-awkward in a relatively seamless way.
This means, at least to me, that calling fastjet functions on dask-awkward inputs should yield the expected output in that case (a dask-awkward graph layer) rather than requiring that requiring the user to call
map_partitions
.