knitr::opts_chunk$set( collapse = TRUE, comment = "#>" )
SigAct is a visualization tool for racking mutational signature activities. It is built based on the results of TrackSig. The objectives of SigAct are:
Please refer to the reference session for the complete reference and information for TrackSig
SigAct can be download from my github page following this link: https://github.com/xindizhang/SigAct.git
SigAct can also installed in R studio using the following code:
devtools::install_github("https://github.com/xindizhang/SigAct.git")
SigAct requires three results files from TrackSig: mistures.csv, changepoints.txt, phis.txt.
If you do not have these data avaliable, you can go to TrackSig. TrackSig takes VCF file of point mutation, generates all the above dataf files and a pdf file of mutational signature activity. For more detail, please see:
There are two sets of input example data, example script and example results in SigAct package for reference and learning purpose. The following example is demonstrated using these data files
SigAct can be used in RStudio by script or in Rshiny interfaces:
MutAct function takes the three required input file and returns a plot of mutational signature activty across pesudo-time, and a vector of signatures in the samples. You can use MutAct for both single sample and two chronologically orderd samples. For two samples, it gives a list of list containing the return values mentioned above for both samples.
See the code below for example:
# For single sample # Assign files sigActPoints <- system.file("extdata", "sigActPoints.csv", package = "SigAct") changepoints <- system.file("extdata", "changepoints.txt", package = "SigAct") phis <- system.file("extdata", "phis.txt", package = "SigAct") # Generate plot for sinhle sample sinResult <- MutSig(sigActPoints, changepoints, phis) # display the plot sinResult[[1]] # (continued) for two samples sigActPoints2 <- system.file("extdata", "sigActPoints2.csv", package = "SigAct") changepoints2 <- system.file("extdata", "changepoints2.txt", package = "SigAct") phis2 <- system.file("extdata", "phis2.txt", package = "SigAct") MutSig(sigActPoints, changepoints, phis, sigActPoints2, changepoints2, phis2)
SigAct provides function to check the proposed etiology of a given signature. It takes the signature ID as an input and returns its description
signature <- "S1" sigProposedEtiology(signature)
Example output for code above: [1] "S1: An endogenous mutational process initiated by spontaneous or enzymatica deamination of 5-mehylcytosine to thymine which generates G:T mistaches in double strand DNA. Failure to detect and remove these mistaches prior to DNA replication results in fixation of the T substitution for C."
For single sample, imply run function runSinApp()
and will lead you to a Rshiny page. You are allowed to select three file as input and a mutational signature activity plot will be generated. The signatures and their proposed etiology will pop up at the bottom at the interface page when you click the plot.
For two samples, run runMultiApp()
. A interface will show up and requires six input files. After all files are select, the mutational signature activity vs. pesudotime plot will be shown on the interface. You can check the mutational signatures and their proposed etiology for each plot.
Note that The code for this package is greatly inspired by TrackSig. Particular of the following scripts with function names in parethese:
Please follow the link to the github and the paper: * Github: https://github.com/YuliaRubanova/TrackSig * Literature: https://www.biorxiv.org/content/early/2018/11/15/260471 Authors: Yulia Rubanova, Ruian Shi, Roujia Li, Jeff Wintersinger, Nil Sahin, Amit Deshwar, Quaid Morris. TrackSig: reconstructing evolutionary trajectories of mutations in cancer. 2018. PCAWG Evolution and Heterogeneity Working Group, PCAWG network
Access data: Octomber and December, 2018
Infomation of the proposed etiology is based on Mutalisk, a wbsite tool for somatic genome mutations analysis For more infomation:
Access data: Octomber, 2018
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.