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 13:02] – gkazhoya | teaching:gsoc2018 [2018/01/23 08:34] – [pracmln] ahaidu | ||
---|---|---|---|
Line 4: | Line 4: | ||
====== Google Summer of Code 2018 ====== | ====== Google Summer of Code 2018 ====== | ||
~~NOTOC~~ | ~~NOTOC~~ | ||
+ | |||
+ | In the following we shortly present the open source frameworks that are participating for this year's Google Summer of Code. | ||
+ | |||
+ | For the **proposed topics** see [[# | ||
+ | |||
+ | |||
+ | ===== Software ===== | ||
+ | |||
===== pracmln ===== | ===== pracmln ===== | ||
Line 53: | Line 61: | ||
===== CRAM - Cognition-enabled Robot Executive ===== | ===== 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 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 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:// | CRAM is an open-source project hosted on [[https:// | ||
- | project page ([[http:// | + | [[http:// |
and tutorials that help to get started. | and tutorials that help to get started. | ||
Line 156: | Line 162: | ||
Contact: [[team/ | 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: