-
Notifications
You must be signed in to change notification settings - Fork 12
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
378 geom accuracy wrong slices #399
Merged
Merged
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
The mask is now calculated from slices 1 and 5 (instead of 7) as per the ACR guidance.
The slice index (ie 0 for slice 1 etc) is now an input to the geometric accuracy function, rather than fixed at slice 7. Also, get_geometric_accuracy_slice1 and get_geometric_accuracy_slice5 are combined into a generic get_geometric_accuracy function.
Changed syntax in unit tests to updated syntax in get_geometric_accuracy function
Corrections after some of the tests on Github failed (line too long, too many blank lines)
On slice 1 the mask was being generated incorrectly on the GE data (it was extending outside the phantom). Some pixels from outside the phantom had signal value above the masking threshold, so these were being picked up and incorporated in the mask. I increased the masking threshold from 0.05 to 0.07 and this meant that the background pixels were no longer being picked up.
changing the unit test values to the new correct values from slices 1 and 5
Following changes to the create mask function in ACR object, amendments to the acr ghosting and acr slice position unit tests were made to accommodate minor variation in results.
resolves #378 |
sophie22
requested changes
Jan 18, 2024
sophie22
reviewed
Jan 18, 2024
Slice 7 is needed for ghosting, uniformity and snr
simplify variables
sophie22
approved these changes
Jan 18, 2024
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.
Thank you! All comments have been satisfactorily addressed.
Happy to merge :)
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.
The ACR geometric accuracy test was measuring from slice 7 rather than slices 1 and 5 as per the ACR guidance. I have:
I then realised that the mask was being created incorrectly on slice 1 of the GE data (this was not previously an issue as the slice was being created from slice 7). This was because one of the pixel values outside the phantom was above the masking threshold value. I have changed the threshold value so that it is no longer picking up background noise pixels and including these in the mask. The images on the report look acceptable but some future work could be to test this with more GE data. I then changed three of the unit tests accordingly, as there were very minor variations in the results following this change.