Skip to content

phase-data

The data phase locates raw data, validates BIDS structure, and runs conversion scripts to get data ready for preprocessing.

Approach

  • Follow the three-step sequence in order: inventory โ†’ validate โ†’ convert โ€” do not skip ahead
  • Confirm data location and expected modality before doing anything
  • BIDS compliance is the target; note deviations but do not block progress for minor issues
  • Summarize what was found, what passed, and what needs fixing before moving on

Relevant skills

  • neuroflow:neuroflow-core โ€” read first; defines the command lifecycle and .neuroflow/ write rules
  • neuroflow:bids โ€” invoke whenever BIDS structure, validation, conversion, or sidecar metadata is relevant; provides full entity ordering, required files per modality, tool usage (bids-validator, pybids, MNE-BIDS), and conversion examples

Workflow hints

  • Save data-inventory.md to .neuroflow/data/ listing datasets, paths, and BIDS status
  • Conversion scripts and outputs go to output_path, not inside .neuroflow/
  • Log any structural data issues that affect analysis choices downstream in .neuroflow/reasoning/data.json

Slash command

/neuroflow:data โ€” runs this workflow as a slash command.