Repository navigation
Add apply curation to gui - #224
Conversation
|
Clearly I totaly I lost the control here. |
|
Haha, I don't think so Sam! The core logic has changed much - most of the gross code is related to storing the chain of curations and being able to save them! |
|
|
||
| def apply_curation(self): | ||
|
|
||
| if self.original_analyzer is None: |
|
@alejoe91 @samuelgarcia I think this is ready! |
|
@chrishalcrow I tested this and added a |
|
@chrishalcrow done! fixed the QT selection and added CurationView settings mapping the Ready to merge on my end! |
|
Note that this is needed to avoid failures due to all non-mergeable units: SpikeInterface/spikeinterface#4804 |
Allows the user to apply the current curation to the analyzer, creating a new analyzer in memory.
What this PR does:
apply_curationbutton, we create a new, curated analyzer in memory. All views are_reinitialized and theCurationModelis created and stored incontroller.applied_curationsand the current curation is cleared. Now the user can start curating again._reinitializemethod to all Views, allowing the view to update when the analyzer is updated (might also be useful for re-computations!)SequentialCuration.iterative_curationflag to the cli or therun_mainwindowfunction.I think this is pretty much done!
To do:
allow user to undo apply