Skip to content

Changes

Page history
adlofts created page: prep authored by Andrew Lofts's avatar Andrew Lofts
Hide whitespace changes
Inline Side-by-side
essinit.md
View page @ e7b3f6a6
......@@ -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.
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.
......@@ -166,7 +166,7 @@ To tell the script where to flag, you need to give it Onevents and Offevents **O
* Config Example: A study where participants are asked to clear their mind for 5 min. The start of this task is event 11 and the end is 22. In this case Inevents would not work, as they would only gather 12 sec of the task,6 at the start and 6 at the end on either side of the start and stop events. Instead if you specify the pair ```[Onevent], 11```and ```[Offevent], 22``` that would ensure that the whole 5min is set as in task recording. Notice how 11 and 22 are a paired set. If 11 was always on but off alternated between 22 and 33, then you would specify the following in the config:```[Onevent], 11 11```and ```[Offevent], 22 33```. 11 is recorded twice but each time it has a different stop indicator. You also have to be weary about the number of events of each type you have in the file. **For every On there must be an Off**, since the marking function uses intervals.
If you do not have a prebuilt ESS and you don not fill out the config file you will prompted with the following GUI that asks for the same information.
If you do not have a prebuilt ESS and you do not fill out the config file you will prompted with the following GUI that asks for the same information.
Depending on which method you are using simply type in the event numbers separated by spaces. For example ```22 33```. If your study does not contain events that suit either of these methods you can manually add *Recording Start* and *Recording Stop* marks. To do this select the *Manual Mode* checkbox.
![events](/uploads/38fbc765ee402361dffbc6e0f34c0795/events.png)
......