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

PERF: change computation type for fft: float --> double #866

Merged
merged 2 commits into from
Oct 7, 2019

Conversation

ntustison
Copy link
Member

@ntustison ntustison commented Oct 7, 2019

Mirrors the N4 changes in ITK here

@ntustison ntustison merged commit d073c62 into master Oct 7, 2019
@ntustison ntustison deleted the n3-fft-computation-type branch October 7, 2019 20:10
@gdevenyi
Copy link
Contributor

gdevenyi commented Oct 7, 2019

Huh, I think I've been bitten by this bug :)

@ntustison
Copy link
Member Author

Yeah, I should've updated sooner.

@cookpa
Copy link
Member

cookpa commented Oct 8, 2019 via email

@ntustison
Copy link
Member Author

No, not a known bug, but if you follow the link in my original posting, you'll see that @hjmjohnson encountered a float vs. double issue when processing many scans through N4. Since N3 and N4 share the same histogram sharpening function, I thought it should be propagated to our ANTs version of N3. The other commit was due to a recent change in the N4 code where they exposed the ReconstructBiasField function so I took advantage of that to trim down some lines of code in N4BiasFieldCorrection.cxx.

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.

3 participants