# About the SlicerAutoscoperM category

**URL:** <https://discourse.slicer.org/t/about-the-slicerautoscoperm-category/23599>\
**Category:** SlicerAutoscoperM\
**Created:** [May 26, 2022, 6:39pm UTC](https://discourse.slicer.org/t/about-the-slicerautoscoperm-category/23599 "2022-05-26T18:39:01Z")\
**Posts on this page:** 1\
**Page:** 1

<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:** [May 26, 2022, 6:39pm UTC](https://discourse.slicer.org/t/about-the-slicerautoscoperm-category/23599/1 "2022-05-26T18:39:01Z")

</div>

SlicerAutoscoperM is a Slicer extension currently under development, dedicated to image-based 3D motion tracking of skeletal structures.

Our goal is to provide researchers and developers with a powerful tool for precise and accessible motion analysis.

Visit the [SlicerAutoscoperM website](https://autoscoperm.slicer.org/) to learn more about this project.

This category serves as a discussion and support platform for all things related to SlicerAutoscoperM. Whether you have questions, need assistance, or want to report bugs and suggest new features, we welcome your active participation!

✨ Join the conversation and be a part of the community driving motion analysis with SlicerAutoscoperM!
