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 have been setting up the silicon probe recording.
I used the Cambridge Neurotech H3 silicon probe.
But, there are one bad channel (It seems like sine wave unlike another channels) and one reference channel (I selected the channel for referencing all channels on Open Ephys GUI channel map plugin). Small part of the recording data (binary file for the KS) is below.
I configured H3 probe channel map for KS2.5 channel map (there are two unconnected channels, bad channel and reference channel).
I am not sure this is right (when I change the connection of that two channels, KS results are also different.)
(Question for phy2) In the probe view in phy2, I got confused.
There are unconnected two channels. I think it should be CH30 above the unconnected channel. In this case, CH28 is not same at CH28 in the recording data. Is it right..?
Thank you
The text was updated successfully, but these errors were encountered:
Hi,
I have been setting up the silicon probe recording.
I used the Cambridge Neurotech H3 silicon probe.
But, there are one bad channel (It seems like sine wave unlike another channels) and one reference channel (I selected the channel for referencing all channels on Open Ephys GUI channel map plugin). Small part of the recording data (binary file for the KS) is below.
I configured H3 probe channel map for KS2.5 channel map (there are two unconnected channels, bad channel and reference channel).
I am not sure this is right (when I change the connection of that two channels, KS results are also different.)
(Question for phy2) In the probe view in phy2, I got confused.
There are unconnected two channels. I think it should be CH30 above the unconnected channel. In this case, CH28 is not same at CH28 in the recording data. Is it right..?
Thank you
The text was updated successfully, but these errors were encountered: