Intan loader

[tdincer]

Based on the "One file per channel type format" section of the official intan manual (page 11): https://intantech.com/files/Intan_RHS2000_data_file_formats.pdf

Task list:

• [x] file path (channel) - output connection needs to be done. If pattern returns more than 1 file, the outputs should be clearly associated with the file name. This is optional. Current version works fine if the pattern is a full file name (e.g "amp-B-000.dat").
• [ ] Ideally read_qstring and read_header functions should be imported from intan. We need to decide on how to operate the intan. I guess the decision will be made with Alessio.
• [x] Do basic reading
• [x] Add docstrings.

For the completeness of the discussion:

• The official example notebook does not work for Alex's data.

[kabilar]

Thanks @tdincer. Drafted this pull request since we wouldn't want to add hardcoded paths to this package.

[tdincer]

@kabilar This PR is to a new branch. It's meant to keep track of the changes. Iterations should be done forking this PR. Not by copy pasting the content.

[tdincer]

@JaerongA and @kabilar I cleaned the code. Let's iterate from here addressing the issues discussed in slack.

[tdincer]

@JaerongA What do we need to return to make this loader useful for array-ephys?

[JaerongA]

@JaerongA What do we need to return to make this loader useful for array-ephys?

The original intan code used to ouput everything (including all the parameters) into a single dictionary format. We might needs parameter values as well. To be completely sure of what's really needed, it'd be worth ingesting some sample data in the element-array-ephys pipeline.

[kabilar]

@kabilar This PR is to a new branch. It's meant to keep track of the changes. Iterations should be done forking this PR. Not by copy pasting the content.

Thanks @tdincer. Whoops, misread the pull request. You are right.