2016
DOI: 10.1007/978-3-319-44427-7_13
|View full text |Cite
|
Sign up to set email alerts
|

Observing the Effects of Overdesign in the Automatic Design of Control Software for Robot Swarms

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

1
11
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
4
3

Relationship

4
3

Authors

Journals

citations
Cited by 14 publications
(12 citation statements)
references
References 40 publications
1
11
0
Order By: Relevance
“…Such a procedure would greatly benefit off-line fully-automatic, semi-automatic (humanin-the-loop), and manual design. In particular, in the case of fully-automatic design, such evaluation procedure could contribute to handle the so-called overdesign: it has been shown that, past an optimal number of steps of the design process, the performance observed in reality diverges from the one in simulation (Birattari et al 2016). As a consequence, protracting a design process indefinitely could be counterproductive.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…Such a procedure would greatly benefit off-line fully-automatic, semi-automatic (humanin-the-loop), and manual design. In particular, in the case of fully-automatic design, such evaluation procedure could contribute to handle the so-called overdesign: it has been shown that, past an optimal number of steps of the design process, the performance observed in reality diverges from the one in simulation (Birattari et al 2016). As a consequence, protracting a design process indefinitely could be counterproductive.…”
Section: Discussionmentioning
confidence: 99%
“…It is also understood that the performance drop is a relative problem: instances of control software produced by different methods or under different conditions may be affected to different degrees. This can lead to a phenomenon that we call rank inversion: an instance of control software outperforms another one in simulation, but is outperformed by the latter when they are evaluated on physical robots (Francesca et al 2014;Birattari et al 2016). On the other hand, what remains an open issue is the true nature of the reality gap.…”
Section: Introductionmentioning
confidence: 99%
“…EvoStick was formally defined in [18] to serve as a yardstick in the study of Vanilla, but had been previously analyzed in [19]. It was subsequently included in other empirical studies [17,16,5,33]. EvoCom targets the e-puck platform, as it is modeled by RM 2-see Table 1.…”
Section: Protocolmentioning
confidence: 99%
“…The relative nature of performance drops might result in what we shall call a rank inversion: control software A outperforms control software B in simulation, but B outperforms A when assessed on the physical robots. Rank inversions can be observed when comparing instances of control software produced by different design methods [19], or by the same one at different steps along the optimization process [4]. Indeed, Birattari et al [4] observed a phenomenon that they called overdesign: past an optimal number of steps of the optimization process, the performance obtained in reality diverges from the one obtained in simulation.…”
Section: Introductionmentioning
confidence: 99%