-
Notifications
You must be signed in to change notification settings - Fork 6
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
Freemuxlet fails during popscle dsc-pileup due to different order of bam and vcf. #25
Comments
Hey here are my suggestions:
outside the nextflow pipeline? Maybe tabix indeed solves the problem but due to the reason that hadge doesnt mount the tbi into the working directory, freemuxlet can not find this file and fails again. That could also be possible. |
Thanks again for the fast response, amazing support! I will let you know what worked. |
Keep them coming @bednarsky ! Thank you for playing with hadge. We're happy to provide additional assistance if necessary. |
Please feel free to reopen this issue if you are still running into issues and we would be happy to help troubleshoot further. |
I had an issue with the header and the table of vcf files using different formatting. I changed all formatting to the one in the bam files, namely ch1, chr2 etc, and then the reordering with popscle_helper_tools worked, and the process continued. These are my commands to download and prepare the files.
Removing the contig lines, as proposed here, statgen/popscle#25 (comment), led to different downstream errors. |
Sorry for having so many questions and thank you in advance for your help!
Freemuxlet fails with this error:
Do you know this issue? What is your recommended solution? I tried popscle_helper_tools to reorder the vcf file, but it is currently still failing, see issue on that repo.
Also note this line
Finished identifying 0 samples to load from VCF/BCF
→ is this usual, or does this point to an earlier error?This issue occured for both hg38 (which matches the ref genome used for demultiplexing) and hg19 (which I used first by accident).
Really appreciate all your work!
The text was updated successfully, but these errors were encountered: