-
Notifications
You must be signed in to change notification settings - Fork 1
Calculate geometry #58
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
Open
toqduj
wants to merge
21
commits into
main
Choose a base branch
from
calculate_geometry
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
WIP Adding a geometry calculator that would calculate for each pixel:
When possible with uncertainty estimates. This assumes that the data dimensions follows [..., ..., (Q2,) (Q1,) Q0]. rank_of_data of 0, 1, 2, indicates whether we use 1, 2, or 3 dimensions for our data. The remaining dimensions are assumed to be dependent on external variables such as frames, temperature, position, etc.
Needs some thought, though. For example, for a Mythen strip detector data read-in, we actually use dimensions of [1280, 1] and a rank_of_data of 2, as we have finite size pixels...