Heberto Mayorquin
Heberto Mayorquin
This PR is not mean to be merged but to add a concrete implementation to suggest in #1544. This PR probably is incomplete and it has errors. The idea here...
So here: ``` _event_channel_dtype = [ ("name", "U64"), ("id", "U64"), ("type", "S5"),
As I am taking a look I realize that the `get_probe` method returns a dummy probe from the contact vector: https://github.com/SpikeInterface/spikeinterface/blob/bfe9fb649b58c48d2a04949061154f75f8e08b1f/src/spikeinterface/core/baserecordingsnippets.py#L255-L282 I am looking at the `set_probe` and I don't...
From today's meeting. ## Context: Spikeinterface has two internal representation time: cheap: sampling_frequency and t_start expensive: time_vector ## Fine control of the time Right now `t_start` is a public attribute...
From the meeting. @zm711 please correct if I got anything wrong python 3.13 only supports numpy 2.0 on windows. We can't support numpy 2.0 because of neo issues. We are...
We have solved many of these but we did not write regression tests for them. This issue should serve as a list of those PRs so we can add regression...
Currently the `generate_unic_locations` enforces the unit constrain with a simple rejection sampling algorithm that is non-deterministic: https://github.com/SpikeInterface/spikeinterface/blob/55c7de1f2762315af406b5131b5bf0da5fd5767c/src/spikeinterface/core/generate.py#L2007-L2029 But I think this is a clear use case for the Bridson's algorithm...
[Discussion] Improve the way we handle signals of different nature when they come in the same stream
On neo the concept of a stream indicates that the underlying data has the same: * dtype * shape * sampling_rate And that makes a lot of sense in neo...
The following is a bug when setting missing properties with unicode strings in `base.set_property`: ```python from spikeinterface.core import generate_recording num_channels = 5 recording = generate_recording(num_channels=5, durations=[1.0]) channel_ids = ["a", "b",...