-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathtested.yaml
804 lines (802 loc) · 35.4 KB
/
tested.yaml
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
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
---
user_name: "tested"
scenario:
name: "Industrial use cases"
description: "TestEd is the testbed to simulate the industrial narrow space
workstations.
It can help to reconfigured its length and width hence there are many
configuration that can be tested.
Due to the workspace optimization techniques and lean manufacturing, the
modern workstations are narrow.
TestEd can help to simulate these workstations to test the wearable
technology new concepts and prototypes.
Its modular design and flexibility can help to quickly prepare the intended
workstation.
The inbuilt sensors and actuators ensure the data collection and safety of
the subjects.
For example, TestEd project demonstrate three configurations taken from
automotive, construction and aeronautical industry.
These configurations are by varying the length and width of the testbed i.e.
config_Auto: L = 1533mm and W = 641mm; config_cont: L = 3000mm and
W = 1400mm; conf_aero: L = 4500 and W = 1410"
image: undef
protocol:
- id: 49
name: "tested_narrow_auto"
name_readable: "Industrial Use-Cases in Narrow Spaces (Auto)"
definition: "This protocol helps to benchmark the new wearable technologies
for narrow workspaces.
The user must know number of PI''s, number of subjects, length and
distance between the walls, number of runs and number of assiatnce levels
of wearable robot before starting the test.
Once the Testbed is configured to the desired scenario.
The data is collected with and without the wearable robot/device.
The protocol helps the user to test both relative data analysis and
absolute data analysis.
Below we describe the three configurations of the testbed:
conf_auto: In sitting/standing posture, with both feet on the floor of the
TestEd test bed with truck bending/straight.
The subject performs a circular inspection of a profile placed on the
force sensitive wall of the testbed.
The subject will hold the quality control gauge in one hand to find the
distance between the gap and flush of the profile."
image: tested/img01.png
keywords:
- walking
- standing
- sitting
- maintaining posture in industrial use-case
bipedal_system: [Prosthesis, exoskeleton, human]
pi_algo: [pi_hrmonitoring, pi_metaboliccost, pi_chrono, pi_balance, pi_rangeofmotion, pi_questionnaire, pi_borgscale10]
duration: 20-30s/run/subject
controlled_variables:
- name: distance_automotive
definition: "Distance between mobile panel and the fix panel"
type: double
range: [0.6, 1.5]
unit: m
- name: subject_weight
definition: Subject weight
type: double
range: [15, 150]
unit: kg
- name: gender
definition: Subject gender (1 male 0 female)
type: Boolean
range: [0, 1]
unit: na
- name: assistance_level
definition: Assistance device assistance (1, 2, 3, 4 - low, med, high ,
no. 5- noExo)
type: integer
range: [1, 5]
unit: na
- name: number_runs
definition: total number for runs for each testing cycle
type: integer
range: [1, max]
unit: na
- name: number_subjects
definition: total number of subects
type: integer
range: [1, max]
unit: na
- name: force
definition: max applied force measured by the force sensitive walls
type: double
range: [0, 100]
unit: kg
- name: height1
definition: Vertical height from floor, STARTING point for lift and
END point for lower
type: double
range: [0, 3]
unit: m
- name: height2
definition: Vertical height from floor, END point for lift and
STARTING point for lower
type: double
range: [0, 3]
unit: m
- name: load
definition: load that subject manipulate
type: double
range: [0, 15]
unit: kg
- name: velocity
definition: speed of walking
type: double
range: [0.1, 2]
unit: m/sec
- name: horizontalMovement
definition: Horizontal movement of workpiece
type: double
range: [0, 1.6]
unit: m
- name: slope
definition: Grade of the walking surface
type: double
range: [0, 20]
unit: "%"
- name: mainOption1
definition: 1. Maintenance of body posture or 2. Other tasks
type: integer
range: [1, 2]
unit: na
- name: subOption1
definition: "If user choose 1. Maintenance of body posture user must
select one of the following sub options: 1. Sitting or 2. Standing or
3. Standing and Bending
If user chooses 2. Other tasks then user must select one of the
following 22 options: 1: Stoop lift or 2: Squat lift or 3: One hand
lift or 4: Arm lift or 5. Stoop lower or 6. Squat lower or 7. Arm
lower or 8. Walking or 9. Carrying, loads held at arms length at sides
(1 or 2 hands) or 10. Carrying, loads held against thighs or against
waist or 11. Holding, at arms length, against thighs or at sides (2
hands) or 12. Holding against waist or 13. Holding, at arms length in
one hand or 14. Pushing/pulling, at bench height (0.8 meters) or 15.
Pushing/pulling, at 1.5 meters height or 16. Lateral movement of arms
of 180 degrees, 2 hands or 17. Lateral movement of arms of 180
degrees, 1 hand or 18. 90 degrees arms lateral movement, standing, 1
or 2 hands or 19: 90 degrees arms lateral movement, sitting, 2 hands
or 20. 90 degrees arms lateral movement, sitting, 1 hand or 21:
Forward movement of arms, standing, 1 or 2 hands or 22: Forward
movement of arms, sitting, 1 or 2 hands"
type: Integer
range: [1, 22]
unit: na
testbed:
- item: Instrumented walls
type: combined
file_sheet: To be provided
- item: Motion Capture System
type: sensor
file_sheet: https://www.technaid.com/products/
- item: Force Plate
type: sensor
file_sheet: We can argue whether it is embedded into the testedbed
(so to be described through first line, or to be mentioned here)
- item: Polar H10
type: sensor
file_sheet: https://support.polar.com/e_manuals/H10_HR_sensor/Polar_H10_user_manual_English/manual.pdf
step_description: undef
step_list:
- description: "Configure the TestEd software and select the scenario and
assistance levels of the exoskeleton (Available configuarations:
1. conf_auto)"
detail: "We have developed this software internally for managing the
testing.
This software will be available for EUROBENCH.
This is a web based application that can help to manage the testing
on the testbed.
In addition, it will serve as a platform to collect the user
feedback via questionnaires (digitally)."
- description: "Select the number of PI''s, runs, subjects"
detail: "To ensure the successfull testing this information is vital.
The testing process can be flexible where a test manager can know
number of PI’s evaluated during the TestEd test session.
He can know number runs and can know number of subjects in advance to
plan the testing accordingly."
- description: "Configure, locate and position the measurment devices"
detail: "SOP of measurment devices and requirements."
- description: "Place the subject to the starting position for the first
run without exoskeleton"
- description: Trigger to start the data
- description: "a. The subject enters from the left side of the testbed
with tools, measurment devices and w/wout exoskeleton.
b. Depending on the testbed configuration the subject will take few or
several steps to reach the designated location, where he can perform
the task.
c. This location is predefined and prepared for the testing.
For example for automotive component quality check the target
component must must be installed in the testbed before testing starts.
d. The subject will complete the task. He may maintain a posture, or
perform a repetative task of low frequency or high frequency.
For example, in automotive case he will check the quality of the
component with the help of the quality gauge.
e. After task completion the subject can take few steps to exit the
testbed."
detail: "All data will be recorded from the testbed and the measurement
devices.
From testbed the proximity sensor data for entrance and exit, load
cell data from the middle module wall, accelerometer data from the
hurdles, accelerometer data from the remaining module walls.
We expect to collect the data from measuremnt devices: Force plate,
Polar H10, Fitbit 3, Motion Capture System and manual inclinometer."
- description: Trigger to stop the data
- description: Repeat the number of designated runs for without
exoskeleton and with exoskeleton
has_multiple_run: true
has_multiple_condition: true
has_multiple_subject: true
- name: "tested_narrow_cont"
name_readable: "Industrial Use-Cases in Narrow Spaces (Cont)"
definition: "This protocol helps to benchmark the new wearable technologies
for narrow workspaces.
The user must know number of PI''s, number of subjects, length and
distance between the walls, number of runs and number of assiatnce levels
of wearable robot before starting the test.
Once the Testbed is configured to the desired scenario.
The data is collected with and without the wearable robot/device.
The protocol helps the user to test both relative data analysis and
absolute data analysis.
Below we describe the three configurations of the testbed:
conf_cont: In a standing posture, with both feet on the floor of the
TestEd test bed.
The subject performs a horizontal movement with the tip of the Tig
welding torch while holding the stick in another hand."
image: undef
keywords:
- walking
- standing
- sitting
- maintaining posture in industrial use-case
bipedal_system: [Prosthesis, exoskeleton, human]
pi_algo: [pi_hrmonitoring, pi_metaboliccost, pi_chrono, pi_balance, pi_rangeofmotion, pi_questionnaire, pi_borgscale10]
duration: 20-30s/run/subject
controlled_variables:
- name: distance_automotive
definition: "Distance between mobile panel and the fix panel"
type: double
range: [0.6, 1.5]
unit: m
- name: subject_weight
definition: "Subject weight"
type: double
range: [15, 150]
unit: kg
- name: gender
definition: "Subject gender (1 male 0 female)"
type: boolean
range: [0, 1]
unit: na
- name: assistance_level
definition: Assistance device assistance (1, 2, 3, 4 - low, med, high ,
no. 5- noExo)
type: integer
range: [1, 5]
unit: na
- name: number_runs
definition: total number for runs for each testing cycle
type: integer
range: [1, max]
unit: na
- name: number_subjects
definition: total number of subects
type: integer
range: [1, max]
unit: na
- name: force
definition: max applied force measured by the force sensitive walls
type: double
range: [0, 100]
unit: kg
- name: height1
definition: Vertical height from floor, STARTING point for lift and
END point for lower
type: double
range: [0, 3]
unit: m
- name: height2
definition: Vertical height from floor, END point for lift and
STARTING point for lower
type: double
range: [0, 3]
unit: m
- name: load
definition: load that subject manipulate
type: double
range: [0, 15]
unit: kg
- name: velocity
definition: speed of walking
type: double
range: [0.1, 2]
unit: m/sec
- name: horizontalMovement
definition: Horizontal movement of workpiece
type: double
range: [0, 1.6]
unit: m
- name: slope
definition: Grade of the walking surface
type: double
range: [0, 20]
unit: "%"
- name: mainOption1
definition: 1. Maintenance of body posture or 2. Other tasks
type: integer
range: [1, 2]
unit: na
- name: subOption1
definition: "If user choose 1. Maintenance of body posture user must
select one of the following sub options: 1. Sitting or 2. Standing or
3. Standing and Bending
If user chooses 2. Other tasks then user must select one of the
following 22 options: 1: Stoop lift or 2: Squat lift or 3: One hand
lift or 4: Arm lift or 5. Stoop lower or 6. Squat lower or 7. Arm
lower or 8. Walking or 9. Carrying, loads held at arms length at sides
(1 or 2 hands) or 10. Carrying, loads held against thighs or against
waist or 11. Holding, at arms length, against thighs or at sides (2
hands) or 12. Holding against waist or 13. Holding, at arms length in
one hand or 14. Pushing/pulling, at bench height (0.8 meters) or 15.
Pushing/pulling, at 1.5 meters height or 16. Lateral movement of arms
of 180 degrees, 2 hands or 17. Lateral movement of arms of 180
degrees, 1 hand or 18. 90 degrees arms lateral movement, standing, 1
or 2 hands or 19: 90 degrees arms lateral movement, sitting, 2 hands
or 20. 90 degrees arms lateral movement, sitting, 1 hand or 21:
Forward movement of arms, standing, 1 or 2 hands or 22: Forward
movement of arms, sitting, 1 or 2 hands"
type: Integer
range: [1, 22]
unit: na
testbed:
- item: Instrumented walls
type: combined
file_sheet: To be provided
- item: Motion Capture System
type: sensor
file_sheet: https://www.technaid.com/products/
- item: Force Plate
type: sensor
file_sheet: We can argue whether it is embedded into the testedbed (so to be
described through first line, or to be mentioned here)
- item: Polar H10
type: sensor
file_sheet: https://support.polar.com/e_manuals/H10_HR_sensor/Polar_H10_user_manual_English/manual.pdf
step_description: undef
step_list:
- description: "Configure the TestEd software and select the scenario and
assistance levels of the exoskeleton (Available configuarations:
2. conf_cont)"
detail: "We have developed this software internally for managing the
testing.
This software will be available for EUROBENCH.
This is a web based application that can help to manage the testing
on the testbed.
In addition, it will serve as a platform to collect the user
feedback via questionnaires (digitally)."
- description: "Select the number of PI''s, runs, subjects"
detail: "To ensure the successfull testing this information is vital.
The testing process can be flexible where a test manager can know
number of PI’s evaluated during the TestEd test session.
He can know number runs and can know number of subjects in advance to
plan the testing accordingly."
- description: "Configure, locate and position the measurment devices"
detail: "SOP of measurment devices and requirements."
- description: "Place the subject to the starting position for the first
run without exoskeleton"
- description: Trigger to start the data
- description: "a. The subject enters from the left side of the testbed
with tools, measurment devices and w/wout exoskeleton.
b. Depending on the testbed configuration the subject will take few or
several steps to reach the designated location, where he can perform
the task.
c. This location is predefined and prepared for the testing.
For example for automotive component quality check the target
component must must be installed in the testbed before testing starts.
d. The subject will complete the task. He may maintain a posture, or
perform a repetative task of low frequency or high frequency.
For example, in automotive case he will check the quality of the
component with the help of the quality gauge.
e. After task completion the subject can take few steps to exit the
testbed."
detail: "All data will be recorded from the testbed and the measurement
devices.
From testbed the proximity sensor data for entrance and exit, load
cell data from the middle module wall, accelerometer data from the
hurdles, accelerometer data from the remaining module walls.
We expect to collect the data from measuremnt devices: Force plate,
Polar H10, Fitbit 3, Motion Capture System and manual inclinometer."
- description: Trigger to stop the data
- description: Repeat the number of designated runs for without
exoskeleton and with exoskeleton
has_multiple_run: true
has_multiple_condition: true
has_multiple_subject: true
- name: "tested_narrow_aero"
name_readable: "Industrial Use-Cases in Narrow Spaces (Aero)"
definition: "This protocol helps to benchmark the new wearable technologies
for narrow workspaces.
The user must know number of PI''s, number of subjects, length and
distance between the walls, number of runs and number of assiatnce levels
of wearable robot before starting the test.
Once the Testbed is configured to the desired scenario.
The data is collected with and without the wearable robot/device.
The protocol helps the user to test both relative data analysis and
absolute data analysis.
Below we describe the three configurations of the testbed:
conf_aero: In a sitting posture, with both feet on the floor of the
TestEd test bed with straight truck, the subject performs installation of
two curved sheets on the force sensitive wall and then fasten the sheets
in vertical straight line with electrical screw driver.
The fastening will be performed with one hand holding the screw driver
while the second hand guide the screw."
image: undef
keywords:
- walking
- standing
- sitting
- maintaining posture in industrial use-case
bipedal_system: [Prosthesis, exoskeleton, human]
pi_algo: [pi_hrmonitoring, pi_metaboliccost, pi_chrono, pi_balance, pi_rangeofmotion, pi_questionnaire, pi_borgscale10]
duration: 20-30s/run/subject
controlled_variables:
- name: distance_automotive
definition: "Distance between mobile panel and the fix panel"
type: double
range: [0.6, 1.5]
unit: m
- name: subject_weight
definition: Subject weight
type: double
range: [15, 150]
unit: kg
- name: gender
definition: Subject gender (1 male 0 female)
type: Boolean
range: [0, 1]
unit: na
- name: assistance_level
definition: Assistance device assistance (1, 2, 3, 4 - low, med, high ,
no. 5- noExo)
type: integer
range: [1, 5]
unit: na
- name: number_runs
definition: total number for runs for each testing cycle
type: integer
range: [1, max]
unit: na
- name: number_subjects
definition: total number of subects
type: integer
range: [1, max]
unit: na
- name: force
definition: max applied force measured by the force sensitive walls
type: double
range: [0, 100]
unit: kg
- name: height1
definition: Vertical height from floor, STARTING point for lift and
END point for lower
type: double
range: [0, 3]
unit: m
- name: height2
definition: Vertical height from floor, END point for lift and
STARTING point for lower
type: double
range: [0, 3]
unit: m
- name: load
definition: load that subject manipulate
type: double
range: [0, 15]
unit: kg
- name: velocity
definition: speed of walking
type: double
range: [0.1, 2]
unit: m/sec
- name: horizontalMovement
definition: Horizontal movement of workpiece
type: double
range: [0, 1.6]
unit: m
- name: slope
definition: Grade of the walking surface
type: double
range: [0, 20]
unit: "%"
- name: mainOption1
definition: 1. Maintenance of body posture or 2. Other tasks
type: integer
range: [1, 2]
unit: na
- name: subOption1
definition: "If user choose 1. Maintenance of body posture user must
select one of the following sub options: 1. Sitting or 2. Standing or
3. Standing and Bending
If user chooses 2. Other tasks then user must select one of the
following 22 options: 1: Stoop lift or 2: Squat lift or 3: One hand
lift or 4: Arm lift or 5. Stoop lower or 6. Squat lower or 7. Arm
lower or 8. Walking or 9. Carrying, loads held at arms length at sides
(1 or 2 hands) or 10. Carrying, loads held against thighs or against
waist or 11. Holding, at arms length, against thighs or at sides (2
hands) or 12. Holding against waist or 13. Holding, at arms length in
one hand or 14. Pushing/pulling, at bench height (0.8 meters) or 15.
Pushing/pulling, at 1.5 meters height or 16. Lateral movement of arms
of 180 degrees, 2 hands or 17. Lateral movement of arms of 180
degrees, 1 hand or 18. 90 degrees arms lateral movement, standing, 1
or 2 hands or 19: 90 degrees arms lateral movement, sitting, 2 hands
or 20. 90 degrees arms lateral movement, sitting, 1 hand or 21:
Forward movement of arms, standing, 1 or 2 hands or 22: Forward
movement of arms, sitting, 1 or 2 hands"
type: Integer
range: [1, 22]
unit: na
testbed:
- item: Instrumented walls
type: combined
file_sheet: To be provided
- item: Motion Capture System
type: sensor
file_sheet: https://www.technaid.com/products/
- item: Force Plate
type: sensor
file_sheet: We can argue whether it is embedded into the testedbed (so to be
described through first line, or to be mentioned here)
- item: Polar H10
type: sensor
file_sheet: https://support.polar.com/e_manuals/H10_HR_sensor/Polar_H10_user_manual_English/manual.pdf
step_description: undef
step_list:
- description: "Configure the TestEd software and select the scenario and
assistance levels of the exoskeleton (Available configuarations:
2. conf_aero)"
detail: "We have developed this software internally for managing the
testing.
This software will be available for EUROBENCH.
This is a web based application that can help to manage the testing
on the testbed.
In addition, it will serve as a platform to collect the user
feedback via questionnaires (digitally)."
- description: "Select the number of PI''s, runs, subjects"
detail: "To ensure the successfull testing this information is vital.
The testing process can be flexible where a test manager can know
number of PI’s evaluated during the TestEd test session.
He can know number runs and can know number of subjects in advance to
plan the testing accordingly."
- description: "Configure, locate and position the measurment devices"
detail: "SOP of measurment devices and requirements."
- description: "Place the subject to the starting position for the first
run without exoskeleton"
- description: Trigger to start the data
- description: "a. The subject enters from the left side of the testbed
with tools, measurment devices and w/wout exoskeleton.
b. Depending on the testbed configuration the subject will take few or
several steps to reach the designated location, where he can perform
the task.
c. This location is predefined and prepared for the testing.
For example for automotive component quality check the target
component must must be installed in the testbed before testing starts.
d. The subject will complete the task. He may maintain a posture, or
perform a repetative task of low frequency or high frequency.
For example, in automotive case he will check the quality of the
component with the help of the quality gauge.
e. After task completion the subject can take few steps to exit the
testbed."
detail: "All data will be recorded from the testbed and the measurement
devices.
From testbed the proximity sensor data for entrance and exit, load
cell data from the middle module wall, accelerometer data from the
hurdles, accelerometer data from the remaining module walls.
We expect to collect the data from measuremnt devices: Force plate,
Polar H10, Fitbit 3, Motion Capture System and manual inclinometer."
- description: Trigger to stop the data
- description: Repeat the number of designated runs for without
exoskeleton and with exoskeleton
has_multiple_run: true
has_multiple_condition: true
has_multiple_subject: true
pi:
- name: hrmonitoring
name_readable: "HR monitoring"
description: "This metrics is based on the RR interval (time between
successive heart beats) analysis for short-term intervals.
The PI is composed of four values: the RMSSD (Root mean square of the
successive differences), the SDNN (Standard deviation of the NN (R-R)
intervals), NN50 (The number of adjacent NN intervals that differ from
each other by more than 50 ms) and the PNN50 (proportion of NN50 divided
by the total number of NN (R-R) intervals).
The obtained values can be compared with state of the art tables at:
1. https://hrvcourse.com/wp-content/uploads/2016/07/HRVAgeGender-Table-1080x497.png
2. https://journals.plos.org/plosone/article/file?id=10.1371/journal.pone.0118308&type=printable"
unit: msec
output: vector
intra_run_aggregation: na
# todo: check their proposition
inter_run_aggregation: na
visu: undef
inter_cond_aggregation: undef
inter_subject_aggregation: undef
- name: metaboliccost
name_readable: "Metabolic cost"
description: "This metrics is based on the analytical prediction of the
metabolic rate in kilocalories (kcal) of a human performing static and
dynamic tasks.
The user can select two type of tasks:
1. Static task (postureMaintain) that calculates the metabolic cost based
on body static postures.
The function inputs are body weight and the opt1a.
The user can further select the three sub-options based on the task under
investigation: 1. Sitting or 2. Standing or 3. Standing and Bending
2. Dynamic task (otherTasks) that calculates the metabolic cost based on
dynamic tasks.
The function inputs all variables [please see the table at Initial Code
Structure: https://github.com/jamatics/pi_ctag/blob/master/metabolicCost/src/README.md ]
except opt1.
The user can further select the twenty-two (22) sub-options based on the
task under investigation:
1: Stoop lift, 2: Squat lift, 3: One hand lift, 4: Arm lift, 5. Stoop
lower, 6. Squat lower, 7. Arm lower, 8. Walking, 9. Carrying, loads held
at arms length at sides (1 or 2 han ds), 10. Carrying, loads held against
thighs or against waist, 11.Holding, at arms length, against thighs or at
sides(2 hands), 12. Holding against waist, 13. Holding, at arms length in
one hand, 14. Pushing/pulling, at bench height (0.8 meters), 15.
Pushing/pulling, at 1.5 meters height, 16. Lateral movement of arms of 180
degrees, 2 hands, 17. Lateral movement of arms of 180 degrees, 1 hand,
18. 90 degrees arms lateral movement, standing, 1 or 2 hands, 19. 90
degrees arms lateral movement, sitting, 2 hands, 20. 90 degrees arms
lateral movement, sitting, 1 hand, 21. Forward movement of arms, standing,
1 or 2 hands, 22. Forward movement of arms, sitting, 1 or 2 hands.
The metric results can help the use to combine selected sub-task metabolic
cost in kcal and quickly check the metabolic load of the task under
investigation."
unit: Kcal
output: vector
intra_run_aggregation: na
# todo: check their proposition
inter_run_aggregation: na
visu: undef
inter_cond_aggregation: undef
inter_subject_aggregation: undef
- name: chrono
name_readable: "chrono"
description: Time to complete the task
unit: sec
output: scalar
intra_run_aggregation: na
inter_run_aggregation: undef
visu: undef
inter_cond_aggregation: undef
inter_subject_aggregation: undef
- name: balance
name_readable: "balance"
description: "This metrics is based on the DPSI (Dynamic Posture Stability
Index) that assesses the subject ability to maintain balance while
transformation between static to dynamic stance.
The PI is composed of six values: areaDPSI (sum of all the DPSI at all
time steps), areaDPSIvsTime (normalized sum of all the DPSI with respect
to time), maxat (maximum DPSI value during the experiment), maxTime
(time at maximum DPSI value), minat (minimum DPSI value during the
experiment) and mixTime (time at minimum DPSI value).
The obtained values can be compared with state of the art table
[see article table 1] (subjected to the same measurement protocol of the
following article):
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC1323292/"
unit: na
output: vector
intra_run_aggregation: na
inter_run_aggregation: undef
visu: undef
inter_cond_aggregation: undef
inter_subject_aggregation: undef
- name: rangeofmotion
name_readable: "Range of motion"
description: "This metrics will provide the user to check if the applied
joint angles are within the allowable permissible range established by
the standards.
The PI is composed of joint-wise three values: counter_r_[joint name]
(this counter represents how many times the joint angles remains within
or outside the permissible limits), maxVal_r_[joint name]
(this value represents the maximum value of the joint angle during the
experiment) and minVal_r_[joint name] (this value represents the minimum
value of the joint angle during the experiment).
The user can select the allowable joint angle and insert in the PI.
Following are the main reference that can provide such values:
https://books.google.com/books?hl=en&lr=&id=TSluDQAAQBAJ&oi=fnd&pg=PR1&dq=measurement+of+joint+motion&ots=2gaQs8AiB0&sig=5c8ikDlPh13i1wEhxu-FC6P-dRA"
unit: degree
output: vector
intra_run_aggregation: na
inter_run_aggregation: undef
visu: undef
inter_cond_aggregation: undef
inter_subject_aggregation: undef
- name: questionnaire
name_readable: "Questionnaire"
description: This metric obtains the quantitative analysing in terms of
usability, impact and utility.
The questions are designed in to address these three criterion.
unit: na
output: vector
intra_run_aggregation: na
inter_run_aggregation: undef
visu: undef
inter_cond_aggregation: undef
inter_subject_aggregation: undef
- name: borgscale10
name_readable: "borg scale 10"
description: This metric measures the Human perceived feedback by the borg
scale quantitative implementation.
It is 0-10 point scale where 0 represent no discomfort and 10 represents
agonizing.
The scale represents the increased level of discomfort as we move from 0
towards 10.
unit: na
output: vector
intra_run_aggregation: na
inter_run_aggregation: undef
visu: undef
inter_cond_aggregation: undef
inter_subject_aggregation: undef
pi_algo:
- name: pi_hrmonitoring
description: undef
url_paper: undef
url_code: https://github.com/jamatics/pi_ctag
docker_host: eurobenchtest/pi_ctag:v0.0.1
docker_name: eurobenchtest/pi_ctag:v0.0.1
pi: [hrmonitoring]
input_files: [hrv.csv]
input_command: [./run_pi_hrMonitoring, hrv.csv]
language: octave
implemented: true
- name: pi_metaboliccost
description: undef
url_paper: undef
url_code: https://github.com/jamatics/pi_ctag
docker_host: eurobenchtest/pi_ctag:v0.0.1
docker_name: eurobenchtest/pi_ctag:v0.0.1
pi: [metaboliccost]
input_files: [chrono.csv, subject_info.yaml, condition.yaml, subject_condition_choice_metabolicCost.yaml]
input_command: [./run_pi_metabolicCost, chrono.csv, subject_info.yaml, condition.yaml, subject_condition_choice_metabolicCost.yaml]
language: octave
implemented: true
- name: pi_chrono
description: undef
url_paper: undef
url_code: https://github.com/jamatics/pi_ctag
docker_host: eurobenchtest/pi_ctag:v0.0.1
docker_name: eurobenchtest/pi_ctag:v0.0.1
pi: [chrono]
input_files: [chrono.csv]
input_command: [./run_pi_chrono, chrono.csv]
language: octave
implemented: true
- name: pi_balance
description: undef
url_paper: undef
url_code: https://github.com/jamatics/pi_ctag
docker_host: eurobenchtest/pi_ctag:v0.0.1
docker_name: eurobenchtest/pi_ctag:v0.0.1
pi: [balance]
input_files: [balance.csv, subject_info.yaml]
input_command: [./run_pi_balance, balance.csv, subject_info.yaml]
language: octave
implemented: true
- name: pi_rangeofmotion
description: undef
url_paper: undef
url_code: https://github.com/jamatics/pi_ctag
docker_host: eurobenchtest/pi_ctag:v0.0.1
docker_name: eurobenchtest/pi_ctag:v0.0.1
pi: [rangeofmotion]
input_files: [jointAngles.csv]
input_command: [./run_pi_rangeofMotion, jointAngles.csv]
language: octave
implemented: true
- name: pi_questionnaire
description: undef
url_paper: undef
url_code: https://github.com/jamatics/pi_ctag
docker_host: eurobenchtest/pi_ctag:v0.0.1
docker_name: eurobenchtest/pi_ctag:v0.0.1
pi: [questionnaire]
input_files: [questionnaire_medAssist.csv]
input_command: [./run_pi_questionnaire, questionnaire_medAssist.csv]
language: octave
implemented: true
- name: pi_borgscale10
description: undef
url_paper: undef
url_code: https://github.com/jamatics/pi_ctag
docker_host: eurobenchtest/pi_ctag:v0.0.1
docker_name: eurobenchtest/pi_ctag:v0.0.1
pi: [borgscale10]
input_files: [questionnaire_borgScale10.csv]
input_command: [./run_pi_borgScale10, questionnaire_borgScale10.csv]
language: octave
implemented: true