# Definitions

**Annotations:**<span style="font-weight: 400;"> Data describing the gene models, pathways, ontologies, and other relevant biological information. Annotations are always associated with a reference genome and are consumed during a command execution through the argument or input variables.</span>

**Argument(s):** <span style="font-weight: 400;">Parameter variables that are defined with a key-value pair (</span>*<span style="font-weight: 400;">Example: --Threads 10</span>*<span style="font-weight: 400;">). Arguments are used by the tools during command building.</span>

**Command:**<span style="font-weight: 400;"> Fundamental unit of a tool that executes a specific job.</span>

**Data Store:**<span style="font-weight: 400;"> Stores all data types uploaded into the user's account. The data store is subdivided (sequence data, references, annotations, and metadata) for easy access.</span>

**Execution Flow:**<span style="font-weight: 400;"> Displays the list of tools in the execution order</span>

**FileList:**<span style="font-weight: 400;"> List of files used by a tool/command</span>

**File:**<span style="font-weight: 400;"> A single file used by a tool/command</span>

**Metadata:**<span style="font-weight: 400;"> Data that describes an experiment. Metadata is used for data analysis through the options, argument, or input variables.</span>

**Merge Step:**<span style="font-weight: 400;"> A step in a pipeline that merges all the input files into a single output file.</span>

**My Pipelines:**<span style="font-weight: 400;"> Pipelines shown within a project. Pipelines can be copied from the Pipeline Library into a project.</span>

**Hub:**<span style="font-weight: 400;"> Pipelines are grouped into categories (Hub) based on function.</span>

**Input(s):** <span style="font-weight: 400;">Any data files used in a command. These are either uploaded by the user or generated within an executed job.</span>

**Jobs:**<span style="font-weight: 400;"> Each execution of a pipeline is designated with a job ID.</span>

**Option(s):**<span style="font-weight: 400;"> Command parameters that are defined with a single word (</span>*<span style="font-weight: 400;">Example: --ignore</span>*<span style="font-weight: 400;">). These are used by the tools while command building.</span>

**Output(s):** <span style="font-weight: 400;">Data files created during pipeline execution.</span>

**Pipeline:**<span style="font-weight: 400;"> A set of computational tools, which run either sequentially or parallelly in order to achieve a specific data analysis objective. Tools/commands are designated as steps in a pipeline.</span>

**Pipeline Library:**<span style="font-weight: 400;"> The list of pre-configured pipelines available on the platform</span>

**Projects:** <span style="font-weight: 400;">Self-contained mini-workspaces, where sample sets can be analyzed independently without interference from other data, using multiple pipelines.</span>

**Reports:**<span style="font-weight: 400;"> Results of a pipeline execution are aggregated into easily understandable formats for quick viewing.</span>

**Sample Set:**<span style="font-weight: 400;"> A set of samples (cohort) selected within a project. Sample sets are used for data analysis.</span>

**Tool:**<span style="font-weight: 400;"> A bioinformatics software program that solves a specific biological problem. A tool can contain multiple commands (Example: Samtools index, sort)</span>