Skip to content

pipeio_flow_new should auto-register flow (or prompt for registry_scan)

Observed: pipeio_flow_new("preprocess_motion") scaffolds the directory structure correctly but does NOT add the flow to .projio/pipeio/registry.yml. This means pipeio_run(flow="preprocess_motion") immediately fails with "Unknown flow". The user must manually call pipeio_registry_scan to register it.

Expected: Either: 1. pipeio_flow_new auto-calls pipeio_registry_scan after scaffolding, OR 2. pipeio_flow_new returns a message like "Flow scaffolded. Run pipeio_registry_scan to register it." so agents know the next step.

Impact: Caused 2 wasted tool calls during a flow creation session. Agents don't know they need registry_scan unless they've seen this before.

Source context: pixecog

PixEcog (pixecog): Neuropixels and ECoG dataset and analysis

Recent commits: 

27a75e5 Preprocess_ieeg DAG redesign: ttl_removal before interpolate, two-tier badlabel, auto-skip TTL, pre-lowpass LNR
42cf0d9 Preprocess_ieeg redesign: DAG reorder, two-tier badlabel, auto-skip TTL, pre-lowpass LNR, cross-subject TTL analysis, notebooks published
6b295b2 Update badlabel audit note: full pipeline comparison (85 new vs 7 legacy vs 71 TTL), zarr fix confirmed, 97.2% TTL catch rate

README:

type: readme

Quick Start for Collaborators

Follow this checklist to get started with Pixecog documentation and workflows.

🐀 Pixecog Project — Compact Overview

Core principles

  • One immutable BIDS raw dataset (raw/) as the canonical baseline
  • Each analysis pipeline ha