> 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/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-reference_material-list/000002446.md).

# Demultiplex information from DRAGEN on the NextSeq 1000/2000

1. If performing **DRAGEN FASTQ generation locally**, demultiplex files can be found in following directory.

Other Locations > Computer >usr > local > Illumina > runs > \[runfolder] > Analysis > 1 > Data> Reports

*

```
* Demultiplex\_Stats.csv
```

```
* Top\_Unknown\_Barcodes.csv
* SampleSheet.csv

![](/files/rgWxN5XZv3W0ysVKNnc6)
```

DRAGEN analysis outputs an IndexMetricsOut.bin file to /\<Run Folder>/Analysis/#/Data/Reports/IndexMetricsOut.bin

To view the Indexing information within Sequencing Analysis Viewer, collect this file and place in the InterOp folder.

2. If using **DRAGEN FASTQ generation in the cloud**:

Select the link outlined below on the run and then follow the same path as described above.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-25e15757c94ec28d6691f69c2c34378dec4b8fb2%2Fimage2.png?alt=media\&token=0e018987-3257-49cb-b97a-e18000ffedc9)

3. If using **local DRAGEN bclConvert**, FASTQs are generated locally but uploaded to the cloud. DRAGEN output files are found in the BaseSpace Run, not the project.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-ec301e3330a0f3fbac9c74ea32ef8ec07ba33915%2Fimage3.png?alt=media\&token=dfd73294-cc9f-4e28-ba55-0a85b8208356)

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #2446), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000002446%20-%20Instrumentation%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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.illumina.com/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-reference_material-list/000002446.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.
