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

Mity merge - IndexError: list index out of range #12

Open
anjalijain22 opened this issue Feb 22, 2022 · 5 comments
Open

Mity merge - IndexError: list index out of range #12

anjalijain22 opened this issue Feb 22, 2022 · 5 comments

Comments

@anjalijain22
Copy link

Hi,
I'm running into the below IndexError with mity merge:

mity 0.3.0
mity vcf merge
Traceback (most recent call last):
File "/home/ajain/.local/bin/mity", line 29, in
args.func(args)
File "/home/ajain/.local/lib/python3.9/site-packages/mitylib/commands.py", line 191, in _cmd_merge
merge.do_merge(args.mity_vcf, args.nuclear_vcf, args.prefix, genome)
File "/home/ajain/.local/lib/python3.9/site-packages/mitylib/merge.py", line 139, in do_merge
mity_number = mity_line.split("Number=")[1]
IndexError: list index out of range

The command I'm using is - mity merge --prefix combined --mity_vcf file.mity.vcf.gz --nuclear_vcf file_nuclear.vcf.gz in which the file.mity.vcf.gz file was generated using the mity call function.

I'd really appreciate your help on how to resolve this error. Thanks in advance!

@drmjc
Copy link
Member

drmjc commented Mar 14, 2022

Hi, what nuclear variant caller did you use? I think it's failing on a line that's specific for GATK HaplotypeCaller. Thanks

@anjalijain22
Copy link
Author

anjalijain22 commented Mar 15, 2022

Thanks for your reply!
Yes, I used the GATK HaplotypeCaller. What would be the workaround for this error?

@drmjc
Copy link
Member

drmjc commented Mar 15, 2022 via email

@anjalijain22
Copy link
Author

Sure, here are the nuclear and mity vcf files -
sample_mity.vcf.gz
sample_nuclear.vcf.gz

@drmjc
Copy link
Member

drmjc commented Mar 23, 2022

Hi @anjalijain22,
thanks, but these vcf files are malformed, with aberrant " throughout - you'll see what i mean when you open them. I've spent a good while trying to fix them, but i get a different error relating to unicode that makes me think there's something wrong with the files. I'm gonna give up on these for now. perhaps try to deidentify them via a regex using a pipe rather than an editor.

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

2 participants