Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
create_your_own_knowrob_package [2012/12/01 10:00] – tenorthcreate_your_own_knowrob_package [2014/06/05 11:38] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Create your own KnowRob package ====== +#REDIRECT doc:create_your_own_knowrob_package
- +
-If your application requires functionality beyond that one already provided by the standard KnowRob packages, you will need to create your own KnowRob package. The following description assumes that you would like to add knowledge in terms of OWL ontologies, or implement new Prolog predicates, or both. If you would just like to link against e.g. some Java libraries provided by the packages, you don't have to follow the description below, but can just implement a normal ROS package that depends on the respective KnowRob packages. +
- +
-The answer depends on which kind of package you would like to create: +
- +
-(1) If the package implements new Prolog functionality or contains custom OWL files, you should create a package similar to e.g. comp_spatial. It should be a normal ROS package that, in addition, contains the following files: +
- +
-<code> +
-  |- owl +
-  |  \- your_file.owl +
-  |- prolog +
-     |- init.pl +
-     \- your_module.pl +
-</code> +
- +
-The init.pl should initialize the package, which may include loading dependencies, parsing OWL files, and registering RDF namespaces. Have a look at e.g. comp_spatial for an example. The owl.in or pl.in files you will find in some packages are required since the RDF parser needs global paths for loading files referenced by an OWL file. owl.in files therefore contain a placeholder that is replaced during compilation as specified in your CMakeLists.txt. Once you have set up your package like this, you can launch the system using  +
-    rosrun rosprolog rosprolog your_package +
- +
-(2) If you would just like to use existing packages in your program, e.g. to send queries via jpl or to call Java methods in one of the packages, it's enough to just depend on the KnowRob package. +
- +
-Regarding which package to depend on, this depends on which functionality you would like to use. You just need to list the direct dependencies in your manifest, their dependencies are automatically included as well. Common candidates could be to depend on mod_vis (if you would like to use the visualization somewhere) or on ias_semantic_map (if you would like to use that map). +
- +
- +