> 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/iseq-100/instrumentation-iseq-100-reference_material-list/000002287.md).

# File Paths on the iSeq 100

**iSeq 100 File Paths:**

**Temporary Run Folder:** D:\Illumina\iSeq Runs\[RunFolder]

* Data
  * \Intensities\Basecalls\L001 (to locate BCL files)
* InterOp
* Logs
  * Cycles
* RTALogs
* Thumbnail\_Images
  * \L001\Cx.1 (where "x" corresponds to cycle number)
* RunCompletionStatus.xml
* RunInfo.xml
* RunParameters.xml
* SampleSheet.csv

**Default Output Run Folder**\*\*:\*\* D:\SequencingRuns\[RunFolder]

* Data
  * \Intensities\Basecalls\L001 (to locate BCL files)
* InterOp
  * IndexMetricsOut.bin
* Logs
  * Logs.zip
* RTALogs
* Thumbnail\_Images
  * \L001\Cx.1 (where "x" corresponds to cycle number)
  * \NormalizedFC for a zoomed-out picture of flow cell (useful in certain troubleshooting instances)
* RunCompletionStatus.xml
* RunInfo.xml
* RunParameters.xml
* SampleSheet.csv

**Secondary Analysis Files:** D:\Illumina\SequencingRuns\[Runfolder]\Alignment\_1 where "alignment\_#" is the number of the analysis/requeue, such as "1" for the initial analysis

* Present when Local Run Manager performed secondary analysis.
* DemultiplexSummaryF1L1.txt
* SampleSheetUsed.csv

**Pre-Run Check Logs**\*\*:\*\* D:\Illumina\iSeq Pre-Run Checks

* Images
* Logs
* Reports

**System Check Results**\*\*:\*\* D:\Illumina\iSeq System Checks\[Date System Check performed]

**Control Software Logs**\*\*:\*\* C:\Program Files\Illumina\iSeqSbsControlSoftwareServer\Logs

**Universal Copy Service (UCS) Logs**\*\*:\*\* C:\ProgramData\*\Illumina\UniversalCopyService\Logs\
\*The ProgramData folder may be hidden. To un-hide files, click on the View tab in the File Explorer window and ensure the box for “Hidden items” is checked.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #2287), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000002287%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/iseq-100/instrumentation-iseq-100-reference_material-list/000002287.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.
