Repository navigation
Submit a PR to the main BIDS spec on scans.tsv/concurrency #42
Description
TO DO:
- Review relevant contribution guidelines
- Check for previous similar PRs to better understand how to approach this
- Understand necessary changes to the schema?
- Draft an [ENH?] issue on the main BIDS specification
- Post issue on main BIDS specification
- Submit corresponding [ENH] PR
- (?) Submit corresponding [SCHEMA] PR
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
- Status
Activity
[-]Submit a PR to the main BIDS spec on scans.tsv concurrency[/-][+]Submit a PR to the main BIDS spec on scans.tsv/concurrency[/+]m-miedema commentedon Feb 12, 2026
I found these examples helpful in envisioning how to format an issue/PR:
bids-standard#779
bids-standard#816
bids-standard#2340
I found these examples helpful in envisioning how changes to the schema might work:
bids-standard#1839 (comment)
(^ bonus helpful reminder against master branch PRs)
bids-standard#1881
bids-standard#798
I found these examples helpful in previous discussion of the use of scans.tsv for timing:
bids-standard#2231
bids-standard#1324
bids-standard#2296 <-- particularly relevant as Oscar suggests that scans.tsv could become mandatory
bids-standard#1796 (comment) <-- I saw some mentions of recording.tsv in 2024ish conversations, I'm not sure if this is still something that BIDS is evolving towards
bids-standard#86 (comment) <-- relevant for discussing RecordingDuration and potential duplication of information