Back to the main page.
Bug 1810 - test_ft_timelockanalysis fails
| Status | CLOSED FIXED |
| Reported | 2012-11-06 14:16:00 +0100 |
| Modified | 2019-08-10 11:55:50 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P3 normal |
| Assigned to: | Arjen Stolk |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Arjen Stolk - 2012-11-06 14:16:22 +0100
An initial check reveals a mismatch between the output from timelockanalysis on stored raw data, and the stored (already) timelocked data.
Arjen Stolk - 2012-11-06 14:31:01 +0100
In one particular case (k=6), it pertains to a mismatch between the grad.chanunit fields of a bti148 MEG dataset. i.e. data.grad.chanunit contains 'unknown's whereas datanew.grad.chanunit contains 'T's In another case (k=7), there's an additional field in datanew, namely 'type' (= 'bti248'). Also here a similar mismatch between the chanunit fields is present. Additionally, the chanpos fields are dissimilar. In summary, it seems test datasets get outdated due to newer implementations of functions. This needs decision on a general strategy as similar problems have been reported for other functionalities (e.g. test_ft_componentanalysis?)
Arjen Stolk - 2012-12-05 15:30:03 +0100
fixed, presumably since the recent bugbinge (nov 2012) when all 'template' files in testdata were updated.
Robert Oostenveld - 2019-08-10 11:51:54 +0200
This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue describing the issue on https://github.com/fieldtrip/fieldtrip/issues.