Closed chrisan97 closed 7 months ago
Hi @chrisan97,
Thank you for your question and sorry for the late reply, this slipped through the cracks. Not sure if this is still useful for you, but I'll leave the answer here for completeness.
Your are absolutely right in finding that discrepancy between all insertions on the public database, and the insertions that have the spikes.times.npy dataset. The two insertions for which we didn't release the spikes.times.npy didn't pass quality control. I am not sure why they were released at all, but sometimes only part of the data might be made public for specific reasons.
The easiest way to adapt your query to only return the probe insertions that pass through VISp and have spikes.times.npy data is like this:
insertions = one.search_insertions(atlas_acronym=brain_acronym, datasets='spikes.times.npy', query_type='remote')
As of today, this will return 70 insertions, while omitting the datasets keyword argument will return 72.
Regarding the clusters table, this is a convenience dataset specific to the brainwidemap release. The clusters table and the individual datasets on the database are synced, i.e. the data contained in this table, and the data you will obtain from downloading individual datasets from the database are the same. Note, however, that the clusters table does not contain the spike times, so if you need that information you will still have to download the spikes.times.npy datasets. The best way to access this data is by using the SpikeSortingLoader.
Also, the clusters table only contains probe insertions that are part of the brainwidemap release. Currently I believe all insertions on the database are represented in the clusters table, however, in the future the above query might return insertions that are not part of the brainwidemap release, and thus not in the clusters table.
If you want to download the most up-to-date version of the clusters table, please use this function from the paper-brain-wide-map repository.
Hope this helps and sorry again for the delay, Julia
(I am closing this issue but feel free to re-open if you have further questions)
Hello, I am trying to extract all recordings from VISp. I did this by
The number of good_insertions come out to be 47, but the # of detected insertions in VISp come to be 49. I noticed this issue while I was trying to do
which was to create a table of clusters that are in VISp. If I iterate through the insertions pids instead of good_insertions, it flips me an error, presumably because some files are missing from the database.
I have also noticed that there is an alternative way to extract units, which is to use the cluster tables directly from the database. What is more accurate at this point? Should I resort to the below method instead of the above method?
Thanks, Chris