Author Topic: Ancestry: Seeing the regions on profile page of a non-match  (Read 440 times)

Offline goldfinch99

  • RootsChat Extra
  • **
  • Posts: 51
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Ancestry: Seeing the regions on profile page of a non-match
« on: Sunday 15 December 24 10:40 GMT (UK) »
Sometimes when researching the lines of matches I click on profiles for people who have a certain name in their tree.  Sometimes even though they don't show as a DNA match, at the bottom of the profile page it will show the ancestral regions, in the same way it does for DNA matches

Does anyone know why this is?  Is it because the person is a 6cM match but doesn't meet the 8CM limit to show up in matches?

Offline melba_schmelba

  • RootsChat Aristocrat
  • ******
  • Posts: 1,847
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Ancestry: Seeing the regions on profile page of a non-match
« Reply #1 on: Monday 23 December 24 19:55 GMT (UK) »
Sometimes when researching the lines of matches I click on profiles for people who have a certain name in their tree.  Sometimes even though they don't show as a DNA match, at the bottom of the profile page it will show the ancestral regions, in the same way it does for DNA matches

Does anyone know why this is?  Is it because the person is a 6cM match but doesn't meet the 8CM limit to show up in matches?
Good question! I am not sure I have noticed this. But I do know that 6-7cM matches are in some way still active, as they still get updated as common ancestor links for those that have saved them.

Online familydar

  • RootsChat Aristocrat
  • ******
  • Posts: 1,051
    • View Profile
Re: Ancestry: Seeing the regions on profile page of a non-match
« Reply #2 on: Monday 23 December 24 20:04 GMT (UK) »
For anc to know someone's ethnicity, that person must have taken a DNA test, they just don't match with you.

Jane :-)
ALLEN
BARR, BARRATT, BERRY, BRADLEY,BRAMLEY,BRISTOW,BROWN,BUGBIRD,BUTLER
CAIN,CARR,CHAPMAN,CHARLES,CH*LTON,CHESTER,COCKETT
COLLASON,COLLYER,CORKERY
DARLING, DENYER,DICKERSON,DOLLING,DURBAN
FARMER,FURNELL
GIBSON,GILES,GROOMBRIDGE
HALL,HAMBIDGE,HARMES,HART,HICKS,HILL,HOLLOWAY
JACKSON
K*AT*S
LANCASTER,LINTON
MCDONALD,MCFADEN,MEARS,MILLARD
NICOLAS,NOAK,NORTH
PARFIT,PORTER
RIPPINGALE,ROBINS
SEARLE,SPENCER,STEDHAM
TYLER,TILLY,TUCKWELL
WADE,WAGER,WALKER,WATSON,WEBB,WITHRINGTON,WOOD

Offline melba_schmelba

  • RootsChat Aristocrat
  • ******
  • Posts: 1,847
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Ancestry: Seeing the regions on profile page of a non-match
« Reply #3 on: Monday 23 December 24 21:36 GMT (UK) »
For anc to know someone's ethnicity, that person must have taken a DNA test, they just don't match with you.

Jane :-)
Yes, but as gf indicated, previously you didn't see any DNA related data for a profile unless you or an account you manage match them, it seems like this might have changed, unless it was a bug.


Offline goldfinch99

  • RootsChat Extra
  • **
  • Posts: 51
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Ancestry: Seeing the regions on profile page of a non-match
« Reply #4 on: Tuesday 24 December 24 13:24 GMT (UK) »
I don't think it's a recent change. I did the test nearly 3 years ago I've noticed this a few times.  And it's usually when I've opened a tree belonging to a match but they don't have many names on it, so I start putting names from their tree into the search function, and then click the names of users who have that name in their tree.  That's what made me think it could be that they do match but don't reach the current 8cm cut-off to show as a match.

These are all ones where I can't figure out the common ancestor, but this person is on a possible common ancestor line, and it makes me think this could be a sign that I  have found a line for the common ancestor and that the glitch may have occurred when they reduced matches to 8 from 6cM and someone forgot to change it so that the ancestral regions didn't show up even though it says they're either not a match or haven't tested. This seems to be a logical way for the glitch to be introduced, that it's a holdover of old code and someone removed the upper parts of the code but forgot to scroll down through the code and remove this part.