Skip to content
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

find solution for multi-column data #4

Open
vhewes opened this issue Sep 20, 2022 · 0 comments
Open

find solution for multi-column data #4

vhewes opened this issue Sep 20, 2022 · 0 comments

Comments

@vhewes
Copy link
Collaborator

vhewes commented Sep 20, 2022

the code currently writes some types of information (event ID, Euclidean & planar coordinates) as 2D HDF5 groups, which causes issues when loading into a dataframe. we should definitely fix the event ID to be separate columns (run, subrun, event) to bring this format into line with that of the MultiIndex approach utilised by PandAna, but it would be good to find solutions for coordinate systems too.

ideally we would find a way to abstract away planar information automatically (ie. handle [u,v,y] for DUNE or [x,y] for NOvA using the same code) when separating into columns, or to just work with multi-element columns natively. whatever works. for Euclidean coordinates we can just do this the old-fashioned way, but if we find a neat solution for planar coordinates, perhaps it'll make sense to use it for Euclidean too.

cerati pushed a commit to cerati/numl that referenced this issue Feb 20, 2023
disable chunking/compression for empty datasets
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant