# Citing Slicer modules/extensions

**URL:** <https://discourse.slicer.org/t/citing-slicer-modules-extensions/3217>\
**Category:** Feature requests\
**Created:** [June 18, 2018, 5:14pm UTC](https://discourse.slicer.org/t/citing-slicer-modules-extensions/3217 "2018-06-18T17:14:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [June 18, 2018, 5:14pm UTC](https://discourse.slicer.org/t/citing-slicer-modules-extensions/3217/1 "2018-06-18T17:14:32Z")

</div>

When I use Slicer in a publication, I have been citing this paper.

Kikinis R, Pieper SD, Vosburgh KG. 2014. 3D Slicer: A Platform for Subject-Specific Image Analysis, Visualization, and Clinical Support. In: Intraoperative Imaging and Image-Guided Therapy. Springer, New York, NY. p 277–289. Available from: [3D Slicer: A Platform for Subject-Specific Image Analysis, Visualization, and Clinical Support | SpringerLink](https://link.springer.com/chapter/10.1007/978-1-4614-7657-3_19)

However, there are many extensions and other functionalities that are not part of the core, where citing only this paper is not appropriate to acknowledge their contributions. I also noticed that acknowledgement sections of modules usually does not necessarily provide a citation, beyond a URL to documentation, which is under help.

What I had in mind is something similar to R citation function. e.g. for a non-peer reviewed contribution:

> citation(‘Hotelling’)

To cite package ‘Hotelling’ in publications use:

James M. Curran (2013). Hotelling: Hotelling’s T-squared test and variants. R package version  
1.0-2. [CRAN - Package Hotelling](https://CRAN.R-project.org/package=Hotelling)

A BibTeX entry for LaTeX users is

@Manual{,  
title = {Hotelling: Hotelling’s T-squared test and variants},  
author = {James M. Curran},  
year = {2013},  
note = {R package version 1.0-2},  
url = {[CRAN - Package Hotelling](https://CRAN.R-project.org/package=Hotelling)},  
}

or a peer-reviewed paper example

> citation(‘geomorph’)

To cite package ‘geomorph’ in a publication use:

Adams, D.C., and E. Otarola-Castillo. 2013. geomorph: an R package for the collection and analysis  
of geometric morphometric shape data. Methods in Ecology and Evolution. 4:393-399.

A BibTeX entry for LaTeX users is

@Article{,  
title = {geomorph: an R package for the collection and analysis of geometric morphometric shape data},  
author = {D.C. Adams and E. Otarola-Castillo},  
journal = {Methods in Ecology and Evolution},  
year = {2013},  
volume = {4},  
pages = {393-399},  
}

As geomorph is evolving quickly, you may want to cite also its version number (found with  
‘library(help = geomorph)’).

---

<div class="post-metadata">

**Author:** ![dokay1](https://avatars.discourse-cdn.com/v4/letter/d/b4bc9f/32.png) [@dokay1](https://discourse.slicer.org/u/dokay1)\
**Post date:** [July 28, 2022, 6:36pm UTC](https://discourse.slicer.org/t/citing-slicer-modules-extensions/3217/2 "2022-07-28T18:36:33Z")

</div>

Is there a citation I could use for the level tracing tool in 3D Slicer?

---

<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:** [July 28, 2022, 6:45pm UTC](https://discourse.slicer.org/t/citing-slicer-modules-extensions/3217/3 "2022-07-28T18:45:24Z")

</div>

I don’t believe there was ever a publication about that tool. Citing the Slicer reference and pointing to the files in the repo would probably be good practice if you are going for reproducibility (also note the version of Slicer).

Here’s one of the files that describes the implementation: [Slicer/itkLevelTracingImageFilter.h at main · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/blob/main/Libs/vtkITK/itkLevelTracingImageFilter.h)