... | ... | @@ -148,13 +148,13 @@ Depending on which method you are using simply type in the event numbers separat |
|
|
|
|
|
![events](/uploads/38fbc765ee402361dffbc6e0f34c0795/events.png)
|
|
|
|
|
|
If you selected *Manual Mode* then this little GUI will pop up. This GUI simply warns you that you are entering the Vised-Marks editor and that any annotations you use will be added to the marks structure. The two commands you will be using are:
|
|
|
If you selected *Manual Mode* then this little GUI will pop up. This GUI simply warns you that you are entering the Vised-Marks editor and that any annotations you add here will be added to the marks structure permanently. The two commands you will be using are:
|
|
|
* ```a``` to drop a RecStart event at your cursor
|
|
|
* ```b``` to drop a RecStop event at your cursor
|
|
|
See the example below where we placed events before and after each block of tasks.
|
|
|
![events2](/uploads/ed4a00ef37fd4d59ed7a979d5f7078c3/events2.png)
|
|
|
![vised3](/uploads/fcc6034816cd3f29dc38781760c4ea8f/vised3.png)
|
|
|
After you click *Update Marks Structure* the events that you dropped into the data will be saved into the events information structure. Vised Marks will then proceed to place *Out of task Marks* everywhere outside your boundaries. Below is a example of what the final result will look like if you were to plot the data afterwards.
|
|
|
After you click *Update Marks Structure* the events that you dropped into the data will be saved into the events information structure. Vised Marks will then proceed to place *Out of task Marks* everywhere outside your boundaries. Below is a example of what the final result will look like if you were to plot the data afterwards, note that below we plotted the whole file at once so you could get a birds eye view.
|
|
|
![events5](/uploads/8e0c5b4c3044b2c85479bfe184a4f9a4/events5.png)
|
|
|
|
|
|
These methods may seem like a lot of work but they can easily be simplified by using the events that already exist in the experiment. For the example above if we used Inevents we could have listed all of the event types in the experiment in the config file. We would get the same result as there were no events during the break times. That method would have run automatically and would have saved bunch of time. Consider your experiment when choosing a marking method.
|
... | ... | |