# RFC : is there interest in this custom module - Guided vein segmentation

**URL:** <https://discourse.slicer.org/t/rfc-is-there-interest-in-this-custom-module-guided-vein-segmentation/31002>\
**Category:** VMTK\
**Created:** [August 5, 2023, 6:59pm UTC](https://discourse.slicer.org/t/rfc-is-there-interest-in-this-custom-module-guided-vein-segmentation/31002 "2023-08-05T18:59:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)\
**Post date:** [August 5, 2023, 6:59pm UTC](https://discourse.slicer.org/t/rfc-is-there-interest-in-this-custom-module-guided-vein-segmentation/31002/1 "2023-08-05T18:59:48Z")

</div>

Hi all,

I am contemplating merging this module, [Guided vein segmentation](https://github.com/chir-set/Tools7/tree/master/GuidedVeinSegmentation), in SlicerVMTK, so that it become easily available.

Beforehand, I wish to know if other users find it worthwhile as an addition to SlicerVMTK.

Its purpose is to segment _major_ veins from CT angioscans, considering that the veins are not contrast enhanced. I find it quite efficient and useful for surgical planning in some complex aortic cases namely. Please read the notes on its homepage.

It does not use the VMTK libraries themselves, rather the Segment Editor effects only.

It’s now in my repository, moving it to SlicerVMTK is easy. I’ll do so if some users find interest in it, unless Slicer devs or VMTK devs object this proposal.

Thank you for any input.

---

<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:** [August 5, 2023, 7:08pm UTC](https://discourse.slicer.org/t/rfc-is-there-interest-in-this-custom-module-guided-vein-segmentation/31002/2 "2023-08-05T19:08:21Z")

</div>

That sounds useful to me. SlicerVMTK started as a way to expose VMTK code in Slicer, but I think it’s much better to have a comprehensive set of vessel-related tools in a single extension, like SlicerRT is for RT.

---

<div class="post-metadata">

**Author:** ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)\
**Post date:** [August 6, 2023, 3:27pm UTC](https://discourse.slicer.org/t/rfc-is-there-interest-in-this-custom-module-guided-vein-segmentation/31002/3 "2023-08-06T15:27:46Z")

</div>

With one supportive view from a Slicer developer, I’ll proceed with the integration of this module in SlicerVMTK ASAP.

Thank you @pieper.

---

<div class="post-metadata">

**Author:** ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)\
**Post date:** [August 7, 2023, 1:52pm UTC](https://discourse.slicer.org/t/rfc-is-there-interest-in-this-custom-module-guided-vein-segmentation/31002/4 "2023-08-07T13:52:13Z")

</div>

Hi @pieper ,

Just a quick follow-up, it’s merged in [#89](https://github.com/vmtk/SlicerExtension-VMTK/pull/89).

Regards.