Major Updates and Improvements to MyHeritage DNA Matching

MyHeritage has made major updates and improvements to the company’s DNA Matching service.

Anyone who took a MyHeritage DNA test, and anyone who uploaded DNA data from another service, will now receive even more accurate DNA Matches; more plentiful matches (about 10 times more); fewer false positives; more specific and more accurate relationship estimates; and indications on lower confidence DNA Matches to help focus research efforts.

The company also also added an initial release of the long-requested chromosome browser.

More information can be found in the MyHeritage Blog post at:  http://bit.ly/2mtj0ZO.

8 Comments

Fewer false hits? I got 3260 false hits and only 2 accurate matches. I keep track of cousins up to 8th level.

Like

This is fantastic news for those of us who use this site for the international DNA matches. I get far more on My Heritage for my Aunt’s DNA than on any of the other sites.

Like

One thing missing from My Heritage is shared matches. I use this function on Ancestry to help categorize matches without family trees.

Like

YEAH!!! Doin’ the Genealogy Happy Dance. GREAT NEWS!!! They added a chromosome browser. Now if they would just use black or dark grey for their text so I could read it, I would be sooo happy.

And Maureen, they do have shared matches. Click the expand button. Now with the chromosome browser, we can have real matches, not possible or probable matches like we have on Ancestry. Please remember that with Ancestry, we have NO provable matches.

Like

    I still can’t find the chromosome browser for my MyHeritage DNA matches – unless it is somehow hiding in the extremely tiny pale gray text that borders on the invisible. Until I read the comments here, I thought maybe the blog announcing the chromosome browser was premature, and the browser itself had still not been put into production. The rest of the blog is worth reading, too. It concerns me that there is so much fiddling with the DNA data behind the scenes, and so little technical documentation about exactly what is happening and what the consequences are.

    Like

    The chromosome browser data is located on each individual DNA Match page. From your DNA Match page, next to each match, on the far right hand side of the screen, you will see a purple button that says “Review DNA Match”. If they have a tree, there is also a “View tree” button. Click Review DNA Match to see your surnames in common (and ancestors if applicable) matches in common, ethnicity and at the bottom, the Chromosome Browser. You can download the match in a spreadsheet – especially useful for 1st or 2nd cousin matches with multiple matching strings.

    It’s not perfect, but is still 500% better than any of the pseudo matching tools offered by Ancestry. Thanks MyHeritage.

    Like

I’m having a problem with smart matches and record matches. I don’t want to confirm anything I haven’t researched but am just starting out so I don’t have a lot of information going back. Do I say “don’t confirm” even if some of the names are in my tree?

Like

    No, I don’t confirm those smart and record matches either, even if it is in my own tree, because when I pull each match up there simply is no visible source match information to confirm it. That is a really huge data gap. If I am doing something wrong, somebody educate me please.

    Like

Leave a Reply

Name and email address are required. Your email address will not be published.

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s

You may use these HTML tags and attributes:

<a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <pre> <q cite=""> <s> <strike> <strong> 

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: