Last updated: 2024-09-17
Checks: 7 0
Knit directory: rss-net-results/
This reproducible R Markdown analysis was created with workflowr (version 1.7.1). 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 results in this page were generated with repository version b0dad18. See the Past versions tab to see a history of the changes made to the R Markdown and HTML files.
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 repository in which changes were
made to the R Markdown (analysis/t2d2012_gene.Rmd) and HTML
(docs/t2d2012_gene.html) files. If you’ve configured a
remote Git repository (see ?wflow_git_remote), click on the
hyperlinks in the table below to view the files as they were in that
past version.
| File | Version | Author | Date | Message |
|---|---|---|---|---|
| html | bd81094 | xiangzhu | 2020-12-02 | Build site. |
| html | f40af1c | xiangzhu | 2020-11-30 | Build site. |
| html | 71c765c | Xiang Zhu | 2020-06-02 | Build site. |
| html | 95af013 | xiangzhu | 2020-03-08 | Build site. |
| Rmd | 671088b | xiangzhu | 2020-03-08 | wflow_publish("analysis/*_gene.Rmd") |
| html | 8fde153 | xiangzhu | 2020-02-06 | Build site. |
| html | 8209433 | xiangzhu | 2020-01-30 | Build site. |
| html | 88f531a | xiangzhu | 2019-11-07 | Build site. |
| html | 700adc7 | xiangzhu | 2019-10-20 | Build site. |
| Rmd | dc54e9d | xiangzhu | 2019-10-20 | wflow_publish("analysis/t2d2012_gene.Rmd") |
For the given trait, prioritization results of network genes are summarized as the following two tables, the first one for network transcription factors (TFs) and the second one for network target genes (TGs).
\(P_1\) columns: 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;
“\(P_1^{\sf base}\)”, obtained from fitting RSS-NET baseline model \(M_0\);
“\(P_1^{\sf near}\)”, obtained from fitting RSS-NET enrichment model \(M_1\) to the “near-gene” control network;
“\(P_1^{\sf net}\)”: obtained from fitting RSS-NET enrichment model \(M_1\) to a given gene regulatory network;
“H-distance”: the physical distance, in base pair, between a given network gene and its nearest GWAS hit based on the same GWAS;
“Nearest hit”: the nearest GWAS hit to a given network gene, reported in publication of the same GWAS. The “none” values in this column indicate that there is no published GWAS hit on the same chromosome as the network gene. For display purposes only, when the value of “Nearest hit” is “none”, the corresponding “H-distance” shown below is the largest integer which can be represented (2147483647).
Differences between \(P_1^{\sf net}\) and reference \(P_1\) estimates (\(P_1^{\sf base}\) or \(P_1^{\sf near}\)) reflect the influence of regulatory network enrichment on genetic associations, which can help identify putatively new trait-associated genes.