DAJIN2 is a genotyping tool for genome-edited samples, utilizing nanopore sequencer target sequencing.
The name DAJIN is derived from the phrase 一網打尽 (Ichimou DAJIN or Yīwǎng Dǎjìn), symbolizing the concept of capturing everything in one sweep.
conda create -n env-dajin2 -c conda-forge -c bioconda python=3.10 DAJIN2 -y
conda activate env-dajin2
pip install DAJIN2
[!CAUTION] If you encounter any issues during the installation, please refer to the Troubleshooting Guide
In DAJIN2, a control that has not undergone genome editing is necessary to detect genome-editing-specific mutations. Specify a directory containing the FASTQ/FASTA (both gzip compressed and uncompressed) or BAM files of the genome editing sample and control.
After basecalling with Guppy, the following file structure will be output:
fastq_pass
├── barcode01
│ ├── fastq_runid_b347657c88dced2d15bf90ee6a1112a3ae91c1af_0_0.fastq.gz
│ ├── fastq_runid_b347657c88dced2d15bf90ee6a1112a3ae91c1af_10_0.fastq.gz
│ └── fastq_runid_b347657c88dced2d15bf90ee6a1112a3ae91c1af_11_0.fastq.gz
└── barcode02
├── fastq_runid_b347657c88dced2d15bf90ee6a1112a3ae91c1af_0_0.fastq.gz
├── fastq_runid_b347657c88dced2d15bf90ee6a1112a3ae91c1af_10_0.fastq.gz
└── fastq_runid_b347657c88dced2d15bf90ee6a1112a3ae91c1af_11_0.fastq.gz
Assuming barcode01 is the control and barcode02 is the sample, the respective directories are specified as follows:
fastq_pass/barcode01
fastq_pass/barcode02
For basecalling with Dorado (dorado demux
), the following file structure will be output:
dorado_demultiplex
├── EXP-PBC096_barcode01.bam
└── EXP-PBC096_barcode02.bam
[!IMPORTANT] Store each BAM file in a separate directory. The directory names can be set arbitrarily.
dorado_demultiplex
├── barcode01
│ └── EXP-PBC096_barcode01.bam
└── barcode02
└── EXP-PBC096_barcode02.bam
Similarly, store the FASTA files outputted after sequence error correction with dorado correct
in separate directories.
dorado_correct
├── barcode01
│ └── EXP-PBC096_barcode01.fasta
└── barcode02
└── EXP-PBC096_barcode02.fasta
Assuming barcode01 is the control and barcode02 is the sample, the respective directories are specified as follows:
dorado_demultiplex/barcode01
/ dorado_correct/barcode01
dorado_demultiplex/barcode02
/ dorado_correct/barcode02
The FASTA file should contain descriptions of the alleles anticipated as a result of genome editing.
[!IMPORTANT] A header name >control and its sequence are mandatory.
If there are anticipated alleles (e.g., knock-ins or knock-outs), include their sequences in the FASTA file too. These anticipated alleles can be named arbitrarily.
Below is an example of a FASTA file:
>control
ACGTACGTACGTACGT
>knock-in
ACGTACGTCCCCACGTACGT
>knock-out
ACGTACGT
Here, >control
represents the sequence of the control allele, while >knock-in
and >knock-out
represent the sequences of the anticipated knock-in and knock-out alleles, respectively.
DAJIN2 allows for the analysis of single samples (one sample vs one control).
DAJIN2 <-s|--sample> <-c|--control> <-a|--allele> <-n|--name> \
[-g|--genome] [-t|--threads] [-h|--help] [-v|--version]
Options:
-s, --sample Specify the path to the directory containing sample FASTQ/FASTA/BAM files.
-c, --control Specify the path to the directory containing control FASTQ/FASTA/BAM files.
-a, --allele Specify the path to the FASTA file.
-n, --name (Optional) Set the output directory name. Default: 'Results'.
-g, --genome (Optional) Specify the reference UCSC genome ID (e.g., hg38, mm39). Default: '' (empty string).
-t, --threads (Optional) Set the number of threads. Default: 1.
-h, --help Display this help message and exit.
-v, --version Display the version number and exit.
# Download example dataset
curl -LJO https://github.com/akikuno/DAJIN2/raw/main/examples/example_single.tar.gz
tar -xf example_single.tar.gz
# Run DAJIN2
DAJIN2 \
--control example_single/control \
--sample example_single/sample \
--allele example_single/stx2_deletion.fa \
--name stx2_deletion \
--genome mm39 \
--threads 4
By using the batch
subcommand, you can process multiple files simultaneously.
For this purpose, a CSV or Excel file consolidating the sample information is required.
[!NOTE] For guidance on how to compile sample information, please refer to this document.
DAJIN2 batch <-f|--file> [-t|--threads] [-h]
options:
-f, --file Specify the path to the CSV or Excel file.
-t, --threads (Optional) Set the number of threads. Default: 1.
-h, --help Display this help message and exit.
# Donwload the example dataset
curl -LJO https://github.com/akikuno/DAJIN2/raw/main/examples/example_batch.tar.gz
tar -xf example_batch.tar.gz
# Run DAJIN2
DAJIN2 batch --file example_batch/batch.csv --threads 4
Upon completion of DAJIN2 processing, a directory named DAJIN_Results is generated.
Inside the DAJIN_Results directory, the following files can be found:
DAJIN_Results/tyr-substitution
├── BAM
│ ├── tyr_c230gt_01
│ ├── tyr_c230gt_10
│ ├── tyr_c230gt_50
│ └── tyr_control
├── FASTA
│ ├── tyr_c230gt_01
│ ├── tyr_c230gt_10
│ └── tyr_c230gt_50
├── HTML
│ ├── tyr_c230gt_01
│ ├── tyr_c230gt_10
│ └── tyr_c230gt_50
├── MUTATION_INFO
│ ├── tyr_c230gt_01.csv
│ ├── tyr_c230gt_10.csv
│ └── tyr_c230gt_50.csv
├── read_plot.html
├── read_plot.pdf
└── read_summary.xlsx
The BAM directory contains the BAM files of reads classified per allele.
[!NOTE] Specifying a reference genome using the
genome
option will align the reads to that genome.
Withoutgenome
options, the reads will align to the control allele within the input FASTA file.
The FASTA directory stores the FASTA files of each allele.
The HTML directory contains HTML files for each allele, where mutation sites are color-highlighted.
For example, Tyr point mutation is highlighted in green.
The MUTATION_INFO directory saves tables depicting mutation sites for each allele.
An example of a Tyr point mutation is described by its position on the chromosome and the type of mutation.
read_summary.xlsx describes the number of reads and presence proportion for each allele.
Both read_plot.html and read_plot.pdf illustrate the proportions of each allele.
The chart's Allele type indicates the type of allele, and Percent of reads shows the proportion of reads for each allele.
The Allele type includes:
[!WARNING] In PCR amplicon sequencing, the % of reads might not match the actual allele proportions due to amplification bias.
Especially when large deletions are present, the deletion alleles might be significantly amplified, potentially not reflecting the actual allele proportions.
[!NOTE] For frequently asked questions, please refer to this page.
For more questions, bug reports, or other forms of feedback, we'd love to hear from you!
Please use GitHub Issues for all reporting purposes.
Please refer to CONTRIBUTING for how to contribute and how to verify your contributions.
Please note that this project is released with a Contributor Code of Conduct.
By participating in this project you agree to abide by its terms.
For more information, please refer to the following publication: