> 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/partek/partek-flow/tutorials/bulk-rna-seq/viewing-a-dot-plot-for-a-gene.md).
# Viewing a dot plot for a gene
In addition to the volcano plot showing all genes, we can view expression levels of each gene on a dot plot.
* Double-click the **Filtered feature list** data node to open the task report
* Click the **FDR step up** header in the 5uM vs. 0uM section to sort by ascending FDR step up
In the task report table, there is a column labeled View with three icons    in each row.
* Select  to open a dot plot for the gene KLHDC7B
The dot plot for KLHDC7B (Figure 1) shows each sample as a point with normalized reads count on the y-axis. Samples are separated and colored by treatment group.
Figure 1. Dot plot for KLHDC7B
For more information about the dot plot, please see the [Dot Plot](/partek/partek-flow/user-manual/visualizations/dot-plot.md) user guide. To return to the DESeq2 report, switch to the browser table with filtered feature list.
In the DESeq2 report, you can select  to view additional information about the statistical results for a gene or select  to view the region in Chromosome View. Chromosome View is discussed in the next section of the tutorial.
## Additional Assistance
If you need additional assistance, please visit [our support page](http://www.partek.com/support) to submit a help ticket or find phone numbers for regional support.
---
# 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/partek/partek-flow/tutorials/bulk-rna-seq/viewing-a-dot-plot-for-a-gene.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.
