-
Notifications
You must be signed in to change notification settings - Fork 50
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
Chromosome order potential issue #152
Comments
Sending an example bigwig could be useful. The dictionary order in python isn't always guaranteed, depending on the version of python you're using. |
Thank you for answering! Here in the google drive folder there are:
When I open this bigwig with pyBigWig I get None on the Chr10: In IGVjs browser, embedded in my Dash application, I get smth on the Chr10: |
I am also having this issue, chromosomes 10 - 22 do not have any data when using pyBigWig! It also affects bigwigAverage! |
I'm not sure if this kind of problem has been already reported, but I couldn't find any clues on how to solve it, so decided to write my question here.
I made a bunch of bigwig files using bedGraphToBigWig tool.
The chromosome order in my bedgraph files was right (Chr1...Chr9,Chr10,..). When converting the files, I also provided the chrom.sizes file with right chromosome order.
I can open the bigWig files in the IGV browser, and they look OK, I can browse to any position and the information is displayed correctly.
But when I open the files with pyBigWig, for some reason Chr10 can't be accessed. I'm not sure, but can it be related to the chromosome order problem? Because when I display the chromosome order with
bw.chroms()
command, I get the wrong alphabetical order (which was not originally in bedGraph files, and doesn't correspond to the genome file chromosome order):ucsc's bigWigInfo returns also the alphabetical order (despite the chrom.sizes file I provided for bedGraphToBigWig the chromosome order was correct):
I can send the examples of bedGraph and bigwig files if they are needed.
The text was updated successfully, but these errors were encountered: