Skip to content

Commit

Permalink
RF: reword/shorten "Participant names and other labels" referring to …
Browse files Browse the repository at this point in the history
…<label>s and <index>es
  • Loading branch information
yarikoptic committed May 10, 2019
1 parent b390ddc commit 372cfe7
Showing 1 changed file with 7 additions and 9 deletions.
16 changes: 7 additions & 9 deletions src/02-common-principles.md
Original file line number Diff line number Diff line change
Expand Up @@ -307,15 +307,13 @@ Example:

## Participant names and other labels

BIDS uses custom user-defined labels in several situations (naming of
participants, sessions, acquisition schemes, etc.) Labels are strings and MUST
only consist of letters (lower or upper case) and/or numbers. If numbers are
used we RECOMMEND zero padding (e.g., `01` instead of `1` if you have more than
nine subjects) to make alphabetical sorting more intuitive. Please note that the
sub- prefix is not part of the subject label, but must be included in file names
(similarly to other key names). In contrast to other labels, run and echo labels
MUST be integers. Those labels MAY include zero padding, but this is NOT
RECOMMENDED to maintain their uniqueness.
BIDS allows for custom user-defined `<label>`s and `<index>`es e.g., for
naming of participants, sessions, acquisition schemes, etc. Note that they
MUST use only allowed characters as described in [Definitions](02-common-principles.md#definitions)
above. In `<index>`es we RECOMMEND zero padding (e.g., `01` instead of `1`
if you have more than nine subjects) to make alphabetical sorting more
intuitive. Zero padding is NOT RECOMMENDED to be used to maintain their
uniqueness.

## Units

Expand Down

0 comments on commit 372cfe7

Please sign in to comment.