> 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-genomics-suite/user-manual/visualizations.md).

# Visualizations

This user guide illustrates:

* [Dot Plot](/partek/partek-genomics-suite/user-manual/visualizations/dot-plot.md)
* [Profile Plot](/partek/partek-genomics-suite/user-manual/visualizations/profile-plot.md)
* [XY Plot / Bar Chart](/partek/partek-genomics-suite/user-manual/visualizations/xy-plot-bar-chart.md)
* [Volcano Plot](/partek/partek-genomics-suite/user-manual/visualizations/volcano-plot.md)
* [Scatter Plot and MA Plot](/partek/partek-genomics-suite/user-manual/visualizations/scatter-plot-and-ma-plot.md)
* [Sort Rows by Prototype](/partek/partek-genomics-suite/user-manual/visualizations/sort-rows-by-prototype.md)
* [Manhattan Plot](/partek/partek-genomics-suite/user-manual/visualizations/manhattan-plot.md)
* [Violin Plot](/partek/partek-genomics-suite/user-manual/visualizations/violin-plot.md)

This user guide assumes the user is familiar with the hierarchy of spreadsheets and analysis in Partek Genomics Suite.

Many plots available in Partek Genomics Suite are not discussed in this user guide. A more thorough review of Partek Genomics Suite visualizations can be found in **Chapter 6: The Pattern Visualization System** of the Partek User's Manual available from **Help > User’s Manual** in the Partek Genomics Suite main toolbar.

There is no specific data set for this tutorial. You may use one of your own microarray experiments or use a data set from one of our tutorials.

Visualizations are generated using data from a spreadsheet. Some visualizations allow interactive filtering on the plot, but others do not. If you only wish to include certain rows or columns in a visualization, you may need to create a spreadsheet with only the rows or columns of interest by applying a filter and cloning the spreadsheet.

In general, probe(set)/gene intensity values may be visualized from either an ANOVA spreadsheet or a filtered ANOVA spreadsheet. Because intensity data is stored in the parent spreadsheet, the parent and child spreadsheets should be visible in the spreadsheet navigator with the appropriate parent/child relationship (Figure 1).

![](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-ce54fb74263bccbf8d687bd8ff68f72fbac7a636%2Fimage2017-8-15%2011_49_25.png?alt=media)

Figure 1. Down\_Syndrome-GE is the parent spreadsheet; ANOVAResults and A are child spreadsheets of Down\_Syndrome-GE

## 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-genomics-suite/user-manual/visualizations.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.