pipeio_nb_exec output convention unclear — _executed.ipynb in .src/¶
When pipeio_nb_exec runs a notebook, it writes the executed output to .src/<name>_executed.ipynb alongside the jupytext .py source. This is confusing because:
.src/is supposed to contain only.pysource files (per CLAUDE.md: "If you find.ipynbin.src/, it's a bug — delete it")- Users expect the executed notebook to be the main
.ipynbin the parent workspace dir, or at least clearly documented - The
_executedsuffix makes it look like a leftover artifact
Suggestion¶
Either:
- Write executed output to the parent workspace dir (alongside the main .ipynb) with a clear naming convention
- Document the convention in the pipeio guide
- Or add a pipeio_nb_publish step that copies the executed notebook to the workspace dir
Source context: pixecog¶
PixEcog (pixecog): Neuropixels and ECoG dataset and analysis
Recent commits:
8dc0d9d Pipeline docs: gitignore docs/pipelines/, relocate hand-authored files
96cd1ec Refactor sharpwaveripple/contracts: extract generic helpers to utils/io, remove pipelines __init__.py
36f9326 Add result note directory and sample note
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
Related Notes¶
- issue-arash-20260410-000346-439918.md — Both are pipeio notebook workflow issues filed on the same date
- issue-arash-20260409-232034-115590.md — pipeio_nb_exec env/execution behavior — directly related to how nb_exec works
- issue-arash-20260408-042020-224344.md — pipeio docs_collect scripts issue — related pipeio notebook/docs tooling
- issue-arash-20260409-163158-458231.md — pipeio docs_collect output convention issues — similar theme of unclear output placement