You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am trying to use the newest version of coffea with Dask on a NanoAOD with messy cross-references (i.e., Electron_genPartIdx exists but GenPart does not). On futures, I could use:
NanoAODSchema.warn_missing_crossrefs = True
as a fix. On Dask, this does not seem to work, and the error of:
RuntimeError: Parsing indexer Electron_genPartIdx, expected to find collection GenPart but did not
persists.
To Reproduce
This issue can be reproduced by plugging this sample file: root://eospublic.cern.ch//eos/root-eos/benchmark/Run2012B_SingleMu.root
into a processor which executes on Dask. For a basic example:
Describe the bug
I am trying to use the newest version of coffea with Dask on a NanoAOD with messy cross-references (i.e., Electron_genPartIdx exists but GenPart does not). On futures, I could use:
NanoAODSchema.warn_missing_crossrefs = True
as a fix. On Dask, this does not seem to work, and the error of:
RuntimeError: Parsing indexer Electron_genPartIdx, expected to find collection GenPart but did not
persists.
To Reproduce
This issue can be reproduced by plugging this sample file:
root://eospublic.cern.ch//eos/root-eos/benchmark/Run2012B_SingleMu.root
into a processor which executes on Dask. For a basic example:
Expected behavior
Expected behavior should be to run the processor without any issue, as happens with futures.
Output
Additional context
A potential fix was offered by Nick:
but this fix only works with a set number of workers. If autoscaling is allowed, new workers don't get the fix applied to them.
The text was updated successfully, but these errors were encountered: