# GeodesicSlicer extension published

**URL:** <https://discourse.slicer.org/t/geodesicslicer-extension-published/10546>\
**Category:** Announcements\
**Created:** [March 4, 2020, 4:57pm UTC](https://discourse.slicer.org/t/geodesicslicer-extension-published/10546 "2020-03-04T16:57:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Frederic](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/frederic/32/4907_2.png) [@Frederic](https://discourse.slicer.org/u/Frederic)\
**Post date:** [March 4, 2020, 4:57pm UTC](https://discourse.slicer.org/t/geodesicslicer-extension-published/10546/1 "2020-03-04T16:57:48Z")

</div>

Dear all,  
We are pleased to inform you that our article about one 3D Slicer extension ([GeodesicSlicer](https://www.slicer.org/wiki/Documentation/4.10/Modules/GeodesicSlicer)) has just been published in NeuroInformatics:

> **[GeodesicSlicer: a Slicer Toolbox for Targeting Brain Stimulation](https://link.springer.com/article/10.1007/s12021-020-09457-9)**
>
> NonInvasive Brain Stimulation (NIBS) is a potential therapeutic tool with growing interest, but neuronavigation-guided software and tools available for the target determination are mostly either expensive or closed proprietary applications. To...

Once again, thanks to @lassoan and @cpinter for their valuable help.

Frederic

---

<div class="post-metadata">

**Author:** ![muntahi398](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muntahi398/32/5302_2.png) [@muntahi398](https://discourse.slicer.org/u/muntahi398)\
**Post date:** [March 10, 2020, 9:38am UTC](https://discourse.slicer.org/t/geodesicslicer-extension-published/10546/2 "2020-03-10T09:38:44Z")

</div>

Hi Frederic,  
thanks for the news, I tried to intall the extension. But in slicer it shows error at starting

```
/NA-MIC/Extensions-28812/GeodesicSlicer/lib/Slicer-4.11/qt-scripted-modules/GeodesicSlicer.py", line 103
ScriptedLoadableModuleWidget.setup(self)
                                       ^

```

TabError: inconsistent use of tabs and spaces in indentation \>

---

<div class="post-metadata">

**Author:** ![Frederic](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/frederic/32/4907_2.png) [@Frederic](https://discourse.slicer.org/u/Frederic)\
**Post date:** [March 10, 2020, 2:11pm UTC](https://discourse.slicer.org/t/geodesicslicer-extension-published/10546/3 "2020-03-10T14:11:02Z")

</div>

Hi @muntahi398,  
I advise you to use the last stable version of 3D Slicer. The software works well on the version 4.10.2.  
After that, I am discovering your bug in the Preview Release. However, this is exactly the same code than the release version. Do you have an idea @jcfr ? Some compilation mistake?  
Thanks.

---

<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:** [March 10, 2020, 3:26pm UTC](https://discourse.slicer.org/t/geodesicslicer-extension-published/10546/4 "2020-03-10T15:26:57Z")

</div>

The error is due to inconsistent use of whitespace: you must either indent only tabs or only spaces, but in the [GeodesicSlicer.py](https://github.com/FredericBr/SlicerGeodesic/edit/master/GeodesicSlicer/GeodesicSlicer.py) you have a random mixture. It should have failed with Slicer-4.10 as well.

I did a quick automatic formatting of the file in Visual Studio Code and submitted a [pull request](https://github.com/FredericBr/SlicerGeodesic/pull/2). I haven’t tested it, so make sure to test the changes yourself.

---

<div class="post-metadata">

**Author:** ![Frederic](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/frederic/32/4907_2.png) [@Frederic](https://discourse.slicer.org/u/Frederic)\
**Post date:** [March 11, 2020, 8:17am UTC](https://discourse.slicer.org/t/geodesicslicer-extension-published/10546/5 "2020-03-11T08:17:40Z")

</div>

Thanks @lassoan.  
Once again, I don’t understand why it’s work on the previous version and not now, but the inconsistent mixture seems to be the way out of the issue.