-
Notifications
You must be signed in to change notification settings - Fork 129
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
feat: switch permit_dask to True by default #922
Conversation
@nsmith- I've had to mangle some parts of the nanoevents schema system to get this all to fit right. I think it's worth a look from you to determine a way to make the non-user facing parts of the interface decent again. |
for more information, see https://pre-commit.ci
@nsmith- can you give this a look and lodge your complaints? May not get fixed in this PR but we can plan it for the future. |
@@ -10,14 +10,14 @@ | |||
fname = "tests/samples/nano_dy.root" | |||
eagerevents = NanoEventsFactory.from_root( | |||
{os.path.abspath(fname): "Events"}, | |||
schemaclass=NanoAODSchema.v6, | |||
schemaclass=NanoAODSchema, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the .v6
specialization still work but is just not needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now the .vX
specializations are a little broken in their original implementation. The functional sub-classing thing you were doing doesn't quite fit into the daskiness.
This PR makes dask-based nanoevents the default.
Currently there are some unrelated blockers for from (dask-)awkward related to numpy reducers.