Skip to content

Question regarding OptiTrack integration and transform processing in Plus Toolkit #1272

Open

Description

@AurelieSar

Dear Plus Toolkit team,

We are currently working on real-time 3D ultrasound reconstruction using motion capture data streamed to PlusServer and 3D Slicer.

For Vicon and QTM systems, we currently use a custom Python bridge:

Mocap SDK → OpenIGTLink server (pyigtl) → Plus OpenIGTLinkTracker device

In this configuration, we observe slight rigid body jitter (especially rotational jitter with Vicon/Nexus Kinematic Fit), which produces visible waviness artifacts in our reconstructed 3D ultrasound volumes.

Interestingly, similar experiments performed with OptiTrack appear significantly more stable.

We were therefore wondering whether the OptiTrack integration in Plus Toolkit performs any additional processing internally, such as:

  • temporal smoothing
  • interpolation
  • buffering
  • transform filtering
  • timestamp correction
  • or any other stabilization step

compared to a generic OpenIGTLinkTracker input such as the one we currently use.

In other words:

  • does the OptiTrack integration in Plus simply forward rigid body transforms,
  • or is there additional processing involved that could explain improved stability?

We are trying to determine whether the observed differences come purely from the mocap systems themselves, or whether part of the stability may also originate from the Plus integration pipeline.

Thank you very much for your help and clarification.

Best regards,

Aurélie Sarcher & Fabien Leboeuf

Activity

  1. adamrankin commented on Apr 29, 2026

    @adamrankin
    Member

    It would appear that Plus does simple retrieval of the transform from the OptiTrack. There is an option for a Motive configuration file, so perhaps that might tell the OptiTrack to perform smoothing.

    There are a number of other tracking devices that perform on-board data processing, but for the most part, Plus simply retrieves the transforms that the trackers send out.

    Plus does do temporal interpolation to synchronize a video frame with an interpolated tracking frame.

    Were you using the OptiTrack with Plus?

  2. AurelieSar commented on Apr 30, 2026

    @AurelieSar
    Author

    Yes, we were using OptiTrack directly through the native Plus integration.

    Thank you very much for the clarification — this is what we suspected, but we wanted to make sure there was no additional hidden processing on the Plus side.

    We are aware of the temporal calibration/interpolation performed in Plus, and we are also able to achieve similar temporal calibration values with Nexus (around 150 ms offset).

    We also checked the MotiveProfileFile configuration and could not find any smoothing-related parameters there; it seems to mainly contain camera and rigid body configuration information.

    What is puzzling for us is that I have tested several other tracking systems in very similar 3D ultrasound reconstruction workflows (OptiTrack Flex13, OptiTrack Duo, NDI Aurora bars, etc.) and I never observed the same fluidity/reconstruction artifacts that we currently see with Nexus.

    So at this stage we believe the issue is probably related either to the Vicon tracking/reconstruction itself or to how the transforms are produced upstream, and we are continuing to investigate the origin of the problem.

    Thank you for your quick answer,
    Best
    Aurélie

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions