> 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/illumina-trupath-genome/additional-information/demo-data.md).
# Demo Data
This page describes how to access different types of demo data.
## Demo Data on Platform Core
Demo Data on Platform Core may be accessed via regional DRAGEN bundles. Navigate to the "Illumina TruPath Genome Folder" within each DRAGEN bundle.
FASTQ Inputs of varying High Molecular Weight (HMW) and Standard Molecular Weight (SMW) extractions are provided as examples using the HG002 NIST Truthset sample, as well as outputs for each.
Additional demo data may be accessed for public TruPath Genome datasets, including six HG002 (GM24385/NA24385) libraries—three HMW and three SMW sample extractions sequenced on a NovaSeq X Series C8 flow cell from 350 ng dsDNA.
ORA FASTQ pairs and matching DRAGEN outputs are provided so you can explore TruPath performance across extraction methods and DNA integrity, intended for Research Use Only (RUO). Navigate to the "TruPath Public Datasets" entitled bundle for the desired region and attach to a given Platform Core project to explore data outputs.
## Demo Data on Basespace
Similarly, Demo Data on Basespace may be accessed in the "Demo Data" section. Navigate on the left hand panel to select "Demo Data." Search "Illumina TruPath Genome" for accessing demo data sequenced on the NovaSeq X and import 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/illumina-trupath-genome/additional-information/demo-data.md?ask=&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.
