# How can I merge different DICOM view in ones? 

**URL:** https://discourse.slicer.org/t/how-can-i-merge-different-dicom-view-in-ones/21619
**Category:** Support
**Tags:** dicom
**Created:** [January 25, 2022, 12:44pm UTC](https://discourse.slicer.org/t/how-can-i-merge-different-dicom-view-in-ones/21619 "2022-01-25T12:44:04Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![AndreaChiericati](https://avatars.discourse-cdn.com/v4/letter/a/ccd318/32.png) [@AndreaChiericati](https://discourse.slicer.org/u/AndreaChiericati)
#### Post date: [January 25, 2022, 12:44pm UTC](https://discourse.slicer.org/t/how-can-i-merge-different-dicom-view-in-ones/21619/1 "2022-01-25T12:44:04Z")

</div>

Hi all,  
Do you know if I could merge different DICOM that have a good quality on one view, but in the others not? Do you know how can I merge it all together?

---

<div class="post-metadata">

### Author: ![Juicy](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@Juicy](https://discourse.slicer.org/u/Juicy)
#### Post date: [January 25, 2022, 10:01pm UTC](https://discourse.slicer.org/t/how-can-i-merge-different-dicom-view-in-ones/21619/2 "2022-01-25T22:01:31Z")

</div>

As far as I am aware there is no effective way of doing this on 3D Slicer. Basically, you have to acquire the scan in high resolution (minimal field of view (FOV) and small slice thickness/interval) at the point of acquisition i.e. when taking the CT scan. Depending on the acquisition parameters used you may be able to reconstruct the CT scan with smaller slice thicknesses/intervals or FOV if you have access to the original CT machine and the scan is still on the machine (if it was taken recently). Have a read of these related posts:

> [@Combining volumes - what am I missing?](https://discourse.slicer.org/t/combining-volumes-what-am-i-missing/2941/2):
>
> In general, these multiple low-resolution acquisitions are not well suited for any 3D processing, so the best would be to acquire proper 3D volume, with as isotropic spacing (cubic voxel shape) as possible. You may try to find toolkits that can create an isotropic super-resolution image from multiple low-resolution sweeps, but this is a difficult image reconstruction problem, so there are no standard solutions. Have a look at this post [Import volume by projections](https://discourse.slicer.org/t/import-volume-by-projections/2871/6) for info on a toolkit that mig…

---

<div class="post-metadata">

### Author: ![stevenagl12](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stevenagl12/32/3391_2.png) [@stevenagl12](https://discourse.slicer.org/u/stevenagl12)
#### Post date: [January 25, 2022, 10:04pm UTC](https://discourse.slicer.org/t/how-can-i-merge-different-dicom-view-in-ones/21619/3 "2022-01-25T22:04:12Z")

</div>

you could do this programmatically, by reading in the first DICOM, and (so long as you know the slices or regions) indexing into the image to change the values themselves to the new values from the new file (so long as spatial dimensions, direction, and such are preserved, especially if you have them registered together).

---

<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: [January 25, 2022, 11:53pm UTC](https://discourse.slicer.org/t/how-can-i-merge-different-dicom-view-in-ones/21619/4 "2022-01-25T23:53:12Z")

</div>

> [@stevenagl12](#):
>
> so long as spatial dimensions, direction, and such are preserved

I don’t think this is the case. @AndreaChiericati would like to merge 3 sets of slices, each set with a different orientation, and fill in the blanks in between the slices that are quite far from each other (slice spacing is huge compared to in-slice pixel spacing). That is an extremely hard task and it cannot be solved in a general way, but you need to have some model that knows how to fill in the gaps. Nowadays this would be implemented by a well-trained deep learning model.

---

<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: [January 25, 2022, 11:58pm UTC](https://discourse.slicer.org/t/how-can-i-merge-different-dicom-view-in-ones/21619/5 "2022-01-25T23:58:13Z")

</div>

> [@lassoan](#):
>
> Nowadays this would be implemented by a well-trained deep learning model.

SynthSR is an example of doing this in the brain. It would be great if people made similar tools for other parts of the body.

> **[GitHub - BBillot/SynthSR: A framework for joint super-resolution and image...](https://github.com/BBillot/SynthSR)**
>
> A framework for joint super-resolution and image synthesis, without requiring real training data - GitHub - BBillot/SynthSR: A framework for joint super-resolution and image synthesis, without requ...

---

<div class="post-metadata">

### Author: ![stevenagl12](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stevenagl12/32/3391_2.png) [@stevenagl12](https://discourse.slicer.org/u/stevenagl12)
#### Post date: [January 26, 2022, 12:50pm UTC](https://discourse.slicer.org/t/how-can-i-merge-different-dicom-view-in-ones/21619/6 "2022-01-26T12:50:50Z")

</div>

Couldn’t you also register the models, resample them to a set voxel dimension, and then insert these slices into the appropriately interpolated regions?

---

<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: [January 26, 2022, 12:53pm UTC](https://discourse.slicer.org/t/how-can-i-merge-different-dicom-view-in-ones/21619/7 "2022-01-26T12:53:30Z")

</div>

Typically the problem is there is missing data. If you have widely spaced slices in one direction they are like lines on ruled writing paper with empty space between. If you have two directions they are like lines on graph paper and the problem is that you don’t know how to fill in the boxes with accurate data.
