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

no calls gives unusual file sets #40

Open
keiranmraine opened this issue Aug 17, 2015 · 2 comments
Open

no calls gives unusual file sets #40

keiranmraine opened this issue Aug 17, 2015 · 2 comments

Comments

@keiranmraine
Copy link
Contributor

If CaVEMan gives no calls during the estep you get a full set of *.muts.vcf files but no *.snps.vcf.

This causes the mergeCavemanResults script to fail.

Not sure how this should be handled ot classified as the data is of no use but a clean run with a warning would be helpful. I encountered this when running an WXS pair from cghub where it appears the tumour and normals don't have any common coverage.

@ghost ghost added bug and removed bug labels Nov 26, 2015
@ghost
Copy link

ghost commented Nov 26, 2015

Unless CaVEMan silently failed between opening and writing the header to the muts file and doing the same for the snps fil I can't see how this could be possible. Is it still replicatable?

@ghost
Copy link

ghost commented Nov 27, 2015

I'll test this and attempt to replicate it soon using an empty normal bam.

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

No branches or pull requests

1 participant