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

Whitespace in INFO field #548

Open
AlistairNWard opened this issue Mar 11, 2024 · 4 comments
Open

Whitespace in INFO field #548

AlistairNWard opened this issue Mar 11, 2024 · 4 comments

Comments

@AlistairNWard
Copy link

When running exomiser, I am receiving the error that the vcf file is malformed because the INFO field has whitespace in it. The vcf spec (4.4) explicitly states that whitespace IS allowed in the INFO field.

htsjdk.tribble.TribbleException: The provided VCF file is malformed at approximately line number 5680: The VCF specification does not allow for whitespace in the INFO field. Offending field value was "XXX"
@julesjacobsen
Copy link
Contributor

Thanks for the report - Exomiser is using the HTSJDK for VCF file parsing and this only has experimental support for VCF v4.4 at the moment. Exomiser can currently read VCF v4.2 files, so you'll need to replace the whitespace with underscores or hyphens for it to be able to read the file.

I'll open a ticket to update the HTSJDK this once support has been added.

@AlistairNWard
Copy link
Author

That makes sense. Thank you. Is it possible to stream a vcf into exomiser? I have thousands of vcf files that I need to process and I don’t want to duplicate them all with the white space removed. I tried using “-vcf -“ and “—vcf stdin” on the command line, but that failed. I’m not too familiar with Java, so was wondering if this was possible?

thanks again

@julesjacobsen
Copy link
Contributor

Sorry, it's not possible to stream the VCF file into Exomiser and unfortunately even the latest HTSJK doesn't support whitespace in VCF files.

@AlistairNWard
Copy link
Author

Thanks for the response. That's what I expected, so we'll work around these requirements.

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