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
{{ message }}
This repository has been archived by the owner on Jan 18, 2020. It is now read-only.
Recent versions of SnpEff default to using strings from the Sequence Ontology to identify types of effects, rather than using the SnpEff-specific EffectType enum names.
Eventually, the importer should be able to identify effects based on the Sequence Ontology strings. Ideally, there should be a way of recognizing effects based on either nomenclature, as they are mutually exclusive when evaluated in a case-sensitive manner, and unambiguous even when ignoring case.
It won't be as simple a matter as adding duplicate entries in the effect table, as the Sequence Ontology strings should map to the same entities as the corresponding classic strings.
The text was updated successfully, but these errors were encountered:
Recent versions of SnpEff default to using strings from the Sequence Ontology to identify types of effects, rather than using the SnpEff-specific
EffectType
enum names.Eventually, the importer should be able to identify effects based on the Sequence Ontology strings. Ideally, there should be a way of recognizing effects based on either nomenclature, as they are mutually exclusive when evaluated in a case-sensitive manner, and unambiguous even when ignoring case.
It won't be as simple a matter as adding duplicate entries in the
effect
table, as the Sequence Ontology strings should map to the same entities as the corresponding classic strings.The text was updated successfully, but these errors were encountered: