Back to the main page.

Bug 3182 - check averaging and keeptrials in freqanalysis+freqdescriptives

Status CLOSED INVALID
Reported 2016-09-14 15:46:00 +0200
Modified 2019-08-10 12:33:26 +0200
Product: FieldTrip
Component: core
Version: unspecified
Hardware: PC
Operating System: Mac OS
Importance: P5 normal
Assigned to:
URL:
Tags:
Depends on:
Blocks:
See also:

Robert Oostenveld - 2016-09-14 15:46:57 +0200

Cecilia reported this by email: I am doing a frequency analysis (induced gamma activity) on MEG data and I was wondering whether it makes a difference to select cfg. keeptrials = 'yes' in the analysis. What I thought is that keeping the trials in ft_freqanalysis and then averaging using ft_freqdescriptives would lead to the same result as using cfg.keeptrials= 'no'. Am I correct? I am getting quite different TFRs representation actually, especially in the baseline. (by using cfg.keeptrials='no' , TFRs are somewhat "cleaner")..


Robert Oostenveld - 2016-09-14 15:49:02 +0200

(In reply to Robert Oostenveld from comment #0) I suspect it is due to her plotting it differently, and/or baseline correcting it differently. But let's check to be suyre


Robert Oostenveld - 2016-09-14 16:05:41 +0200

I tested it, there is no difference between keeptrials=yes or no. ip-145-116-189-182> git commit test_bug3182.m [master 40a3b1a] ENH - added test script for http://bugzilla.fieldtriptoolbox.org/show_bug.cgi?id=3182, no problem detected 1 file changed, 44 insertions(+) create mode 100644 test/test_bug3182.m ip-145-116-189-182> git push Counting objects: 8, done. Delta compression using up to 4 threads. Compressing objects: 100% (8/8), done. Writing objects: 100% (8/8), 1.17 KiB | 0 bytes/s, done. Total 8 (delta 5), reused 0 (delta 0) remote: Resolving deltas: 100% (5/5), completed with 3 local objects. To git@github.com:robertoostenveld/fieldtrip.git fd92fd2..40a3b1a master -> master


Robert Oostenveld - 2019-08-10 12:33:26 +0200

This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue on https://github.com/fieldtrip/fieldtrip/issues.