> 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/correlation-engine/about/demo-videos.md).

# Demo Videos

This page collects introductory and how-to demo videos for Correlation Engine.

{% hint style="warning" %}
Demo videos will be added here as they become available. Check back for updates.
{% endhint %}

## Getting Started

*Demo video: Introduction to Correlation Engine — platform overview, navigation, and first query.*

## Querying Genes and Concepts

*Demo video: How to query Correlation Engine with a gene name, concept, or bioset.*

## Importing Data from ICM

*Demo video: Exporting a differential expression result from Illumina Connected Multiomics and importing it into Correlation Engine.*

## App Walkthroughs

*Demo video: QuickView, Disease Atlas, Body Atlas, and Pharmaco Atlas — a complete walkthrough.*

*Demo video: Using Meta-Analysis to derive consensus gene signatures across multiple biosets.*

*Demo video: Pathway Enrichment (Biogroups) and interpreting enrichment results.*

## Additional Resources

For a playlist of all available how-to and demo videos, see the [Illumina YouTube channel](https://youtube.com/playlist?list=PLKRu7cmBQlahGuzvRfL41txLRPAV3e2uZ).


---

# 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/correlation-engine/about/demo-videos.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.