Closed mrvollger closed 1 month ago
No, you read it correctly, it should strip and add the appropriate tags. I wonder if I missed one somewhere that didn't pop up in our testing. Do you have an example bam-let and vcf-let you can share that reproduces the issue?
Matt
Thanks for the quick reply!
Hmm, this data is private. Is there any way I can get hiphase to tell me the region in which this failure happens, I might be able to share a small enough subset safely.
i.e. can I assume the error is happening here:
chr2:70440214-70440214
I took a look at the code, and I think I know what might be causing this after some local tinkering. Can you give this binary a test and let me know if that resolves it on your end?
Awesome, getting on it right now.
Well past the previous error (now on chr6), so I think it worked, but will confirm when its all done.
All finsihed without error! Looking forward to the patch!
Yea, feel free to use that binary in the interim if you need it. I am running some additional checks since this was a decent sized oversight (we were focused on the VCF part, not so much the BAM part at the time). I suspect we'll have it out sometime later this week though.
Official version after testing is now available here: https://github.com/PacificBiosciences/HiPhase/releases/tag/v1.4.5
If you use bioconda, that will propagate at some point later today
Hi @holtjma,
From the recent change logs, I was excited to read that Hiphase now supports passing in already-phased input and then reprocessing. But when I tried this, I got an error with 1.4.4:
Any ideas? or did I misunderstand the changelog?
Thanks! Mitchell
Full message: