Open
Conversation
MatteoTschesche
requested changes
Dec 9, 2025
MatteoTschesche
left a comment
There was a problem hiding this comment.
Thanks for the work. Here is some feedback. Still need to read everything fully.
debug_laser_mapper.rviz
Outdated
| Value: true | ||
| map: | ||
| Value: true | ||
| robotinobase4/base_link: |
debug_laser_mapper.rviz
Outdated
| {} | ||
| WAIT4: | ||
| {} | ||
| robotinobase4/odom: |
| declare_integratedtopic_argument = DeclareLaunchArgument( | ||
| "integratedTopic", | ||
| default_value="/robotinobase1/scan", | ||
| default_value="/robotinobase2/scan", |
There was a problem hiding this comment.
same here, this needs to be done via workspaces i guess
| ) | ||
| declare_integratedframe_argument = DeclareLaunchArgument( | ||
| "integratedFrameId", default_value="robotinobase1/laser_link", description="Integrated Frame ID" | ||
| "integratedFrameId", default_value="robotinobase2/laser_link", description="Integrated Frame ID" |
| declare_position_tolerance_argument = DeclareLaunchArgument( | ||
| "position_tolerance", | ||
| default_value="0.3", | ||
| default_value="1", |
There was a problem hiding this comment.
is this between robot and scanned line or between scanned line and map position?
There was a problem hiding this comment.
make this clear in the description please
| *line_cluster_index = *tmp_index; | ||
| RCLCPP_INFO(this->get_logger(), | ||
| "tmp_index (Anzahl: %zu):", tmp_index->indices.size()); | ||
| for (std::size_t i = 0; i < tmp_index->indices.size(); ++i) { |
There was a problem hiding this comment.
you also need to delete the loop
5ce5891 to
0d4c6bb
Compare
- Implement LookUp for faster mapping of laser segments to machines - Add rolling average for corrected TF transformations - Add laser TFs for MPS parts - Fix launch file configuration for mapper node - Add offset configuration parameters - Clean up logging statements Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
0d4c6bb to
a75dee9
Compare
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
877265d to
4d7e0b7
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request primarily implements two new features:
The laser_scan_integrator node has been extended with a segmentation function.
The function can be activated via a service call. An example call is:
ros2 service call /robotinobase1/toggle_segmentation laser_scan_integrator_msg/srv/ToggleSegmentation "{enable_segmentation: true}"
Once the service is activated, segmented lines are published on the topic /robotinobase1/line_segments.
A new node called mapper has been added.
This node subscribes to the line_segments topic and checks whether segmented lines can be assigned to a machine.
The mapper node currently only starts if the launch argument start_mapper is set to true:
ros2 launch integrated_scan.launch.py start_mapper:=true
If the launch file is not used, the node can also be started separately, for example via:
ros2 run laser_scan_mapper mapper --ros-args --remap __ns:=/robotinobase4 -p frameID:=robotinobase4 -p use_sim_time:=true -p position_tolerance:=0.3 -p angle_tolerance:=0.5 -p machine_names:="['M-DS','M-SS','M-BS','M-CS1','M-CS2','M-RS1','M-RS2','C-DS','C-BS','C-SS','C-RS1','C-RS2','C-CS1','C-CS2']"