-
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
Mitocondrial chromosome naming, seqlevelsStyle() #8
Comments
I can't reproduce this :(
sessionInfo()
|
Basic reproduction is this:
And this one gives a warning
|
So to sum up, this is the case: seqlevelsStyle support shifting of style when the cases are clear. When there are a mix of styles with only 2 chromosomes, it switches correctly but gives you a warning. When there are a mix of styles with > 2 chromosomes, it switches incorrectly. This is the case I would like, and the most logical is that it behaves as the case for 2 chromosomes, giving a warning, but switching correctly. That is: Which does not happen now. |
I think this is quite a serious issue, I get it all the time warnings like this:
This is after they should have had equal seqlevels naming. So I think a lot of people are losing the sex chromosomes + sometimes mitochondrial, if they use different seqnames and trust that seqlevelsstyle will fix it. |
I thanks for a nice function, I use seqlevelsStyle a lot.
One thing has always bothered me, is for the mitocondrial chromosome.
Two objects with same naming convention as these:
Can show seqlevels as this:
So even though they use the same seqlevelsStyle, the objects does not name the mitochondrial chromosome the same.
Is there a reason for this ? :)
The text was updated successfully, but these errors were encountered: