Skip to content
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

Bcftools pparallel #109

Merged
merged 2 commits into from
Jan 6, 2021
Merged

Bcftools pparallel #109

merged 2 commits into from
Jan 6, 2021

Conversation

rdmorin
Copy link
Contributor

@rdmorin rdmorin commented Dec 21, 2020

This pull request addresses a major issue that has been affecting us when we run Lofreq on whole genome data in somatic mode. Non-ACTGN characters in the reference (e.g. IUPAC ambiguity codes such as W, R, Y) cause strange behaviour and lead to malformed/garbled lines in the VCF somewhat consistently (see #106). The change to plp.c forces these positions to be ignored as it does for Ns in the reference. We have also changed merging to rely on bcftools in an earlier attempt to address this issue (see #108). That change may not be necessary at this point with the current patch to plp.c

I'm interested in having at least the plp.c change added to future releases of lofreq so conda users can benefit from this improvement.

@andreas-wilm andreas-wilm merged commit 3ac8cec into CSB5:master Jan 6, 2021
@andreas-wilm
Copy link
Contributor

Thank you so much!

@Kdreval
Copy link

Kdreval commented Jan 14, 2021

Hi Andreas! We would greatly appreciate it this update will be considered for the next release of the conda version. Thank you in advance!

@andreas-wilm
Copy link
Contributor

Absolutely. It's merged already and will be part of v2.1.6

@Kdreval
Copy link

Kdreval commented Apr 15, 2021

Hi Andreas! There are updated files at Conda, but they seem to be without version bump and refer to v2.1.5. I could not find documentation what has been recently changed, but it seems that update from this PR hasn't been rolled out yet? Just want to remind about it, as it seems v2.1.6 is coming!

@andreas-wilm
Copy link
Contributor

andreas-wilm commented Apr 28, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants