-
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
missing value where TRUE/FALSE needed error with susie_rss #206
Comments
@maguileraf We've seen this error before; does setting |
Thank you for your suggestion @pcarbo. Unfortunately, I get the same error |
Which version of susieR are you using? Do you have the latest version available from GitHub? |
0.12.35 |
I upgraded to the latest version from GitHub (0.12.40) and I keep getting the same error in certain regions. |
@maguileraf Any chance you would be able too share the code and data for one of the regions so we can try to reproduce this error? |
@pcarbo unfortunately, I can't. However, I used refine=T and it fixed the error. |
That's interesting. Thanks for sharing your solution — it may be useful to others. |
@pcarbo refine=T fixed it for certain regions, but I keep getting this error for other regions. Any other suggestions? |
@maguileraf Can you share at least the call to |
|
Can you share the warnings? There might also be some inconsistencies between |
I think it's an inconsistency between z and R. I am using UKB data to run a case/control GWAS using REGENIE. I've used the same file to generate the LD matrix, but I still get inconsistencies. Do you think the covariates used when running the GWAS can cause these discrepancies? |
With REGENIE it is hard to say because it is not the same model as susie. Our general recommendation would be to use a method that uses a similar model to susie (e.g., the linear regression method in PLINK). For case-control data, a linear regression approach might be preferrable to logistic regression. Regarding covariates, you may need to regress out the covariates from the genotype matrix (or LD matrix) if the covariates are correlated with the SNPs. |
@pcarbo I am still trying to make this work. I have access to the individual-level data, but my case and controls are not balanced. Does it make sense to use susie instead of susie_rss? |
@maguileraf Not knowing the full details of your analysis, it is hard to say for sure, but broadly speaking, the use of the full-data linear regression model for case-control data has been better studied and has stronger accuracy guarantees than the summary-data approach, so yes if you are able to use |
Hi there, I had the same issue while running with ref ld matrix. I think it is due to the inconsistency in dimensions between the sumstats file and the ld matrix. For example, if you select a locus of a snp of interest, and then compute the ld matrix in a reference, it is very likely that some snps within the region of the locus are not included in the reference panel. Thus, you might have 2000 rows in the locus, but 1000 rows in the ld matrix. |
@yningvu Can you please share your call to |
Hi, I am trying to run susie_rss and for some regions it works. However for other larger regions, I get the following error message:
WARNING: XtX is not symmetric; forcing XtX to be symmetric by replacing XtX with (XtX + t(XtX))/2
Error in if (neg.loglik.logscale(lV, betahat = betahat, shat2 = shat2, :
missing value where TRUE/FALSE needed
Calls: susie_rss ... single_effect_regression_ss -> optimize_prior_variance
In addition: There were 40 warnings (use warnings() to see them)
Any advice?
The text was updated successfully, but these errors were encountered: