feat: DREDge motion correction (CatGT→DREDge→KS4) + uv/py3.14 env

[tabedzki]

🤖 AI text below 🤖

Summary

Implements Option A from #4: adds DREDge motion correction (SpikeInterface correct_motion(preset="dredge")) as an opt-in preprocessing step in the CatGT → DREDge → Kilosort4 flow. DREDge is one more selectable preproc_tool, mirroring catgt; Kilosort keeps its direct kilosort.run_kilosort call. Also modernizes the environment to uv on Python 3.14.

Note: the correct keyword is preset="dredge" (which internally selects estimate_motion method dredge_ap) — not preset="dredge_ap".

How it works

• run_dredge reads whatever the previous step produced (globs *ap.meta): the flattened CatGT output dir when chained, or raw SpikeGLX if DREDge runs alone. It writes a SpikeGLX-style *.ap.bin + copied *.ap.meta into dredge_output/, which becomes new_raw_data_directory, so the existing Kilosort callers read it unchanged.
• KS4's internal drift corrector is disabled via nblocks=0 in the process paramset, so motion is corrected once (by DREDge). do_correction is not a KS4 parameter (verified: zero hits in the kilosort pkg) and is kept only as an inert, KS2/KS3-friendly key.
• GPU: DREDge does not auto-detect a GPU (KS4 does), so run_dredge passes estimate_motion_kwargs={"device": ...} explicitly (cuda when available, cpu fallback) and frees CUDA memory before the sorter stage.

Changes

• u19_sorting/config.py — register dredge in preproc_tools + preproc_tools_delete_post.
• u19_sorting/preprocess_wrappers.py — dredge branch in preprocess_main; dredge.run_dredge (read → correct_motion → write_binary_recording + copy meta → persist motion/ → lazy-skip) and dredge_check_output.
• pyproject.toml — requires-python >= 3.14; spikeinterface>=0.104.8 (floor, no upper bound); floor ibllib/ONE-api at 4.0.1/3.4.1 to stop the resolver regressing to a stale pre-2024 snapshot; replace the invalid empty license with license-files; point Pyright at .venv. Re-locked so matplotlib/pyarrow resolve cp314 wheels. Retire requirements.txt / setup.py.

Verification

End-to-end on a synthetic drifting recording: exactly one ap.bin+ap.meta, non-trivial motion displacement (≈±30 µm, not the all-zero silent-failure mode), kilosort.io.find_binary locates the output, and a second run lazy-skips.

Linkage (merge together)

• Closes Integrate SpikeInterface (DREDge motion correction) + Kilosort version selection via Apptainer #4
• Companion: feat(slurm): uv env prefetch + conda→uv for ephys jobs U19-pipeline-python#97 (uv env prefetch + conda→uv ephys SLURM; closes U19 #94, #54) and feat: uv python env + DREDge paramset seeds RecordingProcessJobGUI#2 (uv env + DREDge paramset seeds).

🤖 Generated with Claude Code

[tabedzki]

🤖 AI text below 🤖

Companion tracking issue (orchestration side): BrainCOGS/U19-pipeline-python#94 — describes the DataJoint param inserts ('dredge' PreClusterMethod + ParamSet + step) needed to make DREDge selectable. No code change in that repo.