> 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/miniseq/instrumentation-miniseq-reference_material-list/000002378.md).

# File Paths for the MiniSeq Control Software v2.0

The following are commonly used files and file paths for the MiniSeq.

**Temp Run Folder: This folder contains the raw sequencing data output.**

* Location: D:\Illumina\MiniSeq Sequencing Temp\&lt;run folder>
* Folder structure: (Note: the structure of other output folders is similar.)
  * Configs
  * Data
  * Intensities
    * BaseCalls
      * L001 (Base call files, aggregated per cycle)
        * L001 (An aggregated \*.locs file)
  * Images
    * Focus
      * L001 — Focus images (Shows images of clustering on the flow cell prior to cycle 1 of sequencing.)
  * InstrumentAnalyticsLogs (Log files describing instrument analytics steps)
  * InterOp (Binary files used by the Sequencing Analysis Viewer software)
  * Logs (Log files describing operational steps)
  * Recipe (Run-specific recipe file named with reagent cartridge ID)
  * RTALogs (Log files describing analysis steps)
  * RTAComplete.xml (this file is a marker file that indicates RTA processing is complete, and its presence triggers Local Run Manager to queue analysis)
  * RTAConfiguration.xml
  * RunInfo.xml
  * RunNotes.xml
  * RunParameters.xml

**MiniSeq Control Software Logs Folder**

* Location: D:\Illumina\MiniSeq Control Software

\
\
\ <br>

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