event file and noise covariance matrix

✉️ Mailing List Archive (read-only)
1

Hi Eric,

Thank you for your response!
In fact, I input two command
--digtrig 'STI101' and --digtrig STI101
and the results have no difference.
mne_browse_raw recognized the modification since it responded,

Scanning STI101 for triggers...[done]
674 events found in /mnt/share/Huang_zhaoyang_MEG/Yang_Yingxue_MEG_data/MEG/MYB/mi_yu_bi_SEF_R_20120106_raw_tsss.fif
674 events written to /mnt/share/Huang_zhaoyang_MEG/Yang_Yingxue_MEG_data/MEG/MYB/mi_yu_bi_SEF_R_20120106_raw_tsss-eve.fif
Trigger channel : STI101 max_event : 0

When I click the average button, the response is,

single category :
  stim ignore : off
  grad reject : 2000.0 fT/cm
  mag reject : off
  EEG reject : off
  EOG reject : off
  ECG reject : off
  grad flat : off
  mag flat : off
  EEG flat : off
  EOG flat : off
  ECG flat : off
  Do not fix trigger skew
  Average to trigger # 1 :
    t = -200.0 ... 500.0 ms
    event = 1
    ignore = 0
    nave = 0

Obviously, nothing is averaged.

I load the data into matlab using the following function (in which, the stim channel was changed to 'STI101' ),

[ data, times] =mne_ex_read_raw_01('mi_yu_bi_SEF_R_20120106_raw_tsss.fif',10,20);

Then,

plot(data(307,1:1000))

got the following pictures (307 th channels in data is STI101).

The results confirm me that STI101 is the stim channels.

I also read the *-eve.fif created auto by mne_browse_raw,
the result as following,

event=mne_read_events('mi_yu_bi_SEF_R_20120106_raw_tsss-eve.fif')

event =

       12128 192 193
       12139 193 192
       12726 192 194
       12737 194 192
       13273 192 194
       13284 194 192
       13925 192 193
       13936 193 192
       14478 192 193
       14489 193 192
       15050 192 193
       15061 193 192
       15651 192 194
       15662 194 192
       16163 192 193
       16174 193 192
       16747 192 194
       16758 194 192
       17395 192 194
       17406 194 192
       17956 192 193
       17967 193 192
       18460 192 193
       18471 193 192
       19094 192 193
       19105 193 192
       19763 192 193
       19774 193 192
       20397 192 194
       20408 194 192
       20934 192 193
       20945 193 192
       21435 192 193
       21446 193 192
       22119 192 194
       22130 194 192
       22738 192 194
       22749 194 192
       23385 192 194
       23396 194 192
       23923 192 194
       23934 194 192
       24613 192 194

        ... ... ...

I guess that my raw data and --digtrig option are right.
mne_browse_raw works well with stim channel = STI 014 and may be not ready for a difference stim channels.

I also tried to change the Channel name 'STI101' to 'STI 014', but failed.

Anyone encountered the similar questions? How to correct the event recognizing problem?

Best wishes,
Junpeng

ps, the link to download the raw file,
http://share.kupan.me/download/index/?key=yLBcOrzZ42CSstiAvYHxJgTU3tL5dblMWXYKpyKtBmm3PFDkDlSmCLhGf2Ltd7fa4eUtNFXo1jsRY6cC&checkSum=6504a3f9d74441dfe848f804d72b91f0&type=1

------------------ Original ------------------

2

Jungpeng et al.

Just to clarify:

mne_browse_raw works well with other digitital trigger channels as well.
It is not necessary to enclose the channel name in quotes.
An event in mne_browse_raw/mne_process_raw is defined as a transition from value zero to something else. Such transitions do not exist in this measurement.

From the list, it looks like there is always 'offset' 192 present. This equals 128 + 64 = 192, which means that trigger lines 7 and 8 have been permanently up in your setup.
Adding --digtrigmask 63 option should help to get the actual events out.

Best,
Matti