> 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/iscan/microarray-iscan-reference_material-list/000009868.md).

# How does the iScan determine the BeadChip type and select the appropriate scan settings file?

For every beadchip, the DMAP folder contains an .sdf file, which describes the physical dimensions of the beadchip in order to set the scanner to scan the beadchip properly. At the end of the .sdf file, a line assigns the assay type. Following is a screenshot of the end of an .sdf file for a GSA24v3.0 beadchip:

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

**Note**: although the Global Screening Array is an HTS beadchip, LCG and HTS beadchips are processed in very similar ways, with the major difference being the number of samples per chip (LCG have 8 or fewer samples per chip, HTS have 24 samples), hence both are classified by the iScan as LCG assay type beadchips, as they require the same scan parameters.

The choice of which scan settings file to apply for a given assay type is made in the iScan software through the Assay Mapping Tab in the options menu. In the scanner software, select the chevron to access the main menu, then select Tools > Options...

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

Next, select the Assay Mapping tab.

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

The Assay Mapping tab contains two columns, the "Assay Name" and "Scan Settings" columns. The "Assay Name" column lists the Assay types available for scanning on the iScan, and the "Scan Settings" lists the scan settings file that is currently assigned to the given assay types.

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

**Note**: upon selecting the individual Scan Settings assignments in the table, the entries are selectable through a drop-down menu, accessed by the carat on the right side of the entry. While it is possible to assign any existing scan settings file to any given Assay Name, Illumina strongly recommends against changing the settings, as any changes may result in suboptimal scanning results.

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

Reference:

[iScan System Product Documentation](https://support-docs.illumina.com/ARR/iScan/Content/ARR/FrontPages/iscan.htm)

\
\
\ <br>

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