Prerequisites. Before starting the plugin,
please load a VMR file and put all the VTC files (with their linked PRTs) in the current folder of the VMR. Please make sure
that these are linked to a protocol version with millisecond resolution: as in
a normal GLM analysis all the protocols must have the same conditions although
different timing of the trials is accepted. If you have a protocol with volume
resolution, you can open the stimulation protocol, press the "millisecond"
option and save the protocol in its millisecond version. However, in order to
achieve the maximal accuracy of the estimates, it is very important that all
the trial timings are precisely coded in msec.
To start the plugin,
simply click "BOLD Latency Mapping..." in the "Plugins" menu and follow the instructions. The plugin will first ask you, which of the three described VTC
access modes you want to use (see dialog snapshot below).
For the VOI-based modes 1 and 2, you must pre-load
a VOI file in the Region-Of-Interest dialog before starting the plugin. If you want to use a statistical map file for
selecting the voxels to include in the estimation
process, you can calculate a preliminary comprehensive GLM, apply a corrected
threshold (Bonferroni, FDR, Cluster size), overlay
the statistically significant effects of interest and, finally, convert the
resulting map (VMP) into a VTC mask; then, mode 3 must be chosen. It is also
possible to segment manually one or more region of interest using anatomical
(segmentation) or functional (e.g. from another “localizer”
experiment) criteria and use mode 2 for a direct access to the defined regions.
The progress as well as possible detected problems is normally reported in the BrainVoyager QX Log tab; you may find useful to look at the
text output written to the Log tab.
Then, one must select all the VTCs to include in the analysis. When done, a mask file is
also request only for mode 3.
Options. After loading the first VTC, the program will ask you
a series of questions. First, one must choose which condition of the attached
protocol you want to use to define the event onsets, e.g. the starting point of
the temporal window. In the "Clock Task" sample data,
this may be the "Auditory" condition as shown in the snapshot below, showing
the dialog as well as the output in the Log.
The plugin then
asks whether you want to use an interpolation factor to increase the precision
of the fit and the final resolution of the latencies. You can choose between a
factor of "2", "3", or "4" to upsample
the data. If you do not want to use interpolation of the data, enter
"1" (default).
The program then asks for the size of the
time window to be considered for parameter estimation from the onset of each
event (as defined in the protocol). The default guess is "16000"
milliseconds. For short events (shorter then about 3 seconds), this default window
size should be appropriate, but different choices can be appropriate to study
different aspects of the BOLD respone.
The plugin then
asks whether you want to do a single-trial analysis or whether the parameter
estimation should be based on the averaged trial responses only. It is
recommended to first use the averaged responses and to switch to the
single-trial level in a second run of the plugin. In
single-trial mode, the computation time will be considerably higher, but it will
be possible to specify an “alpha” level for displaying a confidence
interval for the average latencies from all single trials (e.g. 0.05 will give
the confidence interval for single-trial based latency at 5%).
It is possible to explicitly require or not a
final return-to-baseline of the responses. If yes, a signal fit is accepted
(and the corresponding latency) only when a complete return to baseline of the
response is detected. If not, any signal behavior is accepted after the onset
of the response. In this case the resulting estimate will be optimized with
respect to the onset latency but the offset of the response is not constrained
anymore with the consequence that the duration latency cannot be used (i.e.
signal does not reach a final “rest” baseline and a duration of the
response cannot be reliably estimated). The use of the “flexible”
version of the fitting procedure allows using short temporal windows wich automatically focuse on
specific temporal components of the BOLD responses (see background document).
Finally the program asks you for the name of
the resulting "BLM" file.
Results. The resulting "BLM" maps can be loaded by
using the "Overlay BOLD Latency Maps" dialog, which can be invoked by
clicking the "Overlay BOLD Latency Maps..." in the "Plugins" menu.
The snapshot below shows the dialog after
loading a resulting BLM file using the "Load .BLM..." button. You may
select one of the four maps, "Onset", "Duration",
"Time-to-peak" and "Amplitude". The first three parameters
are provided in seconds (from the synchronizing event in the protocol) while
the fourth parameter is provided in percent signal change (PSC) units. Note
that the colors in an overlaid map (see right side in snapshot) reflect the
respective units, which are internally stored as pseudo t maps.
Note that results do not only appear as 3D
parameter maps but also in numerical form in the Log of BrainVoyager
QX. The output in the Log is especially important in case that the first mode (VOI-based
estimation) is used since then the estimates for each VOI are provided as shown
on the left side in the snapshot below.
In VOI-based estimation mode 1, there will be
also DAT files available for inspection of the time courses. After invoking the
event-related averaging plot from a standard AVG file, you may load the
averaged event-related time courses and the corresponding trapezoidal fits by
clicking in the AVG dialg and using the "Load
data..." and "Add data..." buttons. In mode 1, the program
always generates DAT files with the average trial responses and their fits but
when single-trial analysis is specified, a TXT file with the estimated
single-trial latencies is provided as well for performing statistics on the
latencies outside Brain Voyager QX. It is possible to load one or more of these
DAT files using the event-related average plot dialog, which pops up when
displaying event-related average (AVG) data in BrainVoyager
QX. Note that the saved DAT files contain the resampled
and possibly interpolated signals, which can be superimposed to each other but
not to the current AVG data because of possible differences in the time
resolution of data points. Finally, in single-trial mode, all the signle trial responses together with their fits are
provided in separate TXT files for all the separate VTCs.