You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a summary statistic from the EAS population(No validation data, No bim, No genotype data), so how can I get the final snplist with corrected beta in the best prs module?
Because No Genotype. so I plan to use LDpred2-auto based on some other public LD data such as 1000genome EAS.
The snplist includes all the matched snps , corrected beta is that beta_auto ? "beta_auto <- rowMeans(sapply(multi_auto[keep], function(auto) auto$beta_est))"
By the way, there are two parts in the guidance (LDpred2-auto: automatic model vs Inference with LDpred2-auto) about LDpred2-auto, just the used parameter is different? which is better reference for my situation?
The text was updated successfully, but these errors were encountered:
koujiaodahan
changed the title
How to get the avaliable snp list used in LDpred2-auto module
How to get the avaliable snp list with corrected beta used in LDpred2-auto module
Feb 29, 2024
beta_auto are the final PGS effect sizes from LDpred2-auto
If you are interested in prediction only, you can use the first one; use the second one if you are also interested in inferring parameters (it is also fine for prediction)
There is a summary statistic from the EAS population(No validation data, No bim, No genotype data), so how can I get the final snplist with corrected beta in the best prs module?
Because No Genotype. so I plan to use LDpred2-auto based on some other public LD data such as 1000genome EAS.
The snplist includes all the matched snps , corrected beta is that beta_auto ? "beta_auto <- rowMeans(sapply(multi_auto[keep], function(auto) auto$beta_est))"
By the way, there are two parts in the guidance (LDpred2-auto: automatic model vs Inference with LDpred2-auto) about LDpred2-auto, just the used parameter is different? which is better reference for my situation?
The text was updated successfully, but these errors were encountered: