> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/dragen-clinical-research-apps/readme/dragen-solid-wgs-tn-pipeline/setup/launching-analysis.md). # Launching Analysis ## UI Options ### Manual Launch of pipeline To manually launch an analysis, configure Analysis Software to run in Platform Core with the following parameters. #### General | Parameter Name | Description | Required | Default | | -------------- | -------------------------------------------------------------------------------------------------------------- | -------- | --------------------- | | User Reference | The custom name of the analysis for later identification. | Yes | Empty | | User Tags | Tags for the analysis to help with categorization and identificaion, enhancing organization and searchability. | No | Empty | | Notification | Add a user to be notified when the analysis completes. | No | No user selected | | Output Folder | The path to the analysis output folder. | No | Project output folder | #### Input Files | Parameter Name | Description | Required | Default | | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------- | | Samplesheet | The SampleSheet.csv for the analysis | Yes | SampleSheet.csv in Input Folder | | Input Directory | The input folder that contains \[bcl, fastq, bam, cram] files to analyze. Multiple input \[fastq, bam, cram] folders can be specified. | Yes | No folder selected | | Custom Parameters Config File | The custom parameters config file for the analysis. | No | No file selected | | Custom Resources Directory | The custom resoruces directory used for the analysis. | No | No folder selected | #### Settings | Parameter Name | Description | Required | Default | | ---------------------- | ----------------------------------------------------------------------------------- | -------- | ------- | | Input Type | The type of files in the Input Folder(s): bcl, fastq, bam, cram. | Yes | bcl | | Reference Genome | The reference genome used for the analysis: \[hs37d5\_chr, hg38]. | Yes | hg38 | | Enable Ora Compression | Compress fastq files using ora compression. \[Only applies when Input Type is bcl]. | No | true | | Enable Post Processing | Use the post-processing scripts at the end of the pipeline analysis. | No | false | | Sample IDs | Optional subset of Sample IDs or Pair IDs to analyze. A comma-separated list. | No | Empty | #### Resources | Parameter Name | Description | Required | Default | | -------------- | ----------------------------------------------------------------------------------- | -------- | ------- | | Storage Size | The storage size to allocate for the analysis. The minimum required value is Large. | Yes | Large | Other available options for the storage size: * "1.2TB" if option selected is Small * "2.4TB" if option selected is Medium * "7.2TB" if option selected is Large * "16TB" if option selected is XLarge * "32TB" if option selected is 2XLarge * "64TB" if option selected is 3XLarge > **Note:** It is recommended to reserve storage size twice the size of the BCL run folder, or the input fastq.gz or bam files, four times the size of the cram file (cram is 30-70% of the bam), and 8 times the size of the fastq.ora (fastq.ora is about 25% of fastq.gz). For information about using pipelines, refer to the BioInsight Platform Core documentation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.bioinsight.illumina.com/dragen-clinical-research-apps/readme/dragen-solid-wgs-tn-pipeline/setup/launching-analysis.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.