Back to the main page.
Bug 1878 - ft_artifact_clip returns a different number of artifacts
| Status | CLOSED FIXED |
| Reported | 2012-12-10 15:11:00 +0100 |
| Modified | 2012-12-31 11:46:27 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Mac OS |
| Importance: | P3 normal |
| Assigned to: | Robert Oostenveld |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Robert Oostenveld - 2012-12-10 15:11:13 +0100
I am processing a HCP dataset in which a lot of clipping artifacts seem to be present, whereas the same dataset in the past did not have any clipping artifacts. I will provide a test script and data.
Robert Oostenveld - 2012-12-10 16:02:09 +0100
I traced it down to the change of the parameters. The cfg I was using in my older script contains cfg.continuous = 'no'; cfg.trl = [ 1 203452 0 ]; cfg.artfctdef.clip.pretim = 0.01; cfg.artfctdef.clip.psttim = 0.01; cfg.artfctdef.clip.thresh = 0.05; <======= cfg.artfctdef.muscle.cutoff = 20; cfg.artfctdef.muscle.trlpadding = 0; cfg.artfctdef.muscle.fltpadding = 0; cfg.artfctdef.muscle.artpadding = 0.01; The thresh option was changed by Diego into timethreshold, but without providing backward compatibility for the end user. So my non-default value of 0.050 was not being used, but rather the default 0.010. I will add a call to ft_checkconfig to fix it. Consequently something like the following should be printed. Warning: use cfg.timethreshold instead of cfg.thresh > In ft_checkconfig at 121 In ft_artifact_clip at 73
Robert Oostenveld - 2012-12-10 16:22:12 +0100
roboos@mentat001> svn commit test/test_bug1878.m ft_artifact_clip.m utilities/ Sending ft_artifact_clip.m Adding test/test_bug1878.m Sending utilities/ft_checkconfig.m Transmitting file data ... Committed revision 7130.