# Workflow for (Manual, Ground Truth) Segmentations in VFSS

**URL:** <https://discourse.slicer.org/t/workflow-for-manual-ground-truth-segmentations-in-vfss/34535>\
**Category:** Support\
**Tags:** segmentation\
**Created:** [February 26, 2024, 3:37am UTC](https://discourse.slicer.org/t/workflow-for-manual-ground-truth-segmentations-in-vfss/34535 "2024-02-26T03:37:54Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [February 26, 2024, 3:39am UTC](https://discourse.slicer.org/t/workflow-for-manual-ground-truth-segmentations-in-vfss/34535/2 "2024-02-26T03:39:49Z")

</div>

See this post about tools used for segmenting 2D time series (ultrasound image sequences):

> [@3D slicer for US segmentation](https://discourse.slicer.org/t/3d-slicer-for-us-segmentation/34526/3):
>
> I think segmentation itself is best done outside of Slicer. I used to install TensorFlow and PyTorch in Slicer’s python environment and run segmentation in Slicer, but then it seemed better to run segmentation in everyone’s favorite AI environment, and communicate with Slicer via OpenIGTLink. You can stream the ultrasound images from Slicer or PLUS to an Anaconda environment and receive the segmentations back in Slicer (or whatever your application is) nearly real time. I still use Slicer for m…

---

_[View the full topic](https://discourse.slicer.org/t/workflow-for-manual-ground-truth-segmentations-in-vfss/34535)._