# Cropped volume to inherit display preferences

**URL:** <https://discourse.slicer.org/t/cropped-volume-to-inherit-display-preferences/20859>\
**Category:** Feature requests\
**Created:** [December 1, 2021, 3:00am UTC](https://discourse.slicer.org/t/cropped-volume-to-inherit-display-preferences/20859 "2021-12-01T03:00:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![DIV](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/div/32/12816_2.png) [@DIV](https://discourse.slicer.org/u/DIV)\
**Post date:** [December 1, 2021, 3:00am UTC](https://discourse.slicer.org/t/cropped-volume-to-inherit-display-preferences/20859/1 "2021-12-01T03:00:43Z")

</div>

In the **Crop Volume** module a user can create a new volume by cropping an existing volume.

Where the _existing volume_ has a display `Preset` configured for 3D rendering in the **Volume Rendering** module and/or display settings (`Lookup Table` and `Window/Level`) configured for slice display in the **Volumes** module, the _cropped volume_ loses this information.

I think it would be a nice default for the cropped volume to inherit this information from the original volume.

—DIV

---

<div class="post-metadata">

**Author:** ![rbumm](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rbumm/32/9404_2.png) [@rbumm](https://discourse.slicer.org/u/rbumm)\
**Post date:** [December 1, 2021, 7:29am UTC](https://discourse.slicer.org/t/cropped-volume-to-inherit-display-preferences/20859/2 "2021-12-01T07:29:28Z")

</div>

With a Slicer preview version, my cropped lung CT (top) gets the same volume window/level preset (“Lung CT”) as the source CT (bottom) [image source @PaoloZaffino open source COV dataset]

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/1/b/1b25df7b6807d44766132ac56b3b10bb6477ac54.jpeg)

---

<div class="post-metadata">

**Author:** ![DIV](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/div/32/12816_2.png) [@DIV](https://discourse.slicer.org/u/DIV)\
**Post date:** [December 10, 2021, 3:29am UTC](https://discourse.slicer.org/t/cropped-volume-to-inherit-display-preferences/20859/3 "2021-12-10T03:29:19Z")

</div>

Hello, Rudolf.  
Just today I have downloaded and installed the latest preview (4.13.0-2021-12-08).  
I can confirm that in this version of 3D Slicer the cropped volume:

- _does_ inherit the 2D slice display settings (per **Volumes** module); but
- _does not_ inherit the 3D reconstruction display settings (per **Volume Rendering** module).

—DIV

---

<div class="post-metadata">

**Author:** ![rbumm](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rbumm/32/9404_2.png) [@rbumm](https://discourse.slicer.org/u/rbumm)\
**Post date:** [December 19, 2021, 6:15pm UTC](https://discourse.slicer.org/t/cropped-volume-to-inherit-display-preferences/20859/4 "2021-12-19T18:15:46Z")

</div>

Sry, late reply. Thank you.

Is cropping and then volume rendering something you use often and lose too much time when selecting the preset? Could you maybe better crop _inside_ volume rendering by using its ROI function? That is what I always do …

---

<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:** [December 19, 2021, 8:13pm UTC](https://discourse.slicer.org/t/cropped-volume-to-inherit-display-preferences/20859/5 "2021-12-19T20:13:54Z")

</div>

> [@DIV](#):
>
> - _does not_ inherit the 3D reconstruction display settings (per **Volume Rendering** module).

You can choose to share volume rendering and cropping settings between multiple volumes. By default they are different, but in Volume Rendering module / Inputs section you can select the same ROI and Property nodes.

But I think @rbumm’s suggestion of cropping in Volume Rendering module is probably a better idea. You can later select the same ROI in Crop Volume module.

---

<div class="post-metadata">

**Author:** ![DIV](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/div/32/12816_2.png) [@DIV](https://discourse.slicer.org/u/DIV)\
**Post date:** [January 18, 2022, 6:22am UTC](https://discourse.slicer.org/t/cropped-volume-to-inherit-display-preferences/20859/6 "2022-01-18T06:22:58Z")

</div>

Hello, Rudolf & Andras.

I would be regularly cropping (in the **Crop Volume** module) and volume rendering according to my current ‘workflow’. I don’t think I would say “often”, though: it would generally be once per CT scan. This is for the purposes of _segmentation_, specifically:

- reducing the volume to be segmented (cutting computational load, and making it easier to see what’s going on); and
- improving the sampling properties (resolution & aspect ratio of voxels), as per the advice below.

> [@How can I configure Slicer to open automatically with my preferred settings for the View Controllers module?](https://discourse.slicer.org/t/how-can-i-configure-slicer-to-open-automatically-with-my-preferred-settings-for-the-view-controllers-module/20233/11):
>
> a one-time cropping and resampling to isotropic spacing before starting segmentation is usually beneficial.

> [@Is Resampling Necessary?](https://discourse.slicer.org/t/is-resampling-necessary/21055/2):
>
> If you are going to need to use filters for smoothing, or do morphological operations (dilation and erosion), you will find that resultant segments will look better if you have isotropic data.

On the other hand I do often use the cropping within the **Volume Rendering** module purely for visualisation. AFAIK, the functionality in that module is not able to restrict the voxels being segmented, nor resample. Did I miss something?

—DIV