Skip to content

Commit 2b03bf0

Browse files
authored
Update README.md
1 parent f97da67 commit 2b03bf0

1 file changed

Lines changed: 14 additions & 5 deletions

File tree

README.md

Lines changed: 14 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,19 @@
77

88
#### Workflow to conduct and plot GO analysis using FuncAssociate
99

10-
1. Generate a list of (foreground) genes and a suitable background
11-
2. Upload to DAVID or FuncAssociate and run appropriate analysis
12-
3. Save the result table as well as the 'entity attribute list'
13-
4. Plot results using plotFuncAssDots()
10+
**1. Generate a list of (foreground) genes and a suitable background**
11+
12+
A suitable background often is not the whole genome but should represent the set of genes that *could* be found in the analysis, e.g. because they contain alternative splicing events or are expressed in the control sample. It is better to use a unique gene identifier such as the ENCODE gene ID rather than the gene name. Gene names change.
13+
14+
**2. Upload to FuncAssociate (or DAVID) and run appropriate analysis**
15+
16+
Examples can be found in the *input* folder. Find [FuncAssociate](http://llama.mshri.on.ca/funcassociate/) and [DAVID](https://david.ncifcrf.gov/).
17+
18+
**3. Save the results table as well as the 'entity attribute list'**
19+
20+
if using FuncAssociate. Examples in the *input* folder.
21+
22+
**4. Plot results using *plotFuncAssDots()***
1423

1524
Huge categories will be removed. If categories overlap more than a threshold, only the more significant one will be kept. Remaining categories will be plotted such that the LOD is on the x-axis, dot size represents the number of genes from the category that were in the foreground, and color reflects p-value:
1625

@@ -25,7 +34,7 @@ plotFuncAssDots(file="input/FuncAssociate_results.tsv",
2534
wid=9, hei=4.5)
2635
~~~~
2736

28-
See plot in _output_ folder for result.
37+
See plot in *output* folder for result.
2938

3039
#### _Disclaimer:_
3140
Input checking is imperfect. If it doesn't work, check that you are submitting the correct files.

0 commit comments

Comments
 (0)