|
Size: 3455
Comment:
|
Size: 3858
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| % The parameters following ### are defined once for all input files: | . % The parameters following ### are defined once for all input files: '''### #correl_type combine''' |
| Line 10: | Line 11: |
| . ### #correl_type combine + #param_file /whateverthepath/param_file.txt % file that defines predictor variables for each trigger value |
'''+ #param_file /whateverthepath/param_file.txt''' % file that defines predictor variables for each trigger value |
| Line 13: | Line 13: |
| + #correl_columns 3 4 5 6 7 8 % specifies which columns in param_file contain the predictor variables | '''+ #correl_columns 3 4 5 6 7 8 '''% specifies which columns in param_file contain the predictor variables |
| Line 15: | Line 15: |
| + #trigger_columns 2 % specifies which column in param_file.txt contains trigger value (can be more than 1 column) | '''+ #trigger_columns 2 '''% specifies which column in param_file.txt contains trigger value (can be more than 1 column) |
| Line 17: | Line 17: |
| + #info_file /whateverthepath/info_file.txt % output file for number of valid trials per input file | '''+ #info_file /whateverthepath/info_file.txt '''% output file for number of valid trials per input file |
| Line 19: | Line 19: |
| + #mag_thresholds 2500 0 1500 0 % tresholds for artefact rejection, magnetometers (fT) | '''+ #mag_thresholds 2500 0 1500 0''' % tresholds for artefact rejection, magnetometers (fT) |
| Line 21: | Line 21: |
| + #grad_thresholds 1000 0 800 0 % tresholds for artefact rejection, gradiometers (fT/cm) | '''+ #grad_thresholds 1000 0 800 0''' % tresholds for artefact rejection, gradiometers (fT/cm) |
| Line 23: | Line 23: |
| + #eog_channels 307 308 % channel number of EOG channels | '''+ #eog_channels 307 308''' % channel number of EOG channels |
| Line 25: | Line 25: |
| + #thresholds 150 0 100 0 % tresholds for artefact rejection, EOG (uV) | '''+ #thresholds 150 0 100 0''' % tresholds for artefact rejection, EOG (uV) |
| Line 27: | Line 27: |
| + #baseline -100 0 % interval for baseline correction with respect to trigger onset | '''+ #baseline -100 0 '''% interval for baseline correction with respect to trigger onset |
| Line 29: | Line 29: |
| + #epoch_length 500 % length of epoch to be analysed | '''+ #epoch_length 500''' % length of epoch to be analysed |
| Line 31: | Line 31: |
| + #pre_stim_time -100 % start latency of epoch (can be different from baseline) | '''+ #pre_stim_time -100''' % start latency of epoch (can be different from baseline) % |
| Line 35: | Line 37: |
| #fif /whateverthepath/MEG_infile.fif % input fiff-file | '''#fif /whateverthepath/MEG_infile.fif''' % input fiff-file |
| Line 37: | Line 39: |
| + #outfif /whateverthepath/MEG_outfile.fif % base for output fiff-file (there will be different files for different regressors) | '''+ #outfif /whateverthepath/MEG_outfile.fif''' % base for output fiff-file (there will be different files for different regressors) |
| Line 39: | Line 41: |
| + #fiff_template /whateverthepath/MEG_template.fif % will be used for head coordinates | '''+ #fiff_template /whateverthepath/MEG_template.fif''' % will be used for head coordinates |
| Line 41: | Line 43: |
| #fif /whateverthepath/MEG_infile2.fif % input fiff-file | % |
| Line 43: | Line 45: |
| + #outfif /whateverthepath/MEG_outfile2.fif % base for output fiff-file (there will be different files for different regressors) | % Add more files in the same way: |
| Line 45: | Line 47: |
| + #fiff_template /whateverthepath/MEG_template2.fif % will be used for head coordinates | '''#fif /whateverthepath/MEG_infile2.fif''' % input fiff-file |
| Line 47: | Line 49: |
| ||<tablewidth="904px" tableheight="442px" tablealign=""> || || ||+ #param_file /whateverthepath/param_file.txt || ||<tablewidth="438px" tableheight="102px" tablealign="">% file that defines predictor variables for each trigger value|| || || || || || || || || || || || || || || || || || || || || || || || || || || || || || || || |
'''+ #outfif /whateverthepath/MEG_outfile2.fif''' % base for output fiff-file (there will be different files for different regressors) '''+ #fiff_template /whateverthepath/MEG_template2.fif''' % will be used for head coordinates % % If you want to assign new values to the triggers in the fiff-file, add "#event_list": '''#fif /whateverthepath/MEG_infile3.fif''' % input fiff-file '''+ #outfif /whateverthepath/MEG_outfile3.fif''' % base for output fiff-file (there will be different files for different regressors) '''+ #fiff_template /whateverthepath/MEG_template3.fif''' % will be used for head coordinates '''+ #event_list /whateverthepath/events3.txt 1''' % The "1" indicates the column(s) in events3.txt that contain(s) the new trigger values. The file must contain as many values as there are triggers in the fiff-file. It will only produce a warning if this is not the case (see the log-file info_file.info_log), so be aware! |
| Line 65: | Line 69: |
| . You can also run regression analysis across multiple files, e.g. several blocks for the same subject. You can also provide an external list of trigger values. | . |
Multiple regression analysis applied to EEG and MEG data
These tools apply multiple linear regression to EEG and MEG data, in contrast to conventional factorial averaging. The input are Neuroscan cnt-files (EEG) or Neuromag fiff-files (MEG), respectively. The output are either ascii, avg (EEG) or fiff-files (MEG), which can be processes just as conventional ERP/ERFs, e.g. with respect to source analysis. These tools are still under development. If you would like more information, please contact olaf.hauk@mrc-cbu.cam.ac.uk . A different approach to regression analysis is also part of SPM5.
In order to run your analysis, you will end up with a script like the following:
- % The parameters following ### are defined once for all input files:
### #correl_type combine
+ #param_file /whateverthepath/param_file.txt % file that defines predictor variables for each trigger value
+ #correl_columns 3 4 5 6 7 8 % specifies which columns in param_file contain the predictor variables
+ #trigger_columns 2 % specifies which column in param_file.txt contains trigger value (can be more than 1 column)
+ #info_file /whateverthepath/info_file.txt % output file for number of valid trials per input file
+ #mag_thresholds 2500 0 1500 0 % tresholds for artefact rejection, magnetometers (fT)
+ #grad_thresholds 1000 0 800 0 % tresholds for artefact rejection, gradiometers (fT/cm)
+ #eog_channels 307 308 % channel number of EOG channels
+ #thresholds 150 0 100 0 % tresholds for artefact rejection, EOG (uV)
+ #baseline -100 0 % interval for baseline correction with respect to trigger onset
+ #epoch_length 500 % length of epoch to be analysed
+ #pre_stim_time -100 % start latency of epoch (can be different from baseline)
%
% The following commands are specified for individual input files:
#fif /whateverthepath/MEG_infile.fif % input fiff-file
+ #outfif /whateverthepath/MEG_outfile.fif % base for output fiff-file (there will be different files for different regressors)
+ #fiff_template /whateverthepath/MEG_template.fif % will be used for head coordinates
%
% Add more files in the same way:
#fif /whateverthepath/MEG_infile2.fif % input fiff-file
+ #outfif /whateverthepath/MEG_outfile2.fif % base for output fiff-file (there will be different files for different regressors)
+ #fiff_template /whateverthepath/MEG_template2.fif % will be used for head coordinates
%
% If you want to assign new values to the triggers in the fiff-file, add "#event_list":
#fif /whateverthepath/MEG_infile3.fif % input fiff-file
+ #outfif /whateverthepath/MEG_outfile3.fif % base for output fiff-file (there will be different files for different regressors)
+ #fiff_template /whateverthepath/MEG_template3.fif % will be used for head coordinates
+ #event_list /whateverthepath/events3.txt 1 % The "1" indicates the column(s) in events3.txt that contain(s) the new trigger values. The file must contain as many values as there are triggers in the fiff-file. It will only produce a warning if this is not the case (see the log-file info_file.info_log), so be aware!