Back to the main page.
Bug 2520 - ft_checkdata fails on componentanalyzed timelock data
| Status | CLOSED DUPLICATE |
| Reported | 2014-04-02 21:44:00 +0200 |
| Modified | 2019-08-10 12:28:47 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Mac OS |
| Importance: | P5 minor |
| Assigned to: | |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | 2518 |
| See also: |
Robert Oostenveld - 2014-04-02 21:44:21 +0200
I noticed this problem while working on bug 2518, and specifically on testing whether topo and topolabel are correctly passed along (i.e. test_bug2518a). You can reproduce it with: ft_preprocessing ft_componentanalysis ft_timelockanalysis % this results in timelock.com ft_checkdata % here it gets confused
Robert Oostenveld - 2014-04-02 22:03:11 +0200
I guess that this could block ft_dipolefitting and ft_sourceanalyssis, especially if these functions use the desired "standard" way of checking the data at the start.
Robert Oostenveld - 2014-04-16 17:23:03 +0200
something similar was reported by Rene, with more details and a piece of test data. I resolved it in that contact. See bug 2539. *** This bug has been marked as a duplicate of bug 2539 ***