From 4cf7e63fa963f615f7d9214d170e31c9335d858e Mon Sep 17 00:00:00 2001 From: Constantinos Eleftheriou Date: Fri, 2 Oct 2026 11:45:47 +0100 Subject: [PATCH] Update lever push durations explanation in README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index cb56b15..cdf8444 100644 --- a/README.md +++ b/README.md @@ -52,7 +52,7 @@ visiomode-analysis session path/to/session.json -o output/ --no-report visiomode-analysis session path/to/session.json -o output/ --with-regressors --regressor-timestamps frame_times.csv ``` -**Lever push durations.** If a `sub-_exp-_ses-_lever-durations.csv` file (columns `push_id`, `duration` in ms) sits next to the session JSON, `session` matches each push to its lever push trial (precued trials, hits and false alarms, in trial order) and adds a `lever_duration` column to the trials CSV. Point it at a file elsewhere with `--lever-durations path/to/durations.csv`. Trials without a lever push have an empty `lever_duration`, and sessions without a durations file have no `lever_duration` column at all. If the durations can't be matched (the file is empty or malformed, `push_id` doesn't run 0..n-1, or the number of pushes doesn't match the number of lever push trials), a warning is printed and the column is left empty for that session. +**Lever push durations.** If a `sub-_exp-_ses-_lever-durations.csv` file (columns `push_id`, `duration` in ms) sits next to the session JSON, `session` matches each push to its lever push trial (precued trials, hits and false alarms, in trial order) and adds a `lever_duration` column to the trials CSV. **Generate regressors** for an already-processed session, aligned to an external timestamp series: