Author Topic: Ancestry Assignment to Both Sides  (Read 2661 times)

Offline phil57

  • RootsChat Veteran
  • *****
  • Posts: 648
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Ancestry Assignment to Both Sides
« Reply #45 on: Wednesday 24 April 24 11:03 BST (UK) »
Yes, as I understand it, the situation is as ikas says.

The segments that your match has in common with you don't contain enough information for Sideview to make a determination based on what it currently knows about the segments of your DNA already assigned to one side or the other, as the information available from that match is not sufficiently in common with your existing assigned matches. If you are certain about the parental side of the match, you can manually assign it and that should help improve the Sideview algorithm for you going forward.
Stokes - London and Essex
Hodges - Somerset
Murden - Notts
Humphries/Humphreys from Montgomeryshire

Offline Steve3180

  • RootsChat Extra
  • **
  • Posts: 2
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Ancestry Assignment to Both Sides
« Reply #46 on: Wednesday 24 April 24 11:59 BST (UK) »
Interesting discussion, I'd like to add my thoughts.
Like many on here my both sides matches jumped from just my sister to about 40, all of which  significantly have 2 segments that match.
It seems to me that the phasing falls into two stages, first separate out the base pairs into phased segments, then allocate those segments to a parent. The first part should be relatively easy given sufficient matches, the second part much harder as it would depend on matches having two or more segments in common. If this is correct then the errors are likely to come in at the parental allocation stage.
So then what I see as the underlying data that Ancestry have calculated would be a bunch of phased segments allocated to one parent or other, say for arguments sake about two hundred. Of these two hundred segments 90% are correctly assigned to a parent and 10% (about 20 segments) wrongly (based on Ancestry's numbers).
So then to get a spurious both sides allocation it is only neccesary to match within one of the segments in the correct group and one of the segments in the wrong group. Hence my both sides matches all have 2 segments in common.
Quite why the number of both sides matches has recently jumped I have no idea, presumably changes in the algorithm.
An interesting side effect of this process would be the ability of Ancestry to eliminate a large amount of IBC matches since they would match neither set of parental phased data.

Online Biggles50

  • RootsChat Veteran
  • *****
  • Posts: 953
    • View Profile
Re: Ancestry Assignment to Both Sides
« Reply #47 on: Wednesday 24 April 24 17:52 BST (UK) »
If only Ancestry bought out Gedmatch and integrated their tools into Ancestry!

With my Both Sides being below 25cM they are not really worth researching.

Same with my Wife’s matches, all are lowish cM.