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

Depth of coverage #35

Open
pc2001 opened this issue Aug 1, 2018 · 2 comments
Open

Depth of coverage #35

pc2001 opened this issue Aug 1, 2018 · 2 comments
Assignees

Comments

@pc2001
Copy link

pc2001 commented Aug 1, 2018

Alex,

Is there any proposal to also include the depth of coverage statistics in the summary output?

thanks!!

@akotlar
Copy link
Collaborator

akotlar commented Aug 1, 2018

Pankaj,

I think we should include that information. To store the site-level depth (total depth) is simple, if it is provided in the VCF file (DP field). I added an issue to bystro-vcf to do so.

To store the data per-sample is harder, because it would probably require us to add a large amount of information to the output.

  • Would we want that information within the annotation output, or as a distinct file?

  • If a distinct file, how should we handle search indexing?

For per-sample information, I think we may be moving to a separate output, and allow users to search both the sample-level output and the variant-level (current annotation) output.

Would you be interested in helping me work through the per-sample question together with Cristina?

@pc2001
Copy link
Author

pc2001 commented Aug 1, 2018

Alex,
Would definitely be v. helpful to store the site level info in the annotation file!

Sure, let me know how I can help!

@akotlar akotlar added this to the Sprint 2 milestone Sep 7, 2023
@akotlar akotlar assigned akotlar and unassigned pc2001 and cristinaetrv Sep 7, 2023
@cristinaetrv cristinaetrv removed this from the Sprint 2 milestone Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants