This is an old revision of the document!
Minutes of the "handover" meeting -- An overview of what's available in KnowRob
Infrastructure
Repositories
Package naming
Package layout
Best practices
- Separate code and data
- Use unique identifiers
- Keep the dependency list small
- Create demo-specific packages with launch files and dependencies
- Put special-purpose functionality into knowrob_addons
- Create wiki pages while developing a novel package, copy/paste your test queries there, make your students do the same to document how their stuff can be used without having to think too much about it
Representations in OWL
Upper ontology
Objects
- Object classes
- Object instances
- Object positions over time
Actions
- Action classes
- Action recipes/task descriptions
- Action instances/log files
Overview of the available KnowRob packages
- rosprolog, json_prolog
- knowrob_common
- comp_temporal, comp_spatial
- knowrob_objects, knowrob_map_tools, knowrob_map_data, comp_orgprinciples
- knowrob_actions
- knowrob_srdl
- tf_prolog
- knowrob_mongo, visualization infrastructure
- knowrob_addons: …
- knowrob_gui
- knowrob_human
- knowrob_tutorials
