The VCF Filter values (e.g., PASS, ., etc) are populated based on the variants that have been analyzed across all loaded genes. This isn't a complete solution, because variants with '.' filters won't be considered as 'FLAGGED FOR NOT MEETING FILTER CRITERIA' until a variant with a 'PASS' filter is encountered. Take, for example the demo data. When first loaded, variants for RAI1, which all have a filter of '.', are not flagged.
After gene PDGFB is selected, a variant with a 'PASS' filter is encountered.
Select RAI1 again. Now its variants are flagged for not meeting filter criteria.
I think that the solution is to have a priori knowledge of all possible filter values used in the loaded VCF.
The VCF Filter values (e.g., PASS, ., etc) are populated based on the variants that have been analyzed across all loaded genes. This isn't a complete solution, because variants with '.' filters won't be considered as 'FLAGGED FOR NOT MEETING FILTER CRITERIA' until a variant with a 'PASS' filter is encountered. Take, for example the demo data. When first loaded, variants for RAI1, which all have a filter of '.', are not flagged.
After gene PDGFB is selected, a variant with a 'PASS' filter is encountered.
Select RAI1 again. Now its variants are flagged for not meeting filter criteria.
I think that the solution is to have a priori knowledge of all possible filter values used in the loaded VCF.