find_origin_slice - Check for 2 peaks when looking for key CBCT slice #482
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.
We noticed the CBCT module for our CatPhan604 was failing to find the proper keyslice of the CBCT - the find_origin_slice method looks for the middle slice within a range, but that range is too large.
As you can see in the image below, there are extra slices which don't contain all the HU modules, which we want to ignore. My solution is to add an extra check that the proper slices should have 2 peaks in the Circular Profile. Once we added this, the proper key slice was found.
Hope that makes sense. Unfortunately I haven't been able to test this for other CatPhan models.