-
Notifications
You must be signed in to change notification settings - Fork 108
Quick Start Example
lthursdayl edited this page Oct 9, 2015
·
22 revisions
We have found it very helpful to keep a document on one of the tracking OpenPTrack computers that has a list, in the appropriate order, of all the commands needed to calibrate and run tracking for a specific OpenPTrack system.
Below is an example of one of our quick start guides, which has (3) Kinect v2 which are named in the network_camera.yaml kinectv2_left, kinectv2_right, and kinectv2_center on three computers with IP addresses of 192.168.100.101, 192.168.100.102, and 192.168.100.103:
On Master (192.168.100.101):
roscore
roslaunch opt_calibration calibration_initializer.launch
Now all all computers in OpenPTrack system including .101:
roslaunch opt_calibration calibration_initializer.launch
On 192.168.100.101:
roslaunch opt_calibration opt_calibration_master.launch
roslaunch opt_calibration sensor_kinectv2_left.launch
On 192.168.100.102:
roslaunch opt_calibration sensor_kinectv2_right.launch
On 192.168.100.103
roslaunch opt_calibration sensor_kinectv2_center.launch
Calibrate per normal procedure
If you are working with OpenPTrack v2, use this wiki instead.
- Time Synchronization
- Pre-Calibration Configuration
- Intrinsic Calibration
- Camera Network Calibration
- Person Tracking
- Object Tracking
- World Coordinate Settings
- Tips and Tricks
- Tested Hardware
- Network Configuration
- Imager Mounting and Placement
- Calibration in Practice
- Quick Start Example
- Imager Settings
- Manual Ground Plane
- Calibration Refinement
How to receive tracking data in:
Notes on contributing to OPT.