-
Notifications
You must be signed in to change notification settings - Fork 242
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
Unexpected behaviour when parsing lists in INFO field #261
Comments
going over old issues... The missing string should be the empty string, but it isn't clear the the double array is legal since the spec doesn't seem to allow for missing individual fields in an array. so that would have to be an error. I think that if strict pasrsing is requested, this record should be deemed not conformant due to the float array, and the string array should have returned one empty string. |
Thanks for considering this issue. I don't see in the specs where empty strings are disallowed. |
I agree.. an empty string should have been created, but not a missing float |
Mention that these conventions apply to *some* tag names where L/P/Q acts as a name suffix -- for others, like DP, the L/P/Q is just part of the name. Replaces and closes samtools#261. Fix quote marks and maths formatting.
I have a VCF file with an
INFO
field that hasA
many values, but these values can be empty, as demonstrated below. Reading this with HTSJDK leads to theFI
andFS
fields having one atomic value instead of a list of two values.Is this intented behaviour?
The text was updated successfully, but these errors were encountered: