# Chest Imaging Platform - Lung Lesion Analyzer error

**URL:** <https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232>\
**Category:** Support\
**Tags:** segmentation\
**Created:** [August 17, 2021, 3:33pm UTC](https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232 "2021-08-17T15:33:53Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![matt-warkentin](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/matt-warkentin/32/4962_2.png) [@matt-warkentin](https://discourse.slicer.org/u/matt-warkentin)\
**Post date:** [August 17, 2021, 3:33pm UTC](https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232/1 "2021-08-17T15:33:53Z")

</div>

Hi all,

I have run into an issue trying to the `Lung Lesion Analyzer` submodule from the `Chest Imaging Platform` extension. For context, this error arises on the current stable build of Slicer on MacOS (version `4.11.20210226`), but the issue does not occur on some previous versions (I can confirm it works on `4.8.1`).

When trying to add a `New Nodule` the following error is produced in the python REPL:

```auto
Traceback (most recent call last):
  File "/Applications/Slicer.app/Contents/Extensions-29738/Chest_Imaging_Platform/lib/Slicer-4.11/qt-scripted-modules/CIP_LesionModel.py", line 1352, in __onAddNoduleButtonClicked__
    self.addNewNodule()
  File "/Applications/Slicer.app/Contents/Extensions-29738/Chest_Imaging_Platform/lib/Slicer-4.11/qt-scripted-modules/CIP_LesionModel.py", line 720, in addNewNodule
    fiducialsNode.AddObserver(fiducialsNode.MarkupAddedEvent, self. __onAddedSeed__ )
AttributeError: 'vtkSlicerMarkupsModuleMRMLPython.vtkMRMLMarkupsFid' object has no attribute 'MarkupAddedEvent'

```

I am not sure whether something has changed on the Slicer side of things that might throw this error, or if this is strictly a `CIP` extension issue. Has the `MarkupEventAdded` attributed been dropped in recent versions?

In any case, in the past I have tried seeking help with bugs by posting issues on their GitHub to no response, so I am turning here for advice.

---

<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:** [August 17, 2021, 8:13pm UTC](https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232/2 "2021-08-17T20:13:38Z")

</div>

Yes, the markups have improved a lot in Slicer since 4.8.1, so if CIP hasn’t been updated then you will probably still need to use the old version. Probably you can move data back and forth easily if you also need to use features of new versions of Slicer.

---

<div class="post-metadata">

**Author:** ![matt-warkentin](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/matt-warkentin/32/4962_2.png) [@matt-warkentin](https://discourse.slicer.org/u/matt-warkentin)\
**Post date:** [August 18, 2021, 2:38pm UTC](https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232/3 "2021-08-18T14:38:01Z")

</div>

Thanks for the response, @pieper.

Does Slicer have any protection against having extensions available in the extension manager for a given version if those extensions haven’t been tested against/updated to that version?

---

<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:** [August 18, 2021, 2:49pm UTC](https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232/4 "2021-08-18T14:49:33Z")

</div>

Extensions are closely tied to the version of Slicer so generally this works well. Often C++ extensions will fail to build if they aren’t compatible with the version of Slicer, so that will make them unavailable, but with python scripts they may fail at runtime with errors like you saw. We don’t really want to prevent people from installing an extension where some parts may be useful and even if other parts are broken. Often extension developers don’t have resources to maintain and update all the code so they rely on motivated community members to help identify and fix issues.

---

<div class="post-metadata">

**Author:** ![matt-warkentin](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/matt-warkentin/32/4962_2.png) [@matt-warkentin](https://discourse.slicer.org/u/matt-warkentin)\
**Post date:** [August 18, 2021, 2:55pm UTC](https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232/5 "2021-08-18T14:55:01Z")

</div>

> [@pieper](#):
>
> We don’t really want to prevent people from installing an extension where some parts may be useful and even if other parts are broken. Often extension developers don’t have resources to maintain and update all the code so they rely on motivated community members to help identify and fix issues.

Totally understandable on both points. I may make an attempt at trying to fix this bug and if so I will submit the PR to the maintainers. Thanks!

---

<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:** [August 18, 2021, 2:56pm UTC](https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232/6 "2021-08-18T14:56:34Z")

</div>

> [@matt-warkentin](#):
>
> I may make an attempt at trying to fix this bug and if so I will submit the PR to the maintainers.

That would be much appreciated!

---

<div class="post-metadata">

**Author:** ![Eserval](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/eserval/32/14650_2.png) [@Eserval](https://discourse.slicer.org/u/Eserval)\
**Post date:** [December 8, 2022, 2:19pm UTC](https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232/7 "2022-12-08T14:19:08Z")

</div>

Hello everyone !

Did we have some sucess in update the Lung Lesion Analyzer tool ?

Best

---

<div class="post-metadata">

**Author:** ![matt-warkentin](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/matt-warkentin/32/4962_2.png) [@matt-warkentin](https://discourse.slicer.org/u/matt-warkentin)\
**Post date:** [December 8, 2022, 5:44pm UTC](https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232/8 "2022-12-08T17:44:25Z")

</div>

@Eserval Sorry, I never ended up getting around to working on a fix.

---

<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 8, 2022, 6:04pm UTC](https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232/9 "2022-12-08T18:04:45Z")

</div>

Thanks @matt-warkentin - is there a demo somewhere of what the lung lesion analyzer actually did? Is it something like MINT lesion functionality?

---

<div class="post-metadata">

**Author:** ![matt-warkentin](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/matt-warkentin/32/4962_2.png) [@matt-warkentin](https://discourse.slicer.org/u/matt-warkentin)\
**Post date:** [December 8, 2022, 6:07pm UTC](https://discourse.slicer.org/t/chest-imaging-platform-lung-lesion-analyzer-error/19232/10 "2022-12-08T18:07:35Z")

</div>

@rbumm This slide deck walks through its basic functionality: [https://chestimagingplatform.org/files/chestimagingplatform/files/lung\_lesion\_analyzer.pdf](https://chestimagingplatform.org/files/chestimagingplatform/files/lung_lesion_analyzer.pdf)

From the following website: [Documentation | Chest Imaging Platform (CIP)](https://chestimagingplatform.org/documentation)