This is the development page of the stackr.
What’s the difference with running stacks directly in the terminal?
Besides running stacks within R, not much, tiny differences here and there that speed up my RADseq workflow:
run_ustacks
and stackr will produce tables and figures automatically.Who’s it for?
It’s not for R or stacks beginners. stacks related issues should be highlighted on stacks google group.
To try out the dev version of stackr, copy/paste the code below:
if (!require("devtools")) install.packages("devtools")
devtools::install_github("thierrygosselin/stackr")
library(stackr)
To get the citation, inside R:
citation("stackr")
Web site with additional info: http://thierrygosselin.github.io/stackr/
stackr is maturing, but in order to make the package better, changes are inevitable. Argument names are very stable and follows stacks development closely.
stackr package provides wrapper functions to run STACKS process_radtags, ustacks, cstacks, sstacks, rxstacks and populations inside R.
Below, a flow chart showing the corresponding stacks modules and stackr corresponding functions.