Read evoked dataset(s).
The filename, which should end with
The index or list of indices of the evoked dataset to read. FIF files can contain multiple datasets. If None, all datasets are returned as a list.
tupleof length 2
The time interval to consider as “baseline” when applying baseline
None, do not apply baseline correction.
If a tuple
(a, b), the interval is between
(in seconds), including the endpoints.
None, the beginning of the data is used; and if
None, it is set to the end of the interval.
(None, None), the entire time interval is used.
(a, b) includes both endpoints, i.e. all
t such that
a <= t <= b.
Correction is applied to each channel individually in the following way:
Calculate the mean signal of the baseline period.
Subtract this mean from the entire
None (default), do not apply baseline correction.
Note that if the read
Evoked objects have already
been baseline-corrected, the data retrieved from disk will
always be baseline-corrected (in fact, only the
baseline-corrected version of the data will be saved, so
there is no way to undo this procedure). Only after the
data has been loaded, a custom (additional) baseline
correction may be optionally applied by passing a tuple
None will not remove an existing
baseline correction, but merely omit the optional, additional
Either ‘average’ or ‘standard_error’, the type of data to read.
If False, available projectors won’t be applied to the data.
If True, allow loading of data that has been recorded with internal active compensation (MaxShield). Data recorded with MaxShield should generally not be loaded directly, but should first be processed using SSS/tSSS to remove the compensation signals that may also affect brain activity. Can also be “yes” to load without eliciting a warning.
Changed in version 0.23: If the read
Evoked objects had been baseline-corrected before
saving, this will be reflected in their
baseline attribute after