-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in .replace_seqlevels_style #14
Comments
Hello, I am having the same issue when trying to run crispRdesignR from the command line on a custom genome available on VectorBase. The BSgenome is installed successfully. The error message showed up at the "annotating off-targets" step. There is no error when the off-target annotation step is skipped using the parameter "annotateoffs = FALSE".
I tried to create the BSGenome package following the documentation using two alternative ways:
forgeBSgenomeDataPkgFromNCBI(assembly_accession="GCA_000473445.2",pkg_maintainer=NA,organism="Anopheles farauti",destdir="BSgenomeForge/",circ_seqs=character(0)) The BSGenome sequences names obtained as a result of forgeBSgenomeDataPkgFromNCBI are different to the ones contained in the VectorBase so I renamed the chromsomes names in the GTF file to match the BSGenome sequences names. Thank you for your help |
Hello @vmurigneu, For me, the problem doesn't come from the custom BS genome package created for this purpose. It comes directly from the GTF annotation files that I upload to crispRdesignR. When I checked the code of the function inducing the error, I saw that it came from this command: GenomeInfoDb::seqlevelsStyle(gtf) <- "UCSC" The problem is that the gtf is not in UCSC format and I haven't managed to format it with the tools available so far. Because in my case I'm at contig level, so the chromosome names don't follow UCSC recommendations. Is the genome you are using on a database or have you created a BSgenome package of your genome directly without going through a database? The replacement of sequence names has not fixed your problem if I have understood correctly. Have you also checked that the coordinates of the sequences are similar because they may be on different conventions and therefore with a difference of 1 base pair. Can you please make me a head of your gtf annotation file and your chromosome size file for example where there are the names of the sequences in your genome? Let me know if you success to fix this issue or suggestion please, Thank you two |
Hi @El-Castor Yes I agree with you, the error comes from this line of code. I did create the BSgenome package (using two different methods, see my previous post) as the species was not already available. The gtf looks like this:
It was converted from GFF. Does your GTF file contains the header? The header was removed during the gff to gtf conversion. Thank you |
I am having the exact same problem with my custom genome. I built the BSgenome successfully and get the same error when I look for off-targets. It's rather pointless without the ability to use this option. Has there been a solution to the problem? Thanks! |
hi @maltesemike no I suspect solving this will require modifying the R code. My understanding from reading a bit about the GenomeInfoDb package is that custom genome are not supported in regards to the seqlevelsStyle UCSC style. |
thanks @vmurigneu this is a real shame, it makes the tool completely unusable for non-model genomes, which is what it was purported to do. any chances of a quick fix @dylanbeeber ? |
Hello,
First of all, thank you for your tool it is very usefull. I am trying to use it for a custom genome. I build the necessary BSgenome library and install my genome successfully.
I success also to install and launch crispRdesignR GUI Shiny app and launch the sgRNA desing and off-target assessment. Unfortunatly at the and of the computing the app become grey and it blocked without producing the off-target output file.
Below you have the terminal showed error:
Do you have any idea what I am doing wrong ? Tell me if you need more specific informations.
Thank in advance for your help
The text was updated successfully, but these errors were encountered: