You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running this script will show blocks of motion dots (soon also moving gratings) and static dots. Motion blocks will show dots(/gratings) moving in one of four directions (up-, down-, left-, and right-ward)
59
62
60
63
By default it is run in `Debug mode` meaning that it does not run care about subjID, run n., fMRI triggers, Eye Tracker, etc..
61
64
62
65
Any details of the experiment can be changed in `setParameters.m` (e.g., experiment mode, motion stimuli details, exp. design, etc.)
63
66
64
-
### 3.2. <aname='setParameters'></a>setParameters
67
+
### 3.2. <aname='setParameters'></a>setParameters
65
68
66
69
`setParameters.m` is the core engine of the experiment. It contains the following tweakable sections:
67
70
@@ -77,38 +80,44 @@ Any details of the experiment can be changed in `setParameters.m` (e.g., experim
-`cfg`: PTB/machine configurations returned by `setParameters` and `initPTB`
84
88
-`expParameters`: parameters returned by `setParameters`
85
89
-`logFile`: structure that stores the experiment logfile to be saved
86
90
87
-
#### 3.3.2. <aname='Output:'></a>Output:
91
+
#### 3.3.2. <aname='Output:'></a>Output:
92
+
88
93
- Event `onset`
89
94
- Event `duration`
90
95
91
96
The dots are drawn on a square that contains the round aperture, then any dots outside of the aperture is turned into a NaN so effectively the actual number of dots on the screen at any given time is not the one that you input but a smaller number (nDots / Area of aperture) on average.
Creates the sequence of blocks and the events in them. The conditions are consecutive static and motion blocks (Gives better results than randomised). It can be run as a stand alone without inputs to display a visual example of possible design.
95
101
96
-
#### 3.4.1. <aname='EVENTS'></a>EVENTS
102
+
#### 3.4.1. <aname='EVENTS'></a>EVENTS
103
+
97
104
The `numEventsPerBlock` should be a multiple of the number of "base" listed in the `motionDirections` and `staticDirections` (4 at the moment).
98
105
99
-
#### 3.4.2. <aname='TARGETS:'></a>TARGETS:
106
+
#### 3.4.2. <aname='TARGETS:'></a>TARGETS:
107
+
100
108
- If there are 2 targets per block we make sure that they are at least 2 events apart.
101
109
- Targets cannot be on the first or last event of a block
102
110
103
-
#### 3.4.3. <aname='Input:-1'></a>Input:
111
+
#### 3.4.3. <aname='Input:-1'></a>Input:
112
+
104
113
-`expParameters`: parameters returned by `setParameters`
105
114
-`displayFigs`: a boolean to decide whether to show the basic design matrix of the design
106
115
107
-
#### 3.4.4. <aname='Output:-1'></a>Output:
116
+
#### 3.4.4. <aname='Output:-1'></a>Output:
117
+
108
118
-`expParameters.designBlockNames` is a cell array `(nr_blocks, 1)` with the name for each block
109
119
-`expParameters.designDirections` is an array `(nr_blocks, numEventsPerBlock)` with the direction to present in a given block
110
120
-`0 90 180 270` indicate the angle
111
121
-`-1` indicates static
112
122
-`expParameters.designSpeeds` is an array `(nr_blocks, numEventsPerBlock) * speedEvent`
113
123
-`expParameters.designFixationTargets` is an array `(nr_blocks, numEventsPerBlock)` showing for each event if it should be accompanied by a target
0 commit comments