Back to the main page.
Bug 1541 - neighbourselection is slow when providing data as input
| Status | CLOSED DUPLICATE |
| Reported | 2012-06-20 13:46:00 +0200 |
| Modified | 2019-08-10 11:55:52 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P3 normal |
| Assigned to: | |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Jörn M. Horschig - 2012-06-20 13:46:19 +0200
the reason for this is that neighbourselection then only subselects channels/neighbours that actually are in the data (I implemented this after request by Stephen with a stimple&stupid for loop). Some people are annoyed by this slowness - should this be changed?
Jörn M. Horschig - 2012-06-20 15:39:52 +0200
. *** This bug has been marked as a duplicate of bug 1462 ***
Robert Oostenveld - 2019-08-10 11:51:55 +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.