# Real-time collaborative segmentation #2

**URL:** <https://discourse.slicer.org/t/real-time-collaborative-segmentation-2/44373>\
**Category:** Support\
**Created:** [September 6, 2025, 4:52pm UTC](https://discourse.slicer.org/t/real-time-collaborative-segmentation-2/44373 "2025-09-06T16:52:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gregsharp.geo](https://avatars.discourse-cdn.com/v4/letter/g/6bbea6/32.png) [@gregsharp.geo](https://discourse.slicer.org/u/gregsharp.geo)\
**Post date:** [September 6, 2025, 4:52pm UTC](https://discourse.slicer.org/t/real-time-collaborative-segmentation-2/44373/1 "2025-09-06T16:52:09Z")

</div>

Hello friends. Good to be back.

I read the topic ( [Adding near-real time collaborative manual segmentation](https://discourse.slicer.org/t/adding-near-real-time-collaborative-manual-segmentation/29255) ) with interest, and it partly answered my questions. But it seems maybe different use case, so I started a new topic.

Is Slicer a good platform for collaborative (desktop, no VR) manual segmentation? Two users would edit segmentations simultaneously in the same scene, with near real-time update, and maybe a third view-only workstation. The VNC solution seems not be suitable; but maybe this is possible through OpenIGTLink?

Also, what is the current state of Slicer dual screen?

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [September 6, 2025, 5:09pm UTC](https://discourse.slicer.org/t/real-time-collaborative-segmentation-2/44373/2 "2025-09-06T17:09:54Z")

</div>

> [@gregsharp.geo](#):
>
> Is Slicer a good platform for collaborative (desktop, no VR) manual segmentation? Two users would edit segmentations simultaneously in the same scene, with near real-time update,

Slicer is a great platform for collaborative segmentation. but what’s the use case for **simultaneous segmentation with near real-time update?** Also are segmenters segmenting the same structure or adjacent structures (but not the same thing)?

If you give more information we can give more to do the point feedback.

> [@gregsharp.geo](#):
>
> Also, what is the current state of Slicer dual screen?

You can dock out the module pane, python console and log and move them to a second screen, but the main application window (with viewers) will be on a single monitor.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [September 6, 2025, 5:32pm UTC](https://discourse.slicer.org/t/real-time-collaborative-segmentation-2/44373/3 "2025-09-06T17:32:11Z")

</div>

👋 @gregsharp.geo

Here’s an experiment to test the multiscreen idea. It would be pretty easy to make something like this a core feature.

```auto
w = qt.QWidget()
w.setLayout(qt.QVBoxLayout())
t = slicer.app.layoutManager().threeDWidget(0)
w.layout().addWidget(t)
w.show()

```

For collaborative segmentation projects, @muratmaga and I have been working on [MorphoDepot](https://github.com/MorphoCloud/SlicerMorphoDepot) which aims to handle the bookkeeping. I could imagine adding some realtime features, but like Murat I’m not sure I see the use case.

---

<div class="post-metadata">

**Author:** ![gregsharp.geo](https://avatars.discourse-cdn.com/v4/letter/g/6bbea6/32.png) [@gregsharp.geo](https://discourse.slicer.org/u/gregsharp.geo)\
**Post date:** [September 6, 2025, 5:56pm UTC](https://discourse.slicer.org/t/real-time-collaborative-segmentation-2/44373/4 "2025-09-06T17:56:29Z")

</div>

> [@muratmaga](#):
>
> Slicer is a great platform for collaborative segmentation. but what’s the use case for **simultaneous segmentation with near real-time update?** Also are segmenters segmenting the same structure or adjacent structures (but not the same thing)?

Yes of course. My use case is adaptive radiotherapy (RT).

In North America 2025, a small subset (\<1%) of RT procedures have become more like surgery. We plan and treat on the spot. Traditional RT uses a pre-planned radiation plan every day, adjusting only for patient translation and rotation.

In 2025, these adaptive treatments are perhaps 45 minutes with perhaps 4-5 persons (including a physician). A traditional treatment is perhaps 15 minutes with perhaps 2-3 persons (and no physician). Adaptive RT is high quality, but access is limited due to cost.

The goal would be for to allow a smaller non-physician team (two people) to segment avoidance structures at the same time, reducing the treatment time. Physician would come at the end, review and edit if needed, and then we treat within 20 mins.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [September 6, 2025, 6:34pm UTC](https://discourse.slicer.org/t/real-time-collaborative-segmentation-2/44373/5 "2025-09-06T18:34:56Z")

</div>

This is a great use case Greg. Have you tried nnInteractive to speed up the segmentation?

Also, given the results we’ve seen in other fields, I think we would be able to train AI models for this task given a decent set of ground truth segmentations.