Refine
Year of publication
Document Type
Conference Type
- Sonstiges (13)
- Konferenz-Abstract (3)
- Konferenzartikel (2)
Language
- English (18)
Has Fulltext
- no (18)
Is part of the Bibliography
- yes (18) (remove)
Institute
- Fakultät Elektrotechnik und Informationstechnik (E+I) (bis 03/2019) (15)
- Fakultät Maschinenbau und Verfahrenstechnik (M+V) (4)
- Fakultät Elektrotechnik, Medizintechnik und Informatik (EMI) (ab 04/2019) (3)
- Fakultät Medien und Informationswesen (M+I) (bis 21.04.2021) (1)
- IMLA - Institute for Machine Learning and Analytics (1)
Open Access
- Open Access (18)
- Bronze (16)
After having described many different aspects of our team software in previous years, in this paper we take the freedom to describe the magmaChallenge framework provided by the magmaOffenburg team. The framework is used as a benchmark tool to run different challenges like the running challenge in 2014 or the kick accuracy challenge in 2015. This description should serve as a documentation to simplify the maintenance by the community and to add new benchmarks in the future.
This paper describes the new Sweaty II humanoid adult size robot trying to qualify for the RoboCup 2016 adult size humanoid competition. Based on experiences during RoboCup 2014, the Sweaty robot has been completely redesigned to a new robot Sweaty II. A major change is the use of linear actuators for the legs. Another characteristic is its indirect actuation by means of rods. This allows a variable transmission ratio depending on the angle of a joint.
This paper describes the Sweaty II humanoid adult size robot trying to qualify for the RoboCup 2017 adult size humanoid competition. Sweaty came 2nd in RoboCup 2016 adult size league. The paper describes the main characteristics of Sweaty that made this success possible, and improvements that have been made or are planned to be implemented for RoboCup 2017.
Team description papers of magmaOffenburg are incremental in the sense that each year we address a different topic of our team and the tools around our team. In this year’s team description paper we focus on the architecture of the software. It is a main factor for being able to keep the code maintainable even after 15 years of development. We also describe how we make sure that the code follows this architecture.