> 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/microarray/general/microarray-general-troubleshooting-list/000001484.md).

# How to identify which Manifest and Cluster Files were used to generate a GTC File?

Illumina software such as Beeline, GenomeStudio, or BlueFuse Multi may return errors when loading a GTC (Genotype Call) file if the Product Files (Manifest and/or Cluster File) do not exactly match those used during GTC generation.

To ensure compatibility, follow the steps below to identify the Product Files used during GTC generation:

1. Right click the GTC file and open it in a text editor, like Notepad++.

   ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-42cfe693c76cba2d18d29207c9a521fc7e7523b8%2Fimage1.jpg?alt=media)

**Figure 1.** Open a GTC file with a text editor.

2. The GTC file is encoded in a non‑human‑readable (binary) format, however, certain embedded text strings—such as the Manifest and Cluster file names—remain human‑readable.
3. Use the search function (Ctrl+F) in the text editor and search for “.bpm”, which is the file extension for the manifest file.
4. Similarly, use Ctrl+F to search for “.egt” to locate the cluster file name.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-a2a77aa0bcd71c67d2ffe86676254443e08095f5%2Fimage2.jpg?alt=media)

**Figure 2.** Identifying the product files (manifest and cluster files) used to generate a GTC file.

\
\
\ <br>

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