> 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-faq-list/000003633.md).

# When will FASTQ files be N-masked in Local Run Manager, MiSeq Reporter, bcl2fastq, and BCL Convert?

A common step when creating FASTQ files is to trim adapter sequences. This removes sequencing artifacts that could negatively affect downstream analysis, such as mapping and alignment.

For libraries with short insert sizes (e.g. around 40bp or smaller), it's possible to observe entire reads of poly-N sequences. This is also referred to as N-masking. If the number of bases remaining after adapter trimming is less than `--mask-short-adapter-reads` value, the remaining sequences will be replaced with N-bases.

The following lists the Illumina software and the default `--mask-short-adapter-reads` used for analysis:

* Local Run Manager (LRM)
  * `--minimum-trimmed-read-length 32`
* MiSeq Reporter (MSR)
  * `--minimum-trimmed-read-length 32`
* bcl2fastq
  * `--minimum-trimmed-read-length 22`**Note:** bcl2fastq on BaseSpace (also referred to as Generate FASTQ) uses the default value of 35.
* BCL Convert
  * `--minimum-trimmed-read-length 22`

\
\
\ <br>

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