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
Some programs don't do a great job of typing or sizing the output VCF fields. E.g., this is some SnpEff output (I think)
##INFO=<ID=GDI-Phred,Number=.,Type=String,Description="Phred-scaled GDI scores">
##INFO=<ID=GDI,Number=.,Type=String,Description="gene damage index score, a genome-wide, gene-level metric of the mutational damage that has accumulated in the general population from doi 1>
This has been marked as String, Number=".", where it probably should be Integer, Number=1.
One way we could do this is to check the correspondence between the VCF types in the VCF metadata with the types in the Zarr schema, and to push that field through a "conversion" code path if they are not compatible. So, here, we'd see that the original VCF type is String and the Zarr type is int, and we'd have to pass the field through an integer parsing code path.
An nice feature to add at some point then would be to take an input Zarr schema and to automatically detect some common mistyped fields and correct them.
The text was updated successfully, but these errors were encountered:
Some programs don't do a great job of typing or sizing the output VCF fields. E.g., this is some SnpEff output (I think)
This has been marked as String, Number=".", where it probably should be Integer, Number=1.
One way we could do this is to check the correspondence between the VCF types in the VCF metadata with the types in the Zarr schema, and to push that field through a "conversion" code path if they are not compatible. So, here, we'd see that the original VCF type is String and the Zarr type is int, and we'd have to pass the field through an integer parsing code path.
An nice feature to add at some point then would be to take an input Zarr schema and to automatically detect some common mistyped fields and correct them.
The text was updated successfully, but these errors were encountered: