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
within PostSorting,
within compare_first_and_second_half.py,
within get_half_of_the_data_cell(prm, spike_data_in, synced_spatial_data_in, half='first_half'):
line 2 looks to calculate the midpoint of the recording in seconds however instead computes half the range. for example:
min=2 seconds
max=5 seconds
then end_of_first_half_seconds should be 3.5
using the above equation
end_of_first_half_seconds = 1.5
this is less that the minimum time and therefore not possible, a fix I've implemented on my dual sorting branch uses
The bug:
within PostSorting,
within compare_first_and_second_half.py,
within get_half_of_the_data_cell(prm, spike_data_in, synced_spatial_data_in, half='first_half'):
line 2 looks to calculate the midpoint of the recording in seconds however instead computes half the range. for example:
min=2 seconds
max=5 seconds
then end_of_first_half_seconds should be 3.5
using the above equation
end_of_first_half_seconds = 1.5
this is less that the minimum time and therefore not possible, a fix I've implemented on my dual sorting branch uses
swapping the minus for a plus changes the computation to taking the midpoint of max and min.
Could someone please check to confirm my interpretation on this?
Running environment
The text was updated successfully, but these errors were encountered: