From 034dfc5f2e91e36bc94279095fe63f88eb5b2e9e Mon Sep 17 00:00:00 2001 From: Chris Markiewicz Date: Tue, 22 Aug 2023 15:10:45 -0400 Subject: [PATCH] FIX: Schema definition of reference_frame --- src/schema/objects/columns.yaml | 11 ++++------- src/schema/rules/tabular_data/motion.yaml | 2 +- 2 files changed, 5 insertions(+), 8 deletions(-) diff --git a/src/schema/objects/columns.yaml b/src/schema/objects/columns.yaml index b96b4dff35..7e2dd1fd7e 100644 --- a/src/schema/objects/columns.yaml +++ b/src/schema/objects/columns.yaml @@ -377,16 +377,13 @@ reference__ieeg: - type: string enum: - n/a -# reference frame column for channels.tsv files for motion data -reference_frame__motion: - name: reference +reference_frame: + name: reference_frame display_name: Reference frame description: | Specification of a reference frame in which the motion data are to be interpreted. - The value MUST match any of used key-value pair in the `*_channels.json` file in the motion directory. - It is RECOMMENDED to use a meanigful combination of `RotationRule`, `RotationOrder` - and `SpatialAxis` for the specification. - If a channel is not to be interpreted in a reference frame use `n/a`. + The description of the levels in `*_channels.json` SHOULD use `RotationRule`, + `RotationOrder` and `SpatialAxis` for the specification. anyOf: - type: string - type: string diff --git a/src/schema/rules/tabular_data/motion.yaml b/src/schema/rules/tabular_data/motion.yaml index 2e1dd8a555..3f2f86ae96 100644 --- a/src/schema/rules/tabular_data/motion.yaml +++ b/src/schema/rules/tabular_data/motion.yaml @@ -13,11 +13,11 @@ motionChannels: columns: name__channels: required component: required - reference_frame__motion: recommended type__channels: required tracked_point__channels: required units__motion: required placement__motion: recommended + reference_frame: recommended description: optional sampling_frequency: optional status: optional