> 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-array/dragen-array-v1.3/product-guides/dragen-array-cloud-analysis/overview/dragen-array-genotyping.md).

# DRAGEN Array Genotyping

## Custom Configuration Options

When using **DRAGEN Array – Genotyping** cloud analysis type, you have the following configuration options available via the "Add Custom Configuration" option in Configuration Settings:

* **Output File Selection**: Flexibility to turn off/on specific output files
  * VCF output can be toggled on or off
  * Final Report output can be toggled on or off
* **GenCall Score Cutoff**: Adjustable threshold for genotype calling quality

## Recommendations

* **For non-human species**: It is recommended to turn off VCF output, as VCF generation requires genome mapping which is only provided for human genomes (GRCh37 and GRCh38).
* **For large sample numbers**: It is recommended to turn off Final Report output, as Final Report files can become very large with high sample counts and may impact performance.

## Applicable Arrays

For specific product compatibility, see the [Product & Analysis Compatibility](/dragen-array/dragen-array-v1.3/overview/our-features.md#_product_compatability) table.


---

# 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-array/dragen-array-v1.3/product-guides/dragen-array-cloud-analysis/overview/dragen-array-genotyping.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.