> 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/general/software-general-reference_material-list/000002685.md).

# How to add a Custom Reference Genome in Local Run Manager

Local Run Manager (LRM) allows for use of custom reference genomes for alignment.

In order to use a custom reference genome in LRM, the genome files must be set up with a specific folder structure.

The path to a reference genome is:

**C:\Illumina\Genomes\&lt;Species>\&lt;Agency>\&lt;Version>\&lt;Sequence>\WholeGenomeFasta\genome.fa**

The default location for reference genomes in LRM is \*\*C:\Illumina\Genomes\*\*. However, the default location can be changed.

To check the default location in LRM: From *Local Run Manager* > *Tools* > *System Settings* > *System Configuration*.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-9ad0145cba268a1d603a394cfef03b4cf6bacbca%2Fimage1.png?alt=media\&token=fb674e9a-d804-461e-afc9-95920f6ce60a)

To create the specific folder structure for the custom reference genome:

1. In **C:\Illumina\Genomes**, create a folder named for the species of your reference genome.
2. In the species folder, create a folder named for the agency that published the reference genome. For example UCSC, NCBI, or Illumina.
3. In the agency folder, create a folder named for the version of the reference genome. For example hg19, mm9, or 2005-10-07.
4. In the version folder, create a folder named **Sequence**.
5. In the Sequence folder, create a folder named **WholeGenomeFasta**.
6. Rename the reference genome FASTA file to **genome.fa**.
7. Add **genome.fa** and its associated **GenomeSize.xml** file to the **WholeGenomeFasta** folder. Example of the file path for the hg19 UCSC reference genome: **C:\Illumina\Genomes\Homo\_sapiens\UCSC\hg19\Sequence\WholeGenomeFasta\genome.fa**

**Notes:**

* The genome column must specify the location for the custom reference genome in the sample sheet. Example of the Genome column in sample sheet: **Homo\_sapiens\UCSC\hg19\Sequence\WholeGenomeFasta**
* In the LRM DNA Amplicon analysis module, variant annotation is supported for human genomes only, and not supported for custom genomes.

For more information, see the [Local Run Manager software guide](https://support.illumina.com/sequencing/sequencing_software/local-run-manager/documentation.html).

\
\
\ <br>

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