# Hiding patient in hierarchy

**URL:** https://discourse.slicer.org/t/hiding-patient-in-hierarchy/11850
**Category:** Support
**Created:** [June 3, 2020, 4:52pm UTC](https://discourse.slicer.org/t/hiding-patient-in-hierarchy/11850 "2020-06-03T16:52:55Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![gcsharp](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/gcsharp/32/863_2.png) [@gcsharp](https://discourse.slicer.org/u/gcsharp)
#### Post date: [June 3, 2020, 4:52pm UTC](https://discourse.slicer.org/t/hiding-patient-in-hierarchy/11850/1 "2020-06-03T16:52:55Z")

</div>

When I click on the eyeball at the patient level the subject hierarchy, I would expect it to hide the entire patient (both CT and structure set), but it only hides the structure set. Is this a bug or is this “works as designed”?

![2020-06-03_12-46_1](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/b/9/b98f8563cec6c97bd6ccc437f6802b897e80b771.png)

---

<div class="post-metadata">

### Author: ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)
#### Post date: [June 3, 2020, 5:53pm UTC](https://discourse.slicer.org/t/hiding-patient-in-hierarchy/11850/2 "2020-06-03T17:53:42Z")

</div>

Volume slice visibility is done through a completely different mechanism than the visibility of other data types such as models, segmentations, fiducials, etc. The normal eye icon affects only these kinds of data (and now with a recent improvement also volume rendering), but not 2D volume visibility. You can see that also the icon indicates that it is different.

As I remember there is an option in the study right-click menu "Show volumes in study"m but I’m not sure if there is one for hiding as well.

---

<div class="post-metadata">

### Author: ![gcsharp](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/gcsharp/32/863_2.png) [@gcsharp](https://discourse.slicer.org/u/gcsharp)
#### Post date: [June 3, 2020, 6:29pm UTC](https://discourse.slicer.org/t/hiding-patient-in-hierarchy/11850/3 "2020-06-03T18:29:49Z")

</div>

Thank you Csaba. Yes, I assumed that this behavior is because the of the different mechanisms. Clicking the eyeball+volume does show and hide the volume. The eyeball at the study level doesn’t do anything. My opinion is that usability is improved if parent levels hide their children, regardless of the mechanism difference. I’ll go ahead and file a bug report, but obviously this is not anything urgent.

> <https://github.com/Slicer/Slicer/issues/4961>
>
> The visibility toggle button (ie. the eyeball button) in the subject hierarchy can be used to show or hide the children...

---

<div class="post-metadata">

### Author: ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)
#### Post date: [June 3, 2020, 9:20pm UTC](https://discourse.slicer.org/t/hiding-patient-in-hierarchy/11850/4 "2020-06-03T21:20:20Z")

</div>

This is something that has caused us a headache for years. Until last year the eye icon of the parents showed/hid all the children one by one. Then we made a change (in course of the Model Hierarchy rework) that the children’s displayable managers consider the folder type parents’ visibility.

If the study item does not affect the children (of type segmentation, model, etc.), then it is a bug.  
If the volume show/hide does not work, then it is also a bug.  
But there might be some things that are features 🙂 I’ll do some testing tomorrow.

---

<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: [June 3, 2020, 9:46pm UTC](https://discourse.slicer.org/t/hiding-patient-in-hierarchy/11850/5 "2020-06-03T21:46:24Z")

</div>

Yes, the problem is that volume display is different from all other nodes, as there is a limit on how many volumes can be displayed at once.

With multi-volume rendering, the issue is resolved for 3D views.

We could also update the slice views to be able to display any number of volumes. It would make the behavior more consistent and there are applications where display of more than 2 volumes would be useful.

---

<div class="post-metadata">

### Author: ![gcsharp](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/gcsharp/32/863_2.png) [@gcsharp](https://discourse.slicer.org/u/gcsharp)
#### Post date: [June 3, 2020, 10:12pm UTC](https://discourse.slicer.org/t/hiding-patient-in-hierarchy/11850/6 "2020-06-03T22:12:04Z")

</div>

> [@cpinter](#):
>
> If the study item does not affect the children (of type segmentation, model, etc.), then it is a bug.  
> If the volume show/hide does not work, then it is also a bug.

Those are working very well for me. Show/hide is very usable, almost perfect!

---

<div class="post-metadata">

### Author: ![Danielle\_Wasserman](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/danielle_wasserman/32/13559_2.png) [@Danielle\_Wasserman](https://discourse.slicer.org/u/Danielle_Wasserman)
#### Post date: [June 21, 2022, 8:33pm UTC](https://discourse.slicer.org/t/hiding-patient-in-hierarchy/11850/7 "2022-06-21T20:33:51Z")

</div>

I’m afraid that I have the recurring problem of not being able to hide the model by clicking the eye in the hierarchy. It happened yesterday with one specimen and now it is happening with multiples. I can hide the markups but not the 3d model and I must be able to do it to proceed with my markup placement. I hope very much to resolve as soon as possible as I am incredibly behind on my work.

---

<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: [June 22, 2022, 1:22am UTC](https://discourse.slicer.org/t/hiding-patient-in-hierarchy/11850/8 "2022-06-22T01:22:32Z")

</div>

The problem was reported [here](https://github.com/Slicer/Slicer/issues/6445) and a fix will be available in tomorrow’s Slicer Preview Release.
