Chris Markiewicz
Chris Markiewicz
I'm going to merge to fix the builds. It might be worth re-adding CircleCI config just for the artifacts, but triggered on a `[circleci]` tag in the commit message or...
I'm perfectly happy with `null`, but I can catch an error, too.
I've got a broken https://github.com/nipreps/fmriprep/pull/3423 that is paired with this. I figure I should get that working before merging this. Was aiming for 25.0, but it was delayed enough.
Looks like that's been there since the beginning: https://github.com/nipreps/sdcflows/commit/368bbc04ce1c7c3f04b1bb206cd3c1dd36eb9648 So this is an untested workflow. I guess I would just add `in_reference` to the `inputnode` and pass an appropriate reference....
@psadil Sorry about the long delay. I'm marking this as draft just so I know that it's waiting on you. Please feel free to mark as ready again whenever you...
This is still relevant.
Is the proposal to create TRACEW to mean trace-weighted in addition to, or in lieu of TRACE?
cc @neurolabusc I believe the ADC/TRACE definitions were motivated by your use case. Does this make sense to you?
Something like: ```yaml AgeRefRecommended: selectors: - path == "/participants.tsv" - '"age" in columns' fields: AgeReference: recommended ```
If `Reference` is added to column definition objects... ```json { "age": {"Units": "years", "Reference": "birth"} } ``` We can add a check in `schema.rules.checks.something` ```yaml AgeReferenceEnumeration: issue: ... selectors: -...