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.

Sign up for GitHub

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

Jump to bottom

set=Intersection is not fully informative; add FOUND_IN tag? #59

Open
dnil opened this issue Oct 12, 2022 · 2 comments
Open

set=Intersection is not fully informative; add FOUND_IN tag? #59

dnil opened this issue Oct 12, 2022 · 2 comments

Comments

@dnil
Copy link
Contributor

dnil commented Oct 12, 2022

This is a little bit of a classic! Since it will not be obvious between runs what callers were combined for set=Intersection merges (found by all callers). The FOUND_IN tag used by some other tools is rather nice, and very similar to svdb_origin. I think we'll add the latter as a synonym in Scout, but it would not hurt renaming it FOUND_IN here - or adding it if you find they differ on edge cases.
@dnil
Copy link
Contributor Author

dnil commented Oct 12, 2022

Parsing it now: Clinical-Genomics/scout#3630 - but FOUND_IN would still not hurt, at a low prio.

@J35P312
Copy link
Owner

J35P312 commented Oct 19, 2022

Hello! I have added SUPP_VEC similar to SURVIVOR:

it is a list of 1 or 0 telling which callers detected the variant. The callers are listed in the header. Maybe that is good enough?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dnil @J35P312