Processing Outcomes and Retained Trials

The Batch Manager’s Reports tab provides two complementary views. They read persisted processing products; neither is a replacement for scientific inspection or a claim that every existing result used your intended settings.

Processing Outcomes

Open Processing outcomes…, choose the branch and grouping scope, then refresh. The report summarizes prerequisites, ICA/artefact decisions, averages and clean-trial output availability for the batch recordings.

A count such as 24/24 describes discovered outputs for that scope. A missing file, an output not requested, and unavailable metadata are different states. Read the notes rather than treating every blank or unavailable field as zero. A completed-looking row does not prove that the entire recording is scientifically acceptable.

Branch selection matters: main’s results are not branch-local averages. Grouping selection matters too: profile-suffixed products differ from ungrouped products. Use the same branch/profile as the run you want to audit.

Refresh after processing completes or files change. CSV export preserves a tabular snapshot for your records.

Retained Trials

Open Retained trials per condition… and select the branch/grouping scope. Inspect accepted/total and rejected counts by recording and condition.

For grouped/constrained products, a valid completed trial-selection manifest identifies the actual retained set. An unavailable or invalid manifest must not be interpreted as a legitimate zero-trial result. Tooltips and diagnostics provide the reason when the report cannot resolve a value.

Distinguish artefact acceptance from final profile selection. A recording can have 1,017 artefact-accepted trials but retain 990 after balancing; the extra 27 were removed by the profile, not by the artefact detector.

Refresh and export CSV after verifying the intended scope. To investigate a suspicious count, compare the log, editing report and selection manifest for that same recording and branch.