Note: DeepSpCas9variants provides guide RNA designs and efficiency predictions with optimized scaffold.
The Load Example button is able to replicate the example inputs shown in this help page for quick testing of the DeepxCas9 web server. Simply click the Load Example button then press Submit Job to obtain an example results page.
Input Format: Nine formats reach the same designer, and each one resolves to the target sequences this model scores: FASTA, Gene Symbol, NMID, Ensembl ID, HGNC ID, Genomic Position, Edit Sequence (an unedited/edited pair), ClinVar ID and COSMIC ID. Picking one shows the fields it needs and hides the rest. Edit Sequence, ClinVar ID and COSMIC ID are the three formats that specify an edit, so those three also produce the homology-directed repair (HDR) donor columns described below.
Input Method (FASTA): You can either enter the FASTA text or upload a FASTA file.
.txt
.fa
.fasta
When uploading files, press the [+] button to add files. Uploaded files can be cleared by pressing either of the checkmark buttons.
Example Input:
>MIR99AHG/LINC00478 (chr21:16,587,284-16,587,784) CAGACAGCATTAGAGTTGGCTTGAGAATTGCCGTACTTTGCTTCCCTTTGTATGTATTTC TTGTATGCTGCCGAGTCACTGATGGCTAGCTCTGTCTGGCAAGTAATTCAAAAATGCTGT TTATGTAGAAAGGAAAGGTAGGGACTTTACCACACTCTGTCATTAAAGGGAGCAATTGAA GAACAAAGGAACTGAGTAAATACCTATATATTGCCTTTTGTGTTGCGAAACACTGTAGCA CAAACACATTTGTGTTCAGCCAAATGTTTTACTTCCTTTTGTAATAACGCATATAGTAGG TTGTCTCCACATATGTACAAGAATCCATATTTTATTTAAACGTATATAGTCAATTGTTCA TATTTATAGGCTGCAAACATTTCTCAATCTCAAAGACTTTTACATATCCACTCCCACACA GCTATTTGTTATTATTTTAAAAGTTCTTAAATTAAAAAAAAAAATAAAATATACTAATAT CTCTGTTGGTTGATTTTATTA
A gene identifier is looked up in Human (GENCODE v50 on GRCh38) or Mouse (GENCODE M39 on GRCm39). The selector appears with the four gene formats, and it is offered wherever the genome-wide off-target search offers Mouse, so a run that screens against the mouse genome can design in mouse as well.
A mouse symbol from an older nomenclature resolves to the current one and the job log states the substitution — Olfr1 designs against Or1e16. Whichever of the four gene formats is chosen, Mouse replaces the identifier box with Enter Mouse Gene Name or ID, which takes a mouse symbol or a mouse Ensembl gene ID. ClinVar ID and COSMIC ID carry no species selector: both are human variant databases, and both resolve against the human reference.
Olfr1
Or1e16
There is no HDR mode switch: the input format decides. When the input format specifies an edit — an unedited/edited sequence pair, a ClinVar ID or a COSMIC ID — every candidate guide is also reported with what it needs for HDR. The other six formats identify the target without specifying an edit, so no donor is designed from them and the donor columns are absent rather than blank.
Cut site (1-based in the target sequence) is the blunt SpCas9-family cut, between protospacer positions 17 and 18 — three bases from the PAM.
Cut site (1-based in the target sequence)
Each candidate carries these columns, in the results table and in the downloadable files alike:
Cut-to-edit distance (nt)
HDR donor rank in the target
Donor (sense)
Donor (antisense)
Donor length (nt)
Left arm (nt)
Right arm (nt)
Requested arms (nt)
Indel length not a multiple of 3
Blocking mutation
Donor note
What you can set: homology arm lengths (100/100 nt by default, 50/50, or a custom pair between 25 and 1000 nt), the donor strand, whether to add a blocking mutation, and the donor template type — a chemically synthesized single-stranded oligodeoxynucleotide (ssODN) by default, with the donor note saying when a template outgrows standard oligo synthesis and should be ordered as a long single-stranded DNA (ssDNA) fragment instead; long ssDNA for those longer templates; or a double-stranded DNA (dsDNA) duplex, which arrives as one Duplex donor (dsDNA) column instead of the strand pair. The guide sequence is deliberately not yours to specify — the guides are this model's own ranked candidates, and a donor is built for each of them.
Duplex donor (dsDNA)
Cloning Vector decides whether the results carry an ordering-ready oligo pair, and it is set to SpCas9 / lentiGuide-Puro (BbsI or BsmBI) by default. Every candidate then gains Oligo (forward) and Oligo (reverse), in the results table and in the downloadable files alike: the two strands that anneal into the digested vector, each presenting its own 4 nt 5' overhang — CACC on the forward strand, AAAC on the reverse. The guide between them is written (G/g)N19, position 1 replaced by the G the U6 promoter transcribes from.
Oligo (forward)
Oligo (reverse)
CACC
AAAC
Setting the vector to None (No Oligo Output) leaves both columns out rather than blank. The four overhang fields — Forward 5′, Reverse 5′, Forward 3′ and Reverse 3′ — override what the vector supplies; left blank, each takes the vector's own. A guide carrying anything outside A, C, G and T gives an empty pair, because there is nothing orderable to write.
The Off-target score (higher = less specific) column is a mismatch-tolerance score, not a count of sites in a genome. It asks a narrower question than its name suggests: for this guide, how much activity would survive a single mismatch, averaged over every single-mismatch variant of the protospacer. A guide that tolerates mismatches well is a guide that is more likely to cut somewhere it was not aimed at, which is why a higher number is the worse one.
It comes from the SpCas9 cutting frequency determination (CFD) table of Doench, Fusi et al. (2016), so it needs no genome and costs nothing beyond the on-target prediction. The table is indexed over the 20 nt protospacer and takes no PAM, so it describes the RNA-DNA duplex readout that SpCas9 and its engineered PAM variants share; what distinguishes those variants sits in the PAM-interacting domain, which the table does not read. It cannot tell you where an off-target is, and it does not know whether any of those variants occurs in your genome at all.
For that, set Genome-wide off-target search to Human or Mouse. That search adds one Genome-wide specificity (higher = more specific) column, which runs the other way round: there, higher is better. Every site it finds is condensed into that single number; the individual loci are not listed, so no chromosome, coordinate or strand for them reaches the table. The two are different measurements and both may appear. The sites that search finds are scored on the same table, so the two columns differ only in the question they answer -- one guide against every single-mismatch variant of itself, one guide against the sites a genome really holds -- and never in how a mismatch is weighed.
Genome-search scoring is where that last clause stops holding. The CFD table knows which base was swapped for which, and was fitted on SpCas9 with an NGG PAM; the MIT position weights (Hsu et al. 2013) know only how tolerant each position is, and were fitted across nucleases rather than on one. Neither is a superset of the other. Leaving the setting on CFD only is the behaviour described above; choosing CFD and MIT adds a second Genome-wide specificity, MIT (higher = more specific) column, aggregated from the same search over the same sites, so the two readings can be compared directly on the guides you are choosing between. The choice applies to the genome search alone -- averaged over a complete single-mismatch panel the MIT weights return one number for every guide of a given length, which is a constant rather than a measurement, so the genome-free column is always the table's.
A PAM class column reads primary where the row's PAM is one of this nuclease's documented ones — NG, GAA or GAT — and secondary where the row belongs to a wider PAM class the model was trained to score but the nuclease is not documented to cut. Both are real target sites the model scores; the column is what says which class a row belongs to.
PAM class
primary
secondary
The results page produces the DeepxCas9 Score and percentile compared to the test data for each designed guide RNA sequence.
You may click on each row to update the Selected Target Details visualization. The red highlight is the PAM sequence.
You can download the full results as a ZIP file using the Download Results button.
The location is indicated using the following format.
Starting base pair from the beginning of the whole input sequence: ending base pair from the beginning of the whole input sequence
Example 1. 59:88 (Interpretation) The 30 bp target sequence spans from the 59th to the 88th bp of the input sequence, counting from the beginning of the whole input sequence.
Example 2. 96:67 (Interpretation) The 30 bp target sequence spans from the 96th to the 67th bp of the input sequence, counting from the beginning of the whole input sequence. Thus, the target sequence containing the PAM is the reverse complement of the input sequence.
Input Sequence: The 30 bp region in the input sequence containing the target sequence. If the PAM is in the input sequence, the input sequence is identical to the target sequence. If the PAM is on the opposite strand of the input sequence, the input sequence is reverse complementary to the target sequence. The PAM sequence or the reverse complementary sequence of the PAM is indicated in red.
Target sequence: The 30 bp target sequence including the PAM, which is indicated in red.
Guide RNA sequence: 20 nt guide RNA sequence.
GC content: GC content of the 20 bp protospacer sequence (guide RNA sequence)
DeepxCas9 or DeepSpCas9-NG score: A DeepxCas9 or DeepSpCas9-NG score is the expected indel frequency (expressed as a percentage) at the target sequence when the single guide RNA (sgRNA) and Cas9 variants are lentivirally delivered into HEK293T cells for three days. For example, if the DeepxCas9 score at a certain target sequence is 10, then the expected indel frequency at the target sequence at three days after lentiviral delivery of xCas9 and sgRNA is 10%. For users' information, we provide the actual relations between the measured indel frequency and the DeepxCas9 or DeepSpCas9-NG score; the following plot shows an almost linear y = x relationship between the predicted score and measured indel frequency at lentivirally integrated target sequences three days after lentiviral delivery of either xCas9 or SpCas9-NG and the corresponding sgRNAs in HEK293T cells.
Note: If there is polyT within the guide RNA sequence, the presence of polyT would be described here.
Percentile rank of the DeepxCas9 or DeepSpCas9-NG score: The percentile rank was calculated based on the large data sets of DeepxCas9 scores at 4,956 target sequences and DeepSpCas9-NG scores at 4,641 target sequences. These 4,956 and 4,641 target sequences were randomly selected from the human genome without any prior information about the activity of the corresponding sgRNAs (21 and 7 target sequences were chosen per 5-nt PAM for xCas9 and SpCas9-NG, respectively). A percentile rank of 100 represents the highest Cas9 activity, whereas a percentile rank of 0 represents the lowest activity. The relations between the percentile rank of the score and the actual score in DeepxCas9 and DeepSpCas9-NG are shown below for users’ information.
The following example interactive outputs are available for reference:
COSMIC. COSMIC is a product of Genome Research Limited (Wellcome Sanger Institute). It is free for academic and non-commercial use; commercial use requires a COSMIC licence. Lookups here resolve a single user-typed identifier — no COSMIC data is listed, browsable or served in bulk.
If you have any questions, bug reports, or suggestions, please do not hesitate to contact us through the Support page.