# Pipelines is based on Cromwell and WDL

Cromwell is an open-source Broad Institute based tool that is a Workflow Management System for bioinformatics. The language that is used to write the “tasks” for Cromwell is called the Workflow Description Language (WDL or pronounced as wee-dle): a human readable language for data processing workflows.

The basic Cromwell workflow consists of the Workflow which is the main driver of your pipeline; Tasks which include how your input is processed either in files parsed in or strings/other data types; Output which are how your processed output is processed out in files or strings/other data types.

For more information on how Cromwell functions and works, the documentation website is very well curated and can be found [here](https://cromwell.readthedocs.io/en/stable/) with the GitHub repository (that also contains the link to the community forum) can be found [here](https://github.com/broadinstitute/cromwell).

All commands and and runtime parameters would be written in WDL where syntax definitions and descriptions can be found [here](https://support.terra.bio/hc/en-us/sections/360007274612).

**Note:** When running a workflow in Cromwell, you will usually be submitting two files which are the .wdl and .json file where the .wdl file will contain the basic Cromwell workflow written in WDL whereas the .json file will point to the input and output files/strings/data types that will be parsed through your workflow. The subsequent subsections here will explore how to run basic and genetics applications specific pipelines.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.finngen.fi/working-in-the-sandbox/running-analyses-in-sandbox/pipelines-tool-instructions/pipelines-is-based-on-cromwell-and-wdl.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.