You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For most lines we are obviously seeing a lot of MISSING values, and hence a lot of redundant INFO keys. Most other annotation programs would default to not output the key if the variant it is found to be missing in the source.
What is the intention here, keep them to be sure the variant was correctly processed? Or be able to lift them out easily? A new INFO key format standard brewing that I'm not aware of? 😊
Of course we can remove them afterwards, but a flag to change this behaviour would be practical, assuming you have a need for them in some applications.
The text was updated successfully, but these errors were encountered:
Thank you for the good work!
For most lines we are obviously seeing a lot of
MISSING
values, and hence a lot of redundantINFO
keys. Most other annotation programs would default to not output the key if the variant it is found to be missing in the source.What is the intention here, keep them to be sure the variant was correctly processed? Or be able to lift them out easily? A new INFO key format standard brewing that I'm not aware of? 😊
Of course we can remove them afterwards, but a flag to change this behaviour would be practical, assuming you have a need for them in some applications.
The text was updated successfully, but these errors were encountered: