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

Moving the navigation goals to the ontology #198

Open
alex-mitrevski opened this issue Jul 5, 2019 · 2 comments
Open

Moving the navigation goals to the ontology #198

alex-mitrevski opened this issue Jul 5, 2019 · 2 comments

Comments

@alex-mitrevski
Copy link
Member

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.

@argenos
Copy link
Contributor

argenos commented Jul 8, 2019

I'll also draft the changes for moving them to the topological map

@alex-mitrevski
Copy link
Member Author

I've started addressing this with b-it-bots/mas_knowledge_base#11

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants