-
Notifications
You must be signed in to change notification settings - Fork 38
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
New Map format #35
Comments
updated map format to include restrictions |
Hi, I was wondering if it would be worth including the field's datum in the topological map format, and if so, should it be included in the meta field or as a field in root? Also, we should consider that there is already a field for the transform between the metric map and the topo map so probably this won't be necessary. |
@MikHut any comments? |
It might be nice to include the datum so you can do things independently with the topomap, however, the datum is required by a lot of nodes so it might be best to just keep the one, and all the nodes get it from the same place instead of storing it independently |
I discovered that there is no field called edge_id for the edges in the new map, the old map had the edge id which was used by the navigate.py followroute() function. I think we should add that here as well. |
The edge id field has been added in #44 - it just isnt here in the issue. Just added it.
…On Thu, Jan 7, 2021 at 8:19 AM Ayush Sharma ***@***.***> wrote:
I discovered that there is no field called edge_id for the edges in the
new map, the old map had the edge id which was used by the navigate.py
followroute() function. I think we should add that here as well.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF3YS3VV3JZHAT5QEW3C2ZDSYVVCVANCNFSM4S2646EA>
.
--
*Dr Adam Binch* | Senior Robotics Engineer
SAGA ROBOTICS LTD // THORVALD
Think Tank
Lincoln LN6 7FL
Office: 01522837293
Mobile Phone +44 7940 835 628
|
The config field for an edge is now a list of dictionaries, with each setting a parameter to reconfigure and contains the parameter's namespace, name and value. |
The restrictions field for a node and for an edge has been changed from: restrictions:
robot_type: "Narrow"
task_name: "NOT_UV"
transition: "exact_pose" to: restrictions_planning: (robot_tall & task_transportation) | ~ robot_narrow
restrictions_runtime: pose_exact A restriction is now a boolean sentence (default='True'). In other words nodes and edges are not restricted by default. |
default edge goal field changed from goal:
target_pose: $node.pose to goal:
target_pose:
header:
frame_id: $node.parent_frame
pose: $node.pose and field |
This seems to be done for now but will keep as an open issue as there could be changes in the future @Jailander @francescodelduchetto |
This is the proposed new map format for topnav2
The text was updated successfully, but these errors were encountered: