Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflicting results between parent_clade and parent_lineage #205

Closed
ktmeaton opened this issue Nov 10, 2022 · 0 comments
Closed

Conflicting results between parent_clade and parent_lineage #205

ktmeaton opened this issue Nov 10, 2022 · 0 comments

Comments

@ktmeaton
Copy link
Owner

ktmeaton commented Nov 10, 2022

Conflict has been observed between the populations reported between parent_clade and parent_lineage. Example:

  • parent_clade: Omicron/BA.4/22A,Omicron/BA.2.12/22C
  • parent_lineage: BA.5.2.1*,BA.2.12.1*
  • parent_lineage_confidence: 0.28,0.688

Note that the first parent is contested, as the clade is reported to be BA.4, while the most likely lineage is BA.5.2.1*. This conflict is also seen in the first parent's confidence, which is low at 0.28.

To draw attention to this, I could create a new field called parent_conflict. If a parent_lineage is not a descendant of the corresponding parent_lineage, this field could be set to true.

At first, this will just be a field for exploratory purposes. But if it appears to help with identifying false positives, this could be a default filter to excluded samples with parent conflict.

ktmeaton pushed a commit that referenced this issue Dec 19, 2022
This was referenced Feb 22, 2023
ktmeaton pushed a commit that referenced this issue Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant