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

Intermediate VCF, BD clarification #2

Closed
Lenbok opened this issue Nov 4, 2015 · 1 comment
Closed

Intermediate VCF, BD clarification #2

Lenbok opened this issue Nov 4, 2015 · 1 comment

Comments

@Lenbok
Copy link
Member

Lenbok commented Nov 4, 2015

For the decision (BD) field, it is fairly obvious what TP/FP/FN mean, but it could be good to clarify the meaning of 'N' (and what the intended use is).

Am I right in assuming a 'N' is used to indicate that the call was not assessed / skipped / other? And I assume where there is no call (i.e. empty GT), the field should just have a regular VCF missing value '.'.

In vcfeval, calls may have non TP/FP/FN status either because they were ignored from comparison (e.g. outside of BED region; non-variant GT; SV or symbolic; having non-pass FILTER; exceeding maximum length; off-reference), or if the variant could not be assessed due to being in a region that turned out to exceed maximum evaluation complexity -- I assume these would need to end up with BD as 'N' or perhaps missing.

Lenbok pushed a commit that referenced this issue Nov 5, 2015
Updating from original
@pkrusche
Copy link
Member

pkrusche commented Nov 5, 2015

Yes, this was the intention with "N" : flag calls that were not compared / could not be assigned a truth status. The BT field (#3) could give additional information on what happened.

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