... | ... | @@ -156,7 +156,7 @@ The pipeline proceeding this script needs to be contain specific events that ind |
|
|
These tags will be identified and used as your On/Off/In events respectively.
|
|
|
|
|
|
**Onevents/Offevents/Inevents**
|
|
|
To tell the script where to flag, you need to give it Onevents and Offevents **OR** Inevents. Using this information *New* Standardised events will be created and placed at the same latency as your other marks.
|
|
|
To tell the script where to flag, you need to give it Onevents and Offevents **OR** Inevents. Using this information **New**, **Standardised** events will be created and placed at the same latency as your other marks.
|
|
|
|
|
|
* **In events** are events that need to be surrounded within In task time. Any time that is not within 3 sec of an Inevent is considered out of task. This is ideal for studies with many repeated tasks that are within a few seconds of each other.
|
|
|
* Config Example: A Go/NoGo task with 1 as Go and 2 as NoGo with one or the other every 2 seconds. This task has many short breaks between the sessions. Inevents would be ideal as you could specify ```[Inevent], 1 2```and that would ensure that all of the Go and NoGo tasks are included for ICA, while the breaks and lead up times would be removed.
|
... | ... | |