You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the near future, Astronauts will need to carry out autonomous operations as they venture beyond Low Earth Orbit. For many of the activities that the astronauts perform, the same training is provided to all crew members months ahead of their mission. A system that provides real-time operations support that is optimized and tailored to each astronaut's psychophysiological state at the time of the activities and which can be used during the training leading up to the mission would significantly improve human spaceflight operations.
9
+
10
+
In this challenge, solvers were asked to determine the present cognitive state of a trainee based on biosensor data, as well as predict what their future cognitive state will be, three seconds in the future.
11
+
12
+
## Data loading
2
13
3
14
The provided data has a high frequency (1 sec = thousands of rows), but the labeling was done manually. Also, final predictions are expected to have a frequency of one (one second = one row). I decided to transform the data so second equals one row both for training and testing. I rounded all timestamps to the closes second and tested several approaches:
4
15
1. Take the first value
@@ -8,17 +19,17 @@ The provided data has a high frequency (1 sec = thousands of rows), but the labe
8
19
9
20
The first approach showed the best results.
10
21
11
-
# EDA
22
+
##EDA
12
23
13
24
During EDA, I noticed that the timestamps might have “holes” between neighbors. The hole is defined as: if the delta time between two neighbors' rows is above one second, there is a “hole” between them. These two neighbors belong to different “sessions.” I noticed that the sensor data between other sessions might be different. I also noticed that the actual target is always constant within these sessions. I incorporated my findings into feature generation and postprocessing of my predictions.
14
25
15
26
16
-
# Creating target
27
+
##Creating target
17
28
18
29
We have to predict cognitive start for time `t` and `t+3`. The target for `t` is equal to the value of the `induced_state` column. The target for `t+3` is the same as the target for `t` because the cognitive state is the same within the session. The data and target are the same, so I decided to train a single model, and use the same model for making predictions for `t` and `t+3`. Note: There is a separation between `t` and `t+3` models in the code. I decided to keep it just in case the data would be different in the future.
19
30
20
31
21
-
# Feature generation
32
+
##Feature generation
22
33
23
34
I had several ideas on features generation, and I combined them into the following groups.
24
35
@@ -29,23 +40,23 @@ I had several ideas on features generation, and I combined them into the followi
29
40
5 - Features based on the distances between eyes positions and gazing points.
30
41
31
42
32
-
# Validation
43
+
##Validation
33
44
34
45
I used stratified group k fold for validation. Stratified = each fold has approximately the same number of samples for each class. Group = provided `test_suite` column.
35
46
36
47
37
-
# Model
48
+
##Model
38
49
39
50
I used the Lightgbm classifier. I optimized hyperparameters using Optuna. The final prediction is the average predictions of several Lightgbm classifiers with different hyperparameters.
40
51
41
-
# Postprocessing
52
+
##Postprocessing
42
53
43
54
As mentioned in EDA, the target is the same within a single session. Therefore, I post-processed predictions by calculating the rolling average of the model’s predictions from the beginning of the session till time `t` (including time `t`) for which we’re making predictions.
44
55
45
-
# Important features
56
+
##Important features
46
57
47
58
To determine the most important features for making predictions for time t, I used built-in SHAP values calculation. Then, I selected top-3 sensor features from the output.
48
59
49
-
# Libraries
60
+
##Libraries
50
61
51
62
You can find the list of used libraries in `requirenments.txt`.
0 commit comments