Last updated: 2022-10-21
Checks: 2 0
Knit directory: lglasso_data_analysis/
This reproducible R Markdown analysis was created with workflowr (version 1.7.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! 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 32545ac. 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/
Ignored: analysis/.Rhistory
Ignored: analysis/networkcommon_he.png
Ignored: data/heterc1/
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/index.Rmd) and HTML (docs/index.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 |
|---|---|---|---|---|
| Rmd | f1fba0a | Jie Zhou | 2022-10-21 | updated code for all the figures and tables |
| html | f1fba0a | Jie Zhou | 2022-10-21 | updated code for all the figures and tables |
| Rmd | 520f495 | Jie Zhou | 2022-10-21 | updated code for all the figures and tables |
| html | 520f495 | Jie Zhou | 2022-10-21 | updated code for all the figures and tables |
| Rmd | e045a4e | Jie Zhou | 2022-09-29 | complete version |
| html | e045a4e | Jie Zhou | 2022-09-29 | complete version |
| Rmd | dd32d09 | Jie Zhou | 2022-09-28 | create the repo |
| html | dd32d09 | Jie Zhou | 2022-09-28 | create the repo |
| html | 4d8e172 | Jie Zhou | 2022-09-27 | Build site. |
| Rmd | 716a0c1 | Jie Zhou | 2022-09-27 | Start workflowr project. |
This website demonstrate the specific procedures to reproduce the results in the paper Identifying Microbial Interaction Networks Based on Irregularly Spaced Longitudinal 16S rRNA sequence data. If you are only interested in how to use the R package lglasso associated with this paper rather than the results in the paper, you could just check the vignette by click the link, R package lglasso.
In the paper, we compared the proposed network identification algorithm lglasso with other conventional algorithms, i.e., glasso, neighborhood method, GGMselect-CO1 and GGMselect-LA. It is shown that the proposed lglasso outperform the other methods when the data are longitudinal. In order to carry out the simulation studies, in addition to the functions defined in package lglasso, we also defined some other functions to facilitate the simulation. These functions are then sourced into the simulation scripts.
Unfortunately, because the authors have not been authorized to disclose the real data used in the paper, we only demonstrate the procedure used to reproduce the results in simulation studies in the paper.
In order to run the script, you need to install the package first, using the following code,
remotes::install_github("jiezhou-2/lglasso",ref = "conditional")Note since in each figure, there are four scenarios being investigated which only differ in terms of their parameter settings, so only the code for one of the four scenarios are displayed. You can change the parameter setting to get the results for other settings. The same rule is used for the results in the tables. Also since the running code can take hours,if possible, I would suggest you to submit the code to a server instead of on your local computer.