> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/icm/analyses/analysis-functionality/settings/library-file-management/microarray-library-files.md).

# Microarray Library Files

Microarray library files can be managed under *Microarray library files* section on *Other library files* tab on the *Library file management* page (Figure 1). The chip name and download source of stored Microarray library files will be shown in the table in this section.

<figure><img src="https://580316046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWMxqQAMFOJtu98OBk9KN%2Fuploads%2Fgit-blob-28a6c34218d46fb6c02ff559be73b5a9f262b76e%2Fimage%20(490).png?alt=media" alt=""><figcaption><p align="center">Figure 1. Microarray libraries files section in Connected Multiomics library file management page.</p></figcaption></figure>

Microarray probe tab files are used for processing microarray data in Connected Multiomics. When microarray intensity data files (e.g. Affymetrix .CEL files) are imported into a project, the chip type is automatically detected and the appropriate probe tab annotation file is downloaded. Thus, you would normally not need to manually add any probe tab annotation files.

To add a custom probe tab file (e.g. for a custom chip), click the **+ Add probe sequence** button at the *Microarray library files* section (Figure 1). Scroll to the bottom of the *Chip name* drop-down list and choose **Other / Custom**. Name the chip by typing into the *Custom name* box and click the **Create** button (Figure 2). Characters such as $ \* | \ : " < > ? / % cannot be used in custom names.

<figure><img src="https://580316046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWMxqQAMFOJtu98OBk9KN%2Fuploads%2Fgit-blob-7a5c28a58d0257e7c50a8245c6fa0d426be27d3a%2Fimage%20(491).png?alt=media" alt=""><figcaption><p align="center">Figure 2. Adding a custom probe tab file e.g. for a custom microarray chip.</p></figcaption></figure>

A custom probe tab file can be added from your local computer by clicking the My Computer option. When browsing for files, only the files with relevant file extensions will be visible (.probe\_tab and various compressed formats).

To add manifest, one needs to click the **+ Add manifest** button at the *Microarray library files* section (Figure 1). In the dialog, choose the right file from the dropdown list and push the Create button to compete the task (Figure 3).

<div align="center"><figure><img src="https://580316046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWMxqQAMFOJtu98OBk9KN%2Fuploads%2Fgit-blob-d4fc6041a970d5f2c8cc70f1d32ef005a9d02dea%2Farray-manifest.png?alt=media" alt="" width="320"><figcaption><p>Figure 3. Add manifest dialog for microarray data in Connected Multiomics.</p></figcaption></figure></div>


---

# 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://help.bioinsight.illumina.com/icm/analyses/analysis-functionality/settings/library-file-management/microarray-library-files.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.
