-
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
Image matching approaches #3
Comments
There is also another small issue about the brain volume definition: whenever we count the number of true negatives (TNs), we should count them over the brain volume and not the whole image! Otherwise we are sing an even larger number of TN voxels... |
Can we just input your ICV Image derived during normalization ? Dr Cyril Pernet Sent from my HTC mobile phone ----- Reply message ----- There is also another small issue about the brain volume definition: whenever we count the number of true negatives (TNs), we should count them over the brain volume and not the whole image! Otherwise we are sing an even larger number of TN voxels... You are receiving this because you were assigned. The University of Edinburgh is a charitable body, registered in |
Yep, that's exactly the idea! :-) |
Image matching approaches
There are different ways to evaluate the match or overlap between 2 binary images, typically a proposed image (the segmentation we want to check) and a reference image (the segmentation we think is the truth). The methods described here under should be implemented in a function, such as image_overlap.m first introduced by @CPernet .
Here are a few possible measures:
Are currently available within the image_overlap.m:
References for segmentation comparison
The text was updated successfully, but these errors were encountered: