Open Lestropie opened 6 years ago
An added criterium (on top of the connected-components WM filter) that potentially defines...
those spurious WM voxels outside the brain
...but doesn't include those "inside" the brain could be to check if they "touch the background", the latter being defined as the inverted brain mask. So if that makes sense, you could
The output of step 5 should then hopefully be the voxels that you'd want to exclude. These shouldn't include the spurious WM voxels inside the brain any more, if they didn't "touch the background".
Of course, this all hinges on the voxels that you want to exclude touching the background. I imagine that's the case? This is a small band of voxels just beyond the "real CSF" right? An there's nothing "beyond" those erroneous WM voxels any more that separates them from the very border of the brain mask?
Suspect it wouldn't be sensitive enough: Too few of the erroneous WM voxels will be at the outer edge of the mask. It tends to be skull that comes out as WM, but that's not necessarily the outer edge of the brain mask either. :-/
Hmm, yeah, I can imagine that indeed. In that case, I've got the feeling it's unavoidably going to be messy in one way or another... The next closest thing to patch up the above strategy in that case would be to, rather than requiring them to strictly "touch" the background, allow a certain distance (but that becomes an arbitrary parameter then of course...). I can imagine these voxels would still be (hopefully much) closer to the background than the ones in subcortical GM, so there might be a relatively safe and robust default for such a distance parameter.
In
fast
, voxels outside the brain left behind by bad skull stripping can be labelled as white matter, resulting in erroneous seeding / tracking in ACT. So in5ttgen fsl
I run a connected-components filter on the WM image, and instead null these voxels from the output image (so they're treated as being outside the brain). However, the logic constructed around this fails to take into account the possibility that such a voxel may lie partly inside a sub-cortical GM structure. When this occurs (albeit likely erroneous in its own right), and the sub-cortical GM fraction is neither 1 nor 0 but somewhere in between, the recombination offast
WM/GM/CSF images with the SGM images from FIRST results in a non-unity sum of partial volume fractions, which5ttcheck
then warns the user about.So I need to re-think the logic around this operation, and ideally find a way to remove those spurious WM voxels outside the brain but also prevent this warning from being issued when such an observation is made inside the brain.