From f93d3e2b011fe1c1de93d0094ca45584ddd49936 Mon Sep 17 00:00:00 2001 From: Théo de la Hogue Date: Mon, 28 Aug 2023 15:05:01 +0200 Subject: Improving gaze analysis pipeline documentation. --- .../ar_frame_configuration_and_execution.md | 29 ++++++---------------- 1 file changed, 8 insertions(+), 21 deletions(-) (limited to 'docs/user_guide/gaze_analysis_pipeline/ar_frame_configuration_and_execution.md') diff --git a/docs/user_guide/gaze_analysis_pipeline/ar_frame_configuration_and_execution.md b/docs/user_guide/gaze_analysis_pipeline/ar_frame_configuration_and_execution.md index f1264c7..3e18f3e 100644 --- a/docs/user_guide/gaze_analysis_pipeline/ar_frame_configuration_and_execution.md +++ b/docs/user_guide/gaze_analysis_pipeline/ar_frame_configuration_and_execution.md @@ -29,11 +29,6 @@ Here is a simple JSON ArFrame configuration file example: "ExploitExploreRatio": { "short_fixation_duration_threshold": 0 } - }, - "heatmap": { - "size": [320, 180], - "sigma": 0.025, - "buffer": 0 } } ``` @@ -54,8 +49,6 @@ print("scan path:", ar_frame.scan_path) for module, analyzer in ar_frame.scan_path_analyzers.items(): print('scan path analyzer module:', module) - -print("heatmap:", ar_frame.heatmap) ``` Finally, here is what the program writes in console: @@ -67,7 +60,6 @@ gaze movement identifier type: