> 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/bluefuse-multi/microarray-bluefuse-multi-troubleshooting-list/000005043.md).

# Important file types for analysis of BeadArray data in BlueFuse Multi

BlueFuse Multi uses different file types throughout installation, experiment import, and downstream data processing, each serving a specific purpose within the workflow.

Illumina scanning platforms such as the iScan and the NextSeq 550 generate Infinium BeadArray data (raw image and intensity data files- IDATs) that are required for downstream analysis in BlueFuse Multi. Compatibility of specific BeadChip types with the NextSeq 550 system varies. Refer to the Illumina Knowledge article *“*[Which Infinium BeadChip types can be scanned using the NextSeq 550?](/microarray/general/microarray-general-faq-list/000003871.md)*”* for detailed guidance.

A critical component of the BlueFuse Multi workflow is the annotation database, which must be installed and made available within the software environment. The annotation database contains probe-level information, genomic positions, and content-specific details required to interpret array data accurately. BlueFuse Multi integrates the raw data files with the annotation database to perform normalization, feature extraction, and result generation.

**Table 1.** Install File Types in BlueFuse Multi

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">File Type</td><td valign="top">Description</td><td valign="top">File Extension</td></tr><tr><td valign="top">Brf</td><td valign="top"><p>- BlueFuse Registration File obtained from Illumina Technical Support</p><p>- Required to register the copy of the software for versions 4.4 and below</p></td><td valign="top">.brf</td></tr><tr><td valign="top">Annotation database</td><td valign="top"><p>- Contains information about the human genome to aid in the interpretation of experimental results.</p><p>- Includes the position of genes, exons and publicly available data on CNV frequency shown in the DecisionTrack pane within BlueFuse Multi.</p><p>- Uses information from major public databases such as ENSEMBL for gene annotation, OMIM for inherited diseases, and DGV and dbVAR for genetic healthy or disease variants.</p><p>- Lists products eligible for analysis under the particular Annotation database. Products not listed cannot apply the Annotation database for analysis</p><p>- Used by BlueFuse Multi during analysis and visualization of experiments</p></td><td valign="top">.db</td></tr></tbody></table>

**Table 2.** BeadArray-Specific File Types used with CytoChip Module

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">File Type</td><td valign="top">Description</td><td valign="top">File Extension</td></tr><tr><td valign="top">GTC</td><td valign="top"><p>- Genotype call file that incorporates fluorescent image file information</p><p>- iScan software can be configured to create GTC file automatically as part of scanning or user may use Beeline software to convert IDATs to GTCs.</p><p>- BlueFuse Multi can automatically extract information from the GTC file name to identify the type of array, the barcode and specific subarray location on the slide, and assign the correct settings</p></td><td valign="top">.gtc</td></tr><tr><td valign="top">SNP Manifest File</td><td valign="top"><p>- Contains SNP probe information</p><p>- Specific for each BeadArray type</p><p>- After a SNP Manifest file is imported and used within a BlueFuse Multi database, it is stored directly in that database.</p></td><td valign="top">.bpm</td></tr><tr><td valign="top">SNP Cluster File</td><td valign="top"><p>- Provides reference information used in the analysis of the BeadArray</p><p>- After a SNP Cluster file is imported and used within a BlueFuse Multi database, it is stored directly in that database. The stored cluster file is managed by BlueFuse Multi and is accessed automatically during genotype calling and downstream analysis as required.</p></td><td valign="top">.egt</td></tr></tbody></table>

Additional resources:

* [BlueFuse Multi Software Guide](https://support.illumina.com/downloads/bluefuse-multi-software-reference-guide-15053620.html)
* [BlueFuse Multi Annotation Database](https://support.illumina.com/downloads/bluefuse-multi-annotation-dbs.html)
* Illumina Knowledge [Using Beeline to regenerate GTC files with an alternate cluster file or manifest file](/microarray/other-illumina-array-software/microarray-other-illumina-array-software-reference_material-list/000002205.md)
* Illumina Knowledge [How to generate VCF files from Illumina BeadArray data](/microarray/general/microarray-general-reference_material-list/000003079.md)

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                   |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #5043), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000005043%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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.illumina.com/microarray/bluefuse-multi/microarray-bluefuse-multi-troubleshooting-list/000005043.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.