ERROR: Reference and target files have no markers in common in interval: 6:63979-21294564
2
3
Entering edit mode
3.7 years ago
jkheirm ▴ 30

Hello,

I am a novice in the world of bioinformatics. I am attempting to work out genotype imputation for a set of 8K+ samples. I am only interested in imputing data for chromosome 6 to be used in later downstream analysis. I am using Beagle for the genotype imputation using the following script:

java -Xss5m -Xmx16g \
-jar beagle.18May20.d20.jar \
gt=immuno_chrom6_for_imputation.vcf.gz \
ref=chr6.1kg.phase3.v5a.b37.bref3 \
map=plink.chr6.GRCh37.map \
out=immuno_chr6_imputed \
nthreads=16 \
ne=20000 \
impute=true \
seed=-99999

The data was passed down to me and i was told that the appropriate reference genome to use is the hg19 (GRCh37) build. When I run this script, i get the following error.

ERROR: Reference and target files have no markers in common in interval: 6:63979-21294564

Is there a way troubleshoot this? I queried my dataset based off position values and the interval 63979-21294564 is about 800 samples out of 8894.

Any help would be greatly appreciated!

beagle imputation • 2.2k views
ADD COMMENT
1
Entering edit mode
2.9 years ago
Raquel ▴ 10

I had the same error with beagle5.1 and what solved my problem was to increase the window size from the default value (50) to 100cM:

java -Xss5m -Xmx16g \
-jar beagle.18May20.d20.jar \
gt=immuno_chrom6_for_imputation.vcf.gz \
ref=chr6.1kg.phase3.v5a.b37.bref3 \
map=plink.chr6.GRCh37.map \
out=immuno_chr6_imputed \
nthreads=16 \
ne=20000 \
impute=true \
window=100 \
seed=-99999

You can try to keep increasing the window size until it finds a good overlap for being able to impute. Hopefully that works for you as well.

ADD COMMENT
0
Entering edit mode
3.2 years ago
Domi • 0

Hello there! I am facing a very similar issue. Did you manage to solve the issue out?

ADD COMMENT
0
Entering edit mode

follow up: Have you tried running any earlier Beagle versions? I ran the same input files that were producing the exact same error on Beagle5.1 on Beagle4.0 and everything went smoothly.

Best

ADD REPLY

Login before adding your answer.

Traffic: 2346 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