Last updated: 2020-04-24
Checks: 2 0
Knit directory: BgeeCall_practical/
This reproducible R Markdown analysis was created with workflowr (version 1.6.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! 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 6da0a8d. 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/
Untracked files:
Untracked: PCA_dim_1vs2.png
Untracked: PCA_prop_explained_variance.png
Untracked: analyis.R
Untracked: dif_expressed_genes.tsv
Untracked: inputFile.tsv
Untracked: merge.R
Untracked: release.tsv
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/exercices.Rmd) and HTML (docs/exercices.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 | 6da0a8d | Julien | 2020-04-24 | wflow_publish(files = c(“analysis/analysis.Rmd”, “analysis/classes_description.Rmd”, |
4 RNA-Seq libraries of Drosophila melanogaster just arrived in your RStudio cloud project. All data you need are stored in the input_files directory at the root of your project. You and your virtual colleague have one hour to analyse these data and escape the Zoom room.
Generate present/absent expression calls for the RNA-Seq library SRX109273.
R commands are available in the page One library
Explanation of BgeeCall classes and their most important slots are available in the page BgeeCall classes
Important information :
D. melanogaster NCBI ID : 7227
GTF gene annotations file and fasta transcriptome file are in the directory input_files/ensembl
fastq files are in the directory input_files/fastq/SRX109273/
use /cloud/project/output_files as your working_path
use /cloud/project/output_files/SRX109273 as your output_dir
Even if the generation of kallisto index takes time, you can still manage to escape the Zoom room
Generate present/absent expression calls for the libraries SRX109272 using a file as input R commands and explanation of columns of the file are available in the page List of libraries Explanation of BgeeCall classes and their most important slots are available in the page BgeeCall classes
Important information :
A template of the tsv (Tabular Separated Values) file is available at input_files/inputFile.tsv. You can edit it in RStudio with the function file.edit(“PATH_TO_FILE”) or in the terminal. This file already contains information to run BgeeCall for library SRX109273 (exercice 1). You can keep these information and run BgeeCall for 2 libraries or remove them and run BgeeCall only for library SRX109272.
fastq files of library SRX109272 are in the directory /cloud/project/input_files/fastq/SRX109272/ Do not forget to provide the same working_path than in exercice 1 in order to use previously generated kallisto index
Information about the cutoff for this library are available at /cloud/project/YOUR_OUTPUT_DIR/gene_cutoff_info_file.tsv
Fortunatly your collaborator worked well and run BgeeCall on the 2 remaining libraries. She even merged TPM values of the 4 libraries in one file where rows correspond to genes and columns correspond to libraries. More importantly, she only kept in this file genes considered as present in the 4 libraries. Everything is ready for downstream analysis. She is now counting on you to do a PCA on these data
Important information :
The file generated by your collaborator is available at input_files/downstream_analysis/present_TPMs.tsv The code to run the PCA is described in the page Processing data
Once more your collaborator was extremely productive. She merged raw counts of the 4 libraries in one file where rows correspond to genes and columns correspond to libraries. More importantly, she only kept in this file genes considered as present in the 4 libraries. She is now counting on you to do a differential expression analysis on these data.
Important information :
The file generated by your collaborator is available at input_files/downstream_analysis/present_counts.tsv The code to run the PCA is described in the page Processing data
Congratulations!!!! You managed to escape the Zoom room on time. Are you sure you did not copy/paste R code without trying to understand it? If you want more do not hesitate to run again the differential expression analysis taking as input the file input_files/downstream_analysis/present_counts.tsv. This file contains all genes (present and absent)