-
Notifications
You must be signed in to change notification settings - Fork 8
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
modkit dmr - failed to read tabix index #178
Comments
Hello @lilypeck, There shouldn't be any changes in modkit v0.2.7 to v0.2.8 with respect to how the tabix index is handled. However, I did update the dependencies that
Thanks. |
Hello @ArtRand
I have attached two .tbi files which failed. I have also checked the bedmethyls.gz and they are complete (with the same Thanks Lily barcode21_U_CG.bedmethyl.gz.tbi.txt |
Hello @lilypeck, I was able to reproduce the error using noodles version 0.69.0 (the version in modkit 0.2.8), the error does not occur with version 0.50.0 (the version in modkit 0.2.7). What is strange, however, is that the tabix indices that I have in tests and some others I've used seem to be parsed without complaint. Could you tell me what version of tabix --version
tabix (htslib) 1.18
Copyright (C) 2023 Genome Research Ltd. If you give me a few minutes I can get you a build with the older version of the library to unblock your work, but I'd like to get to the bottom of the problem also. So to summarize, please:
|
Hello @ArtRand
The complete .bedmethyl is too big to upload, so I have uploaded the first 1m lines. Or if you have an email address I could send you a copy? And yes very happy for you to use these to exercise the bug. Thank you very much for your help. |
Hi @ArtRand |
[bug] Tabix indices don't load See merge request machine-learning/modkit!176
@lilypeck Great, this fix is also in the 0.4.1 release. |
Hello
I am getting a very basic error:
My script is:
However I don't think the error is related to my
.tbi
files, because I have re-run a script that previously successfully completed with mod_kit 0.2.7, and it now fails with this error for mod_kit 0.2.8.Is there something you can see that might be causing this?
Thank you in advance!
Lily
The text was updated successfully, but these errors were encountered: