TwoSampleMR and ieugwasr
0
3
Entering edit mode
S T ▴ 90
@s-t-4287
Last seen 2.1 years ago
United Kingdom

Hi there, I am trying to use the TwoSampleMR package and ieugwasr for MR analysis and have been trying to clump SNPs using local LD file, but getting this error. I wonder if you know how it can be resolved? Thanks. E


clumped_all_exp_dat<-ld_clump(
    dplyr::tibble(rsid=x[,1], pval=x$pval_beta, id=x$phenotype_id),
    plink_bin = genetics.binaRies::get_plink_binary(),
    bfile = "/path/GWAS/EUR",
clump_r2=0.3
)

Logging to /tmp/Rtmp2j13gV/file93515a195b97.log.
Options in effect:
  --bfile /well/cartography/users/pcz760/PID/GWAS/EUR
  --clump /tmp/Rtmp2j13gV/file93515a195b97
  --clump-kb 10000
  --clump-p1 0.99
  --clump-r2 0.3
  --out /tmp/Rtmp2j13gV/file93515a195b97

385575 MB RAM detected; reserving 192787 MB for main workspace.
Allocated 19299 MB successfully, after larger attempt(s) failed.
8550156 variants loaded from .bim file.
503 people (0 males, 0 females, 503 ambiguous) loaded from .fam.
Ambiguous sex IDs written to /tmp/Rtmp2j13gV/file93515a195b97.nosex .
Using 1 thread (no multithreaded calculations invoked).
Before main variant filters, 503 founders and 0 nonfounders present.
Calculating allele frequencies... done.
8550156 variants and 503 people pass filters and QC.
Note: No phenotypes present.
Warning: No significant --clump results.  Skipping.
Error in file(file, "rt") : cannot open the connection
In addition: Warning messages:
1: In format_data(random_df, type = "exposure", phenotype_col = "phenotype",  :
  The following columns are not present but are helpful for harmonisation
eaf

2: In file(file, "rt") :
  cannot open file '/tmp/Rtmp2j13gV/file93515a195b97.clumped': No such file or directory
ieugwasr clumping TwoSampleMR • 1.8k views
ADD COMMENT
0
Entering edit mode

Hello, I am facing the same problem. Did find a solution ?

ADD REPLY

Login before adding your answer.

Traffic: 586 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6