[Bug] Sharkbite Bug - all segmentations have a visual bug impacting ink detection training. about volume-cartographer HOT 4 CLOSED

Please post the image, a screenshot of the same error in 3D, and if possible, a zip containing the textured mesh (obj + tif + mtl).

from volume-cartographer.

I have given an example here, where the segmentation line has been pulled too far in VC, leaving a steep edge in the 3D image, and sharkbites in the tif (centered in each frame). I've been running the smoothing function in VC and it gets rid of 3/4 of the sharkbites. RICHI is saying his new algorithm is good enough to not have this happen, and we will be able to inspect his results hopefully in the coming week. So with any luck we have sidestepped the issue here.

12931.zip

from volume-cartographer.

Smoothing the mesh (--mesh-resample-smoothing 3) during vc_render makes this bug less severe. example command:

vc_render -v ../ -s {segmentation number} -o out.obj --output-ppm out.ppm --mesh-resample-smoothing 3
vc_layers_from_ppm -v ../ -p out.ppm --output-dir layers/

This is an easy fix that could also be run on the already existing segments

from volume-cartographer.

Yeah, as shown in your images, the surface "significantly" changed shape between two slices (significantly as far as the meshing is concerned). I don't think this is likely to cause much issue for any downstream tasks like ink-id or anything of that sort.

I'm not quite sure what one would do to fix this in any sort of automatic sense. It's possible that, in general, someone needs to do that with the surface they're segmenting and it just so happens to be wrong here. I don't know. This feels like something a good segmentation editor might be able to handle.

from volume-cartographer.