-
Notifications
You must be signed in to change notification settings - Fork 5
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
ENH k-space wrapping for Hermitian images #65
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test file is redundant so I removed it.
return contract_hermitian_y(im_exp) | ||
|
||
|
||
# I am leaving this code here for posterity. It has a bug that I cannot find. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rmjarvis @jecampagne If any of you have a chance to look for bugs in the code below, that'd be cool. No worries if not!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! just two questions below
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After working through the image interp pr I am worried there is a bug here. Going to hold off on merging.
I am merging this code with the fixes to address the PR comments above into PR #60 since it is needed for tests there. |
This PR has a very naive, but working implementation of k-space wrapping for Hermitian images. The code expands the image from its compressed format to the fully explicit Hermitian format, wraps then using simple code, and then cuts away the parts not needed.
I tried a more memory efficient algorithm that didn't involve the expansion but could not get it working. I've left that code commented out in case someone else can find the bug.
todo: