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

Ignore cue_* fields in choppers which interfere with loading #98

Merged
merged 1 commit into from
Feb 2, 2023

Conversation

SimonHeybrock
Copy link
Member

Similar to the same mechanism we use for detector data.

Similar to the same mechanism we use for detector data.
Copy link
Member

@jl-wynen jl-wynen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you remind me why they need to be skipped?

@SimonHeybrock
Copy link
Member Author

SimonHeybrock commented Feb 2, 2023

They provide an index into a potentially long dimension, from the Nexus docs:

In order to make random access to timestamped data faster there is an optional array pair of cue_timestamp_zero and cue_index. The cue_timestamp_zero will contain coarser timestamps than in the time array, say every five minutes. The cue_index will then contain the index into the time,value pair of arrays for that coarser cue_timestamp_zero.

These fields have a different length than the data, so they prevent loading it as a DataArray. Since they contain no actual information we skip them.

@SimonHeybrock SimonHeybrock merged commit 6f112a9 into main Feb 2, 2023
@SimonHeybrock SimonHeybrock deleted the ignore-chopper-cue-fields branch February 2, 2023 09:15
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

Successfully merging this pull request may close these issues.

2 participants