You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When deleting a subset from SpikeSortingSelection in the v1 pipeline, the delete step attempts to delete all entries from SpikeSortingOutput.CurationV1.
Suspect it's a failure to join and restrict tables correctly during the merge delete due to the remapping of primary keys between levels.
To Reproduce
fromspyglass.spikesorting.spikesorting_mergeimportSpikeSortingOutputimportspyglass.spikesorting.v1assgsrestr= {"nwb_file_name":"BS2820231107_.nwb", "sort_group_id": 9}
rec_restr= (sgs.SpikeSortingSelection.proj() * (sgs.SpikeSortingRecordingSelection&restr).proj()).fetch('recording_id', as_dict=True)
del_key= (sgs.SpikeSortingSelection&rec_restr& {"sorter_param_name": "franklab_probe_ctx_30KHz"}).fetch("KEY",as_dict=True)
sgs.SpikeSortingSelection&del_key# gives 6 entries
(sgs.SpikeSortingSelection).delete(del_key) # deletes 6 entries from SpikeSortingSelection, all entries from SpikeSortingOutput.CurationV1
The text was updated successfully, but these errors were encountered:
Describe the bug
When deleting a subset from
SpikeSortingSelection
in the v1 pipeline, the delete step attempts to delete all entries fromSpikeSortingOutput.CurationV1
.Suspect it's a failure to join and restrict tables correctly during the merge delete due to the remapping of primary keys between levels.
To Reproduce
The text was updated successfully, but these errors were encountered: