IMRCLab / IMRCLab/motion_capture_tracking

Negative time point in rclcpp::Time

Open
#23 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
83
Forks
44
PR merge metrics
No merged PRs in 30d

Description

Hey guys, great project thank you very much. I am facing the following issue sometimes where I get negative time and I was hoping you might have an idea why.

Appreciate any help.

After launching with:

ros2 launch mocap_optitrack mocap.launch.py config:=mocap_probe.yaml

I get the following error sporadically (about 6 times in an hour):

[INFO] [launch]: All log files can be found below /home/athena/.ros/log/2024-12-03-18-12-18-412721-Athena-6406
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [launch.user]: Config path: /home/athena/Downloads/mocap_optitrack/install/mocap_optitrack/share/mocap_optitrack/config/mocap_probe.yaml
[INFO] [mocap_node-1]: process started with pid [6407]
[mocap_node-1] [WARN] [1733267538.442367401] [mocap_node]: Could not get server version, using auto
[mocap_node-1] [INFO] [1733267538.443137514] [mocap_node]: Creating socket...
[mocap_node-1] [INFO] [1733267538.443151154] [mocap_node]: Setting socket options...
[mocap_node-1] [INFO] [1733267538.443155504] [mocap_node]: Local address: 0.0.0.0:1511
[mocap_node-1] [INFO] [1733267538.443163621] [mocap_node]: Binding socket to local address...
[mocap_node-1] [INFO] [1733267538.443168193] [mocap_node]: Joining multicast group 239.255.42.99...
[mocap_node-1] [INFO] [1733267538.443177112] [mocap_node]: Enabling non-blocking I/O
[mocap_node-1] [WARN] [1733267539.443798329] [mocap_node]: Client has not received server info request. Parsing data message aborted.
[mocap_node-1] [WARN] [1733267539.444066737] [mocap_node]: Client has not received server info request. Parsing data message aborted.
[mocap_node-1] [WARN] [1733267539.444279789] [mocap_node]: Client has not received server info request. Parsing data message aborted.
[mocap_node-1] [WARN] [1733267539.444460162] [mocap_node]: Client has not received server info request. Parsing data message aborted.
[mocap_node-1] [WARN] [1733267540.445453675] [mocap_node]: Client has not received server info request. Parsing data message aborted.
[mocap_node-1] [INFO] [1733267540.445780131] [mocap_node]: NATNet Version : 4.1.0.0
[mocap_node-1] [INFO] [1733267540.445802976] [mocap_node]: Server Version : 3.1.1.1
[mocap_node-1] [INFO] [1733267540.459861089] [mocap_node]: Initialization complete
[mocap_node-1] terminate called after throwing an instance of 'std::runtime_error'
[mocap_node-1]   what():  cannot store a negative time point in rclcpp::Time

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the reported ros2 launch mocap_optitrack mocap.launch.py config:=mocap_probe.yaml command and reviewing the mocap_probe.yaml configuration. Trace the initialization path around the reported server-version warnings and the rclcpp::Time exception. Done means the intermittent negative-time crash is reproduced and its cause and required fix are documented or resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
robotics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.