> 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/emedgene/release-notes/change_log/change_log_pipeline_529.md).

# Change log pipeline 5.29

## **Features:**

* Support for DRAGEN 3.10 (support for Graph coming in 5.30)
* Support for SV insertions called from Manta
* Compound heterozygous filter supports SVs (in addition to CNV/SNV/indel)
* Compound heterozygous feature for duos (single parent and proband)
* Annotate cases with Emedgene Curate data
* Support for DRAGEN repeats with ExpansionHunter. For customers using their own pipeline, custom header needs to be added to file.
* Added STR annotation engine for 1K Genomes and gnomAD
* Support for DRAGEN SV caller. For customers using their own pipeline, custom header needs to be added to file.
* Retrieve and annotate with variant interpretation from Emedgene Curate
* Support for ingesting files from ICA2 storage

## **Enhancements:**

* Improvement of de novo variant quality from DRAGEN
* Enhancement | Update revel generation script, change revel file path to fix GRCh38 bugs in revel data


---

# 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/emedgene/release-notes/change_log/change_log_pipeline_529.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.