# Multiple partial volumes reconstruction

**URL:** <https://discourse.slicer.org/t/multiple-partial-volumes-reconstruction/25786>\
**Category:** Support\
**Tags:** registration, segmentation, multivolume\
**Created:** [October 20, 2022, 12:37am UTC](https://discourse.slicer.org/t/multiple-partial-volumes-reconstruction/25786 "2022-10-20T00:37:51Z")\
**Posts on this page:** 1\
**Showing post:** 19

<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:** [October 31, 2022, 7:22pm UTC](https://discourse.slicer.org/t/multiple-partial-volumes-reconstruction/25786/19 "2022-10-31T19:22:17Z")

</div>

> [@mikebind](#):
>
> Is the right way to do that to fork the current Sandbox, update with my new code, and then create a pull request?

Yes. Thank you!

> [@mikebind](#):
>
> Is there a way to automatically add a warning of some kind to CLI modules if a user tries to select a transformed node as an input? It is not always obvious to end users that a module they select is a CLI module behind the scenes, and even if they did know, it is not obvious that soft transforms are ignored for these modules.

I agree, it would make sense. I’ve created a [new topic to discuss this](https://discourse.slicer.org/t/cli-modules-ignore-parent-transform/25987).

> [@Young\_Wang](#):
>
> I aligned those volumes, followed by applying and hardening the corresponding transforms.

The module currently stitches the volumes by splitting them along one of the 3 image axes. In the example above, the images seem to overlap in a very complex pattern. To accommodate such cases, the module could be updated to compute a weighted average of all the input images. The distance map computed from non-empty voxel locations could be used as weighting coefficients.

---

_[View the full topic](https://discourse.slicer.org/t/multiple-partial-volumes-reconstruction/25786)._