[FieldTrip] Different cfg.poststim values in ft_preprocessing alters signal
Barnett, Benjy
benjy.barnett.20 at ucl.ac.uk
Wed Feb 3 18:30:14 CET 2021
Hey Stephen,
Thanks for your help! Whilst this certainly answers my question about the slight difference between different trial lengths, the huge spikes at the beginning of trials remains regardless of whether I filter the data as a whole first, or if I segment into trials and then filter. Here’s my code for doing the filtering first (my code for the alternative way is in my initial post):
cfg = [];
cfg.dataset = full_path;
cfg.continuous = 'yes';
%cfg.demean = 'yes';
%cfg.baselinewindow = baselinewindow;
cfg.lpfilter = 'no';
cfg.hpfilter = 'no';
cfg.dftfilter = 'yes';
data = ft_preprocessing(cfg);
cfg=[];
cfg.dataset=full_path;
cfg.trialdef.prestim=0.175;
cfg.trialdef.poststim=0.600;
cfg.trialdef.eventvalue=[6 7];
cfg.trialdef.eventtype='STI101';
cfg = ft_definetrial(cfg);
trl = cfg.trl(:,1:3);
cfg = [];
cfg.trl = trl;
data_segmented = ft_redefinetrial(cfg,data);
cfg = [];
cfg.resamplefs = 250;
data_ds = ft_resampledata(cfg, data_segmented);
cfg = [];
cfg.channel = 'MEGGRAD';
cfg.keeptrials = 'yes';
data_TL = ft_timelockanalysis(cfg,data_ds);
plot(data_TL.time,squeeze(mean(data_TL.trial(:,39,:),1))) %17, 23 and 39 are examples of spikes in channels
[cid:81B23B81-2E1C-4A5E-939F-6E3343FC4409 at home][cid:C209709C-82A9-454F-B83C-EE4534E79468 at home]
I’m still seeing spikes as in the images attached. Something else strange: when I change the poststim parameter to 0.075 instead of 0.175 (keeping everything else equal), the direction of the spike completely switches (see third image attached). This happens regardless or ft_definetrial/preprocessing order. Moreover, when I look at the signal across the single trial encapsulating all the data (i.e. before segmentation), there are none of these huge spikes where every event would be, only a few spikes that I assume are SQUID jumps.
[cid:D20BCD8D-EAA8-4B7A-8B4C-BE46A7FBE18D at home][cid:6115EB0D-6852-47F1-849B-CBE23A57FEE5 at home]
This makes me think the issue is coming at the ft_definetrial() step. But since this does not read in the actual MEG data, I can’t work out what is causing this effect, it certainly doesn’t seem to be an issue with my data. I’ve added a couple of lines to the ft_trialfun_general function, so to be sure I’ve removed them and am just using the default version yet the problem is persisting.
Any assistance is of course greatly appreciated. Thanks!
Benjy
On Feb 2, 2021, at 4:14 PM, Stephen Whitmarsh <stephen.whitmarsh at gmail.com<mailto:stephen.whitmarsh at gmail.com>> wrote:
Hey Benjy,
I would suspect this has to do with your (dft) filtering, which depends on the amount of data, and perhaps some small numerical differences due to resampling. Strange jumps at onset/offset of data segments also often indicate something to do with filtering.
To avoid this, and to create a fair comparison between your different trial duration segmentation, I would do the following:
- preprocess all your data as one long 'trial'. I.e. without segmentation. Do all your filtering at this step, i.e. at one go over all your data. This gives you the maximum frequency resolution & ability to filter low frequencies.
- segment your filtered data into trials using ft_redefinetrial.
- do your resampling
- check the different triallengths.
If anything stays slightly different, I would imagine it has to do with the resampling, because samples will end up slightly different on your axis, creating numerical differences. You could resample before segmenting, which would be more efficient, but then you'll have to deal with changing timing of your markers which would still be in the original samplerate. Dealing with time-axis and samples is a pain so personally I therefore always let FT deal with the resampling after trial segmentation.
Have fun,
Stephen
Op di 2 feb. 2021 om 16:36 schreef Barnett, Benjy <benjy.barnett.20 at ucl.ac.uk<mailto:benjy.barnett.20 at ucl.ac.uk>>:
Hey. When I am preprocessing my MEG neuromag data, I’m noticing that the signal of my channels are altered depending on how long after the stimulus I include in the trial, even in the portion of the trial that is overlapping between the two cases. For instance, if I use cfg.poststim = 2.5 in one run and cfg.poststim = 0.6 in a second, the two signals are not identical up until 0.6 seconds. Please see my code and attached plots of a Grad sensor in these two cases up to 0.6 seconds.
% define trials
cfg = [];
cfg.dataset = full_path;
cfg.trialdef.prestim = 0.175;
cfg.trialdef.poststim = 0.6; % compare with 2.5 seconds
cfg.trialdef.eventvalue = [6 7 9];
cfg.trialdef.eventtype = 'STI101';
cfg = ft_definetrial(cfg);
% preprocess
cfg.demean = 'yes';
cfg.baselinewindow = [-0.175 0.025];
cfg.lpfilter = 'no';
cfg.hpfilter = 'no';
cfg.dftfilter = 'yes';
split_files{1} = ft_preprocessing(cfg); %preprocess
%%%%%%%%%%%Downsampling%%%%%%%%%
cfg = [];
cfg.resamplefs = 250;
data = ft_resampledata(cfg, split_files{1});
%%Visualisation
cfg = [];
cfg.channel = 'MEGGRAD';
cfg.keeptrials = 'yes';
data = ft_timelockanalysis(cfg,data);
Xlim([-0.2 0.6])
plot(data.time,squeeze(mean(data.trial(:,39,:),1)))
As you can see from the plots attached, these signals are not identical when they should be (shouldn’t they?). The first plot is when I Use 2.5 seconds post stim and the second is using 0.6. I’ve altered the xlim to show only up to 600ms on both. Also, can anyone explain these huge spikes at the beginning of trials, that’s my next problem to solve.
Thanks
<2_5_ch39_full.png><600_ch39_full.png>
_______________________________________________
fieldtrip mailing list
https://mailman.science.ru.nl/mailman/listinfo/fieldtrip<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.science.ru.nl%2Fmailman%2Flistinfo%2Ffieldtrip&data=04%7C01%7C%7Cd5bce0b0bd7d42360fe308d8c798fa4e%7C1faf88fea9984c5b93c9210a11d9a5c2%7C0%7C0%7C637478807143731653%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FF%2FVokvcknAhcAfE3jyxVVZtY7kWUOQlmWlySFw12Rs%3D&reserved=0>
https://doi.org/10.1371/journal.pcbi.1002202<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoi.org%2F10.1371%2Fjournal.pcbi.1002202&data=04%7C01%7C%7Cd5bce0b0bd7d42360fe308d8c798fa4e%7C1faf88fea9984c5b93c9210a11d9a5c2%7C0%7C0%7C637478807143731653%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=P1qCeEY18OkQ8BJZ8yY4LX56%2Brg19SUOHOrPq%2BaAxlM%3D&reserved=0>
_______________________________________________
fieldtrip mailing list
https://mailman.science.ru.nl/mailman/listinfo/fieldtrip
https://doi.org/10.1371/journal.pcbi.1002202
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.science.ru.nl/pipermail/fieldtrip/attachments/20210203/d44cc39e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-1.png
Type: image/png
Size: 41121 bytes
Desc: PastedGraphic-1.png
URL: <http://mailman.science.ru.nl/pipermail/fieldtrip/attachments/20210203/d44cc39e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-2.png
Type: image/png
Size: 24951 bytes
Desc: PastedGraphic-2.png
URL: <http://mailman.science.ru.nl/pipermail/fieldtrip/attachments/20210203/d44cc39e/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot 2021-02-03 at 11.29.20 AM.png
Type: image/png
Size: 17444 bytes
Desc: Screenshot 2021-02-03 at 11.29.20 AM.png
URL: <http://mailman.science.ru.nl/pipermail/fieldtrip/attachments/20210203/d44cc39e/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: long_trial_single_channel.png
Type: image/png
Size: 28428 bytes
Desc: long_trial_single_channel.png
URL: <http://mailman.science.ru.nl/pipermail/fieldtrip/attachments/20210203/d44cc39e/attachment-0003.png>
More information about the fieldtrip
mailing list