bids-validator icon indicating copy to clipboard operation
bids-validator copied to clipboard

Validator for the Brain Imaging Data Structure

Results 317 bids-validator issues
Sort by recently updated
recently updated
newest added

The CLI is currently not exhaustively tested, or at least I couldn't find it. (If it **is** tested, can somebody please point me to the tests?) As far as I...

effort: low
impact: medium

original proposal as a PR in BIDS: https://github.com/bids-standard/bids-specification/pull/858 seems to be getting approved and if merged soon will enter a release after v1.6.0-203-g811e17e2 ,

effort: medium
enhancement
impact: high

Following https://github.com/bids-standard/bids-specification/pull/802#discussion_r896492464 To be BIDS compliant, SNIRF files should contain only a single run. The validator does not currently check this, but it would be great if it does. SNIRF...

effort: high
enhancement
impact: medium

Could be as simple as expanding the total number of files in Summary instead of ``` Summary: Available Tasks: Available Modalities: 14966 Files, 750.13GB movie MRI 88 - Subjects rest...

effort: medium
enhancement
impact: high

The idea is really to annotate the validator output with descriptor/signature of the state of the dataset which was validated, so if the output of the bids-validator is provided as...

effort: medium
enhancement
impact: medium

I initially asked about this in https://github.com/bids-standard/bids-specification/issues/869. For some file collections (e.g., multi-echo or complex-values fMRI data), the files all come from the same acquisition and MUST have the same...

enhancement

inspired by - https://github.com/bids-standard/bids-validator/issues/1930 I think we should make it very easy for PRs against bids-specification, which change schema, to run validator using modified schema against target (or all) bids-examples....

Could take all the error codes from the schema etc. But more so -- validate overall structure! ATM neither legacy nor deno validators seems to care about config file being...

see spec issue: - https://github.com/bids-standard/bids-specification/issues/952 Optional metadata fields and files that are n/a should just be omitted. For example an `events.tsv` file with just headers.

Seems like another good spot for --debug level warnings. _Originally posted by @nellh in https://github.com/bids-standard/bids-validator/pull/1547#discussion_r1093675127_