Annotating an Enrichment Map

Requirements

• Cytoscape version at least 3.2.0

• WordCloud version at least 2.0.2

• ClusterMaker version at least 0.9.3

Creating an annotation set

Once you have created your Enrichment Map, selecting “Annotate Clusters” in the EnrichmentMap app menu will let you add annotations. The “Annotate!” button creates a new annotation set. It should be noted that labels are automatically generated using WordCloud, and some manual adjustment will often be necessary.

Specifying gene set descriptions

You will need to select a column from the gene set descriptions drop down menu. This column is used by WordCloud to create a cloud from which the labels for the clusters are generated. This can be any column of strings, but in general labels are generated best when there are more words to work with.

Clustering

By default, the MCL (Markov Cluster) algorithm is used by clusterMaker. Alternatively, if you want to tune the parameters of clusterMaker yourself, you can run clusterMaker and select the column outputted by clusterMaker by clicking on the “Select cluster column” radio button in the “Advanced Clustering Options panel. These columns must be either integers, or lists of integers.

Laying out clusters

Selecting the “Layout nodes by cluster” option will rearrange the nodes in your network, grouping them by network and applying a Prefuse Force Directed Layout to each group. This reduces the amount of overlap between clusters and makes the annotations easier to read and interpret. Alternatively, repositioning can be done manually by selecting clusters in the table, dragging the nodes to a new location, and pressing the “Update” button. Multiple clusters can be selected by doing a Command+click for Mac users or Ctrl+click for other operating systems.

Changing labels

The text labels for each cluster can be manually adjusted. It is recommended to look at the WordClouds when doing this, by selecting “WordCloud” in the “Autofocus Preferences” menu. The parameters of WordCloud, such as specifying words to exclude, delimiters, and stemming, can be adjusted in its panel. For these changes to take effect, you must update both the WordCloud and the annotations. You can also manually edit the labels, by double-clicking on the cluster in the table, and changing the text.

Frequency Asked Questions

• How are the labels computed? The labels are computed by gathering all of the descriptions of each gene set and passing them to WordCloud. WordCloud parses these and assigns sizes to each word, proportional to the frequency of the words in the cluster, optionally normalized to consider how frequently the words occur in the entire network. These words are then sorted in order of size. One at a time, the largest word in the cloud is added until the label is 4 words long, or the next largest word is considerably smaller than the most recent word. An advantage is given to words in the same WordCloud groups (colours) as words already added to the label. This advantage can be specified in the Display Options Panel. ‘Considerably smaller’ is defined as below a specified fraction of the previous word’s size - by default set to be 0.3 from the first word to the second, 0.8 from second to third, and 0.9 from third to fourth. This can also be specified in the Display Options Panel.

• Why are some of the WordClouds blank, but still giving labels? Sometimes, WordCloud assigns a font size of 0 to words appearing infrequently. The annotation process will take this into consideration and still create a label out of these words.

• Why aren’t all of the clusterMaker algorithms available? Only some of the algorithms in clusterMaker produce output that can be easily parsed and used to partition the nodes for annotations.

Contact

Arkady Arkhangorodsky (aarkhangorodsky@gmail.com)

Ruth Isserlin (ruth.isserlin@utoronto.ca)

Known bugs

ClusterMaker doesn’t run properly on a second enrichment map

• This is a clusterMaker problem that the clusterMaker developers are working on fixing
• This also creates a problem when trying to save the session file
• To get around this, run clusterMaker through its menu rather than from the annotation panel