Chris Markiewicz

This would be an easy one to write in schema, if you want to make a PR to the spec: ```yaml rules.checks.hints.BehavioralOnsetAndDuration: issue: code: BEH_ONSET_DURATION message: Some message level: warning...

Do you know if this is a change from previous processing, a long running issue, or subject-specific?

> @effigies, your review please. Sorry, I don't have any time to work on this at the moment.

It's unclear to me what you're trying to do. What do you get out of your MATLAB code? Do you have an example file where you can show the differences...

Variable TRs should be achievable with the `VolumeTiming` metadata field. That was added to account for sparsely acquired fMRI (in particular, clustered volume acquisition (CVA), which can't be easily handled...

It looks like the two things that this adds over `VolumeTiming` are `ScanStart` and the possibility of frame acquisition durations (I assume a frame is a volume in this context?)...

Sounds like a great idea! The places to implement this would be: * Rendering code: https://github.com/bids-standard/bids-specification/blob/master/tools/schemacode/src/bidsschematools/render/tables.py * Wrapper: https://github.com/bids-standard/bids-specification/blob/master/tools/mkdocs_macros_bids/macros.py * Macro definition: https://github.com/bids-standard/bids-specification/blob/master/tools/mkdocs_macros_bids/main.py

Looking at BIDSSelect (https://github.com/poldracklab/fitlins/blob/55ae712/fitlins/interfaces/bids.py#L387-L446), it looks like we just use the masks found next to BOLD files. I was pretty sure that we gave the option not to use masks...

[Glossary entry](https://bids-specification--2151.org.readthedocs.build/en/2151/glossary.html#bigbrain2015-enums): [Coordinate systems table](https://bids-specification--2151.org.readthedocs.build/en/2151/appendices/coordinate-systems.html#standard-template-identifiers):

While we only use that function once in the app, we use it a lot in the tests.