Back to the main page.
Bug 1256 - because of caching of data and header information wrong data can be read
| Status | CLOSED DUPLICATE |
| Reported | 2012-01-13 11:28:00 +0100 |
| Modified | 2019-08-10 11:55:53 +0200 |
| Product: | FieldTrip |
| Component: | fileio |
| Version: | unspecified |
| Hardware: | All |
| Operating System: | All |
| Importance: | P3 enhancement |
| Assigned to: | |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Marianne Severens - 2012-01-13 11:28:37 +0100
There is a bug in the way the caching of the header info for the biosig data is done in read_biosig_data (in the private folder of the fileio), which can cause wrong data to be read without you knowing it when you read several data files after each other. I think the problem is dir(filename) in line 35 and 43, because this gives an emty structure (on windows and mac). To quickly fix the problem I have removed the dir and just use filename instead. But I'm not sure this solution works in all cases.
Marianne Severens - 2012-02-16 14:30:35 +0100
I've looked a bit deeper into the bug and found out that it happens because I use a filename only (so not with the full directory before it). I now see in the help of the definetrial that you should specifiy the full directory. (I always added the path of the file) So the problem will not happpen to people who read the help functions very good ;), but maybe it is good to build a check around the input of the filename, so this will not happen to anyone else! Sorry for bothering you with my stupid mistakes!
Boris Reuderink - 2012-03-21 15:29:24 +0100
Thank you Marianne for reporting this issue. Although it maybe is not a bug, it is a usability problem that we should think about.
Roemer van der Meij - 2012-05-16 13:18:22 +0200
basic problem is related to bug 1471 *** This bug has been marked as a duplicate of bug 1471 ***
Robert Oostenveld - 2019-08-10 11:51:57 +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.