> 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/basespace/sequence/plan-runs/set-up-planned-run/custom-noise-baseline-file.md).

# Custom Noise Baseline File

If using somatic mode, you can generate a custom noise baseline file. The noise baseline file is built using normal samples that do not match to the subject the samples are from. The recommended number of normal samples is 50.

To generate a custom noise baseline file, use one of the following methods:

* Use the DRAGEN Bio-IT Platform server. See the *DRAGEN Bio-IT Platform Online Help* for instructions.
* Use DRAGEN Baseline Builder App on BaseSpace Sequence Hub. Use the BCL Convert pipeline in BaseSpace Sequence Hub Run Planning to generate FASTQ files. After the sequencing run is complete and 50 samples are available, input the FASTQ files into the DRAGEN Baseline Builder App.

{% hint style="info" %}
For instructions to import noise baseline files to your instrument, refer to the system guide for your instrument `NextSeq 2000 System Guide (document # 1000000109376)`
{% endhint %}


---

# 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/basespace/sequence/plan-runs/set-up-planned-run/custom-noise-baseline-file.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.