Back to the main page.
Bug 2950 - ft_rejectvisual returns wrong sampleinfo for rejected trials on concatenated data
| Status | CLOSED WONTFIX |
| Reported | 2015-08-26 12:34:00 +0200 |
| Modified | 2019-08-10 12:41:44 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Linux |
| Importance: | P5 trivial |
| Assigned to: | |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Ana Todorovic - 2015-08-26 12:34:39 +0200
Greetings, 'trippers! Would it be possible to have ft_rejectvisual return trial numbers instead of sample numbers, for rejected trials? Fieldtrip gives back the sampleinfo for these trials, but I ran into a problem when trying to work out the correct trial numbers from this information. Namely, my dataset is a concatenation of several recordings, where the sampleinfo doesn't always grow in numbers from trial to trial (every added dataset starts from zero) - and for some reason the samples of the rejected trials didn't align well with the sampleinfo in the concatenated dataset. It worked well for early, but not late trials. There is already a variable in the ft_rejectvisual script called 'removed' that contains the information on rejected trial numbers. I fished it out on my local copy of fieldtrip, so it should be fairly easy to implement as the default. In the case of my data this information was accurate.
Jan-Mathijs Schoffelen - 2017-01-17 12:22:40 +0100
It's unclear what the status of this one is, but given the fact that we're severely underpowered in terms of people contributing to fixing issues on bugzilla, Robert and JM have decided to close the low-priority bugs for now. This in order to keep the number of open bugs manageable. Feel free to reopen it, if you are willing to move this one forward towards a more proper resolution.
Robert Oostenveld - 2019-08-10 12:35:30 +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 on https://github.com/fieldtrip/fieldtrip/issues.