-
Notifications
You must be signed in to change notification settings - Fork 47
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
Number of CSs #228
Comments
@Xi-Cao If the result does not change, it means that all CSs satisfied the previous purity criterion. |
Thanks for your reply. |
By the way, considering it affects the output of CSs, is there a recommended |
The basic idea is that there should be one CS for each independent signal (causal SNP), and different regions will have different numbers of causal SNPs. Since susie sometimes outputs a CS containing a very large number of SNPs (each with small PIP), the "purity" filter is helpful for removing these CSs that are likely not interesting. Therefore, we recommend setting "min_abs_corr" to a number larger than zero, but we do not have a recommendation as to the exact number. (The default min_abs_corr = 0.5 often works well.) |
I get it, thank you!😊 |
Hi there,
I'm confused that how the CSs were selected. I thought the order
min_abs_corr
was used to determine the min corr of SNPs incorporated into a CS.While when I tested in another locus, using this command didn't change the number of CSs it originally found. So why didn't it capture some new CSs with lots of SNPs, that have very small min corr?
Thanks,
xicao
The text was updated successfully, but these errors were encountered: