I am currently having an issue with thresholding an imported ultrasound scan. when i am setting the thresholding values, the area to be affected is shown as i would expect, like this:
however, after the threshold operation completes, the result is very different. it will cover the entire scan instead of just the selected parts. it looks like this:
if a model is created, it will use the data from the second image.
does anyone know what might be causing this, and how it can be fixed? thanks.
Threshold preview uses the rendered 2D images in the views, so it’s working a completely different way than the actual volume threshold. The result in the second screenshot seems like memory garbage. Not sure why it shows up like this.
Is your ultrasound image a single-component grayscale image?
Slicer-4.10 had the problems that you show above but in recent nightly versions, Segment Editor can directly work on color images (it internally converts color images to grayscale). Please try latest nightly version of Slicer and report back.
It looks like you are correct. I downloaded the recent nightly build, 4.11.0 rev 27539, and ran the threshold operation again. the result is the same as the pre-application outline suggests and the model generated from it lines up with this. post threshold:
