You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#1049 (and recently merged #1036) inspired me to look at re-used suffixes which ATM might have duplicate and varying specification (in terms of extensions) across different data types:
so I thought that may be such definitions could somehow also be centralized?
and alternative to centralization could be just a unittest which verifies that identical suffixes, which are present in different data types, have identical extensions across datatypes etc?
or may be it is just impossible anyways since some suffixes (like `meg`) might have quite complicated rules (but seems specific to a modality, hence I added "in different data types" above
rules/datatypes/meg.yaml-# First group
rules/datatypes/meg.yaml-- suffixes:
rules/datatypes/meg.yaml: - meg
rules/datatypes/meg.yaml- extensions:
rules/datatypes/meg.yaml- - / # corresponds to BTi/4D data
rules/datatypes/meg.yaml- - .ds/
rules/datatypes/meg.yaml- - .json
rules/datatypes/meg.yaml- - .fif
--
rules/datatypes/meg.yaml-# Specifically, it's dat files with "acq-calibration"rules/datatypes/meg.yaml-- suffixes:rules/datatypes/meg.yaml: - megrules/datatypes/meg.yaml- extensions:rules/datatypes/meg.yaml- - .datrules/datatypes/meg.yaml- entities:rules/datatypes/meg.yaml- subject: requiredrules/datatypes/meg.yaml- session: optional--rules/datatypes/meg.yaml-# fif files with "acq-crosstalk"rules/datatypes/meg.yaml-- suffixes:rules/datatypes/meg.yaml: - megrules/datatypes/meg.yaml- extensions:rules/datatypes/meg.yaml- - .fifrules/datatypes/meg.yaml- entities:rules/datatypes/meg.yaml- subject: requiredrules/datatypes/meg.yaml- session: optional
I believe that this came up at last week's schema meeting, and we were going to look at repurposing #1012 to centralize duplicate suffix patterns across datatypes.
#1049 (and recently merged #1036) inspired me to look at re-used suffixes which ATM might have duplicate and varying specification (in terms of extensions) across different data types:
NB due to -A1 could be an incomplete list
so I thought that may be such definitions could somehow also be centralized?
and alternative to centralization could be just a unittest which verifies that identical suffixes, which are present in different data types, have identical extensions across datatypes etc?
or may be it is just impossible anyways since some suffixes (like `meg`) might have quite complicated rules (but seems specific to a modality, hence I added "in different data types" above
edit: upgraded grep as of v1.7.0-329-gd3429fba
The text was updated successfully, but these errors were encountered: