Back to the main page.
Bug 370 - private/prepare_time_freq_data calls fixdimord
| Status | CLOSED WONTFIX |
| Reported | 2011-01-06 15:26:00 +0100 |
| Modified | 2011-01-26 15:42:15 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Mac OS |
| Importance: | P1 normal |
| Assigned to: | Robert Oostenveld |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Robert Oostenveld - 2011-01-06 15:26:06 +0100
private/prepare_time_freq_data calls fixdimord, whereas the dimord should now be fixed in ft_checkdata. todo - remove the call to fixdimord - remove the fixdimord from fieldtrip/private (*) *) there are two, one in private and the other in public/private -> check which one is the external and first remove the external, svn commit, and then (if needed) move the actual original file to the correct place (and commit)
Robert Oostenveld - 2011-01-25 23:51:16 +0100
changed multiple bugs to ASSIGNED to roboos
Robert Oostenveld - 2011-01-26 12:58:33 +0100
I looked at it, but the functions at t he higher level don't solve it at the moment manzana> vi ft_timelockstatistics.m % % check if the input data is valid for this function % for i=1:length(varargin) % % FIXME at this moment (=10 May) this does not work, because the input might not always have an avg % % See freqstatistics % %varargin{i} = ft_checkdata(varargin{i}, 'datatype', 'timelock', 'feedback', 'no'); % end manzana> vi ft_freqstatistics.m % check if the input data is valid for this function for i=1:length(varargin) % FIXME at this moment (=2 April) this does not work, because the input might not always have a powspctrm o.i.d. % See email from Juriaan % varargin{i} = ft_checkdata(varargin{i}, 'datatype', 'freq', 'feedback', 'no'); end The solution is to redesign the data selection alltogether
Robert Oostenveld - 2011-01-26 15:41:05 +0100
I closed all the bugs that I resolved earlier today. These have been discussed at the Fieldtrip meeting and should not show up any more at the next meeting. If you feel that one of these bugs should not have been closed, you have to reopen it.