Each pipeline run generates a simplified processing log CSV inside the task folder.
This file records 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

Below is an example entry from a processing log:
timestampstudy_userrun_idproc_statesubj_basenamebids_subjecttaskflagsnet_nbchan_orignet_nbchan_postproc_badchansproc_filt_lowcutoffproc_filt_highcutoffproc_filt_notchproc_filt_notch_widthproc_sRate_rawproc_sRate1proc_xmax_rawproc_xmax_postproc_xmax_percentepoch_lengthepoch_limitsepoch_trialsepoch_badtrialsepoch_percentproc_nCompsproc_removeCompsexclude_category
2025-09-03 04:04:03unknown01K479NCMBQRRQ8QZTGB2CKWDNcompleted_files128_Rest_EyesOpen_D1004sub-451559RestingStateTutorialWARNING: 8 potential reference artifacts detected128128[‘E56’, ‘E128’, ‘E8’, ‘E14’, ‘E17’, ‘E2’]180[60, 120]51000.0250.0303.444.00.1452.0[-1, 1]2970.758121[0, 1, 2, 3, 4, 12, 15, 17, 18, 20, 21, 28, 34, 36, 49, 74]

Processing Log Column Reference

ColumnExample ValueDescription
timestamp2025-09-03 04:04:03Time when the run completed
study_userunknownUser ID (or unknown if not set)
run_id01K479NCMBQRRQ8QZTGB2CKWDNUnique identifier for this run
proc_statecompleted_filesStatus of the run
subj_basename128_Rest_EyesOpen_D1004Original recording file name
bids_subjectsub-451559BIDS subject identifier
taskRestingStateTutorialTask or condition name
flagsWARNING: 8 potential reference artifacts detectedWarnings or notes from preprocessing
net_nbchan_orig128Channels in the raw input
net_nbchan_post128Channels after preprocessing
proc_badchans[E56, E128, E8, E14, E17, E2]List of bad channels removed
proc_filt_lowcutoff1High-pass filter cutoff (Hz)
proc_filt_highcutoff80Low-pass filter cutoff (Hz)
proc_filt_notch[60, 120]Notch filter frequencies applied (Hz)
proc_filt_notch_width5Width of notch filter (Hz)
proc_sRate_raw1000.0Original sampling rate (Hz)
proc_sRate1250.0Resampled rate (Hz)
proc_xmax_raw303.429Duration of raw recording (s)
proc_xmax_post44.0Duration after trimming/cropping (s)
proc_xmax_percent0.145Proportion of usable data kept
epoch_length2.0Epoch length (s)
epoch_limits[-1, 1]Time window per epoch (s)
epoch_trials29Total epochs created
epoch_badtrials7Rejected epochs
epoch_percent0.759Percentage of epochs retained
proc_nComps121Number of ICA components estimated
proc_removeComps[0,1,2,3,4,12,15,17,18,20,21,28,34,36,49,74]Indices of ICA components removed
exclude_categoryCategories of excluded components/channels

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.