-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The waveforms are upside down. #3492
Comments
Could you let us know which recording you are using? Maybe a little bit of the script you ran to make your sorting analyzer. If the gain has the wrong sign this could happen for sure. So it would help us to see what you did to get to this point :) |
Yes I think you might not be looking at the same channel. How are you generating the spikeinterface plot? |
Sorry. I will add my code here.
The 'gain_to_uV' in reportinfo.json is 1.
In fact, in the units of the sorting result, some are same as the picture in Phy, but some are upside down. |
|
Sorry is your "binary_file" saved post-filtering + referencing/preprocessing? The |
Thank you for your reply. I know it's difficult to find the solution without the data.
The "rec_correct" is preprocessed using the pipeline "common_reference" -> "bandpass_filter" -> "correct_motion". |
What if you do sparse=True? I'm pretty sure phy still only picks a subset of channels. So if we use our sparsity (which won't be exactly the same set of channels, but will be close) could you try that? |
Thank you for your advice. But it seems same as before. I will try to load the recording from sorting analyzer's result, and find the difference between the two methods of saving recording. |
I can't find the reason of this problem. The waveforms in the Phy are normal, but the waveforms are upside down when the results are imported into the sorting analyzer.
The text was updated successfully, but these errors were encountered: