ROS Index
|
|
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/tuw-robotics/tuw_multi_robot.git |
| VCS Type | git |
| VCS Version | noetic |
| Last Updated | 2020-12-18 |
| Dev Status | MAINTAINED |
| CI status | Continuous Integration |
| Released | UNRELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Benjamin Binder
- Markus Bader
- Florian Beck
Authors
- Benjamin Binder
tuw_voronoi_graph
This package contains two nodes where one node is used to generate and load voronoi_graphs out of a map automatically, and one node is used to create graphs out of pre-drawn segments in .dxf format.
tuw_dxf_to_graph_node
is a standard executable which takes a .dxf file as input and generates a graph which is saved to be loaded with the tuw_voronoi_graph_node.
The dxf file must contain the original map.pgm (e.g. used by map server) transformed by scale and offset, to give scale and offset to the application (Theoretically any image with the right scale and offset would work as well). Additionally lines, circles and arcs can be included, which are included to generate the segments. All elements which share an endpoint are connected.
Each resutling segment has a width, given by the commandline argument -w and a lenght, which has at least the length of the commandline argument [-l] and at max the length of [2*(-l) - epsilon].
Arguments
-h [ --help ]
Display help message
-i [ --input ] arg (=./segments.dxf)
The path to the file
-o [ --output ] arg (=./graphs/segments)
The output directory
-w [ --width ] arg (=0.600000024)
The width of a segments in meters
-l [ --length ] arg (=1)
The length of a segment in meters
tuw_voronoi_graph_node
Receives a pixel map (occupancy_grid) and converts it into a tuw_msgs::graph message spanning the whole free space of the map. Additionally the graph is saved to a given folder. If a map is allready converted to a graph the graph is loaded from memory to save computation time.
Subscribed Topics
~map (nav_msgs::occupancy_grid)
The map used for planning (used for matching odom pose to graph)
Published Topics
~segments (tuw_multi_robot_msgs::VoronoiGraph)
The generated graph
Parameters
~map_topic (string default: “/map”)
Sets the topic where the map is read from
~map_smoothing (int default: “15”)
Sets the parameter to smooth the map making cleaner voronoi graphs. (Opencv sometimes segfaults during this process (change this param if so). Keeping this param at zero never produces any segfault.
~segments_topic (string default: “/segments”)
The topic where the graph is published.
~segment_length (float default: “0.9”)
Defines the length of a graph segment.
~crossing_opimization (float default: “0.2”)
Crossings which have less distance than this value are merged together
~end_segment_optimization (float default: “0.4”)
End segments (has only one neighbor) which are shorter than this value are removed.
~graph_path (string default: “.”)
Defines the path were the generated graphs are saved
~custom_graph_path (string default: “”)
If this param is set a custom generated graph is loded from this path
tuw segment to graph node
Receives a pixel map (occupancy_grid) and converts it into a tuw_msgs::graph message spanning the whole free space of the map. Additionally the graph is saved to a given folder. If a map is allready converted to a graph the graph is loaded from memory to save computation time.
Subscribed Topics
Published Topics
~segments (tuw_multi_robot_msgs::VoronoiGraph)
The generated graph
Parameters
~segment_file (string default: “segments.yaml”)
The filepath to the defined segments.
~segments_topic (string default: “/segments”)
The topic where the graph is published.
~segment_length (float default: “0.9”)
Defines the length of a graph segment.
Sample Segments File
start_x: [ 0, 2, 3.2, 5] start_y: [ -1.5, -1.5, -2, -4] end_x: [ 2, 3.2, 5, 3] end_y: [ -1.5, -2, -4, -4] space: [ 1.0, 1.0, 1.0, 1.0] origin_x: 15 origin_y: 15 resolution: 0.05
Wiki Tutorials
Package Dependencies
| Deps | Name |
|---|---|
| cv_bridge | |
| geometry_msgs | |
| nav_msgs | |
| roscpp | |
| tf | |
| tuw_multi_robot_msgs | |
| dynamic_reconfigure | |
| catkin |
System Dependencies
| Name |
|---|
| libdxflib-dev |
Dependant Packages
| Name | Deps |
|---|---|
| tuw_multi_robot | |
| tuw_multi_robot_router |
Launch files
- launch/graph_generator.launch
-
- room [default: cave]
- custom_graph_path [default: ]
- launch/demo_publish_graph.launch
-
- room [default: cave]
- launch_rviz [default: true]
- launch_map_server [default: true]
- launch_graph_generator [default: true]
- cfg [default: default]
- load_map [default: ]
- launch/dxf_graph_demo.launch
-
- seg_length [default: 0.5]
- seg_width [default: 0.5]
- dxf_name [default: segments.dxf]
- graph_name [default: graph]
- room [default: cave]
- launch/map_server.launch
-
- room [default: cave]
- launch/rviz.launch
Messages
Services
Plugins
Recent questions tagged tuw_voronoi_graph at Robotics Stack Exchange
|
|
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/tuw-robotics/tuw_multi_robot.git |
| VCS Type | git |
| VCS Version | kinetic |
| Last Updated | 2018-09-17 |
| Dev Status | MAINTAINED |
| CI status | Continuous Integration |
| Released | UNRELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Benjamin Binder
- Markus Bader
- Florian Beck
Authors
- Benjamin Binder
tuw_voronoi_graph
This package contains two nodes where one node is used to generate and load voronoi_graphs out of a map automatically, and one node is used to create graphs out of pre-drawn segments in .dxf format.
tuw_dxf_to_graph_node
is a standard executable which takes a .dxf file as input and generates a graph which is saved to be loaded with the tuw_voronoi_graph_node.
The dxf file must contain the original map.pgm (e.g. used by map server) transformed by scale and offset, to give scale and offset to the application (Theoretically any image with the right scale and offset would work as well). Additionally lines, circles and arcs can be included, which are included to generate the segments. All elements which share an endpoint are connected.
Each resutling segment has a width, given by the commandline argument -w and a lenght, which has at least the length of the commandline argument [-l] and at max the length of [2*(-l) - epsilon].
Arguments
-h [ --help ]
Display help message
-i [ --input ] arg (=./segments.dxf)
The path to the file
-o [ --output ] arg (=./graphs/segments)
The output directory
-w [ --width ] arg (=0.600000024)
The width of a segments in meters
-l [ --length ] arg (=1)
The length of a segment in meters
tuw_voronoi_graph_node
Receives a pixel map (occupancy_grid) and converts it into a tuw_msgs::graph message spanning the whole free space of the map. Additionally the graph is saved to a given folder. If a map is allready converted to a graph the graph is loaded from memory to save computation time.
Subscribed Topics
~map (nav_msgs::occupancy_grid)
The map used for planning (used for matching odom pose to graph)
Published Topics
~segments (tuw_multi_robot_msgs::VoronoiGraph)
The generated graph
Parameters
~map_topic (string default: “/map”)
Sets the topic where the map is read from
~map_smoothing (int default: “15”)
Sets the parameter to smooth the map making cleaner voronoi graphs. (Opencv sometimes segfaults during this process (change this param if so). Keeping this param at zero never produces any segfault.
~segments_topic (string default: “/segments”)
The topic where the graph is published.
~segment_length (float default: “0.9”)
Defines the length of a graph segment.
~crossing_opimization (float default: “0.2”)
Crossings which have less distance than this value are merged together
~end_segment_optimization (float default: “0.4”)
End segments (has only one neighbor) which are shorter than this value are removed.
~graph_path (string default: “.”)
Defines the path were the generated graphs are saved
~custom_graph_path (string default: “”)
If this param is set a custom generated graph is loded from this path
tuw segment to graph node
Receives a pixel map (occupancy_grid) and converts it into a tuw_msgs::graph message spanning the whole free space of the map. Additionally the graph is saved to a given folder. If a map is allready converted to a graph the graph is loaded from memory to save computation time.
Subscribed Topics
Published Topics
~segments (tuw_multi_robot_msgs::VoronoiGraph)
The generated graph
Parameters
~segment_file (string default: “segments.yaml”)
The filepath to the defined segments.
~segments_topic (string default: “/segments”)
The topic where the graph is published.
~segment_length (float default: “0.9”)
Defines the length of a graph segment.
Sample Segments File
start_x: [ 0, 2, 3.2, 5] start_y: [ -1.5, -1.5, -2, -4] end_x: [ 2, 3.2, 5, 3] end_y: [ -1.5, -2, -4, -4] space: [ 1.0, 1.0, 1.0, 1.0] origin_x: 15 origin_y: 15 resolution: 0.05
Wiki Tutorials
Package Dependencies
| Deps | Name |
|---|---|
| cv_bridge | |
| geometry_msgs | |
| nav_msgs | |
| roscpp | |
| tf | |
| tuw_multi_robot_msgs | |
| dynamic_reconfigure | |
| catkin |
System Dependencies
| Name |
|---|
| libdxflib-dev |
Dependant Packages
| Name | Deps |
|---|---|
| tuw_multi_robot | |
| tuw_multi_robot_router |
Launch files
- launch/graph_generator.launch
-
- room [default: cave]
- custom_graph_path [default: ]
- launch/demo_publish_graph.launch
-
- room [default: cave]
- launch_rviz [default: true]
- launch_map_server [default: true]
- launch_graph_generator [default: true]
- cfg [default: default]
- load_map [default: ]
- launch/dxf_graph_demo.launch
-
- seg_length [default: 0.5]
- seg_width [default: 0.5]
- dxf_name [default: segments.dxf]
- graph_name [default: graph]
- room [default: cave]
- launch/map_server.launch
-
- room [default: cave]
- launch/rviz.launch
Messages
Services
Plugins
Recent questions tagged tuw_voronoi_graph at Robotics Stack Exchange
|
|
Package Summary
| Tags | No category tags. |
| Version | 0.0.0 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/tuw-robotics/tuw_multi_robot.git |
| VCS Type | git |
| VCS Version | melodic |
| Last Updated | 2020-12-17 |
| Dev Status | MAINTAINED |
| CI status | Continuous Integration |
| Released | UNRELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Benjamin Binder
- Markus Bader
- Florian Beck
Authors
- Benjamin Binder
tuw_voronoi_graph
This package contains two nodes where one node is used to generate and load voronoi_graphs out of a map automatically, and one node is used to create graphs out of pre-drawn segments in .dxf format.
tuw_dxf_to_graph_node
is a standard executable which takes a .dxf file as input and generates a graph which is saved to be loaded with the tuw_voronoi_graph_node.
The dxf file must contain the original map.pgm (e.g. used by map server) transformed by scale and offset, to give scale and offset to the application (Theoretically any image with the right scale and offset would work as well). Additionally lines, circles and arcs can be included, which are included to generate the segments. All elements which share an endpoint are connected.
Each resutling segment has a width, given by the commandline argument -w and a lenght, which has at least the length of the commandline argument [-l] and at max the length of [2*(-l) - epsilon].
Arguments
-h [ --help ]
Display help message
-i [ --input ] arg (=./segments.dxf)
The path to the file
-o [ --output ] arg (=./graphs/segments)
The output directory
-w [ --width ] arg (=0.600000024)
The width of a segments in meters
-l [ --length ] arg (=1)
The length of a segment in meters
tuw_voronoi_graph_node
Receives a pixel map (occupancy_grid) and converts it into a tuw_msgs::graph message spanning the whole free space of the map. Additionally the graph is saved to a given folder. If a map is allready converted to a graph the graph is loaded from memory to save computation time.
Subscribed Topics
~map (nav_msgs::occupancy_grid)
The map used for planning (used for matching odom pose to graph)
Published Topics
~segments (tuw_multi_robot_msgs::VoronoiGraph)
The generated graph
Parameters
~map_topic (string default: “/map”)
Sets the topic where the map is read from
~map_smoothing (int default: “15”)
Sets the parameter to smooth the map making cleaner voronoi graphs. (Opencv sometimes segfaults during this process (change this param if so). Keeping this param at zero never produces any segfault.
~segments_topic (string default: “/segments”)
The topic where the graph is published.
~segment_length (float default: “0.9”)
Defines the length of a graph segment.
~crossing_opimization (float default: “0.2”)
Crossings which have less distance than this value are merged together
~end_segment_optimization (float default: “0.4”)
End segments (has only one neighbor) which are shorter than this value are removed.
~graph_path (string default: “.”)
Defines the path were the generated graphs are saved
~custom_graph_path (string default: “”)
If this param is set a custom generated graph is loded from this path
tuw segment to graph node
Receives a pixel map (occupancy_grid) and converts it into a tuw_msgs::graph message spanning the whole free space of the map. Additionally the graph is saved to a given folder. If a map is allready converted to a graph the graph is loaded from memory to save computation time.
Subscribed Topics
Published Topics
~segments (tuw_multi_robot_msgs::VoronoiGraph)
The generated graph
Parameters
~segment_file (string default: “segments.yaml”)
The filepath to the defined segments.
~segments_topic (string default: “/segments”)
The topic where the graph is published.
~segment_length (float default: “0.9”)
Defines the length of a graph segment.
Sample Segments File
start_x: [ 0, 2, 3.2, 5] start_y: [ -1.5, -1.5, -2, -4] end_x: [ 2, 3.2, 5, 3] end_y: [ -1.5, -2, -4, -4] space: [ 1.0, 1.0, 1.0, 1.0] origin_x: 15 origin_y: 15 resolution: 0.05
Wiki Tutorials
Package Dependencies
| Deps | Name |
|---|---|
| cv_bridge | |
| geometry_msgs | |
| nav_msgs | |
| roscpp | |
| tf | |
| tuw_multi_robot_msgs | |
| dynamic_reconfigure | |
| catkin |
System Dependencies
| Name |
|---|
| libdxflib-dev |
Dependant Packages
| Name | Deps |
|---|---|
| tuw_multi_robot | |
| tuw_multi_robot_router |
Launch files
- launch/graph_generator.launch
-
- room [default: cave]
- custom_graph_path [default: ]
- launch/demo_publish_graph.launch
-
- room [default: cave]
- launch_rviz [default: true]
- launch_map_server [default: true]
- launch_graph_generator [default: true]
- cfg [default: default]
- load_map [default: ]
- launch/dxf_graph_demo.launch
-
- seg_length [default: 0.5]
- seg_width [default: 0.5]
- dxf_name [default: segments.dxf]
- graph_name [default: graph]
- room [default: cave]
- launch/map_server.launch
-
- room [default: cave]
- launch/rviz.launch