# Why my computer bug when I start parenchyma analysis after segmentation?

**URL:** <https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414>\
**Category:** Support\
**Created:** [December 6, 2019, 2:37pm UTC](https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414 "2019-12-06T14:37:19Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Benjamin\_Coiffard](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/benjamin_coiffard/32/5335_2.png) [@Benjamin\_Coiffard](https://discourse.slicer.org/u/Benjamin_Coiffard)\
**Post date:** [December 6, 2019, 2:37pm UTC](https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414/1 "2019-12-06T14:37:19Z")

</div>

Operating system: MacBookPro11,1 ; intel Core i5; 2,6GHz; RAM 8Go  
Slicer version: SlicerCIP 4.10.2

Why my computer bug when I start parenchyma analysis after segmentation?  
I can segment lungs and lobes but the software bug when I perform parenchyma analysis to obtain lung densitometry…  
Is my computer not powerful enough

Thanks  
Benjamin

---

<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:** [December 6, 2019, 2:53pm UTC](https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414/2 "2019-12-06T14:53:54Z")

</div>

Hi -

Can you post the error log and more details as described here:

[https://www.slicer.org/wiki/Documentation/Nightly/Report\_a\_problem](https://www.slicer.org/wiki/Documentation/Nightly/Report_a_problem)

Thanks

---

<div class="post-metadata">

**Author:** ![Benjamin\_Coiffard](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/benjamin_coiffard/32/5335_2.png) [@Benjamin\_Coiffard](https://discourse.slicer.org/u/Benjamin_Coiffard)\
**Post date:** [December 6, 2019, 3:18pm UTC](https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414/3 "2019-12-06T15:18:55Z")

</div>

Hi Steve,  
Thank you for your rapid answer.  
I’m not a developer so I can’t do anything manually…  
I notice first that when I click on Filtering “On” nothing appears.  
Second When I apply for parenchyma analysis from my CT images (precising Label Map Volume = None) segmentation appears but no “Histogram” and no “Chart section”.  
Then when I apply with Label Map Volume = myCTpartialLungLabelMap (segmentation) it starts analysing and then shut down…  
I can’t say anymore.  
See screenshot attached if it’s working  
Regards  
Benjamin

 ![Capture d’écran 2019-12-06 à 10.05.49](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/3/6/3612cedb91dc2cb115261bdf38dd56f0cb5fa823.png)

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [December 6, 2019, 4:01pm UTC](https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414/4 "2019-12-06T16:01:01Z")

</div>

Nothing happens when you click “Filtering on” because there is `AttributeError: QFrame has no attribute named 'setShown'`. This is a problem with the code [here](https://github.com/acil-bwh/SlicerCIP/blob/develop/Scripted/CIP_/CIP/ui/PreProcessingWidget.py#L200-L204). `setShown` is specifically a Qt3 thing that was supported in Qt4 to help with that transition of 3 to 4. That transition happened a long time ago, so not sure how much effort is being put into SlicerCIP recently. Unclear if SlicerCIP will be updated for Slicer5/Slicer-preview which includes the transition to Qt5.

@jcfr and @cpinter have issued some commits to SlicerCIP in the past, but I’m not sure who the best person to contact would be to fix various issues in the code. You say you’re not a developer, but you could potentially create a GitHub account and post an issue to [https://github.com/acil-bwh/SlicerCIP/issues](https://github.com/acil-bwh/SlicerCIP/issues) detailing the problems that you are seeing.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [December 6, 2019, 10:11pm UTC](https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414/5 "2019-12-06T22:11:53Z")

</div>

Look like this particular issue has been addressed in [https://github.com/acil-bwh/SlicerCIP/commit/115959155cdb5f6bfbeffc6c1f794fcb6bdeb509](https://github.com/acil-bwh/SlicerCIP/commit/115959155cdb5f6bfbeffc6c1f794fcb6bdeb509)

Thanks @PNardelli🙏

Since the extensionIndex is already [associated](https://github.com/Slicer/ExtensionsIndex/blob/4468a15a5ca7cc1ae54d84c7b8abb8286d998eb8/Chest_Imaging_Platform.s4ext#L10-L11) with the `develop` branch where the fix has been integrated, tomorrow extensions should include the fix 🎉

---

<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:** [December 10, 2019, 8:15pm UTC](https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414/6 "2019-12-10T20:15:30Z")

</div>

@Benjamin_Coiffard are you able to confirm the fix that @PNardelli provide?

---

<div class="post-metadata">

**Author:** ![Benjamin\_Coiffard](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/benjamin_coiffard/32/5335_2.png) [@Benjamin\_Coiffard](https://discourse.slicer.org/u/Benjamin_Coiffard)\
**Post date:** [December 10, 2019, 9:13pm UTC](https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414/7 "2019-12-10T21:13:51Z")

</div>

Hi Steve,  
You know those scripts are just Chinese for me.  
I tried to put this one in the Python Interactor put it doesn’t work from that point…

 ![Capture d’écran 2019-12-10 à 16.11.45](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/4/d/4d7983f45f2d9d49038423c84263b290b0628d6d.png)

---

<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:** [December 10, 2019, 9:48pm UTC](https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414/8 "2019-12-10T21:48:11Z")

</div>

> [@Benjamin\_Coiffard](#):
>
> those scripts are just Chinese for me.

haha 😉

But if you download a new nightly build of Slicer you should be able to install the latest CIP extension.

---

<div class="post-metadata">

**Author:** ![Benjamin\_Coiffard](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/benjamin_coiffard/32/5335_2.png) [@Benjamin\_Coiffard](https://discourse.slicer.org/u/Benjamin_Coiffard)\
**Post date:** [December 10, 2019, 10:55pm UTC](https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414/9 "2019-12-10T22:55:42Z")

</div>

Thanks Steve  
But I tried already but I don’t even know how to install the latest CIP extension on 3D Slicer version 11. There is now CIP in the Extensions Manager.  
I’m going crazy… I really need to use CIP…

---

<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:** [December 11, 2019, 3:16pm UTC](https://discourse.slicer.org/t/why-my-computer-bug-when-i-start-parenchyma-analysis-after-segmentation/9414/10 "2019-12-11T15:16:20Z")

</div>

It looks like there are still some problems with the build and that’s why the extension is not showing up.

@PNardelli do you know how to fix these?

[http://slicer.cdash.org/viewBuildError.php?buildid=1771659](http://slicer.cdash.org/viewBuildError.php?buildid=1771659)

[http://slicer.cdash.org/viewBuildError.php?buildid=1771866](http://slicer.cdash.org/viewBuildError.php?buildid=1771866)