Skip to content

Commit 0b73a7e

Browse files
committed
format fixes
1 parent 78bf458 commit 0b73a7e

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

15-workshop-wrapup.Rmd

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,23 +5,30 @@ Over the last two days, as well as the webinar in October, we've explored the st
55
## Summary of key messages
66

77
**<span style="color: green;">ORA and GSEA are different statistical analyses, and their inputs differ</span>**
8+
89
GSEA: Kolmogorov-Smirnov test, requires a ranked yet unfiltered gene list
910
ORA: Hypergeometric or Fisher’s Exact test, requires a filtered unranked gene list and experimental background gene list
1011

1112
**<span style="color: green;">Always correct for multiple testing</span>**
13+
1214
Never use unadjusted P values, as this will introduce many false positives. Different tools offer different multiple testing correction such as FDR or the more stringent BH. Always report your chosen method and the significance threshold applied to terms.
1315

1416
**<span style="color: green;">Different analysis methods will return different results</span>**
17+
1518
This is expected, due to underlying differences in database, algorithm, P value methods etc. As long as your methods are robust, sensible and reproducible, you can have confidence that your methods will stand up to scrutiny under peer review.
1619

1720
**<span style="color: green;">Ensure reproducibility</span>**
21+
1822
Lack of reproducibility through under-reporting methods is a common issue in this field (see Wijesooriya et al, linked below). Ensure to record all methodological details while you are working, including all the parameters and arguments applied, how the gene lists were generated, versions of databases and tools etc. If using R, specify a seed for constant random number generation in GSEA.
1923

2024
**<span style="color: green;">Interpret your results in their biological context</span>**
25+
2126
Functional categories are often broad and redundant. Use the FEA results as a guide, not the end point. Use visualisations and explore term redundancy methods to help focus results. Validate through aditional means according to the nature of your experiment, with the gold standard being wet-lab rather than *in silico* validation methods.
2227

2328
**<span style="color: green;">There are many databases and tool choices available</span>**
29+
2430
Suitability to your experiment depends on many factors, including:
31+
2532
- Your species, and what tools support it
2633
- What databases and gene sets are relevant to your experiment, from the general (eg GO) to the specific (eg cancer pathways)
2734
- Any privacy restrictions imposed on your data

0 commit comments

Comments
 (0)