You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spike trains have a sampling rate, but right now when we use them, this is little impicit (defaults to 1kHz, but doesn't document this, and has no options for changing.) This should be documented, and made more generalizable
Functions to check for this:
convert_train_to_times
create_spike_train
maybe others (to check)
Also: computing spike trains depends on the unit of the data (ms vs. second), and the start time of the task. For examples, it blows up if times are encoded in UNIX time (as it tries to create a spike_train from time 0).
Spike trains have a sampling rate, but right now when we use them, this is little impicit (defaults to 1kHz, but doesn't document this, and has no options for changing.) This should be documented, and made more generalizable
Functions to check for this:
convert_train_to_times
create_spike_train
Also: computing spike trains depends on the unit of the data (ms vs. second), and the start time of the task. For examples, it blows up if times are encoded in UNIX time (as it tries to create a spike_train from time 0).
Note: relates to #5
The text was updated successfully, but these errors were encountered: