-
Notifications
You must be signed in to change notification settings - Fork 321
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add support for multi-sensor scenarios (#232)
* Fix TF tree usage in ROS 2 wrapper Signed-off-by: Ignacio Vizzo <[email protected]> * Transform the pose instead of the pointcloud * remove include * Remove default base_frame parameter value This will make KISS-ICP work ego-centric as default * Remove unused variable * Do not reuse pose_msg.pose * I'm not ever sure why we did that in first instance * Be more explicit about the stamps and frame_id of the headers * Extract publishing mechanism to a new function (#246) * Convert class member function to more useful utility And fix a small bug, the order was of the transformation before was the opposite, and therefore we were obtaining base2cloud. Since we multiply by both sides we can't really see the difference, but it was conceptually wrong. * Bring back debugging clouds to ros driver * re-arange logic on when and when not to publish clouds * fix lofic * Update rviz2 * Loosing my mind already with this debugging info * Backport tf multisensor fix (#245) * Build system changes for tf fix * Modify params for tf fix * Add ROS 1 tf fixes similar to ROS 2 * Update rviz config * Remove unused debug publishers * Remove unnecessary smart pointers * Update ROS 1 to match ROS 2 changes * Fix style * Remove sophus from build system Fixing now the CI is a big pain * Remove unnecessary alias --------- Signed-off-by: Ignacio Vizzo <[email protected]> Co-authored-by: Tim Player <[email protected]> Co-authored-by: raw_t <[email protected]> Co-authored-by: tizianoGuadagnino <[email protected]>
- Loading branch information
1 parent
da1bff1
commit 062cc44
Showing
11 changed files
with
546 additions
and
265 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.