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

Different somatic calls across Monopogen v.1.0 and v1.6.0 #58

Open
ypershad opened this issue May 9, 2024 · 5 comments
Open

Different somatic calls across Monopogen v.1.0 and v1.6.0 #58

ypershad opened this issue May 9, 2024 · 5 comments
Labels
help wanted Extra attention is needed

Comments

@ypershad
Copy link

ypershad commented May 9, 2024

We are following the example here and noticed the following overlap with the example data between somatic SNV calls made from scRNAseq with v1.0 and v1.6.

image

Are you surprised that ~25% of the variants differ between versions? Do you think that the v1.6 calls are more trustworthy?

Thanks for any input that you have and for building this wonderful tool.

@jinzhuangdou
Copy link
Collaborator

Thanks for you posting such comparison. Your testing is based on our chr20 MAESTER dataset or yourself? I will look at a bit and feedback to you soon.

@ypershad
Copy link
Author

Based on your chr20 MAESTER dataset. Thank you!

@jinzhuangdou jinzhuangdou added the help wanted Extra attention is needed label May 15, 2024
@jan-engelmann
Copy link

Hey,
do you have an update here? 🙏

@jinzhuangdou
Copy link
Collaborator

Hi, could you try the new version (updated in Jun 23,2024)? Only running the LDrefinement step is okay. The current version v1.6.0 imposes more filtering than v1.0.1. In v1.0.1, I noticed there are some loci with multi-alleles. This leads to the inconsistence on sequencing depth counting. The new version has fixed this issue.

@jinzhuangdou
Copy link
Collaborator

jinzhuangdou commented Jun 23, 2024

Another is you can check whether the discordance loci between two versions are both low sequencing depth. The updated version is the optimal one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants