-
Notifications
You must be signed in to change notification settings - Fork 13
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
Mapping Ensembl seqlevels to UCSC for Mmul_10/rheMac10 #79
Comments
Hi Hervé, thanks a lot for the solution! ah= AnnotationHub() Warning message: |
I also tried generating the Grange file with the other method by:
It seems like it works with seqlevels from "ensembl" to "UCSC" without warnings, do you think it's a right format?
seqinfo: 329 sequences from an unspecified genome; no seqlengths |
There's a lot going on here.
The main issue is that this mapping is not properly supported in GenomeInfoDb at the moment.
For example:
The
seqlevelsStyle()
getter gets it wrong (the seqnames are the Ensembl seqnames, not the NCBI ones):And the
seqlevelsStyle()
setter does a very poor job:Here's how low-level utilities
getChromInfoFromEnsembl()
andgetChromInfoFromUCSC()
can be used to do the job. The code is specifically taylored towards Mmul_10/rheMac10 so lacks generality, but it's a start:Then:
Another problem is that EnsDb objects don't support the
seqinfo()
setter sox2
cannot be put back onensdb
:Note that this is a limitation of EnsDb objects (implemented in the ensembldb package), so is kind of a separate issue.
Finally, about this error raised by the
seqlevelsStyle()
setter for EnsDb objects:I guess the error message refers to the Accept-organism-for-GenomeInfoDb.Rmd vignette. However note that those mappings were introduced a long time ago and were never intended to handle scaffolds, only the "main chromosomes". That's because scaffolds are specific to a particular assembly version (e.g. they're not the same in Mmul_10/rheMac10 and in Mmul_8.0.1/rheMac8). So adding a mapping for Macaca mulatta wouldn't actually help here.
The text was updated successfully, but these errors were encountered: