The current GATK version is 3.7-0
Examples: Monday, today, last week, Mar 26, 3/26/04

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Powered by Vanilla. Made with Bootstrap.
GATK 3.7 is here! Be sure to read the Version Highlights and optionally the full Release Notes.
Register now for the upcoming GATK Best Practices workshop, Feb 20-22 in Leuven, Belgium. Open to all comers! More info and signup at

Unable to strand-check genotype likelihoods file, perhaps dimishing Beagle functionality

jjmmiijjmmii Member Posts: 4
edited January 2013 in Ask the GATK team

Dear GATK team and community members,

I used ProduceBeagleInput to create a genotype likelihoods file, and ran beagle.jar according to the example in Beagle gave a warning that it is better to use a reference panel for imputing genotypes and phasing. So I downloaded the recommended reference panel (, but Beagle requires that the alleles be in the same order on both reference and sample files. The tool to do this is (, but it requires both sample and reference files be in .bgl format. This is a little disappointing since not being able to use the reference panel means Beagle's calculations won't be as accurate, although I'm not sure by how much.

I understand that this might be out of the scope of responsibility for the GATK team, but I will greatly appreciate if someone can provide suggestions to allow GATK's input to Beagle be phased using a reference panel. Or hopefully, the GATK team will write a tool to produce .bgl files?



  • Geraldine_VdAuweraGeraldine_VdAuwera Administrator, Dev Posts: 10,993 admin

    Hi Jamie,

    I sympathize with your problem, however we have no plans to produce .bgl files. We have a strong preference for standardized formats (such as VCF) and we do not have the resources to support the production and maintenance of multiple tool-specific formats. I would recommend that you redirect the question to the developers of Beagle and ask them to utilize standard formats.

    From what you describe it sounds like the easiest solution would be to modify the check_strands script to accept different inputs. We can't commit any resources to doing that, but perhaps someone in the community would be willing to do this or has already done so, and may be inclined to share their code with you.

    Good luck!

    Geraldine Van der Auwera, PhD

Sign In or Register to comment.