Back to the main page.
Bug 94 - cfg.outputfile is incompatible with cfg.trackconfig=cleanup
| Status | CLOSED FIXED |
| Reported | 2010-06-21 14:47:00 +0200 |
| Modified | 2011-01-26 15:38:33 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Mac OS |
| Importance: | P5 normal |
| Assigned to: | Tim Engelkes |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Robert Oostenveld - 2010-06-21 14:47:28 +0200
the option cfg.trackconfig=cleanup results in checkconfig removing all unused cfg fields. At the end of some functions the cfg.outputfile has to be written, but that happens after the unused cfg.outputfile has been removed. The consequence is an error ;-( ------------- >> ft_default ft_default = trackconfig: 'cleanup' checkconfig: 'silent' checksize: 100000 ------------- ??? Reference to non-existent field 'outputfile'. Error in ==> ft_timelockanalysis at 514 if ~isempty(cfg.outputfile) Error in ==> timelockanalysis at 17 [varargout{1:nargout}] = funhandle(varargin{:}); To get this to work, the following has to be added to all relevant functions prior to calling checkconfig for the last time. % accessing this field here is needed for the configuration tracking % by accessing it once, it will not be removed from the output cfg cfg.outputfile; Compare ft_preprocessing line 505 and further...
Robert Oostenveld - 2011-01-26 15:37:13 +0100
I closed all bugs that were resolved prior and including 2011-01-25. All resolved bugs should have been discussed by now, therefore we don't want to see them again in the next meeting. Instead, in the next meeting we want to see the recent improvements and fixes.