> 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/miseq-i100-series/instrumentation-miseq-i100-series-reference_material-list/000009212.md).

# File paths on the MiSeq i100 Series

**Background**

The MiSeq i100 Series instrument operates in Kiosk mode and the underlying Linux Operating System (OS) and file system directories are not available to the user. The following directories outline the file paths for the Run Output directory that is copied from the instrument to the Default Output folder for the configured External Storage.

**Run Output Directory**

* `//[server]/[share]/[output-directory]/[RunId]/`
  * `Analysis/[#]/Data/ where # is the analysis number.`
    * `../[Dragen App]/ora_fastq/ : FASTQ Files (DRAGEN/ORA)`
    * `../[Dragen App]/fastq/ : FASTQ Files (GZIP):`
    * `../Demux/ : Demultiplex_Stats.csv, Top_Unknown_Barcodes.csv, IndexMetricsOut.bin`
  * `Config/`
  * `CopyComplete.txt`
  * `Data/`
    * `BaseCall Files: ../Intensities/BaseCalls/L001/C[#].1/L001_1.cbcl where # is the cycle number.`
  * `FirmwareInformation.xml`
  * `InstrumentAnalyticsLogs/`
  * `InterOp/`
  * `Logs/`
  * `Manifest.tsv`
  * `RTAComplete.txt`
  * `RTAExited.txt`
  * `RunCompletionStatus.xml`
  * `RunInfo.xml`
  * `RunParameters.xml`
  * `SampleSheet.csv`

For each on-instrument Analysis, there is an additional `CopyComplete.txt` flag file generated in the output directory within the numbered Analysis folder (e.g. `//server/share/[output-directory]/[InstrumentRunId]/``Analysis/[#]/`) that signals completion of Analysis file copy.

\
\
\ <br>

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