-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
171 lines (168 loc) · 10.7 KB
/
index.html
File metadata and controls
171 lines (168 loc) · 10.7 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
<!doctype html>
<html lang="en">
<head>
<!-- Content to ensure fresh version of page is loaded on browser refresh -->
<meta http-equiv="cache-control" content="no-cache, must-revalidate, post-check=0, pre-check=0" />
<meta http-equiv="cache-control" content="max-age=0" />
<meta http-equiv="expires" content="0" />
<meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />
<meta http-equiv="pragma" content="no-cache" /> <meta charset="utf-8" />
<!-- Content to ensure fresh version of page is loaded on browser refresh -->
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta name="color-scheme" content="light dark" />
<title>ERAS Conference</title>
<meta name="description" content="Engineering Reliable Autonomous Systems Conference" />
<!-- Pico.css -->
<!-- <link
rel="stylesheet"
href="https://cdn.jsdelivr.net/npm/@picocss/pico@2.0.0-rc4/css/pico.min.css"
/> -->
<!-- <link rel="stylesheet" href="eras.css"/> -->
<link rel="stylesheet" href="pico-main/css/pico.min.css" />
<link rel="stylesheet" href="pico-main/css/pico.colors.min.css" />
<link rel="stylesheet" href="eras.css"/>
</head>
<body>
<!-- Header -->
<header class="container">
<div class="grid">
<div>
<h1><a href="index.html"><img src="ERASLogo.jpg" alt="ERAS logo - a horizontal gray magnifying glass looking at a blue robot avoiding a brown object with ERAS above the handle and the year below. It says Engineering Reliable Autonomous Systems in gray text below the image." style="width:3.7em"></a> <!-- To scale properly, make height = f(text height) --></h1>
</div>
<div>
<h1 class="pico-color-amber-750">Engineering Reliable Autonomous Systems</h1>
</div>
</div>
<div>
<table width="100%">
<tr>
<td align="left">
<h3>May 28-29, 2026<br>
Zagreb, Croatia
</h3>
</td>
<td align="right" width="150">
<a href="https://www.ieee.org/"><img src="IEEE-logo.png" alt="IEEE Logo"></a>
<br>
<br>
<a href="https://www.ieee-ras.org/"><img src="ieee-ras-logo.png" alt="IEEE RAS Logo"></a>
</td>
</tr>
</table>
</div>
<nav>
<ul>
<li><a href="index.html">Home</a></li>
<li><a href="2025/index.html">2025 Conference</a></li>
<li><a href="https://2026-erasrobotics.org/">2026 Conference</a></li>
<li><a href="SteeringCommittee.html">Steering Committee</a></li>
</ul>
</nav>
</header>
<!-- ./ Header -->
<main class="container">
<h2>Vision</h2>
<p>A space for all stakeholders across autonomous system reliability to come together to discuss the key remaining problems and present progress made towards solving them.</p>
</main>
<main class="container">
<h2>Scope</h2>
<p>Not just verification, evaluation, or software engineering, but a holistic view of how we engineer reliable autonomous systems. For the purposes of this conference, “autonomous systems” is synonymous with "systems that make their own decisions and can take their own actions," and includes everything from autonomous decision-making software running in a virtual environment to teams of autonomous robots operating in a distributed physical environment, everything from simple reactive systems with no planning capability to complex systems incorporating machine learning and reasoning engines. Contributions addressing aspects of reliability across the entire life cycle of the system are welcome.</p>
<h4>Relevant Topics</h4>
<details open>
<summary role="button" class="pico-background-azure-550">General Understanding of Autonomy</summary>
<ul>
<li>Understanding the issues of autonomy, especially under the excess uncertainty of complex deployments (uncertainty and complexity permeate autonomous system design and operation - reliability requires that we address them)</li>
<li>Development of scientific foundations for autonomy that can drive the development of reliable systems</li>
<li>Application of the scientific method to autonomous systems experimentation and evaluation</li>
<li>Reproducibility, replicability, and generalizability of autonomous systems experiments</li>
<li>Research challenges and roadmaps for future development</li>
</ul>
</details>
<details open>
<summary role="button" class="pico-background-azure-550">Specification and User Needs</summary>
<ul>
<li>Defining, ensuring, and assessing system properties (safety, security, functionality, reliability, dependability, trustworthiness, …)</li>
<li>Stakeholder communication, expressing user needs and experiences, designer decisions and assumptions, test and evaluation results, operational expectations</li>
<li>Specification of requirements</li>
<li>System purpose, goals, and expectations as expressed by designers, testers, certification agents, users, customers, bystanders, etc.</li>
<li>Establishing trust and understanding of autonomous system behavior</li>
</ul>
</details>
<details open>
<summary role="button" class="pico-background-azure-550">Design and Systems Engineering for Reliability</summary>
<ul>
<li>System engineering and design principles (including reliable / dependable robot control architectures, systems that incorporate a range of artificial intelligence capabilities, and assurance for design as well as design for assurance)</li>
<li>Fault handling (including prediction, detection, isolation, identification, response, recovery, prevention, tolerance, removal) and runtime methods for recognition and recovery (monitoring, diagnosis, reonfigurability, verification, assurance) - runtime systems that provide resilience and dynamic functionality - autonomy that exists within the system to handle cases that fall outside nominal bounds)</li>
<li>Understanding and analysing trade-offs in system development (e.g. efficiency vs. transparency/verifiability/explainability; design-time vs. run-time; "Hoping for the best" vs. "Expecting the worst")</li>
</ul>
</details>
<details open>
<summary role="button" class="pico-background-azure-550">Assessing and Communicating Reliability</summary>
<ul>
<li>Test and evaluation techniques, principles, methods, tools, etc.</li>
<li>Verification and validation of autonomy (including techniques, processes, principles, methods, tools, verification of decision making, handling of unknown unknowns, uncertainty, and complexity)</li>
<li>Verification and validation of test and evaluation techniques, tools, etc.</li>
<li>Assurance and evidence (including types of evidence, confidence, evidence gathering, specific assurance cases for autonomous systems, structuring and design principles for assurance case development / integration of evidence into assurance)</li>
<li>Measurement and metrics</li>
<li>Mapping from evaluation results to operational performance</li>
<li>Context and impact of verification and evaluation on reliability</li>
<li>Runtime evaluation and assessment</li>
<li>Perceived and actual reliability</li>
</ul>
</details>
<details open>
<summary role="button" class="pico-background-azure-550">Reliability in Context</summary>
<ul>
<li>Licensure, regulatory approval, and certification</li>
<li>Standards and industry benchmarks</li>
<li>Legal and ethical considerations (including insurance and liability as well as government and public service considerations)</li>
<li>Industrial case studies and considerations</li>
<li>Life cycle considerations and methodologies (impact of reliability concerns on need identification, specification, design, development, evaluation and assessment of trustworthiness, operation, decommission)</li>
<li>Case studies (focused in specific application domains (e.g. healthcare diagnosis and intervention / autonomous driving / domestic robotics), specific environmental domains (e.g. space / maritime / volcanos / office buildings) and specific research domains (e.g. controls / perception))</li>
<li>Problem sets, reliability benchmarks and competitions</li>
</ul>
</details>
</main>
<main class="container">
<h2>Audience</h2>
<p>Our goal is to enable communication and collaboration across researchers, regulators, industry, and end users in support of improving the reliability of autonomous systems.</p>
<details open>
<summary role="button" class="pico-background-azure-550">Research Communities</summary>
<ul>
<li>Verification of autonomy</li>
<li>Evaluation and benchmarking in autonomy and robotics</li>
<li>Software engineering</li>
<li>Scientific foundations of robotics/autonomous systems</li>
<li>Assured autonomy</li>
<li>Safety and security</li>
<li>Trust and trustworthiness</li>
</ul>
</details>
<details open>
<summary role="button" class="pico-background-azure-550">Industry / Commercial</summary>
<ul>
<li>Manufacturers of autonomous and robotic systems</li>
<li>Customers of autonomous and robotic systems</li>
</ul>
</details>
<details open>
<summary role="button" class="pico-background-azure-550">Regulatory</summary>
<ul>
<li>Governmental bodies responsible for assessing autonomous systems</li>
<li>Governmental bodies responsible for interpreting (possibly also creating) laws regarding autonomous systems</li>
<li>Agencies and official bodies responsible for regulating autonomous systems</li>
<li>Standards development organizations</li>
</ul>
</details>
<!-- Footer -->
<footer class="container">
<p> </p>
<small>Copyright ERAS 2024 / Built with <a href="https://picocss.com">Pico</a> •
<a href="https://github.com/picocss/examples/blob/master/v2-html/index.html"
>Source code</a
></small
>
</footer>
<!-- ./ Footer -->
</body>
</html>