From 06a9f84e05194e7e28a6146b20f388dad7126bad Mon Sep 17 00:00:00 2001 From: Elissa Sutlief Date: Wed, 13 May 2026 17:40:44 -0400 Subject: [PATCH] Add 'no kilosort label' to ClusterQualityLabel contents This label already exists in the production database for units created by merge or split during manual curation. Adding it to the code-level contents prevents a skip_duplicates INSERT on schema activation, which fails for read-only database users. --- element_array_ephys/ephys.py | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/element_array_ephys/ephys.py b/element_array_ephys/ephys.py index 60ffa9b5..96f6d7f7 100644 --- a/element_array_ephys/ephys.py +++ b/element_array_ephys/ephys.py @@ -756,6 +756,11 @@ class ClusterQualityLabel(dj.Lookup): ("mua", "multi-unit activity"), ("noise", "bad unit"), ("n.a.", "not available"), + ( + "no kilosort label", + "No kilosort label exists for this unit, likely because it was" + " the result of a merge or split during manual curation.", + ), ]