Last updated: 2019-11-07
Checks: 7 0
Knit directory: rss-peca/
This reproducible R Markdown analysis was created with workflowr (version 1.5.0). The Checks tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.
Great! Since the R Markdown file has been committed to the Git repository, you know the exact version of the code that produced these results.
Great job! The global environment was empty. Objects defined in the global environment can affect the analysis in your R Markdown file in unknown ways. For reproduciblity it’s best to always run the code in an empty environment.
The command set.seed(20180719) was run prior to running the code in the R Markdown file. Setting a seed ensures that any results that rely on randomness, e.g. subsampling or permutations, are reproducible.
Great job! Recording the operating system, R version, and package versions is critical for reproducibility.
Nice! There were no cached chunks for this analysis, so you can be confident that you successfully produced the results during this run.
Great job! Using relative paths to the files within your workflowr project makes it easier to run your code on other machines.
Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility. The version displayed above was the version of the Git repository at the time these results were generated.
Note that you need to be careful to ensure that all relevant files for the analysis have been committed to Git prior to generating the results (you can use wflow_publish or wflow_git_commit). workflowr only checks the R Markdown file, but you know if there are other scripts or data files that it depends on. Below is the status of the Git repository when the results were generated:
Ignored files:
Ignored: .Rhistory
Ignored: .Rproj.user/
Note that any generated files, e.g. HTML, png, CSS, etc., are not included in this status report because it is ok for generated content to have uncommitted changes.
These are the previous versions of the R Markdown and HTML files. If you’ve configured a remote Git repository (see ?wflow_git_remote), click on the hyperlinks in the table below to view them.
| File | Version | Author | Date | Message |
|---|---|---|---|---|
| html | 5eff990 | Xiang Zhu | 2019-08-30 | Build site. |
| html | 49314e0 | xiangzhu | 2019-08-20 | Build site. |
| Rmd | a09fb66 | xiangzhu | 2019-08-20 | wflow_publish(“analysis/scz2014_gene.Rmd”) |
| html | 38c96fc | xiangzhu | 2019-08-20 | Build site. |
| html | f31d109 | xiangzhu | 2019-08-20 | Build site. |
| html | 10d94f2 | xiangzhu | 2019-08-20 | Build site. |
| Rmd | 544854e | xiangzhu | 2019-08-20 | wflow_publish(“analysis/scz2014_gene.Rmd”) |
Prioritization results of network genes are summarized as two tables, one for network transcription factors (TFs) and the other for network target genes (TGs).
P1: posterior probability that at least one SNP within 100 kb of the transcribed region of a given network gene (specified by Gene, Chr., Start and End columns) has non-zero effect on the trait of interest;
H-distance: the physical distance, in base pair, between a given network gene and its nearest GWAS hit;
Nearest hit: the nearest GWAS hit to a given network gene, reported in the corresponding GWAS publication. The “none” values in this column indicate that there is no published GWAS hit on the same chromosome as the network gene.
Note that Baseline P1 and Enrichment P1 are obtained from fitting RSS-NET baseline and enrichment models respectively. Differences between Baseline P1 and Enrichment P1 reflect the influence of network enrichment on genetic associations, which can help identify putatively new trait-associated genes.
TODO: explain Near-gene P1.