# 3D Ultrasound Reconstruction with openIGTL (Verasonics & Polhemus)

**URL:** <https://discourse.slicer.org/t/3d-ultrasound-reconstruction-with-openigtl-verasonics-polhemus/32240>\
**Category:** Support\
**Tags:** ultrasound, volume, visualization, 3d-model, volume-rendering\
**Created:** [October 16, 2023, 7:57am UTC](https://discourse.slicer.org/t/3d-ultrasound-reconstruction-with-openigtl-verasonics-polhemus/32240 "2023-10-16T07:57:17Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [February 20, 2024, 9:06pm UTC](https://discourse.slicer.org/t/3d-ultrasound-reconstruction-with-openigtl-verasonics-polhemus/32240/6 "2024-02-20T21:06:34Z")

</div>

As far as I know, the situation is still the same as described here:

> [@Track images using Polhemus Fastrak electromagnetic tracker](https://discourse.slicer.org/t/track-images-using-polhemus-fastrak-electromagnetic-tracker/7056/6):
>
> I’m not aware of an OpenIGTLink interface for Polhemus. Since cost of development, testing, optimization, maintenance, and support of a new interface would be higher than the cost of an already supported electromagnetic tracker (such as NDI Aurora or Ascension), probably most people end up buying an already supported tracker instead. Surgical navigation users may also end up choosing NDI instead of Polhemus, because NDI appears to be used in many more clinical products. If somebody already has …

---

_[View the full topic](https://discourse.slicer.org/t/3d-ultrasound-reconstruction-with-openigtl-verasonics-polhemus/32240)._