You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since navigation goals can be considered encyclopedic information that is currently stored in YAML files (e.g. here), it makes sense to consider storing the information in the ontology instead in order to centralise the knowledge in one place. An alternative to storing the poses in the ontology is storing them in the topological map.
This would require minor modifications to the move_base action and the navigation goal visualiser, which currently read the goals from the previously mentioned YAML file, as well as the map annotation tool, which creates the YAML file.
I don't foresee this to be a lot of work, so when I have some time, I could draft these modifications in order to show in action how I have imagined the workflow.
The text was updated successfully, but these errors were encountered:
It would be good to resolve b-it-bots/mas_knowledge_base#12 before I proceed however since I wouldn't want to repeat the definitions of classes and properties in multiple ontology files.
Since navigation goals can be considered encyclopedic information that is currently stored in YAML files (e.g. here), it makes sense to consider storing the information in the ontology instead in order to centralise the knowledge in one place. An alternative to storing the poses in the ontology is storing them in the topological map.
This would require minor modifications to the
move_base
action and the navigation goal visualiser, which currently read the goals from the previously mentioned YAML file, as well as the map annotation tool, which creates the YAML file.I don't foresee this to be a lot of work, so when I have some time, I could draft these modifications in order to show in action how I have imagined the workflow.
The text was updated successfully, but these errors were encountered: