Option to run a coilwise CG recon in the coil maps calculation. #40
Conversation
This file contains 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
…ified I simplified the code substantially by hard coding CG calib_size
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.
This adds the option to run a coilwise CG recon to calculate the coil maps.
For now, the default remains the filtered backprojection.
Using a calib size of (24,24,24) it appears that reconstructing the image to twice that size gives slightly better-looking coil maps. The increased cost in computation time is negligible.
The CG recons can have high signal at the edges of the FOV especially the rosettes but also for the radials, to a lesser degree. This messes with the masking of espirit, hence the option to mask out 2 pixels at the edge of the FOV. The code is kind of ugly but I couldn't think of a cleaner option without allocating a second variable.