> 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/software/on-instrument-analysis-software/software-on-instrument-analysis-software-troubleshooting-list/000003817.md).
# Troubleshooting demultiplexing issues using onboard DRAGEN on the NextSeq 1000/2000
DRAGEN software outputs two demultiplexing files called Demultiplex\_Stats.csv and Top\_Unknown\_Barcodes.csv that can be used to troubleshoot demultiplexing issues.\
**Where are the Demultiplex\_Stats.csv and Top\_Unknown\_Barcodes.csv files located?**
\[runfolder]/Analysis/1/Reports
**What information is in the Demultiplex\_Stats.csv?**
The Demultiplex\_Stats.csv file provides the following information:
* sample ID
* index combination
* number of reads
* number of perfect index reads
* number of one mismatch index reads
* number of bases greater than or equal to Q30 (PF)
* mean quality score (PF)
**What information is in Top\_Unknown\_Barcodes.csv?**
The index and index2 columns provide the sequence of the unknown barcode as it was read by the instrument. The # Reads column provides the number of reads that the combination of index and index2 received.
When troubleshooting demultiplexing issues, use the index sequences identified for comparison to the expected index sequences (found in the sample sheet).
Possible causes for poor demultiplexing:
* Index sequences entered in the incorrect orientation in the sample sheet.
* Incorrect index sequences entered in the sample sheet (eg, Nextera vs TruSeq HT, or index A001 vs index A006).
* Poor Index Read sequencing quality (eg, index sequences containing lots of periods, representing “no calls,” near the top of the list).
\
\
\
| |
| :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #3817), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000003817%20-%20Software%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/software/on-instrument-analysis-software/software-on-instrument-analysis-software-troubleshooting-list/000003817.md?ask=&goal=
```
`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.