Skip to content

Commit

Permalink
Initial commit, ready for testing and debugging. Fixed git ignoring t…
Browse files Browse the repository at this point in the history
…he majority of files here. Don't know why it did that in the first place.
  • Loading branch information
michael-weinstein committed Jan 16, 2020
1 parent 341f767 commit 94ede02
Show file tree
Hide file tree
Showing 47 changed files with 4,535 additions and 0 deletions.
77 changes: 77 additions & 0 deletions Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
FROM python:3.6.7

MAINTAINER Michael M. Weinstein, Zymo Research
LABEL version="0.0.1"

WORKDIR /

RUN apt-get update && \
apt install -y autoconf automake make gcc perl zlib1g-dev libbz2-dev liblzma-dev libssl-dev libncurses5-dev && \
cd tmp && \
wget https://github.com/samtools/samtools/releases/download/1.9/samtools-1.9.tar.bz2 && \
tar -xjvf samtools-1.9.tar.bz2 && \
rm samtools-1.9.tar.bz2 && \
cd samtools-1.9 && \
./configure && \
make && \
make prefix=/opt install && \
cd /tmp && \
rm -rf samtools-1.9

ENV PATH "$PATH:/opt/bin"


#set up BWA
RUN cd /tmp &&\
wget https://github.com/lh3/bwa/archive/v0.7.16.tar.gz && \
tar -xvf v0.7.16.tar.gz && \
rm v0.7.16.tar.gz && \
cd bwa-0.7.16 &&\
make && \
cd /tmp && \
cp -r bwa-0.7.16 /opt/ && \
rm -rf bwa-0.7.16

ENV PATH "$PATH:/opt/bwa-0.7.16"


#set up minimap2
RUN cd /tmp &&\
wget https://github.com/lh3/minimap2/archive/v2.17.tar.gz && \
tar -xvf v2.17.tar.gz && \
rm v2.17.tar.gz && \
cd minimap2-2.17 && \
make && \
cd /tmp && \
cp -r minimap2-2.17 /opt/ && \
rm -rf minimap2-2.17

ENV PATH "$PATH:/opt/minimap2-2.17"


#set up scripts
RUN cd /opt && \
mkdir referenceBuild && \
mkdir referenceBuild/reference && \
mkdir miqScoreShotgun

COPY ./reference /opt/referenceBuild/reference

COPY ./requirements.txt /opt/referenceBuild

#doing expensive and unlikely to change build processes here to speed up testing builds
RUN cd /opt/referenceBuild/ && \
pip3 install -r requirements.txt && \
cd reference && \
echo "Indexing gut standard genomes" && \
bwa index zrGutStandard.fasta

#doing cheaper and likely to change build steps now
COPY . /opt/miqScoreShotgun

RUN cd /opt/miqScoreShotgun && \
rm -rf reference && \
mv /opt/referenceBuild/reference . && \
rm -rf /opt/referenceBuild

CMD ["python3", "/opt/miqScoreShotgun/analyzeStandardReads.py"]
674 changes: 674 additions & 0 deletions LICENSE

Large diffs are not rendered by default.

112 changes: 112 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,112 @@
# Shotgun Sequencing MIQ (Measurement Integrety Quotient) Calculator

*Terra incognita,* or land unknown, was a term used by cartographers to describe lands that were known to exist but had not yet been explored well enough to map. While this phrase disappeard from maps over the last few centuries, it is ever-present in science. Biases in microbiome analysis have been known to exist since nearly the time the field began, but for many experiments, they remain *terra incognita.* Exploring this area provides us with a critical next step in the evolution of microbiome research and the constant drive to improve our work.

There is always one more thing to learn.
– Steve Jobs

At Zymo Research, our motto is, "*The beauty of science is to make things simple*," and it is with this principle guiding our efforts that we offer you this software package.
Like many great scientific tools, this package hides much of the complexity of its inner workings in order simplify a common analysis. Under the hood of this system, you'll find [BWA](https://github.com/lh3/bwa "Github"), [Samtools](https://github.com/samtools/samtools), and the [NGS MIQ Score Calculator](https://github.com/Zymo-Research/miqScoreNGSReadCountPublic), the last of which was initially developed for this application. The mission of this application is identical to the [ZymoBIOMICS](https://www.zymoresearch.com/pages/zymobiomics-portfolio) mission: increasing the reproducibility and standardization of microbiome analysis. Due to the multiple dependencies and need for reproducibility of results and environment in this software package, we have packaged it entirely within a [Docker](https://www.docker.com) image to ensure consistency between machines and runs.

#### Publication
Publication on this method is pending. Watch this space for news and a link once it is available on bioRXiv.

## Quick Start Guide

This guide assumes you already have Docker installed and running on your system as well as the privileges to execute Docker commands. To learn more about Docker, please check out [Katacoda](https://www.katacoda.com) for several excellent interactive tutorials on the use of Docker.

#### Downloading and building the image
```
git clone --recursive https://github.com/Zymo-Research/miqScoreShotgunPublic.git
cd miqScoreShotgunPublic
docker build -t miqscoreshotgun .
```

#### Running the analysis
The simplest method to run this analysis (in this writer's opinion, at least) is to have the data ready and waiting in a file structure already set up to mount to the container. Using this practice will ensure that the container finds the expected input files and will output data to the expected location as well as providing an easy system to script against for automation, with iteration only requiring the movement of files.

To do this, create the following directory structure somewhere on your system where you have read and write permissions:

```
.
+-- input
| +-- sequence
| +-- standard_submitted_R1.fastq
| +-- standard_submitted_R2.fastq
+-- working
+-- output
```
This directory can have any name desired (**dataMountDirectory** will be used from here on as its name) so long as it conforms to good naming practices. The files standard_submitted_R1.fastq and standard_submitted_R2.fastq are where this docker will look for read 1 and read 2 data, respectively, if no other files are specified. If running in SE or LONG mode, only standard_submitted_R1.fastq will be used. These file names will work even if the fastq files are compressed using gzip.

To run this container, you need only supply the path to the above-described directory structure and a sample name:

```
docker container run -v [pathTo]/dataMountDirectory:/data -e SAMPLENAME=My_Sample_Name miqscoreshotgun
```

For more advanced usage, several parameters can be set using environment variables passed into the container at runtime. The environment variables that can be passed are as follows:

| Variable | Type | Default | Description |
| --------------- |:--------------:|:--------:|-------------|
SAMPLENAME | string | **REQUIRED** | A name for the sample, should conform to good file-naming practices
MAXREADCOUNT | integer | 0 | Maximum reads to allow for analysis, will stop if a larger set of reads is provided. (Enter a value less than 1 for no limits)
FORWARDREADS | string | /data/input/sequence/standard_submitted_R1.fastq | Path to forward reads within the container (likely a mounted folder)
REVERSEREADS | string | /data/input/sequence/standard_submitted_R2.fastq | Path to forward reads within the container (likely a mounted folder)
SEQUENCEFOLDER | string | /data/input/sequence | Path to folder containing input sequences within the container
WORKINGFOLDER | string | /data/working | Path to working folder for temporary files
OUTPUTFOLDER | string | /data/output | Folder within the container to write output data
REFERENCEGENOME | string | [folderWithPackage]/reference/zrCommunityStandard.fa | File containing the reference sequence for the standard within the container
FILENAMINGSTANDARD | string | ZYMO | How sequence files will be named (other option is "illumina")
MODE | string | PE | Running mode. PE for paired-end, SE for single end, LONG for Nanopore reads. PE and SE use similar alignment but different analysis logic. SE and LONG use the same analysis logic, but different aligners.


## OUTPUT
All outputs will be written to the designated output folder for the container, which will unmount upon completion of the run.

There will be two primary output files, one report in HTML format and one in JSON format. Examples of these can be seen [here for HTML](https://github.com/Zymo-Research/miqScoreShotgunPublic/blob/master/exampleReport.html) and [here for JSON](https://github.com/Zymo-Research/miqScoreShotgunPublic/blob/master/exampleReport.json). The HTML report is designed to be viewed in a browser and gives an overview of the results for the sample. The JSON report, while human-readable, is designed primarily to facilitate analysis using an automated script. It also provides much more detailed information on the results than the HTML report.
In addition to the two primary files, there will be a log file that can be used in the event of a problem with analysis for additional information on the run. Finally, there will be several files generated by the DADA2 pipeline. If you are familiar with DADA2, you will be familiar with these outputs.

## Contributing

We welcome and encourage contributions to this project from the microbiomics community and will happily accept and acknowledge input (and possibly provide some free kits as a thank you). We aim to provide a positive and inclusive environment for contributors that is free of any harassment or excessively harsh criticism. Our Golden Rule: *Treat others as you would like to be treated*.

## Versioning

We use a modification of [Semantic Versioning](https://semvar.org) to identify our releases.

Release identifiers will be *major.minor.patch*

Major release: Newly required parameter or other change that is not entirely backwards compatible
Minor release: New optional parameter
Patch release: No changes to parameters

## Authors

- **Michael M. Weinstein** - *Project Lead, Programming and Design* - [michael-weinstein](https://github.com/michael-weinstein)
- **Aishani Prem** - *Testing, Design* - [AishaniPrem](https://github.com/AishaniPrem)
- **Mingda Jin** - *Testing, Code Review* - [jinmingda](https://github.com/jinmingda)
- **Shuiquan Tang** - *Design* - [shuiquantang](https://github.com/shuiquantang)
- **Jeffrey Bhasin** - *Design, Code Review* - [jeffbhasin](https://github.com/jeffbhasin)
- **Ryan Kemp** - *Design* - [Zymo Research](https://www.zymoresearch.com)
- **Brian Janssen** - *Design* - [Zymo Research](https://www.zymoresearch.com)
- **Christopher E. Mason** - *Guidance, Testing* - [Cornell University](https://research.cornell.edu/researchers/christopher-e-mason)

See also the list of [contributors](https://github.com/Zymo-Research/miqScoreShotgunPublic/contributors) who participated in this project.

## License

This project is not currently licensed, but will likely be licensed under the GNU GPLv3 License - see the [LICENSE](LICENSE) file for details.
This license restricts the usage of this application for non-open sourced systems. Please contact the authors for questions related to relicensing of this software in non-open sourced systems.

## Acknowledgments

We would like to thank the following, without whom this would not have happened:
* The Python Foundation
* The staff at Zymo Research
* The microbiomics community
* Our customers

---------------------------------------------------------------------------------------------------------------------

#### If you like this software, please let us know at [email protected].
#### Please support our continued development of free and open-source microbiomics applications by checking out the latest microbiomics offerings from [ZymoBIOMICS](https://www.zymoresearch.com/pages/zymobiomics-portfolio)
Loading

0 comments on commit 94ede02

Please sign in to comment.