motion_capture_tracking repository

Repository Summary

Checkout URI https://github.com/IMRCLab/motion_capture_tracking.git
VCS Type git
VCS Version ros2
Last Updated 2024-03-12
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

README

ROS2

motion_capture_tracking

This repository is a ROS 2 package that can receive data from various motion capture systems:

  • VICON
  • Qualisys
  • OptiTrack
  • VRPN
  • NOKOV
  • FZMotion
  • Motion Analysis

For most systems, three different tracking modes are available:

  1. Tracking of rigid body poses via the official software (e.g., Vicon Tracker) using unique marker arrangements.
  2. Tracking of rigid body poses with custom frame-to-frame tracking with identical marker arrangements.
  3. Tracking of unlabeled marker positions using custom frame-to-frame tracking.

The data is directly published via tf2 and a /poses topic that supports different QoS settings.

This package was originally developed for Crazyswarm to track up to 50 flying robots.

Building

To build from source, clone the latest version from this repository into your ROS 2 workspace and compile the package using

cd ros_ws/src
git clone --recurse-submodules https://github.com/IMRCLab/motion_capture_tracking
cd ../
colcon build

Usage

ros2 launch motion_capture_tracking launch.py

The various options can be configured in config/cfg.yaml.

Optitrack: Vendor-specific Instructions

There are two possible backends.

  • "optitrack" uses the Direct Depacketizers option. This works on all platforms, but often has compatibility issues with untested Motive versions and doesn't support all features.
  • "optitrack_closed_source" uses the official SDK (version 4.1.0) (only available on x64 Linux; distributed as a binary library)

Make sure that you have the following settings in Motive:

menu Edit/Settings/Streaming: * Enable NatNet * Use "Transmission Type" Multicast * Enable Unlabeled Markers and Rigid Bodies * Use "Up Axis": Z-Axis * Use the default ports (1510 command, 1511 data)

We recommend that you first try "optitrack" and switch to "optitrack_closed_source" if you encounter any issues.

NOKOV: Vendor-specific Instructions

Since the SDK is not publically available, adding the SDK and building from source is required.

  1. Place the SDK in motion_capture_tracking/deps/libmotioncapture/deps/nokov_sdk (such that there is for example the file motion_capture_tracking/deps/libmotioncapture/deps/nokov_sdk/lib/libSeekerSDKClient.so)
  2. In motion_capture_tracking/CMakeLists.txt change set(LIBMOTIONCAPTURE_ENABLE_NOKOV OFF) to set(LIBMOTIONCAPTURE_ENABLE_NOKOV ON)
  3. Rebuild using colcon build

Technical Background

The ROS package is a wrapper around libmotioncapture and librigidbodytracker. The former is a C++ library that provides a unified interface over different motion capture SDKs to gather pose informations of rigid bodies and/or pointclouds of unlabeled markers. The latter is a C++ library that takes the following inputs: i) a first-order dynamics model, ii) initial poses of rigid bodies, and iii) at every frame a point cloud. It outputs for every frame the best estimate of the robots' poses.

Some more information on the rigid body pose tracking is available in

@inproceedings{crazyswarm,
  author    = {James A. Preiss* and
               Wolfgang  H\"onig* and
               Gaurav S. Sukhatme and
               Nora Ayanian},
  title     = {Crazyswarm: {A} large nano-quadcopter swarm},
  booktitle = {{IEEE} International Conference on Robotics and Automation ({ICRA})},
  pages     = {3299--3304},
  publisher = {{IEEE}},
  year      = {2017},
  url       = {https://doi.org/10.1109/ICRA.2017.7989376},
  doi       = {10.1109/ICRA.2017.7989376},
  note      = {Software available at \url{https://github.com/USC-ACTLab/crazyswarm}},
}

The unlabeled marker tracking is using an optimal assignment with a min-cost max-flow formulation for each frame.

These are current alternatives if no custom tracking is needed:

CONTRIBUTING

No CONTRIBUTING.md found.

Repository Summary

Checkout URI https://github.com/IMRCLab/motion_capture_tracking.git
VCS Type git
VCS Version ros2
Last Updated 2024-03-12
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

README

ROS2

motion_capture_tracking

This repository is a ROS 2 package that can receive data from various motion capture systems:

  • VICON
  • Qualisys
  • OptiTrack
  • VRPN
  • NOKOV
  • FZMotion
  • Motion Analysis

For most systems, three different tracking modes are available:

  1. Tracking of rigid body poses via the official software (e.g., Vicon Tracker) using unique marker arrangements.
  2. Tracking of rigid body poses with custom frame-to-frame tracking with identical marker arrangements.
  3. Tracking of unlabeled marker positions using custom frame-to-frame tracking.

The data is directly published via tf2 and a /poses topic that supports different QoS settings.

This package was originally developed for Crazyswarm to track up to 50 flying robots.

Building

To build from source, clone the latest version from this repository into your ROS 2 workspace and compile the package using

cd ros_ws/src
git clone --recurse-submodules https://github.com/IMRCLab/motion_capture_tracking
cd ../
colcon build

Usage

ros2 launch motion_capture_tracking launch.py

The various options can be configured in config/cfg.yaml.

Optitrack: Vendor-specific Instructions

There are two possible backends.

  • "optitrack" uses the Direct Depacketizers option. This works on all platforms, but often has compatibility issues with untested Motive versions and doesn't support all features.
  • "optitrack_closed_source" uses the official SDK (version 4.1.0) (only available on x64 Linux; distributed as a binary library)

Make sure that you have the following settings in Motive:

menu Edit/Settings/Streaming: * Enable NatNet * Use "Transmission Type" Multicast * Enable Unlabeled Markers and Rigid Bodies * Use "Up Axis": Z-Axis * Use the default ports (1510 command, 1511 data)

We recommend that you first try "optitrack" and switch to "optitrack_closed_source" if you encounter any issues.

NOKOV: Vendor-specific Instructions

Since the SDK is not publically available, adding the SDK and building from source is required.

  1. Place the SDK in motion_capture_tracking/deps/libmotioncapture/deps/nokov_sdk (such that there is for example the file motion_capture_tracking/deps/libmotioncapture/deps/nokov_sdk/lib/libSeekerSDKClient.so)
  2. In motion_capture_tracking/CMakeLists.txt change set(LIBMOTIONCAPTURE_ENABLE_NOKOV OFF) to set(LIBMOTIONCAPTURE_ENABLE_NOKOV ON)
  3. Rebuild using colcon build

Technical Background

The ROS package is a wrapper around libmotioncapture and librigidbodytracker. The former is a C++ library that provides a unified interface over different motion capture SDKs to gather pose informations of rigid bodies and/or pointclouds of unlabeled markers. The latter is a C++ library that takes the following inputs: i) a first-order dynamics model, ii) initial poses of rigid bodies, and iii) at every frame a point cloud. It outputs for every frame the best estimate of the robots' poses.

Some more information on the rigid body pose tracking is available in

@inproceedings{crazyswarm,
  author    = {James A. Preiss* and
               Wolfgang  H\"onig* and
               Gaurav S. Sukhatme and
               Nora Ayanian},
  title     = {Crazyswarm: {A} large nano-quadcopter swarm},
  booktitle = {{IEEE} International Conference on Robotics and Automation ({ICRA})},
  pages     = {3299--3304},
  publisher = {{IEEE}},
  year      = {2017},
  url       = {https://doi.org/10.1109/ICRA.2017.7989376},
  doi       = {10.1109/ICRA.2017.7989376},
  note      = {Software available at \url{https://github.com/USC-ACTLab/crazyswarm}},
}

The unlabeled marker tracking is using an optimal assignment with a min-cost max-flow formulation for each frame.

These are current alternatives if no custom tracking is needed:

CONTRIBUTING

No CONTRIBUTING.md found.

Repository Summary

Checkout URI https://github.com/IMRCLab/motion_capture_tracking.git
VCS Type git
VCS Version ros2
Last Updated 2024-03-12
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

README

ROS2

motion_capture_tracking

This repository is a ROS 2 package that can receive data from various motion capture systems:

  • VICON
  • Qualisys
  • OptiTrack
  • VRPN
  • NOKOV
  • FZMotion
  • Motion Analysis

For most systems, three different tracking modes are available:

  1. Tracking of rigid body poses via the official software (e.g., Vicon Tracker) using unique marker arrangements.
  2. Tracking of rigid body poses with custom frame-to-frame tracking with identical marker arrangements.
  3. Tracking of unlabeled marker positions using custom frame-to-frame tracking.

The data is directly published via tf2 and a /poses topic that supports different QoS settings.

This package was originally developed for Crazyswarm to track up to 50 flying robots.

Building

To build from source, clone the latest version from this repository into your ROS 2 workspace and compile the package using

cd ros_ws/src
git clone --recurse-submodules https://github.com/IMRCLab/motion_capture_tracking
cd ../
colcon build

Usage

ros2 launch motion_capture_tracking launch.py

The various options can be configured in config/cfg.yaml.

Optitrack: Vendor-specific Instructions

There are two possible backends.

  • "optitrack" uses the Direct Depacketizers option. This works on all platforms, but often has compatibility issues with untested Motive versions and doesn't support all features.
  • "optitrack_closed_source" uses the official SDK (version 4.1.0) (only available on x64 Linux; distributed as a binary library)

Make sure that you have the following settings in Motive:

menu Edit/Settings/Streaming: * Enable NatNet * Use "Transmission Type" Multicast * Enable Unlabeled Markers and Rigid Bodies * Use "Up Axis": Z-Axis * Use the default ports (1510 command, 1511 data)

We recommend that you first try "optitrack" and switch to "optitrack_closed_source" if you encounter any issues.

NOKOV: Vendor-specific Instructions

Since the SDK is not publically available, adding the SDK and building from source is required.

  1. Place the SDK in motion_capture_tracking/deps/libmotioncapture/deps/nokov_sdk (such that there is for example the file motion_capture_tracking/deps/libmotioncapture/deps/nokov_sdk/lib/libSeekerSDKClient.so)
  2. In motion_capture_tracking/CMakeLists.txt change set(LIBMOTIONCAPTURE_ENABLE_NOKOV OFF) to set(LIBMOTIONCAPTURE_ENABLE_NOKOV ON)
  3. Rebuild using colcon build

Technical Background

The ROS package is a wrapper around libmotioncapture and librigidbodytracker. The former is a C++ library that provides a unified interface over different motion capture SDKs to gather pose informations of rigid bodies and/or pointclouds of unlabeled markers. The latter is a C++ library that takes the following inputs: i) a first-order dynamics model, ii) initial poses of rigid bodies, and iii) at every frame a point cloud. It outputs for every frame the best estimate of the robots' poses.

Some more information on the rigid body pose tracking is available in

@inproceedings{crazyswarm,
  author    = {James A. Preiss* and
               Wolfgang  H\"onig* and
               Gaurav S. Sukhatme and
               Nora Ayanian},
  title     = {Crazyswarm: {A} large nano-quadcopter swarm},
  booktitle = {{IEEE} International Conference on Robotics and Automation ({ICRA})},
  pages     = {3299--3304},
  publisher = {{IEEE}},
  year      = {2017},
  url       = {https://doi.org/10.1109/ICRA.2017.7989376},
  doi       = {10.1109/ICRA.2017.7989376},
  note      = {Software available at \url{https://github.com/USC-ACTLab/crazyswarm}},
}

The unlabeled marker tracking is using an optimal assignment with a min-cost max-flow formulation for each frame.

These are current alternatives if no custom tracking is needed:

CONTRIBUTING

No CONTRIBUTING.md found.

Repository Summary

Checkout URI https://github.com/IMRCLab/motion_capture_tracking.git
VCS Type git
VCS Version ros2
Last Updated 2024-03-12
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

README

ROS2

motion_capture_tracking

This repository is a ROS 2 package that can receive data from various motion capture systems:

  • VICON
  • Qualisys
  • OptiTrack
  • VRPN
  • NOKOV
  • FZMotion
  • Motion Analysis

For most systems, three different tracking modes are available:

  1. Tracking of rigid body poses via the official software (e.g., Vicon Tracker) using unique marker arrangements.
  2. Tracking of rigid body poses with custom frame-to-frame tracking with identical marker arrangements.
  3. Tracking of unlabeled marker positions using custom frame-to-frame tracking.

The data is directly published via tf2 and a /poses topic that supports different QoS settings.

This package was originally developed for Crazyswarm to track up to 50 flying robots.

Building

To build from source, clone the latest version from this repository into your ROS 2 workspace and compile the package using

cd ros_ws/src
git clone --recurse-submodules https://github.com/IMRCLab/motion_capture_tracking
cd ../
colcon build

Usage

ros2 launch motion_capture_tracking launch.py

The various options can be configured in config/cfg.yaml.

Optitrack: Vendor-specific Instructions

There are two possible backends.

  • "optitrack" uses the Direct Depacketizers option. This works on all platforms, but often has compatibility issues with untested Motive versions and doesn't support all features.
  • "optitrack_closed_source" uses the official SDK (version 4.1.0) (only available on x64 Linux; distributed as a binary library)

Make sure that you have the following settings in Motive:

menu Edit/Settings/Streaming: * Enable NatNet * Use "Transmission Type" Multicast * Enable Unlabeled Markers and Rigid Bodies * Use "Up Axis": Z-Axis * Use the default ports (1510 command, 1511 data)

We recommend that you first try "optitrack" and switch to "optitrack_closed_source" if you encounter any issues.

NOKOV: Vendor-specific Instructions

Since the SDK is not publically available, adding the SDK and building from source is required.

  1. Place the SDK in motion_capture_tracking/deps/libmotioncapture/deps/nokov_sdk (such that there is for example the file motion_capture_tracking/deps/libmotioncapture/deps/nokov_sdk/lib/libSeekerSDKClient.so)
  2. In motion_capture_tracking/CMakeLists.txt change set(LIBMOTIONCAPTURE_ENABLE_NOKOV OFF) to set(LIBMOTIONCAPTURE_ENABLE_NOKOV ON)
  3. Rebuild using colcon build

Technical Background

The ROS package is a wrapper around libmotioncapture and librigidbodytracker. The former is a C++ library that provides a unified interface over different motion capture SDKs to gather pose informations of rigid bodies and/or pointclouds of unlabeled markers. The latter is a C++ library that takes the following inputs: i) a first-order dynamics model, ii) initial poses of rigid bodies, and iii) at every frame a point cloud. It outputs for every frame the best estimate of the robots' poses.

Some more information on the rigid body pose tracking is available in

@inproceedings{crazyswarm,
  author    = {James A. Preiss* and
               Wolfgang  H\"onig* and
               Gaurav S. Sukhatme and
               Nora Ayanian},
  title     = {Crazyswarm: {A} large nano-quadcopter swarm},
  booktitle = {{IEEE} International Conference on Robotics and Automation ({ICRA})},
  pages     = {3299--3304},
  publisher = {{IEEE}},
  year      = {2017},
  url       = {https://doi.org/10.1109/ICRA.2017.7989376},
  doi       = {10.1109/ICRA.2017.7989376},
  note      = {Software available at \url{https://github.com/USC-ACTLab/crazyswarm}},
}

The unlabeled marker tracking is using an optimal assignment with a min-cost max-flow formulation for each frame.

These are current alternatives if no custom tracking is needed:

CONTRIBUTING

No CONTRIBUTING.md found.