Rules for Supported File Format Imports

Support & Discussions
1

Is the idea to support imports for as many file types as possible or to limit to those for which there is a substantial enough user-base for a robust beta test that the import functions work?

I also have an rdh file and could put it into a RawArray but can write a PR to add it as a supported file type if that is in line with the goals of mne (Importing\working with a general format · Issue #5360 · mne-tools/mne-python · GitHub).

This could also be added to the documentation about whether mne is willing to add as many file format imports as contributors are able to write PRs for or whether it’s better to reduce potential errors with rarely used file types and put it on the manufacturers to write conversion scripts.

2

you are suggesting to add a new raw_raw_rdh file?

Alex

3

Yeah I noticed there was an issue opened and closed about it already with the suggestion to just use RawArray though

4

is there a matlab reader for this format? maybe in eeglab or fieldrip?
ready the matlab code I will see how complex this can be.

Alex

5

The company has released python and Matlab readers Downloads | Intan Technologies they aren’t that complex. It doesn’t look like fieldtrip or eeglab have readers although fieldtrip has similar ieeg data format readers Importing your data - FieldTrip toolbox

6

what is the license of the Python reader?

Alex

7

There doesn’t appear to be a license but an author is mentioned in the header

Michael Gibson 17 July 2015

8

can you clarify ? if no BSD compatible license you can come up with your own personal implementation?

Alex

9

Yeah I guess we could reimplement based on the file structure/their code and/or we could email the authors asking for permission to reproduce

10

I didn’t realize how large of a task this was. Maybe I’ll just start with a gist and see if there’s a need.

1 Like