CRISPRseek: offTargetAnalysis -> buildFeatureVectorForScoring increase max.mismatch error
1
0
Entering edit mode
@jacobbradford-16692
Last seen 6.2 years ago

Hi,

As part of my research, I am required to run CRISPRseek, however, I am facing issues using the offTargetAnalysis function. I have read the reference manual and found that this function is perfect to help with what I am trying to achieve. 

I have pasted my script, input file and the output below.

I run the following script:

#!/usr/bin/env Rscript
library(CRISPRseek)
options(error=function()traceback(2))
library("BSgenome.Mmusculus.UCSC.mm10")
results <- offTargetAnalysis("/home/jake/genomes/mm10-ucsc-mod/chr19/100k/chr19.fa", annotatePaired = FALSE, enable.multicore = TRUE, annotateExon = FALSE, max.mismatch = 3, BSgenomeName = BSgenome.Mmusculus.UCSC.mm10, outputDir = "/home/jake/tools/CRISPRseek/0002", overwrite = TRUE, topN=100000000, chromToExclude="", chromToSearch="ucsc-mm10-chr19-full-extract[10000000-10100000]", findgRNAs=TRUE)

 

The input fasta file is as follows (/home/jake/genomes/mm10-ucsc-mod/chr19/100k/chr19.fa):

>ucsc-mm10-chr19-full-extract[10000000-10100000]
TAATGTACAGCTGGACCGAGAATCTCTGTGGGCTCCTACCTGTTTCTCCTCTTTTCTTCAATACATACTGACCTTCACAAGAGAGCTTGCTATCTAATAGGTGTTCTCTCTCTCTCTCTCTCTCT... (100k bases on a single line)

 

However, I receive the following error message:

Error in buildFeatureVectorForScoring(hits = hits, canonical.PAM = PAM,  :
  Empty hits!
Calls: offTargetAnalysis -> buildFeatureVectorForScoring
In addition: Warning message:
In searchHits(gRNAs = gRNAs, PAM = PAM.pattern, BSgenomeName = BSgenomeName,  :
  No matching found, please check your input sequence, and make
            sure you are using the right genome. You can also alter your
            search criteria such as increasing max.mismatch!

 

As according to the error message, I have increased max.mismatch, however, continue to receive the same error. 

Could you please help me resolve this?

 

Kind regards,
Jake.

crisprseek offtargetanalysis • 1.1k views
ADD COMMENT
0
Entering edit mode
Julie Zhu ★ 4.3k
@julie-zhu-3596
Last seen 12 months ago
United States
Jacob, The following parameters need to be reset. BSgenomeName = Mmusculus, chromToSearch = "all" Best regards, Julie On Jul 29, 2018, at 7:37 PM, jacob.bradford [bioc] <noreply@bioconductor.org<mailto:noreply@bioconductor.org>> wrote: Activity on a post you are following on support.bioconductor.org<https: urldefense.proofpoint.com="" v2="" url?u="&lt;a href=" http:="" <a="" href="http://https-3A__support.bioconductor.org" rel="nofollow">https-3A__support.bioconductor.org"="" rel="nofollow">https-3A__support.bioconductor.org&d=DwMDaQ&c=WJBj9sUF1mbpVIAf3biu3CPHX4MeRjY_w4DerPlOmhQ&r=3IbW-yoIQpGZOKgd4i2bgmPHhwHHF5gJMlij5cC5bLU&m=NfCmNuN14-mUxy9xAn3XjQpKAkMrZvUCoUbOKi2eSeA&s=1b4meFwStJ3ptAKsbP8xuOOpft_ZhtzWjZKA_Jpewxg&e="> User jacob.bradford<https: urldefense.proofpoint.com="" v2="" url?u="https-3A__support.bioconductor.org_u_16692_&amp;d=DwMDaQ&amp;c=WJBj9sUF1mbpVIAf3biu3CPHX4MeRjY_w4DerPlOmhQ&amp;r=3IbW-yoIQpGZOKgd4i2bgmPHhwHHF5gJMlij5cC5bLU&amp;m=NfCmNuN14-mUxy9xAn3XjQpKAkMrZvUCoUbOKi2eSeA&amp;s=bXqq15cmH6mojulD4wyV2yK8UsUZwjvzWydt1oHhuRA&amp;e="> wrote Question: CRISPRseek: offTargetAnalysis -> buildFeatureVectorForScoring increase max.mismatch error<https: urldefense.proofpoint.com="" v2="" url?u="https-3A__support.bioconductor.org_p_111488_&amp;d=DwMDaQ&amp;c=WJBj9sUF1mbpVIAf3biu3CPHX4MeRjY_w4DerPlOmhQ&amp;r=3IbW-yoIQpGZOKgd4i2bgmPHhwHHF5gJMlij5cC5bLU&amp;m=NfCmNuN14-mUxy9xAn3XjQpKAkMrZvUCoUbOKi2eSeA&amp;s=uYtSBLMlN-QLV1hCSKY8om1LaA3zvQL48MkSiz2G6h0&amp;e=">: Hi, As part of my research, I am required to run CRISPRseek, however, I am facing issues using the offTargetAnalysis function. I have read the reference manual and found that this function is perfect to help with what I am trying to achieve. I have pasted my script, input file and the output below. I run the following script: #!/usr/bin/env Rscript library(CRISPRseek) options(error=function()traceback(2)) library("BSgenome.Mmusculus.UCSC.mm10") results <- offTargetAnalysis("/home/jake/genomes/mm10-ucsc-mod/chr19/100k/chr19.fa", annotatePaired = FALSE, enable.multicore = TRUE, annotateExon = FALSE, max.mismatch = 3, BSgenomeName = BSgenome.Mmusculus.UCSC.mm10, outputDir = "/home/jake/tools/CRISPRseek/0002", overwrite = TRUE, topN=100000000, chromToExclude="", chromToSearch="ucsc-mm10-chr19-full-extract[10000000-10100000]", findgRNAs=TRUE) The input fasta file is as follows (/home/jake/genomes/mm10-ucsc-mod/chr19/100k/chr19.fa): >ucsc-mm10-chr19-full-extract[10000000-10100000] TAATGTACAGCTGGACCGAGAATCTCTGTGGGCTCCTACCTGTTTCTCCTCTTTTCTTCAATACATACTGACCTTCACAAGAGAGCTTGCTATCTAATAGGTGTTCTCTCTCTCTCTCTCTCTCT... (100k bases on a single line) However, I receive the following error message: Error in buildFeatureVectorForScoring(hits = hits, canonical.PAM = PAM, : Empty hits! Calls: offTargetAnalysis -> buildFeatureVectorForScoring In addition: Warning message: In searchHits(gRNAs = gRNAs, PAM = PAM.pattern, BSgenomeName = BSgenomeName, : No matching found, please check your input sequence, and make sure you are using the right genome. You can also alter your search criteria such as increasing max.mismatch! As according to the error message, I have increased max.mismatch, however, continue to receive the same error. Could you please help me resolve this? Kind regards, Jake. ________________________________ Post tags: crisprseek, offtargetanalysis You may reply via email or visit CRISPRseek: offTargetAnalysis -> buildFeatureVectorForScoring increase max.mismatch error<https: urldefense.proofpoint.com="" v2="" url?u="https-3A__support.bioconductor.org_p_111488_&amp;d=DwQDaQ&amp;c=WJBj9sUF1mbpVIAf3biu3CPHX4MeRjY_w4DerPlOmhQ&amp;r=3IbW-yoIQpGZOKgd4i2bgmPHhwHHF5gJMlij5cC5bLU&amp;m=NfCmNuN14-mUxy9xAn3XjQpKAkMrZvUCoUbOKi2eSeA&amp;s=uYtSBLMlN-QLV1hCSKY8om1LaA3zvQL48MkSiz2G6h0&amp;e=">
ADD COMMENT

Login before adding your answer.

Traffic: 522 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6