Skip to main content
Each pipeline run generates a simplified processing log CSV. You’ll find:
  • Per‑file CSVs under reports/run_reports/
  • A combined task‑level log at <task>/preprocessing_log.csv
These files record the run metadata, preprocessing parameters, and quality‑control results.
It’s designed to make your analysis reproducible, transparent, and easy to audit.

​
Processing Log Example Row (Per‑Run CSV)

Below is an example entry from a processing log:

​
Processing Log Column Reference

​
Why It Matters

  • Traceability: Every preprocessing decision (filters, bad channels, ICA components) is logged.
  • Reproducibility: Logs can be used to replicate runs with identical parameters.
  • Quality Control: Flags highlight potential artifacts or reference issues for review.

​
Next Steps

  • Check the processing log after each run to review filter settings, rejected channels, and ICA removals.
  • Use logs to compare across runs (especially when rerunning tasks that generate backups).
  • Keep logs with your dataset when sharing for full reproducibility.