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 play blocks of motion/static sounds. Motion blocks will play sounds moving in one of four directions (up-, down-, left-, and right-ward)
60
-
61
-
By default it is run in `Debug mode` meaning that it does not care about subjID, run n., fMRI triggers, Eye Tracker, etc..
62
-
63
-
Any details of the experiment can be changed in `setParameters.m` (e.g., experiment mode, motion stimuli details, exp. design, etc.)
64
-
65
-
### 3.2. <aname='setParameters'></a>setParameters
66
-
67
-
`setParameters.m` is the core engine of the experiment. It contains the following tweakable sections:
68
-
69
-
- Debug mode setting
70
-
- Engine parameters:
71
-
- Devices parameters
72
-
- Monitor parameters
73
-
- Keyboard parameters
74
-
- MRI parameters
75
-
- Experiment Design
76
-
- Timing
77
-
- Auditory Stimulation
78
-
- Task(s)
79
-
- Instructions
80
-
- Task #1 parameters
81
-
82
-
#### Let the scanner pace the experiment
83
-
84
-
Set `cfg.pacedByTriggers.do` to `true` and you can then set all the details in this `if` block
85
-
86
-
```matlab
87
-
% Time is here in in terms of number repetition time (i.e MRI volumes)
88
-
if cfg.pacedByTriggers.do
89
-
90
-
cfg.pacedByTriggers.quietMode = true;
91
-
cfg.pacedByTriggers.nbTriggers = 1;
92
-
93
-
cfg.timing.eventDuration = cfg.mri.repetitionTime / 2 - 0.04; % second
94
-
95
-
% Time between blocs in secs
96
-
cfg.timing.IBI = 0;
97
-
% Time between events in secs
98
-
cfg.timing.ISI = 0;
99
-
% Number of seconds before the motion stimuli are presented
100
-
cfg.timing.onsetDelay = 0;
101
-
% Number of seconds after the end all the stimuli before ending the run
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 a possible design.
110
-
111
-
#### 3.3.1. <aname='EVENTS'></a>EVENTS
112
-
113
-
The `numEventsPerBlock` should be a multiple of the number of "base" listed in the `motionDirections` and `staticDirections` (4 at the moment).
114
-
115
-
#### 3.3.2. <aname='TARGETS:'></a>TARGETS:
116
-
117
-
- If there are 2 targets per block we make sure that they are at least 2 events apart.
118
-
- Targets cannot be on the first or last event of a block
119
-
120
-
#### 3.3.3. <aname='Input:'></a>Input:
121
-
122
-
-`expParameters`: parameters returned by `setParameters`
123
-
-`displayFigs`: a boolean to decide whether to show the basic design matrix of the design
124
-
125
-
#### 3.3.4. <aname='Output:'></a>Output:
126
-
127
-
-`expParameters.designBlockNames` is a cell array `(nr_blocks, 1)` with the name for each block
128
-
-`expParameters.designDirections` is an array `(nr_blocks, numEventsPerBlock)` with the direction to present in a given block
129
-
-`0 90 180 270` indicate the angle
130
-
-`-1` indicates static
131
-
-`expParameters.designSpeeds` is an array `(nr_blocks, numEventsPerBlock) * speedEvent`
132
-
-`expParameters.designFixationTargets` is an array `(nr_blocks, numEventsPerBlock)` showing for each event if it should be accompanied by a target
133
-
134
-
135
-
136
54
## Contributors ✨
137
55
138
-
Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):
0 commit comments