Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 [BUG] - Tick timings do not adhere to the specified tick frequency. #129

Open
Oberacda opened this issue Oct 22, 2024 · 4 comments
Open
Labels
bug Something isn't working

Comments

@Oberacda
Copy link
Contributor

Description

When investigating the tick performance I noticed some issues in the way we calculated the tick time for our debug topics.
In addition I noticed that we actually tick the tree at a frequency of 500 Hz when only specifying 10 Hz.

Reproduction URL

https://github.com/fzi-forschungszentrum-informatik/ros2_ros_bt_py

Reproduction steps

1. Load any BT.
2. Record a rosbag with all topics.
3. Run the tree.
4. Visualize 1 / `/BehaviorTreeNode/debug/tick_frequency/data` topic in PlotJuggler

Screenshots

No response

Logs

No response

ROS 2 Version

Jazzy

OS

Ubuntu 24.04

@Oberacda Oberacda added the bug Something isn't working label Oct 22, 2024
@Oberacda
Copy link
Contributor Author

measured_tick_freq_hz

@Oberacda
Copy link
Contributor Author

These are the measurements for running the Problem 1 solution in the roscon24-deliberation-workshop repo two time.

@Oberacda Oberacda changed the title 🐛 [BUG] - 🐛 [BUG] - Tick timings do not adhere to the specified tick frequency. Oct 22, 2024
@Oberacda
Copy link
Contributor Author

The time tracking bug is fixed in #130 but the issues with the invalid tick frequency is still open

@Oberacda
Copy link
Contributor Author

ros_bt_py_tick_frequency_deviation
Ok after fixing another bug in the tick frequency calculation the deviation does not seem too significant.
Nonetheless we might want to investigate where these are coming from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant