Details
-
Type:
Improvement
-
Status: To-Do (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Story Points:0.5
-
Epic Link:
Description
It seems that VCF files are supported by IGB but the insertions in the VCF file have no Selection Info, even though there is much relevant information within the tooltips for these insertions.
This should be fixed in the near future.
Attachments
Activity
Comment from issue IGBF-1380
___________________________
The changes for 4.2 (compared to 4.1)
- INFO field can have one value for each possible allele (code R).
This allows one more possible special value to the number value for an INFO field. IGB does not currently read/use this field. No change needed.
- For all of the ##INFO, ##FORMAT, ##FILTER, and ##ALT meta information, extra fields can be included after the default fields.
As part of a general improvement to the parser, we should include a map for each entry that would be able to these open form values. These values would be part of the selection info for an entry, but they will not affect how the entry is displayed. This can be handled as part of issue IGBF-543.
- Alternate base (ALT) can include *: missing due to a upstream deletion.
I am still figuring out if/how the code might need to change to accommodate this. None of my example v4.2 files use this option.
The <*> notation is explained in section 5.5 of the VCF format specification, but I am still unclear about how this type should be represented. I don't know if the END tag is mandatory when the <*> is used. I think using the END tag when it is present should be part of our general improvement to the parser.