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

For multiple samples, why should cuteSV be run twice? #150

Open
jahemker opened this issue Aug 13, 2024 · 1 comment
Open

For multiple samples, why should cuteSV be run twice? #150

jahemker opened this issue Aug 13, 2024 · 1 comment
Labels
question Further information is requested

Comments

@jahemker
Copy link

Hi, I am planning on calling SVs in multiple samples to get a population set. I saw in #143 that it is recommended to first run cutesv on each sample, merge into a population set, then re-genotype each sample with the population set. Can any insight be provided on why re-genotyping is recommended as opposed to just taking the first merged set?

@tjiangHIT
Copy link
Owner

Hello @jahemker,

Thank you for using cuteSV.

Re-genotyping is recommended in the workflow of joint SV calling for several key reasons:

  1. As the population-scale SV callsets evolve with increasing sample sizes, re-genotyping enables the accurate determination or refinement of original SV zygosities. This is important because initial analyses may have been affected by issues such as insufficient coverage, which could lead to inaccurate SV zygosity determination.

  2. After merging, the breakpoint or size of the corresponding SV might differ from the original one reported by the first-round of cuteSV. Re-genotyping in the second round of cuteSV allows for the determination of SV characteristics based on the new SV targets in each individual.

These steps ensure that the SV callset remains accurate and reflective of the most up-to-date data.

Hope this helps you!

Best regards,

Tao

@tjiangHIT tjiangHIT added the question Further information is requested label Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants