Closed MarineChap closed 3 years ago
Hi Marine,
What version of the GUI are you using? The version number is visible in the lower right of the "Graph" tab.
If it's not 0.5.2.1, can you try upgrading to the latest version? It's available here as an .exe installer and a .zip file.
Thank you for this fast answer. I will look tomorrow to be sure I don't say something wrong. Also, I just learned that the firmware update planned for the Neuropixels did not happen. So we don't have the last version. Do you think it could come from here ? Thanks.
Ok! The Neuropixels plugin is currently only compatible with the older firmware, but we will release an update that works with the newer firmware in ~1 week.
Hello @jsiegle, we are indeed using the 0.5.2.1 version of the gui. But maybe I will just wait one week for the update. We will work in the future with the new firmware anyway. Also, do you have an idea of the latency to read the data on the probe ? I am trying to use the neuropixels in close-loop experiments.
Ok, we will let you know when it's ready. In the meantime, can you attach the file named lastConfig.xml
to this issue? We'd like to figure out why the reload is not working.
The last time we measured it, median latency was quite fast (<2 ms), but the upper bound could be as high as 15 ms. However, we have not run any benchmarks with the latest API/firmware, so I can't promise those numbers are still valid.
The xml file you asked (if you saw before my edit, yes we found it ;) ) lastConfig.txt
Do you have an official benchmark published somewhere ? I have many questions. What is the size of the buffer to read the data ? How this latency is computed ... etc?
Thank you.
Thanks! We did the benchmarking by monitoring the number of packets available each time data was fetched, and multiplying by the packet size. This doesn't take into account the time required to copy the packets into the Open Ephys software buffer, but it's at least a lower bound on the latency.
As far as I know, there are no official numbers for this, so it would be good to do some more rigorous tests with the latest firmware and API. Is this something you'd be willing to help with?
The config file loads fine on our end. Can you try deleting lastConfig.xml
and recoveryConfig.xml
and launching the GUI again? If closing and re-opening still causes it to freeze, let us know.
Hello, I would be happy to help with some latency tests. I will have to do it anyway for Falcon at some point.
We removed both files but still the app does not open. I asked to the PhD student to uninstall and reinstall it and retry but she did not have the time today.
Also in the interval, my colleague did the firmware update so It should not work anyway, right ? Sorry, I am in a confined region with mandatory homeworking. That's not easy to do the test that I want in the lab.
Yes, we need to run some more tests on the plugin version that works with the updated firmware (source code is here), but it should be ready soon.
Edit: I just saw your email - it was lost in junk email for whatever reason ! I will test it as soon as possible. Thank you !
Hello @jsiegle,
What is the status of your update ? I saw a commit named "add to the binary", does that means I just need to reinstall Open-Ephys and add the neuropixels PXI plugin to have the new versions ?
Thank you, Have a good day
The new plugin is amazing.
I answered your email with some comments. I think we can solve this comment as it is now working very well on our computer.
Hello, I hope you will be able to help me. I have very little info to troubleshoot this. So I had a neuropixel PXI reader in OpenEphys. I was able to read signal but little weird because of course I did not put the calibration files at the right place. I closed OpenEphys put the calibration files in the OpenEphys folder and relaunch OpenEphys. Now, the gui is not opening and litterally nothing is happening. See the log below - Could you help me to troubleshoot what is happening ? It seems something is silently failing somewhere.
Thank you for your help ! ps: usually we are using spikeGLX and everything works fine - so definitely not a hardware problem.