Skip to Content
Last modified by Rosa Van Tuijn on 2026/04/13 12:47
From version 2.3
edited by Rosa Van Tuijn
on 2026/03/24 16:12
Change comment: There is no comment for this version
To version 1.11
edited by Tjalling Haije
on 2026/03/23 15:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -h. Test SFT1: System baseline test
1 +h. Test SFT1
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.RosaVanTuijn
1 +XWiki.TjallingHaije
Content
... ... @@ -1,9 +1,9 @@
1 1  **Experiment title**
2 -System baseline test
2 +[Short, descriptive title]
3 3  
4 4  
5 5  **2. Objective / Research Question**
6 -Do the SYNERGISE technologies together improve the SYNERGISE [[Objectives>>2\. Specification.Objectives.WebHome]] (stated below) without negative effects?
6 +Do the SYNERGISE technologies together improve the below SYNERGISE [[Objectives>>2\. Specification.Objectives.WebHome]] without negative effects?
7 7  
8 8  1. Mission effectiveness
9 9  1. Mission efficiency
... ... @@ -10,6 +10,7 @@
10 10  1. FR Health
11 11  1. FR and victim safety
12 12  
13 +
13 13  **3. Hypotheses / Expectations (optional)**
14 14  See the claims from [[UC04.3: Detailed indoor exploration with ANYMAL (USAR)>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYMAL (USAR).WebHome]], being:
15 15  
... ... @@ -21,6 +21,7 @@
21 21  * CL06: improved FR health
22 22  * CL07: degraded mission efficiency
23 23  
25 +
24 24  **4. Scenario / Context**
25 25  ASR3: Detailed indoor exploration
26 26  
... ... @@ -32,6 +32,7 @@
32 32  ** **ANYmal **is mission-ready (battery, controls, and payload checked).
33 33  ** **C3I is online**, role-based views are configurated (Operator/ Analyst/ Team leader/ Safety officer); **5G pods** are installed for connection.
34 34  
37 +
35 35  **5. Participants**
36 36  
37 37  * FR team ROBOT:
... ... @@ -93,6 +93,7 @@
93 93  
94 94  * Building A: Easier location, obstacles and environmental conditions. (clear visibility, ..)
95 95  * Building B: Challenging location, obstacles and environmental conditions for humans and robots (e.g. smoke and obstacles).
99 +*
96 96  
97 97  Trial 1:
98 98  
... ... @@ -104,86 +104,24 @@
104 104  * FR Team ROBOT does Building B
105 105  * FR team HUMAN does Building A
106 106  
111 +
107 107  **9. Measurements**
108 108  
109 -See the measurements from [[UC04.3: Detailed indoor exploration with ANYMAL (USAR)>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYMAL (USAR).WebHome]]. Compare outcomes between the two conditions teams if applicable.
114 +See the measurements from [[UC04.3: Detailed indoor exploration with ANYMAL (USAR)>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYMAL (USAR).WebHome]]
110 110  
111 -|**Claim: Safety**|**Measurment(s)**|**How to test **
112 -|Safer decision before entry|Safe path chosen|(((
113 -* Define ground-truth safe path(s) beforehand so that they can be compared to chosen entry path during the trial
114 -* Score paths beforehand: safe/ suboptimal/ unsafe
115 -)))
116 -|Better decision overall|"How good were you decisions looking back?"|(((
117 -* Hotwash reflection question (likert + open)
118 -* Observations of errors (e.g. near-incidents, unsafe choices)
119 -)))
120 -|Fewer dangerous situations|Near-incident reports|(((
121 -* Define hazards in buildings beforehand and check (with observations of during hotwash) if these hazards are avoided or not
122 -)))
123 123  
124 -|**Claim: Efficiency**|**Measurment(s)**|**How to test **
125 -|Faster mission execution|Total mission completion time|(((
126 -* Timestamp of start (after briefing) till all located victims have been extracted
127 -)))
128 -|Faster inside performance|First responder time inside|(((
129 -* Timestamp of entry building till exist building (last located victim is exstracted)
130 -)))
131 -
132 -|**Claim: Situation Awareness**|**Measurment(s)**|**How to test **
133 -|Before entry |(((
134 -Correctness of reported hazards, victims, layout
135 -)))|(((
136 -* Before entry let squad leader and entry team (seperatly) sketch/map or describe inside of building (harzards, victims, layout) > compare these with the ground-truth
137 -
138 -(((
139 -
140 -)))
141 -)))
142 -|During entry|(((
143 -FR path logs
144 -)))|(((
145 -* Compare plannend vs. executed path (how many or how big were the deviations? and were they acceptable?) and identify detours caused by misjudgment or new information
146 -
147 -(((
148 -
149 -)))
150 -)))
151 -|After mission|(((
152 -Correctness of reported hazards, victims, layout
153 -)))|(((
154 -* Repeat sketching/mapping or descriptive task and compare the outcomes (improvement/ deterioration vs pre-entry)
155 -)))
156 -
157 -|**Claim: Situation Awareness**|**Measurment(s)**|**How to test **
158 -| |(((
159 -
160 -)))|(((
161 -
162 -)))
163 -| |(((
164 -
165 -)))|(((
166 -
167 -)))
168 -| |(((
169 -
170 -)))|
171 -
172 -
173 -
174 174  **10. Procedure (Step-by-Step)**
175 175  
176 -1. __Team preparation__:
119 +1. Team training:
177 177  11. FR team ROBOT is trained in operating the robot, analysing the camera stream, and pinning information on C3I
178 178  11. Squad leader and BoO are trained for both teams in interpreting the health and location sensor data.
179 179  11. Experiment leader knows where hazards and victims are in both buildings.
180 -11. Anymal robot is tested with network in target buildings for experiment (without FR themselves seeing building!)
181 -1. __Experiment preparation:__
123 +1. Usecase preparation
182 182  11. Building is prepped with victims, hazards, etc.
183 -1. __Briefing:__
125 +1. Briefing:
184 184  11. Same for both teams for both building types: Building has been inspected from outside and is estimated safe for entry. Situation inside unknown. Victims possibly present. Goal: find, assess, and extract victims while avoiding and mapping hazards.
185 185  11. One person is notified that their health sensor will be triggered during the Building B (difficult building) situation.
186 -1. __Execution:__
128 +1. Execution:
187 187  11. For FR team ROBOT, see: [[UC04.3: Detailed indoor exploration with ANYMAL (USAR)>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYMAL (USAR).WebHome]]
188 188  11. For FR team HUMAN, see: [[UC04.4: Detailed indoor exploration without ANYMAL (USAR)>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYmal (USAR).WebHome]]
189 189  11. During execution of both teams, performance will be measured by experiment leader:
... ... @@ -191,64 +191,47 @@
191 191  111. Health indicators stay within acceptable range
192 192  111. Time for tackling any health alerts
193 193  111. Track FR path
194 -1. __Hotwash__:
195 -11. Questions (specified per role, couple questions per topic) on:
136 +1. Hotwash:
137 +11. Questions on:
196 196  111. Near-incident report
197 197  111. Path inside
198 198  111. FR location and status of hazards, victims, and layout
199 -111. Mission effectiveness: e.g. self reported effectiveness of decisions
141 +111. Mission effectiveness
200 200  111. Self-reported workload
201 201  111. Trust survey
202 -11. Group discussion with feedback
203 203  
204 -**~11. Planning:**
145 +Planning:
205 205  
206 -* Team preparation: Day before. 1 hour.
147 +* Team training:  Day before. 1 hour.
207 207  * Trial 1:
208 -** Setup scenario: Test day 1. 09:00 - 09:30
149 +** Setup usecase: Test day 1. 09:00 - 09:30
209 209  ** Setup tech and perform checks: Test day 1. 09:00 - 09:30
210 210  ** Briefing of each team individually (outside building): Test day 1: 09:00 - 09:30
211 211  ** Mission execution: Test day 1. 09:30 - 10:30
212 212  ** Hot wash: Test day 1. 10:30-11:00
213 -** Scenario reset: test day 1. 10:30-11:00
154 +** Usecase reset: test day 1. 10:30-11:00
214 214  * Teams switch location: Test day 1. 11:00-11:15
215 215  * Trial 2: 
216 -** (Setup scenario: Test day 1. 12:30 - 13:00)
157 +** Setup usecase: Test day 1. 12:30 - 13:00
217 217  ** Setup tech and perform checks: Test day 1. 12:30 - 13:00
218 218  ** Briefing of each team individually (outside building): Test day 1: 12:30 - 13:00
219 219  ** Mission execution: Test day 1. 13:00 - 14:00
220 220  ** Hot wash: Test day 1. 14:00-14:30
221 -* Cleanup area and store tech. 14:00-14:30
162 +** Cleanup area and store tech. 14:00-14:30
222 222  
223 223  
224 224  
225 -**12. Materials**
226 226  
227 -* For FRs:
228 -** 1x Anymal with teleop setup and networking
229 -** 2x Tablet with C3I for squad leader (one spare)
230 -** 1x Base of Operations with computer with C3I
231 -** 4x Health sensors
232 -** 4x Location sensors
233 -** 8x walky talky with two channels (?) (for FR team and BoO).
234 -* For usecase:
235 -** 2x training building (~~100m2?)
236 -** Enviromental challenges: smoke machine, obstacles, etc.
237 -** ~~8x Actors or dummies for victims.
238 -* 8x Clipboards with papers and pens for hotwash and questionnaires
167 +**~11. Materials / Setup Components**
168 +[List equipment, environment layout, props, simulation assets]
239 239  
240 -**13. Dependencies**
241 241  
242 -* Availability of materials
243 -* Availability and functioning of ANYmal robot with teleoperation and network in target buildings
244 -* Availability of functioning network between robot, FRs, and BoO.
245 -* Availability of:
246 -** Experiment participants
247 -** People willing to play victim
248 -** Experiment leaders
171 +**14. Dependencies**
172 +[Other WPs, required assets, system availability, permissions]
249 249  
250 -**14. Success Criteria**
251 -When mission(s) completed by both teams, and we can compare their performance using the metrics.
252 252  
175 +**15. Success Criteria**
176 +[How do you know the experiment worked as intended?]
253 253  
178 +
254 254