Back to the main page.
Bug 1700 - update the readers in the external/besa directory
Status | CLOSED FIXED |
Reported | 2012-09-05 15:01:00 +0200 |
Modified | 2019-08-10 11:55:41 +0200 |
Product: | FieldTrip |
Component: | external_besa |
Version: | unspecified |
Hardware: | PC |
Operating System: | Mac OS |
Importance: | P3 normal |
Assigned to: | Todor Jordanov |
URL: | |
Tags: | |
Depends on: | |
Blocks: | |
See also: |
Robert Oostenveld - 2012-09-05 15:01:17 +0200
Todor wrote: As promised here are the two new Matlab readers: readBESAfmp.m and readBESAtfcs.m The first one reads FFT-power exported from BESA and the second one reads single trial time-frequency data exported from BESA. There are also two example files if you want to try the readers. As I mentioned there are also two new export functions which allow to Matlab users to export data in ascii format compatible with BESA: besa_save2Avr.m and besa_save2Swf.m The first one exports the data in ascii vectorized format which is used in BESA for sensor level averaged potentials in time domain and the second one is source wave form file format containing source wave forms in time domain.
Robert Oostenveld - 2012-09-05 15:02:51 +0200
TODO by Robert - create svn account, add to appropriate groups by Jorn - explain how to use http://fieldtrip.fcdonders.nl/development/svn by Todor (with help of Jorn) - add the new reading functions - check and if needed update the besa test code (at the moment I don't know where it is)
Robert Oostenveld - 2012-09-05 15:08:28 +0200
i cerated the svn account and set it up so that it can read everything, but only write in trunk/external/besa. That should be enough to start with. The user name is "todjor".
Todor Jordanov - 2012-09-18 09:06:43 +0200
1. Two new readers were added: readBESAfmp.m and readBESAtfcs.m 2. Content of the COPYING file was provided 3. The information in the README file was updated
Robert Oostenveld - 2019-08-10 11:51:44 +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.