ntnu-arl / gbplanner_ros

Graph-based Exploration Planner for Subterranean Environments
BSD 3-Clause "New" or "Revised" License
667 stars 152 forks source link

ground robots #34

Open Shai2022 opened 1 year ago

Shai2022 commented 1 year ago

Hello, Does this repository also support ground robot without legs? Thanks

MihirDharmadhikari commented 1 year ago

Hello @Shai2022,

Yes, the planner can be used for other ground robots as well. However, you will need appropriate path follower for your robot.

Best, Mihir

Shai2022 commented 1 year ago

I apologize for the misunderstanding, but could you please provide more details about what i need to implement ?

MihirDharmadhikari commented 1 year ago

Hello,

The output of the planner is a trajectory of the ROS message type MultiDOFJointTrajectory which is published on the topic /<robot_name>/command/trajectory. You will need to implement a controller for your robot that can subscribe to this trajectory and follow it. Let me know if this helps.

Best, Mihir

yydslsj commented 11 months ago

I apologize for the misunderstanding, but could you please provide more details about what i need to implement ? Hello Have you successfully moved to the ground robot? Thanks

DhruvSinghiitmandi commented 8 months ago

Hi @MihirDharmadhikari Could you please tell more on writing the controller that you speak about here? "Hello,

The output of the planner is a trajectory of the ROS message type MultiDOFJointTrajectory which is published on the topic //command/trajectory. You will need to implement a controller for your robot that can subscribe to this trajectory and follow it."

MihirDharmadhikari commented 8 months ago

Hello @DhruvSinghiitmandi ,

The controller depends on your robot. For the differential drive robot that we provide in the demo, we use a simple pure pursuit path tracker. You can find the implementation here: https://github.com/ntnu-arl/smb_simulator/tree/main/smb_path_tracker. Note that this tracker uses a ROS Action interface, but the underlying controller remains the same even if you use kTopic or kAction in the planner, only the interface changes.

I hope this helps.

Best, Mihir