Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-atten_events.tsv, /sub-01/sub-01_events.tsv, /sub-01/sub-01_task-atten_events.tsv, /sub-01/ses-01/sub-01_ses-01_events.tsv, /sub-01/ses-01/sub-01_ses-01_task-atten_events.tsv, /sub-01/ses-01/func/sub-01_ses-01_events.tsv, /sub-01/ses-01/func/sub-01_ses-01_task-atten_events.tsv

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-atten_events.tsv, /sub-01/sub-01_events.tsv, /sub-01/sub-01_task-atten_events.tsv, /sub-01/ses-02/sub-01_ses-02_events.tsv, /sub-01/ses-02/sub-01_ses-02_task-atten_events.tsv, /sub-01/ses-02/func/sub-01_ses-02_events.tsv, /sub-01/ses-02/func/sub-01_ses-02_task-atten_events.tsv

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-atten_events.tsv, /sub-02/sub-02_events.tsv, /sub-02/sub-02_task-atten_events.tsv, /sub-02/ses-01/sub-02_ses-01_events.tsv, /sub-02/ses-01/sub-02_ses-01_task-atten_events.tsv, /sub-02/ses-01/func/sub-02_ses-01_events.tsv, /sub-02/ses-01/func/sub-02_ses-01_task-atten_events.tsv

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-atten_events.tsv, /sub-02/sub-02_events.tsv, /sub-02/sub-02_task-atten_events.tsv, /sub-02/ses-02/sub-02_ses-02_events.tsv, /sub-02/ses-02/sub-02_ses-02_task-atten_events.tsv, /sub-02/ses-02/func/sub-02_ses-02_events.tsv, /sub-02/ses-02/func/sub-02_ses-02_task-atten_events.tsv

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-atten_events.tsv, /sub-03/sub-03_events.tsv, /sub-03/sub-03_task-atten_events.tsv, /sub-03/ses-01/sub-03_ses-01_events.tsv, /sub-03/ses-01/sub-03_ses-01_task-atten_events.tsv, /sub-03/ses-01/func/sub-03_ses-01_events.tsv, /sub-03/ses-01/func/sub-03_ses-01_task-atten_events.tsv

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-atten_events.tsv, /sub-03/sub-03_events.tsv, /sub-03/sub-03_task-atten_events.tsv, /sub-03/ses-02/sub-03_ses-02_events.tsv, /sub-03/ses-02/sub-03_ses-02_task-atten_events.tsv, /sub-03/ses-02/func/sub-03_ses-02_events.tsv, /sub-03/ses-02/func/sub-03_ses-02_task-atten_events.tsv

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-atten_events.tsv, /sub-04/sub-04_events.tsv, /sub-04/sub-04_task-atten_events.tsv, /sub-04/ses-01/sub-04_ses-01_events.tsv, /sub-04/ses-01/sub-04_ses-01_task-atten_events.tsv, /sub-04/ses-01/func/sub-04_ses-01_events.tsv, /sub-04/ses-01/func/sub-04_ses-01_task-atten_events.tsv

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-atten_events.tsv, /sub-04/sub-04_events.tsv, /sub-04/sub-04_task-atten_events.tsv, /sub-04/ses-02/sub-04_ses-02_events.tsv, /sub-04/ses-02/sub-04_ses-02_task-atten_events.tsv, /sub-04/ses-02/func/sub-04_ses-02_events.tsv, /sub-04/ses-02/func/sub-04_ses-02_task-atten_events.tsv

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-atten_events.tsv, /sub-05/sub-05_events.tsv, /sub-05/sub-05_task-atten_events.tsv, /sub-05/ses-01/sub-05_ses-01_events.tsv, /sub-05/ses-01/sub-05_ses-01_task-atten_events.tsv, /sub-05/ses-01/func/sub-05_ses-01_events.tsv, /sub-05/ses-01/func/sub-05_ses-01_task-atten_events.tsv

Task scans should have a corresponding events.tsv file. It can be included one of the following locations: /events.tsv, /task-atten_events.tsv, /sub-05/sub-05_events.tsv, /sub-05/sub-05_task-atten_events.tsv, /sub-05/ses-02/sub-05_ses-02_events.tsv, /sub-05/ses-02/sub-05_ses-02_task-atten_events.tsv, /sub-05/ses-02/func/sub-05_ses-02_events.tsv, /sub-05/ses-02/func/sub-05_ses-02_task-atten_events.tsv

The most common set of dimensions is: 80,80,54,800 (voxels), This file has the dimensions: 64,64,38,300 (voxels).

The most common set of dimensions is: 80,80,54,800 (voxels), This file has the dimensions: 64,64,38,300 (voxels). The most common resolution is: 2.75mm x 2.75mm x 2.80mm x 0.75s, This file has the resolution: 3.50mm x 3.50mm x 3.50mm x 2.00s.

The most common resolution is: 3.50mm x 3.50mm x 3.50mm x 2.00s, This file has the resolution: 2.75mm x 2.75mm x 2.75mm x 0.75s.

The most common resolution is: 2.75mm x 2.75mm x 2.80mm x 0.75s, This file has the resolution: 2.75mm x 2.75mm x 2.75mm x 0.75s.

The most common set of dimensions is: 80,80,54,800 (voxels), This file has the dimensions: 64,64,38,300 (voxels).

The most common set of dimensions is: 80,80,54,800 (voxels), This file has the dimensions: 64,64,38,300 (voxels). The most common resolution is: 2.75mm x 2.75mm x 2.80mm x 0.75s, This file has the resolution: 3.50mm x 3.50mm x 3.50mm x 2.00s.

The most common set of dimensions is: 80,80,54,800 (voxels), This file has the dimensions: 64,64,38,300 (voxels).

The most common set of dimensions is: 80,80,54,800 (voxels), This file has the dimensions: 64,64,38,300 (voxels). The most common resolution is: 2.75mm x 2.75mm x 2.80mm x 0.75s, This file has the resolution: 3.50mm x 3.50mm x 3.50mm x 2.00s.

The most common set of dimensions is: 80,80,54,800 (voxels), This file has the dimensions: 64,64,38,300 (voxels).

The most common resolution is: 3.50mm x 3.50mm x 3.50mm x 2.00s, This file has the resolution: 2.75mm x 2.75mm x 2.75mm x 0.75s.

Tabular file contains custom columns not described in a data dictionary

Columns: age, sex, LiteBook_use not defined, please define in: /participants.json

The recommended file /README is missing. See Section 03 (Modality agnostic files) of the BIDS specification.