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

Fixing ROS launch system #8

Merged
merged 4 commits into from
Oct 16, 2024
Merged

Conversation

tizianoGuadagnino
Copy link
Collaborator

There were some last-minute changes in the launch system used in the project before the open-source release. In the process the rviz node got removed from the online_node launch, and we didn't realize it because we assumed the default value of the visualize flag was set to false, while it was true. This PR fixes both issues:

  1. Re-introduce the Rviz node into the online_node launch.
  2. Set the visualize flag to false by default
  3. Remove legacy (project is open-source from 5 minutes but ok) parameter bag_filenames

@tizianoGuadagnino tizianoGuadagnino merged commit d898b7c into main Oct 16, 2024
11 checks passed
@tizianoGuadagnino tizianoGuadagnino deleted the online_node_consistency branch October 16, 2024 13:43
tizianoGuadagnino added a commit that referenced this pull request Oct 16, 2024
* We didnt have proper flagging in the online node

* Clean launch common args

* Fix formatting python
benemer added a commit that referenced this pull request Nov 19, 2024
* We didnt have proper flagging in the online node

* Clean launch common args

* Add new threshold

* Update CMakeLists.txt (#7)

Make *USE_SYSTEM_SOPHUS* consistent with the rest of the options.

* Update README.md (#6)

More accurate statement in the readme, the system does not need to follow a unicycle motion model, just the pose correction needs to do that, which applies to much more robotics platforms.

* Add python checks to pre-commit (#9)

* Add black and isort

* Format

* use black for isort

* Fixing ROS launch system (#8)

* We didnt have proper flagging in the online node

* Clean launch common args

* Fix formatting python

* Tiny modification, but makes sense

* Renaming and add configuration for the correspondence threshold

* Fix pipeline

* Consistency in the CMakeLists

* Remove ternary operator and make the two functions consistent

* Update cpp/kinematic_icp/correspondence_threshold/CorrespondenceThreshold.hpp

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>

* Renaming according to Ben's review

* Why a ref

* Odometry Regularization (#19)

* Natural extension to make also the odometry regularization optional

* Consistency in the CMakeLists

* Remove ternary operator and make the two functions consistent

* Update cpp/kinematic_icp/correspondence_threshold/CorrespondenceThreshold.hpp

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>

* Renaming according to Ben's review

* Why a ref

* Use the same default

---------

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>
Co-authored-by: Benedikt Mersch <benedikt.mersch@gmail.com>

---------

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>
Co-authored-by: Benedikt Mersch <benedikt.mersch@gmail.com>
tizianoGuadagnino added a commit that referenced this pull request Nov 19, 2024
* We didnt have proper flagging in the online node

* Clean launch common args

* Add new threshold

* Update CMakeLists.txt (#7)

Make *USE_SYSTEM_SOPHUS* consistent with the rest of the options.

* Update README.md (#6)

More accurate statement in the readme, the system does not need to follow a unicycle motion model, just the pose correction needs to do that, which applies to much more robotics platforms.

* Add python checks to pre-commit (#9)

* Add black and isort

* Format

* use black for isort

* Fixing ROS launch system (#8)

* We didnt have proper flagging in the online node

* Clean launch common args

* Fix formatting python

* Tiny modification, but makes sense

* Renaming and add configuration for the correspondence threshold

* Fix pipeline

* Consistency in the CMakeLists

* Remove ternary operator and make the two functions consistent

* Update cpp/kinematic_icp/correspondence_threshold/CorrespondenceThreshold.hpp

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>

* Renaming according to Ben's review

* Why a ref

* Odometry Regularization (#19)

* Natural extension to make also the odometry regularization optional

* Consistency in the CMakeLists

* Remove ternary operator and make the two functions consistent

* Update cpp/kinematic_icp/correspondence_threshold/CorrespondenceThreshold.hpp

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>

* Renaming according to Ben's review

* Why a ref

* Use the same default

---------

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>
Co-authored-by: Benedikt Mersch <benedikt.mersch@gmail.com>

---------

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>
Co-authored-by: Benedikt Mersch <benedikt.mersch@gmail.com>
tizianoGuadagnino added a commit that referenced this pull request Nov 21, 2024
* We didnt have proper flagging in the online node

* Clean launch common args

* Add new threshold

* Update CMakeLists.txt (#7)

Make *USE_SYSTEM_SOPHUS* consistent with the rest of the options.

* Update README.md (#6)

More accurate statement in the readme, the system does not need to follow a unicycle motion model, just the pose correction needs to do that, which applies to much more robotics platforms.

* Add python checks to pre-commit (#9)

* Add black and isort

* Format

* use black for isort

* Fixing ROS launch system (#8)

* We didnt have proper flagging in the online node

* Clean launch common args

* Fix formatting python

* Tiny modification, but makes sense

* Renaming and add configuration for the correspondence threshold

* Fix pipeline

* Consistency in the CMakeLists

* Remove ternary operator and make the two functions consistent

* Update cpp/kinematic_icp/correspondence_threshold/CorrespondenceThreshold.hpp

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>

* Renaming according to Ben's review

* Why a ref

* Odometry Regularization (#19)

* Natural extension to make also the odometry regularization optional

* Consistency in the CMakeLists

* Remove ternary operator and make the two functions consistent

* Update cpp/kinematic_icp/correspondence_threshold/CorrespondenceThreshold.hpp

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>

* Renaming according to Ben's review

* Why a ref

* Use the same default

---------

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>
Co-authored-by: Benedikt Mersch <benedikt.mersch@gmail.com>

---------

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>
Co-authored-by: Benedikt Mersch <benedikt.mersch@gmail.com>
tizianoGuadagnino added a commit that referenced this pull request Nov 22, 2024
* We didnt have proper flagging in the online node

* Clean launch common args

* Add new threshold

* Update CMakeLists.txt (#7)

Make *USE_SYSTEM_SOPHUS* consistent with the rest of the options.

* Update README.md (#6)

More accurate statement in the readme, the system does not need to follow a unicycle motion model, just the pose correction needs to do that, which applies to much more robotics platforms.

* Add python checks to pre-commit (#9)

* Add black and isort

* Format

* use black for isort

* Fixing ROS launch system (#8)

* We didnt have proper flagging in the online node

* Clean launch common args

* Fix formatting python

* Tiny modification, but makes sense

* Renaming and add configuration for the correspondence threshold

* Fix pipeline

* Consistency in the CMakeLists

* Remove ternary operator and make the two functions consistent

* Add 2d lidar support, need testing

* Restore ros utils to master

* Revise timestamping (#18)

* Query from last stamp in case of frame drops

* Rename

* WIP

* Fix conversions

* Fix build

* Make CI happy

* Add TimeStampHandler module to handle this madness

* Minor renaming

* Try to take care of absolute timestamping of points + scan stamped at
the end

* Comments

* Should fix all cases that came to my mind at this time

* Some comments to make stuff more clear

* Remove useless case, we need to fix deskewing

* Fix condition for clarity

---------

Co-authored-by: tizianoGuadagnino <frevo93@gmail.com>

* Kinematic ICP Threshold (#15)

* We didnt have proper flagging in the online node

* Clean launch common args

* Add new threshold

* Update CMakeLists.txt (#7)

Make *USE_SYSTEM_SOPHUS* consistent with the rest of the options.

* Update README.md (#6)

More accurate statement in the readme, the system does not need to follow a unicycle motion model, just the pose correction needs to do that, which applies to much more robotics platforms.

* Add python checks to pre-commit (#9)

* Add black and isort

* Format

* use black for isort

* Fixing ROS launch system (#8)

* We didnt have proper flagging in the online node

* Clean launch common args

* Fix formatting python

* Tiny modification, but makes sense

* Renaming and add configuration for the correspondence threshold

* Fix pipeline

* Consistency in the CMakeLists

* Remove ternary operator and make the two functions consistent

* Update cpp/kinematic_icp/correspondence_threshold/CorrespondenceThreshold.hpp

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>

* Renaming according to Ben's review

* Why a ref

* Odometry Regularization (#19)

* Natural extension to make also the odometry regularization optional

* Consistency in the CMakeLists

* Remove ternary operator and make the two functions consistent

* Update cpp/kinematic_icp/correspondence_threshold/CorrespondenceThreshold.hpp

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>

* Renaming according to Ben's review

* Why a ref

* Use the same default

---------

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>
Co-authored-by: Benedikt Mersch <benedikt.mersch@gmail.com>

---------

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>
Co-authored-by: Benedikt Mersch <benedikt.mersch@gmail.com>

* We didnt have proper flagging in the online node

* Add new threshold

* Renaming and add configuration for the correspondence threshold

* Fix pipeline

* fixx

* Include timestamps from the projected laser

---------

Co-authored-by: Benedikt Mersch <mersch@igg.uni-bonn.de>
Co-authored-by: Benedikt Mersch <benedikt.mersch@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants