Only average over trains dimension in Scan.bin_by_steps() #269
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This came up at FXE: if you have an array with multiple values per train, such as a spectrum, you naturally want an average spectrum per scan step, but
scan.bin_by_steps(arr)
reduces it down to a single number per scan step instead.This could theoretically break code that relies on it collapsing extra dimensions, but I'm not sure when you'd want that, and it's very easy to do further averaging on the results from this if you need to. So I hope we can just consider it a bug and fix it. 🤞
cc @bermudei