-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PET recon parameter error - need to implement a conditional statement #1897
Comments
behaviour
expected
current
the spec says: RECOMMENDED, but REQUIRED if ReconFilterType is not "none" For instance https://github.com/bids-standard/bids-examples/blob/master/pet001/sub-01/ses-01/pet/sub-01_ses-01_trc-CIMBI36_pet.json#L36 could be removed and be valid (but isn't) |
@rwblair @mnoergaard I'mguessing it's an update in the schema to do? |
I'm going to add a new entry to bids-examples to reflect this case @rwblair as that feels like a good first step. |
The schema seems to match the described rules. Is this maybe a bug in the old, non-schema validator? |
i used the online validator ?? |
Added example to bids-examples in this PR -> bids-standard/bids-examples#427 |
Behaviour
(ReconMethodParameterUnits, ReconMethodParameterValues not present)
expected
current
the spec says: RECOMMENDED, but ReconMethodParameterUnits & ReconMethodParameterValues not in the metadata as REQUIRED if ReconMethodParameterLabels does not contain "none"
The text was updated successfully, but these errors were encountered: