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

Clarification of empty vector representation #617

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pd3
Copy link
Member

@pd3 pd3 commented Dec 16, 2021

as triggered by samtools/bcftools#1622 and #593

State explicitly that missing vectors (.) in fields of variable length are in BCF represented as MISSING,END_OF_VECTOR, i.e. the leading MISSING value must be always present.

@hts-specs-bot
Copy link

Changed PDFs as of 9a5fdb0: VCFv4.3 (diff). This link will expire in 30 days

@jmarshall
Copy link
Member

#593 makes a case that [END_OF_VECTOR, END_OF_VECTOR] would also be a reasonable encoding of this situation.

What is the reason for requiring that “[e]mpty vectors (i.e. vectors with no data available)” be represented as [MISSING, END_OF_VECTOR] (which is seemingly less empty!)?

@jkbonfield
Copy link
Contributor

Fixes #593

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Needs review
Development

Successfully merging this pull request may close these issues.

5 participants