diff options
| -rw-r--r-- | docs/user_guide/gaze_analysis_pipeline/configuration_and_execution.md | 2 | ||||
| -rw-r--r-- | docs/user_guide/gaze_analysis_pipeline/visualisation.md | 5 |
2 files changed, 4 insertions, 3 deletions
diff --git a/docs/user_guide/gaze_analysis_pipeline/configuration_and_execution.md b/docs/user_guide/gaze_analysis_pipeline/configuration_and_execution.md index f4aa2b7..5aca8f3 100644 --- a/docs/user_guide/gaze_analysis_pipeline/configuration_and_execution.md +++ b/docs/user_guide/gaze_analysis_pipeline/configuration_and_execution.md @@ -103,7 +103,7 @@ Timestamped gaze positions have to be passed one by one to [ArFrame.look](../../ # Look ArFrame at a timestamped gaze position ar_frame.look(timestamp, gaze_position) ``` -!!! warning "" +!!! note "" At this point, the [ArFrame.look](../../argaze.md/#argaze.ArFeatures.ArFrame.look) method only process gaze movement identification and scan path analysis without any AOI neither any logging or visualisation supports. diff --git a/docs/user_guide/gaze_analysis_pipeline/visualisation.md b/docs/user_guide/gaze_analysis_pipeline/visualisation.md index 55254dd..99f0259 100644 --- a/docs/user_guide/gaze_analysis_pipeline/visualisation.md +++ b/docs/user_guide/gaze_analysis_pipeline/visualisation.md @@ -57,8 +57,9 @@ Here is an extract from the JSON ArFrame configuration file with a sample where } } }, - "draw_gaze_position": { - "color": [0, 255, 255] + "draw_gaze_positions": { + "color": [0, 255, 255], + "size": 2 } } } |