Naming conventions of entities and suffixes

Entities and suffixes

The boring stuff but useful...

As mentioned in main description, Muscle-BIDS uses various standardized entities and suffixes. Any toolbox is allowed to add as many of those as they want. However, if one uses non-standard entities and suffixes other software packages will probably not know how to use them. The list of BIDS entities can be found here and an overview of how to use entities and which are OPTIONAL or REQUIRED can be found here.

Entities

Within QMRITools the following entities are used. Based on these values the software will know how to handle the data for further processing.

The class words (vol, stk, chunk, rep, acq) are chosen by the Class of the dataset in the config file, see the Muscle-BIDS manual.

Suffixes: data type

The current data-type suffixes are recognized and can be automatically be processed and have their own folders. The data type is set by the Type of the dataset in the config file:

Suffixes: Folder specific

For each data folder, the data that can be stored there is defined by its suffix or combination of suffixes, e.g. "_t1w_fs", "_dwi_ivim_dti", or "_mese_t2". Although any suffixes can be combined and used the following suffixes related to data acquisition and type currently have meaning within QMRITools.

Suffixes: Data processing

When the raw input data is processed its outputs are stored in the derived data folder (by default 03_derivatives, and 04_merged for merged data and segmentations, see files and folders). Within the derived data folder a new Muscle-BIDS structure is created identical to that of the source data.

QMRITools uses suffixes to indicate what data is generated. The following suffixes are used: