Skip to content

Commit

Permalink
Merge pull request #1731 from bids-standard/Remi-Gau-patch-1
Browse files Browse the repository at this point in the history
[FIX] fix typo  in motion.md
  • Loading branch information
Remi-Gau authored Mar 21, 2024
2 parents 6d13c80 + 96a9437 commit 4c642bd
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/modality-specific-files/motion.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,10 +58,10 @@ 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 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.
Expand Down

0 comments on commit 4c642bd

Please sign in to comment.