-
Notifications
You must be signed in to change notification settings - Fork 14
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
Upgrade Pysam #265
Comments
When I try this with pysam 0.15.4 I see a different error, this time in the manta vcf files
Note: I install pysam with the following environment flag (from the setup.py)
Currently I am testing on the develop_v3 branch |
note: the OS environ options do not appear to have any effect (probably b/c installing via wheel so it doesn't have to build from source). I will be leaving these options off for future runs |
For the delly error it looks like it has something to do with this warning in the output
however this should not be an issue since it is a translocation Looks like it may be related to this issue: samtools/bcftools#1154 |
Currently MAVIS is frozen to pysam 0.15.2 because there are some unexpected bugs in later versions. However this is getting harder and harder to support as setuptools/pip has issues with these lower versions
I have commented on this ticket but it was created in 2017 and there has been little to no movement: pysam-developers/pysam#527
When we run the test with the newer versions we see the following error
FAILED tests/end_to_end/test_convert.py::TestConvert::test_delly - assert 17396140 == (7059510 - 670)
After some preliminary debugging I can see that it seems like the END tag of the INFO column is being ignored. In previous versions of pysam (<=0.15.2) this would have been used to create the "stop" field on VariantRecord. Now however it is simply dropped.
Adding a summary of testing here (python3.7 was used, will test other versions once this one is working)
The text was updated successfully, but these errors were encountered: