Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
teaching:gsoc2018 [2018/01/22 09:27] – [RoboSherlock -- Framework for Cognitive Perception] ahaidu | teaching:gsoc2018 [2018/01/22 13:33] – gkazhoya | ||
---|---|---|---|
Line 43: | Line 43: | ||
The OpenEASE web interface as well as further information and publication material can be accessed through its publicly available [[http:// | The OpenEASE web interface as well as further information and publication material can be accessed through its publicly available [[http:// | ||
+ | |||
+ | ===== RobCoG - Robot Commonsense Games ===== | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | The games are split into two categories: (1) VR/Full Body Tracking with physics based interactions, | ||
+ | |||
+ | |||
+ | ===== CRAM - Cognition-enabled Robot Executive ===== | ||
+ | |||
+ | CRAM is a software toolbox for the design, implementation and deployment of cognition-enabled plan execution on autonomous robots. CRAM equips autonomous robots with lightweight reasoning mechanisms that can infer control decisions rather than requiring the decisions to be preprogrammed. This way CRAM-programmed autonomous robots are more flexible and general than control programs that lack such cognitive capabilities. CRAM does not require the whole reasoning domain to be stated explicitly in an abstract knowledge base. Rather, it grounds symbolic expressions into the perception and actuation routines and into the essential data structures of the control plans. CRAM includes a domain-specific language that makes writing reactive concurrent robot behavior easier for the programmer. It extensively uses the ROS middleware infrastructure. | ||
+ | |||
+ | CRAM is an open-source project hosted on [[https:// | ||
+ | [[http:// | ||
+ | and tutorials that help to get started. | ||
+ | |||
+ | |||
===== Proposed Topics ===== | ===== Proposed Topics ===== | ||
Line 94: | Line 111: | ||
Contact: [[team/ | Contact: [[team/ | ||
+ | ==== Topic 3: Unreal - ROS 2 Integration ==== | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | TODO | ||
+ | |||
+ | **Task Difficulty: | ||
+ | | ||
+ | **Requirements: | ||
+ | |||
+ | **Expected Results** We expect to have an integrated communication level with ROS 2 and Unreal Engine on Windows and Linux side. | ||
+ | |||
+ | Contact: [[team/ | ||
+ | |||
+ | |||
+ | ==== Topic 4: Unreal Editor User Interface Development ==== | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | TODO | ||
+ | |||
+ | **Task Difficulty: | ||
+ | | ||
+ | **Requirements: | ||
+ | |||
+ | **Expected Results** We expect to have intuitive Unreal Engine UI Panels for editing, visualizing various RobCoG plugins data and features. | ||
+ | |||
+ | Contact: [[team/ | ||
+ | |||
+ | |||
+ | ==== Topic 5: Unreal - openEASE Live Connection ==== | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | TODO | ||
+ | |||
+ | **Task Difficulty: | ||
+ | | ||
+ | **Requirements: | ||
+ | |||
+ | **Expected Results** We expect to have a live connection with between openEASE and the Unreal Engine editor. | ||
+ | |||
+ | Contact: [[team/ | ||
+ | |||
+ | |||
+ | ==== Topic 6: CRAM -- Visualizing Robot' | ||
+ | |||
+ | **Main Objective: | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | **Task Difficulty: | ||
+ | |||
+ | **Requirements: | ||
+ | * Familiarity with functional programming paradigms: some functional programming experience is a requirement (preferred language is Lisp but Haskel, Scheme, OCaml, Clojure, Scala or similar will do); | ||
+ | * Experience with ROS (Robot Operating System). | ||
+ | |||
+ | **Expected Results:** We expect operational and robust contributions to the source code of the existing robot control system including documentation. | ||
+ | Contact: [[team/ |
Prof. Dr. hc. Michael Beetz PhD
Head of Institute
Contact via
Andrea Cowley
assistant to Prof. Beetz
ai-office@cs.uni-bremen.de
Discover our VRB for innovative and interactive research
Memberships and associations: