Add type hints and tests to analysis package

[joschaschmiedt]

While exploring the API of the analysis package, I saw that there is an implicit abstraction of the Continuous and Spikes classes. I made that abstraction explicit (adding ContinuousAbstract and SpikesAbstract interfaces) and added type hints throughout the analysis package.

I've also added test datasets for the binary, open-ephys and NWB data formats as well as test cases for reading those data in. While doing so I fixed potential bugs

• There was a typo on a float64 dtype (see ecd427b)
• Reading in the Spikes from the open-ephys format test dataset causes a reshaping error (see test_spike_data in test_openephys_format).
• The BinaryRecording contained a call to the non-existent function create_channel_map

If you find any of this useful, feel free to merge and modify my suggestions.

Here's the complete CHANGELOG:

• Dropped support for Python < 3.9
• Refactoring without new functionality or API changes
  • The Continuous and Spike classes of the three formats now have an explicit interface
    (i.e. abstract parent class) and have been renamed to BinaryContinuous, BinarySpike etc.
  • The metadata of Continuous and Spike in the analysis package now are typed dataclasses
    instead of dict objects . This makes accessing metadata more reliable.
  • Type hints have been added to the analysis package.
  • Automated tests for reading Binary, NWB and OpenEphys data formats have been added (incl. GitHub action)
  • Added a RecordingFormat enum for the three formats
  • Added a JSON schema for validating oebin files
  • Added a uv.lock file for reproducible development environments.
• BinaryContinuous and BinarySpike now have __str__ methods to give an overview over
  their contents.

[jsiegle]

Thanks for this! Let us know when you're finished making changes and we will test it out.

[joschaschmiedt]

@jsiegle, I think I'm done with changes from my side. I'd be happy if you could test it out.

[jsiegle]

Thanks, we should be able to take a closer look at this next week.

[joschaschmiedt]

With (the fantastic) 1.0 on the horizon, any news on merging this?

[jsiegle]

There are a lot of (very helpful) changes here, and we will need time to test everything thoroughly. No guarantees it will happen before the 1.0 release, but we will try our best. Thanks again for all of your contributions!