From e7a840e25726d5bdb547fa7ae09170765b079188 Mon Sep 17 00:00:00 2001 From: Remi Gau Date: Wed, 20 Mar 2024 23:00:20 +0100 Subject: [PATCH 1/2] [FIX] fix typo in motion.md --- src/modality-specific-files/motion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/modality-specific-files/motion.md b/src/modality-specific-files/motion.md index 38ff4449cd..aab68e65be 100644 --- a/src/modality-specific-files/motion.md +++ b/src/modality-specific-files/motion.md @@ -61,7 +61,7 @@ to store this information in the `acq_time` column of the [`*_scans.tsv`](../mod The Note that the [BIDS date time format](../common-principles.md#units) allows optional fractional seconds, which SHOULD be used to maximize the precision of the synchronization. Only if the precision of the synchronization is not high enough, the `*_events.tsv` file SHOULD be used to synchronize recordings. In this file, the start- and stop time of the recording of a system are specified in relation to a system to synchronize with. -If more than two systems are to be synchronized, it is up to the user to indntify the "main" system. +If more than two systems are to be synchronized, it is up to the user to identify the "main" system. In case a tracking system provides time information with every recorded sample, these time information MAY be stored in form of latencies to recording onset (first sample) in the `*_motion.tsv` file. From 96a9437e3319984fca07d5f94cc1f58b92be323b Mon Sep 17 00:00:00 2001 From: Remi Gau Date: Wed, 20 Mar 2024 18:02:27 -0400 Subject: [PATCH 2/2] rm typo --- src/modality-specific-files/motion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/modality-specific-files/motion.md b/src/modality-specific-files/motion.md index aab68e65be..6ca4c81dfb 100644 --- a/src/modality-specific-files/motion.md +++ b/src/modality-specific-files/motion.md @@ -58,7 +58,7 @@ When multiple tracking systems are used to record motion or motion capture is us it is advised to provide a possibility to synchronize recordings. The preferred way to do so is to use the acquisition time of the first data point of recordings and to store this information in the `acq_time` column of the [`*_scans.tsv`](../modality-agnostic-files.md#scans-file) file. -The Note that the [BIDS date time format](../common-principles.md#units) allows optional fractional seconds, which SHOULD be used to maximize the precision of the synchronization. +Note that the [BIDS date time format](../common-principles.md#units) allows optional fractional seconds, which SHOULD be used to maximize the precision of the synchronization. Only if the precision of the synchronization is not high enough, the `*_events.tsv` file SHOULD be used to synchronize recordings. In this file, the start- and stop time of the recording of a system are specified in relation to a system to synchronize with. If more than two systems are to be synchronized, it is up to the user to identify the "main" system.