Back to the main page.
Bug 420 - please address the issues below
| Status | CLOSED FIXED |
| Reported | 2011-01-20 11:24:00 +0100 |
| Modified | 2011-02-23 13:50:58 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Mac OS |
| Importance: | P1 normal |
| Assigned to: | Cristiano Micheli |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Jan-Mathijs Schoffelen - 2011-01-20 11:24:04 +0100
@Ana & Cristiano: please team up and address these issues: Dear fieldtrip community, there seems to be a slight inconsistency in the tutorial section on artifact removal (which I otherwise like a lot because it calrifies a lot of the 'black-boxiness' of these particular fieldtrip functions (thanks a lot). The part I am referring to is in the jump removal section. It starts with the lines: % jump cfg = []; if isfield(cfg, 'padding') && cfg.padding~=0 padding = cfg.padding; else padding = 0; end Deal Fieldtrip users, there is something else I do not understand in the tutorial: if you read in the data in trials (as it is done) how can you do padding later as it is suggested. I tried to run the example code on teh website reading in the data such that it contains trials. If I then try to search for muscle artifacts I get the 'subscript indices must be positive or logical ... values', indicating that the code tries to access data that aren't there. If I set the padding to zero (instead of 0.1) it works. So I am wondering wether somehow one should actually run these things on continuous data (contrary to what is indicated in the tutorial)? Thanks