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
I set up an NP2.0 4-shank probe, selecting 96 sites across all shank tips, as shown in the file NP20_4shanks_chanMap.png. After running Kilosort2.5, two files related to the channel map (channel_map.npy and channel_positions.npy) were successfully generated. However, in phy TraceView, the channel order appeared incorrect, with channels listed irrespective of shanks: [0, 48, 49, 241, 192, 193, 240, 1...] from the deepest, as seen in TraceView_incorrect_order_4shanks.png.
How can we view the channels arranged shank by shank, starting from the deepest and connecting them vertically?
Note that the channel positions in ProbeView are correct. Additionally, the green-purple gradient in TraceView matches the shank-by-shank order. Therefore, I do not believe the issue originates from the channel map files.
Thank you for your assistance! GitHubPost.zip (including channel_map.npy and channel_positions.npy)
The text was updated successfully, but these errors were encountered:
I set up an NP2.0 4-shank probe, selecting 96 sites across all shank tips, as shown in the file NP20_4shanks_chanMap.png. After running Kilosort2.5, two files related to the channel map (channel_map.npy and channel_positions.npy) were successfully generated. However, in phy TraceView, the channel order appeared incorrect, with channels listed irrespective of shanks: [0, 48, 49, 241, 192, 193, 240, 1...] from the deepest, as seen in TraceView_incorrect_order_4shanks.png.
How can we view the channels arranged shank by shank, starting from the deepest and connecting them vertically?
Note that the channel positions in ProbeView are correct. Additionally, the green-purple gradient in TraceView matches the shank-by-shank order. Therefore, I do not believe the issue originates from the channel map files.
Thank you for your assistance!
GitHubPost.zip (including channel_map.npy and channel_positions.npy)
The text was updated successfully, but these errors were encountered: