You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
For volumetry calculation, voxels of the projected Bezier Surface couldn't be counted which lead to an incorrect total volume,
To Reproduce
Try to calculate one of the vascular segments' volume directly
Choose one resection surface node and put points on the same vascular segment, recompute volume.
Expected behavior
The total volume of the chosen area should be 463, but when considering the resection surface, the result loses voxels because projected resection voxels couldn't be counted
Screenshots
The text was updated successfully, but these errors were encountered:
From the top of my head. The projected surface probably has a good thickness (image spacing can exacerbate volume of the resection surface), which can contribute to error.
I would try to use 1 voxel thickness for the projected resection (right now it seems to be 3 voxels wide). The connected threshold filter is configured as face connectivity, which should naturally avoid diagonal leaks. I would expect this to reduce the error.
From the top of my head. The projected surface probably has a good thickness (image spacing can exacerbate volume of the resection surface), which can contribute to error.
I would try to use 1 voxel thickness for the projected resection (right now it seems to be 3 voxels wide). The connected threshold filter is configured as face connectivity, which should naturally avoid diagonal leaks. I would expect this to reduce the error.
Simply removing the 3*3*3 barrier will lead to failed connected thresholding in most cases. So I developed an adaptive algorithm for getting proper resolution of the resection surface to make sure it can be projected as a 1*1*1 thickness continuous barrier for region growth.
Bezier surface is controlled by 16 points and the diagonal points pairs ([0,5,10,15] and [3,6,9,12]) would create the longest Bezier curve within the Bezier surface.
The idea is approximate the two diagonal Bezier lines' length of the bezier surface, then divided by minimal voxel space to get a resolution, so that when the Bezier surface polygon is cutting through voxels we have at least one vertex in each voxel. Then when we label the voxels we can get a safe barrier for region growing.
With this method, we can get fewer errors as shown in the figure below.
#227
Describe the bug
For volumetry calculation, voxels of the projected Bezier Surface couldn't be counted which lead to an incorrect total volume,
To Reproduce
Expected behavior
The total volume of the chosen area should be 463, but when considering the resection surface, the result loses voxels because projected resection voxels couldn't be counted
Screenshots
The text was updated successfully, but these errors were encountered: