> 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-somatic-for-idt-custom-panels/review-outputs/outputs.md).

# Output Files

The pipeline generates the following key output files.

## Baseline Builder Outputs (Stage 1)

* **Systematic noise file:** `<output>/systematic-noise/systematic-noise-file/systematic_noise_v2.0_systematic_noise.bed.gz`
* **Excluded regions BED:** `<output>/systematic-noise/systematic-noise-file/blocklist.bed`

## Variant Calling Outputs (Stage 2)

For both tumor and normal samples:

* **Alignment file:** `<output>/<sample_name>/*.bam`
* **Variant call annotated file:** `<output>/<sample_name>/*.hard-filtered.vcf.gz`
* **TMB estimate**
* **Coverage and QC statistics**

The VCF file contains both passing variants (`FILTER="PASS"`) and non-passing variants that did not have sufficient supporting evidence.

For details on the most useful VCF fields, see [Key VCF Fields](/dragen-somatic-for-idt-custom-panels/review-outputs/vcf-fields.md). For navigating to your results in the BSSH or Platform Core UI, see [Where to Find Your Results](/dragen-somatic-for-idt-custom-panels/review-outputs/find-results.md).


---

# 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-somatic-for-idt-custom-panels/review-outputs/outputs.md?ask=<question>&goal=<user_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.