-
Notifications
You must be signed in to change notification settings - Fork 0
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
VipT1BiasCorrection exits with error 111 on some data #2
Comments
Ok, the issue is due to an implicit conversion from float to int in function VipConnectivityChamferErosion function, but the estimated chamfer size (based on volume voxel size) is less than one for BB339F image. So it is rounded to 0, which is not suitable for chamfer erosion size. |
In fact, Check2DMorphoSizeConsistence returns ok for sizes over 0, but I think that VIP morpho functions that uses VipComputeFrontPropagationConnectivityDistanceMap all fails for sizes in [0, 1] |
Another issue follows the first one. White ridges are not properly detected on BB339F data that makes fail the bias correction. |
The reason is that not enough white matter is kept and the main connected component kept is one of the muscles. |
A temporary simple solution may be to manually crop the data to remove the main muscle part |
Describe the bug
VipT1BiasCorrection ends with error 111 and many error messages.
To Reproduce
Steps to reproduce the behavior:
Download files:
Extract BB339F.zip and baseline_mri_BB336F.zip content
In bv environment built on branch 5.0, run the command :
Expected behavior
With another image and an equivalent command, it works well and generates all expected files correctly:
The expected standard output and error:
Screenshots
Not applicable
Environment:
Additional context
Not applicable
The text was updated successfully, but these errors were encountered: