> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/microarray/general/microarray-general-faq-list/000009345.md).

# Is a sample sheet required to run DRAGEN Array?

A sample sheet is not required to run DRAGEN Array, however, it can be used to enable analysis of samples located in different directories or to allow users to select specific samples for analysis rather than processing entire BeadChips.

**For DRAGEN Array Cloud:**

* Only IDAT files are used as input.
* The sample sheet contains the BeadChip barcode and sample position.

**For DRAGEN Array Local:**

* IDAT files can be used as input for 'genotype call' command.
* IDAT sample sheet can be a CSV or JSON formatted file with direct paths to sample IDAT files to enable analysis of samples from different directories.
* GTC files can be used as input for 'genotype gtc-to-vcf' command.
* GTC sample sheet can be a CSV or JSON formatted file with direct paths to sample GTC files to enable analysis of samples from different directories.

Both, DRAGEN Array Cloud and Local, sample sheet templates are available on the [DRAGEN Array Downloads](https://support.illumina.com/array/array_software/dragen-array-secondary-analysis/downloads.html) page.

**References**:

* [DRAGEN Array Sample Sheet templates](https://support.illumina.com/downloads/dragen-array-sample-sheet-templates.html)
* [DRAGEN Array User Guide](https://help.dragenarray.illumina.com/) under section [Input Files](https://help.dragenarray.illumina.com/product-guides/input-files)
* Illumina Knowledge [How to format file path for DRAGEN Array IDAT sample sheet and GTC sample sheet for Windows OS](/microarray/general/microarray-general-faq-list/000008510.md)

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                   |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #9345), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000008510%20-%20Microarray%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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 dynamically by asking a question.

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

```
GET https://knowledge.illumina.com/microarray/general/microarray-general-faq-list/000009345.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.