Back to the main page.

Bug 2486 - provide transition for users from egi_mff version 2 to version 3 file format

Status NEW
Reported 2014-02-27 08:56:00 +0100
Modified 2014-03-19 23:25:02 +0100
Product: FieldTrip
Component: fileio
Version: unspecified
Hardware: PC
Operating System: Mac OS
Importance: P5 normal
Assigned to: Colin Davey
URL:
Tags:
Depends on:
Blocks: 2466
See also:

Robert Oostenveld - 2014-02-27 08:56:35 +0100

On 26 Feb 2014, at 23:15, Colin Davey wrote: Note that our current reader only supports MFF version 3. The three files that your test script uses are in an older format. Would you mind replacing them with files in the version 3 format? We have an app that converts older MFF versions to the newest version, and I can supply you with converted versions of the test files.


Robert Oostenveld - 2014-02-27 09:34:11 +0100

(In reply to Robert Oostenveld from comment #0) There appears to be an unfortunate naming confusion, which I understand as - fieldtrip implementation egi_mff_v1 and egi_mff_v2 - mff dataset format v2 and v3. I guess there is also v1, and possibly intermediate versions (e.g. 1.5, 2.1) The egi_mff_v1 does not use Java or any EGI code. The egi_mff_v2 uses the Java implementation from EGI and is the one we shoudl continue to work on. The comment by Colin states that the latest jar file (at this moment not yet in the fieldtrip distribution) only works with the dataset format v3. There exists a converter that converts v2 datasets to v3. Does it also convert v1 datasets to v3? Is it available for all platforms (windows, linux)


Colin Davey - 2014-02-28 04:18:46 +0100

Robert, to answer your questions: -- The converter converts all earlier mff format versions (0, 1 and 2) to the current version (3). -- The converter is only available on Macs, since our main product is a Mac product. What is the best way to get you converted versions of the test data? Or would it be best to just send you the converter?


Colin Davey - 2014-03-19 23:25:02 +0100

I suggest removing the file Long64ChannelWithEvents from the test script. It turns out there are some problems with this file. We can supply other files to use for testing purposes.