Last modified by Rosa Van Tuijn on 2026/04/13 12:47

From version 1.7
edited by Tjalling Haije
on 2026/03/23 14:15
Change comment: There is no comment for this version
To version 2.2
edited by Rosa Van Tuijn
on 2026/03/24 16:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -h. Test SFT1
1 +h. Test SFT1: System baseline test
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.TjallingHaije
1 +XWiki.RosaVanTuijn
Content
... ... @@ -1,9 +1,9 @@
1 1  **Experiment title**
2 -[Short, descriptive title]
2 +System baseline test
3 3  
4 4  
5 5  **2. Objective / Research Question**
6 -Do the SYNERGISE technologies together improve the below SYNERGISE [[Objectives>>2\. Specification.Objectives.WebHome]] without negative effects?
6 +Do the SYNERGISE technologies together improve the SYNERGISE [[Objectives>>2\. Specification.Objectives.WebHome]] (stated below) without negative effects?
7 7  
8 8  1. Mission effectiveness
9 9  1. Mission efficiency
... ... @@ -10,7 +10,6 @@
10 10  1. FR Health
11 11  1. FR and victim safety
12 12  
13 -
14 14  **3. Hypotheses / Expectations (optional)**
15 15  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:
16 16  
... ... @@ -22,7 +22,6 @@
22 22  * CL06: improved FR health
23 23  * CL07: degraded mission efficiency
24 24  
25 -
26 26  **4. Scenario / Context**
27 27  ASR3: Detailed indoor exploration
28 28  
... ... @@ -34,7 +34,6 @@
34 34  ** **ANYmal **is mission-ready (battery, controls, and payload checked).
35 35  ** **C3I is online**, role-based views are configurated (Operator/ Analyst/ Team leader/ Safety officer); **5G pods** are installed for connection.
36 36  
37 -
38 38  **5. Participants**
39 39  
40 40  * FR team ROBOT:
... ... @@ -94,59 +94,139 @@
94 94  
95 95  Two buildings:
96 96  
97 -* Building A: Challenging location, obstacles and environmental conditions for humans and robots (e.g. smoke and obstacles).
98 -* Building B: Easier location, obstacles and environmental conditions. (clear visibility, ..)
94 +* Building A: Easier location, obstacles and environmental conditions. (clear visibility, ..)
95 +* Building B: Challenging location, obstacles and environmental conditions for humans and robots (e.g. smoke and obstacles).
99 99  
97 +Trial 1:
100 100  
99 +* FR Team ROBOT does Building A
100 +* FR team HUMAN does Building B
101 101  
102 -Trial1:
102 +Trial 2:
103 103  
104 -* FR Team ROBOT does easy
104 +* FR Team ROBOT does Building B
105 +* FR team HUMAN does Building A
105 105  
106 -Team A does first [[UC04.3>>2\. Specification.b\. Use Cases.UC04\.0\: Detailed indoor exploration.UC04\.3\: Detailed indoor exploration with ANYMAL (USAR).WebHome]]
107 -
108 -[Condition A vs B, baseline vs intervention, with/without transparency, etc.]
109 -
110 -
111 111  **9. Measurements**
112 112  
113 -* Objective measures: [E.g., task completion time, errors, navigation metrics]
114 -* Subjective measures: [E.g., trust, workload, clarity, usability questionnaires]
115 -* Logs / sensors: [E.g., robot logs, video, physiological sensors]
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.
116 116  
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 +)))
117 117  
118 -**10. Procedure (Step-by-Step)**
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 +)))
119 119  
120 -1. [Describe preparation]
121 -1. [Briefing]
122 -1. [Execution]
123 -1. [Debrief / Hotwash]
132 +|**Claim: Situation Awareness**|**Measurment(s)**|**How to test **
133 +|Before entry |(((
134 +Correctness of reported hazards, victims, layout
135 +)))|(((
136 +
137 +)))
138 +|During entry|(((
139 +FR path logs
140 +)))|(((
141 +
142 +)))
143 +|After mission|(((
144 +Correctness of reported hazards, victims, layout
145 +)))|
124 124  
125 125  
126 -**~11. Materials / Setup Components**
127 -[List equipment, environment layout, props, simulation assets]
128 128  
149 +**10. Procedure (Step-by-Step)**
129 129  
130 -**12. Safety & Ethical Considerations**
151 +1. __Team preparation__:
152 +11. FR team ROBOT is trained in operating the robot, analysing the camera stream, and pinning information on C3I
153 +11. Squad leader and BoO are trained for both teams in interpreting the health and location sensor data.
154 +11. Experiment leader knows where hazards and victims are in both buildings.
155 +11. Anymal robot is tested with network in target buildings for experiment (without FR themselves seeing building!)
156 +1. __Experiment preparation:__
157 +11. Building is prepped with victims, hazards, etc.
158 +1. __Briefing:__
159 +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.
160 +11. One person is notified that their health sensor will be triggered during the Building B (difficult building) situation.
161 +1. __Execution:__
162 +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]]
163 +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]]
164 +11. During execution of both teams, performance will be measured by experiment leader:
165 +111. Mission completion time
166 +111. Health indicators stay within acceptable range
167 +111. Time for tackling any health alerts
168 +111. Track FR path
169 +1. __Hotwash__:
170 +11. Questions (specified per role, couple questions per topic) on:
171 +111. Near-incident report
172 +111. Path inside
173 +111. FR location and status of hazards, victims, and layout
174 +111. Mission effectiveness: e.g. self reported effectiveness of decisions
175 +111. Self-reported workload
176 +111. Trust survey
177 +11. Group discussion with feedback
131 131  
132 -* Risks: [Describe]
133 -* Mitigations: [Describe]
134 -* Informed consent: [Yes/No + method]
135 -* Data handling: [Describe]
179 +**~11. Planning:**
136 136  
181 +* Team preparation: Day before. 1 hour.
182 +* Trial 1:
183 +** Setup scenario: Test day 1. 09:00 - 09:30
184 +** Setup tech and perform checks: Test day 1. 09:00 - 09:30
185 +** Briefing of each team individually (outside building): Test day 1: 09:00 - 09:30
186 +** Mission execution: Test day 1. 09:30 - 10:30
187 +** Hot wash: Test day 1. 10:30-11:00
188 +** Scenario reset: test day 1. 10:30-11:00
189 +* Teams switch location: Test day 1. 11:00-11:15
190 +* Trial 2: 
191 +** (Setup scenario: Test day 1. 12:30 - 13:00)
192 +** Setup tech and perform checks: Test day 1. 12:30 - 13:00
193 +** Briefing of each team individually (outside building): Test day 1: 12:30 - 13:00
194 +** Mission execution: Test day 1. 13:00 - 14:00
195 +** Hot wash: Test day 1. 14:00-14:30
196 +* Cleanup area and store tech. 14:00-14:30
137 137  
138 -**13. Location & Duration**
139 139  
140 -* Location: [Where does it take place?]
141 -* Duration: [Total time per run + preparation]
142 142  
200 +**12. Materials**
143 143  
144 -**14. Dependencies**
145 -[Other WPs, required assets, system availability, permissions]
202 +* For FRs:
203 +** 1x Anymal with teleop setup and networking
204 +** 2x Tablet with C3I for squad leader (one spare)
205 +** 1x Base of Operations with computer with C3I
206 +** 4x Health sensors
207 +** 4x Location sensors
208 +** 8x walky talky with two channels (?) (for FR team and BoO).
209 +* For usecase:
210 +** 2x training building (~~100m2?)
211 +** Enviromental challenges: smoke machine, obstacles, etc.
212 +** ~~8x Actors or dummies for victims.
213 +* 8x Clipboards with papers and pens for hotwash and questionnaires
146 146  
215 +**13. Dependencies**
147 147  
148 -**15. Success Criteria**
149 -[How do you know the experiment worked as intended?]
217 +* Availability of materials
218 +* Availability and functioning of ANYmal robot with teleoperation and network in target buildings
219 +* Availability of functioning network between robot, FRs, and BoO.
220 +* Availability of:
221 +** Experiment participants
222 +** People willing to play victim
223 +** Experiment leaders
150 150  
225 +**14. Success Criteria**
226 +When mission(s) completed by both teams, and we can compare their performance using the metrics.
151 151  
228 +
152 152