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

cyber vs ros2 #5

Open
daohu527 opened this issue Mar 23, 2022 · 2 comments
Open

cyber vs ros2 #5

daohu527 opened this issue Mar 23, 2022 · 2 comments
Assignees
Labels

Comments

@daohu527
Copy link
Contributor

No description provided.

@daohu527 daohu527 self-assigned this Mar 23, 2022
@daohu527 daohu527 added the core label Mar 23, 2022
@ZhenshengLee
Copy link

ros2 is an eco system consists of client library, tools, drivers and etc. you should compare cyber with rclcpp not ros2.

When using the same backend which is FastDDS, the core difference between cyber and rclcpp is the scheduling.
rclcpp uses waitset-based-executor(single threaded or multithreaded) with the greedy(best effort) scheduling.
cyberrt uses coroutine to schedule the callback task when receiving the msg, which is somehow static scheduling.
the static scheduling is rule based by a schedule config file.

@ZhenshengLee
Copy link

as in ros2 humble, nvidia hardware support was added to rclcpp, the msg transport between hardware engine(cuda, cudla, tensor) get significant improved. This makes rclcpp a prefered platform than cyber. not say there are awesome tools like rviz2, rosbag2, plotjuggler, foxglove to support rclcpp.

the nvidia drive team PPT also point out something.(NOTE: the red words are added by me)

2685142469725961232

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Todo
Development

No branches or pull requests

2 participants