Closed bendichter closed 1 year ago
This would require lot of works.
Mainly mearec is 2 big parts + read/write:
The part 2 could be quite easily ported to spikeinetrface (and it is partilally already done). The part 1 is quite big + specific + strong dependency. So having outiside spikeinterface is wiser I think.
When more time I would be to continue pushing part in spikeinetrface.
Sorry, I was unclear. I meant the SpikeInterface org, not the SpikeInterface repo
It was quite clear I made a shortcut :)
@samuelgarcia I don't understand. What kind of shortcut? Where? I am suggesting we move this repository to the SpikeInterface GitHub organization.
I made the shortcut "Move to SpikeINterface" = move code logic inside spikeinertface module But you meant "Move to SpikeINterface" = transfert the repo to the SpikeInterface organisation I read it too quickly
Hi guys, I'm in favor of moving to the SI org :)
ok great @alejoe91 I think you might be the only one who can do that
And done: https://github.com/SpikeInterface/MEArec
We might want to officially consider this library part of the SpikeInterface suite. Thoughts?