Implement a simple system to have backward compatibility for Analyzer extension#3215
Implement a simple system to have backward compatibility for Analyzer extension#3215alejoe91 merged 23 commits intoSpikeInterface:mainfrom
Conversation
|
oups |
|
Here's what I don't understand. Now that we've added the |
|
Since the most recent commit, nothing I do works. I tried going back in and just deleting |
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
|
Here's the current bug in merge units |
|
I have to finish up a presentation at the moment, so I can test another round in the background, but I can't track down this bug. Just let me know when ready for another test :) |
|
Never mind I put the list in as a list instead of list of list. Let me try again :) |
|
Okay the merge code works from loading an analyzer from 08MAY24 :) !! |
For me it works for waveform extractor folders loaded as analyzers from last year :P |
|
I hope you both have tried sigui for this dataset. |
|
It has a probegroup. Has that been patched yet? |
|
Not sure the problem is fully solved. While I can load the analyzer you gave me @alejoe91 for testing the merging, when applying new functions recursively, I still have errors such as nbefore = int(self.params["ms_before"] * self.sorting_analyzer.sampling_frequency KeyError: 'ms_before' |
|
@yger I know, will push a fix tomorrow! |
|
@yger fixed! The templates were not an extensions so they required a fix before in the code |
…ility.py Co-authored-by: Zach McKenzie <92116279+zm711@users.noreply.github.com>
This simple system enabling to hack on load
self.paramsandself.datawhen a new features are implemented in an analyzer extension that imply new parameters and new variable in data.It was for instace the case for template similarity