Author Topic: Ancestry removing matches less than 8cM  (Read 11580 times)

Offline jillruss

  • RootsChat Marquessate
  • *******
  • Posts: 4,824
  • Poppy
    • View Profile
Re: Ancestry removing matches less than 8cM
« Reply #99 on: Sunday 09 August 20 17:20 BST (UK) »
Speaking as a computer ignoramus, it confused the hell out of me and I wouldn't dare try it.

Also, it says to minimise the number of matches you choose, suggesting that you, say, go from 6.3 to 6.6 but am I the only one who can't get those boxes to show the decimal point? It will only take whole numbers.

I wasn't going to bother (mostly because I'd have to go through my own matches as well as those of my 3 brothers) but 'fear of missing out' took over and I started. I now have maroon dots in front of my eyes even though I stopped about 5 minutes ago!

I also started by stupidly calling my new category 'UNKNOWN' which, of course, meant I had to scroll down each time to the bottom of my column of colour coded groups, so I hastily went back in and renamed it ANON so that its near the top!!

Then I made the mistake of scrolling down to see just how many 7.9 matches there were - sorry, as someone once said: 'life's short and then you die'. Unless I get that 'missing out' feeling back, that's it - no more. I've checked mine and my brothers' common ancestor matches under 8.0 and made sure I found a home for them but, otherwise, I surrender. White flag, and all!! If I carry on, I shall either need one of those nice cardies with the long sleeves that tie at the back, or I shall publicly badmouth each and everyone of those Ancestry bods who came up with this daft idea.

Incidentally, what IS the 'logic' behind this decision?

Are we absolutely sure that, failing a quickie degree in computer science from the Open University, there isn't a quicker, easier way of just 'selecting all' and bunging them in a colour coded (oh, here come those maroon spots again!) column?  Ancestry should have come up with one before they laid this on us.

How do we know they're not going to do a repeat announcement for the 8-10 cM category in a few months time?

HELP!!!

 BATHSHEBA BOOTHROYD bn c. 1802 W. Yorks.

Baptism nowhere to be found. Possibly in a nonconformist church near ALMONDBURY or HUDDERSFIELD.

Offline durhamgirl73

  • RootsChat Veteran
  • *****
  • Posts: 635
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Ancestry removing matches less than 8cM
« Reply #100 on: Sunday 09 August 20 17:58 BST (UK) »
I put mine into two groups named 6cm and 7cm.

I have finished one lot of 7cm = 13,138

I am currently at 14,261 of 6cm still going

What are we like!

btw I was wondering if later other lower cms with new decimal were going to go too!

Offline LizzieL

  • RootsChat Marquessate
  • *******
  • Posts: 7,974
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Ancestry removing matches less than 8cM
« Reply #101 on: Sunday 09 August 20 19:45 BST (UK) »
Here's what I did after getting the heads up from Melba about the method to automate tagging Matches.
I opened my matches in Firefox. Don't usually use this browser so I had to wait for lots of updates.
I loaded all Ancestry matches, then selected 6 - 6 cM . Decimal places don't seem possible. I started by selecting public linked trees, I pressed function (brown key Fn on my keyboard) and at same time F12. This opened a window in the bottom half of the screen, from which I selected the Console tab. I pasted in the text from the attached text file. I had opened the text file in Notepad, clicked select all and copied and pasted it in. I had made my group for all the matches the second one down after the "star"group and called it "!general". You will need to edit the text file to make it the same as your group in line 6
var groupTitle = "!general"; 
Change group name inside in quotes to your group name.
It is best if you give it a name to make it the second in the list, otherwise you need to change the group number in line 42
var myTag = choices[2].getElementsByClassName("checkbox");

Once you have pasted text in to "console" press run
If it stops, press run again
If it restarts it will skip the matches already tagged and go onto new ones.

hope it works fot you
Berks / Oxon: Eltham, Annetts, Wiltshire (surname not county), Hawkins, Pembroke, Partridge
Dorset / Hants: Derham, Stride, Purkiss, Sibley
Yorkshire: Pottage, Carr, Blackburn, Depledge
Sussex: Goodyer, Christopher, Trevatt
Lanark: Scott (soldier went to Jersey CI)
Jersey: Fowler, Huelin, Scott

Offline CelticMom

  • RootsChat Veteran
  • *****
  • Posts: 709
    • View Profile
Re: Ancestry removing matches less than 8cM
« Reply #102 on: Wednesday 12 August 20 02:12 BST (UK) »
Has anyone worked out if we need to be tagging 8cm too or are those all safe?

I’m guessing it’s not worth doing those with no trees, what about unlinked trees?
Anderson & Marr - Midlothian & East Lothian
Bennett - Devonport
Catleugh & Shiells - East Lothian
Galvin, McLaren, Cullen & Dowling - Waterford, Ireland
Littlejohns - Plymouth & London
Mansfield - Benfleet & St Pancras
Michelin - London
Newlands - Midlothian & Fife
Paterson - Canongate, Midlothian
Rutherford and Johnston - Roxburghshire
Taylor - East Lothian & Berwickshire
Thomson - Leith & Muthill
Thorney, Hawkin, Lewis - Herefordshire
Small & Paulin - Northumberland
Varrall - Kent


Offline melba_schmelba

  • RootsChat Aristocrat
  • ******
  • Posts: 1,658
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Ancestry removing matches less than 8cM
« Reply #103 on: Wednesday 12 August 20 12:11 BST (UK) »
Has anyone worked out if we need to be tagging 8cm too or are those all safe?

I’m guessing it’s not worth doing those with no trees, what about unlinked trees?
Since they introduced the decimal points and stopped rounding, I think we can assume all untagged 8.0 cM and up will not be removed. Ones without trees might have shared matches so you can't necessarily say they are of no value, but you would have to look at each individually without some other 3rd party tools like genetic affairs or shared clustering becoming available again. Also of course, ones that currently have no trees may have trees in the near future. What I am not clear about is we will actually be able to search these sub 8 cM matches in the future?

Offline durhamgirl73

  • RootsChat Veteran
  • *****
  • Posts: 635
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Ancestry removing matches less than 8cM
« Reply #104 on: Wednesday 12 August 20 13:26 BST (UK) »
Can anyone tell me when the "beginning of late August" is?  ::)

Offline youngtug

  • RootsChat Marquessate
  • *******
  • Posts: 4,307
    • View Profile
Re: Ancestry removing matches less than 8cM
« Reply #105 on: Wednesday 12 August 20 14:02 BST (UK) »
Probably after late middle August
.http://www.rootschat.com/links/05q2/   
  WILSON;-Wiltshire.
 SOUL;-Gloucestershire.
 SANSUM;-Berkshire-Wiltshire
 BASSON-BASTON;- Berkshire,- Oxfordshire.
 BRIDGES;- Wiltshire.
 DOWDESWELL;-Wiltshire,Gloucestershire
 JORDAN;- Berkshire.
 COX;- Berkshire.
 GOUDY;- Suffolk.
 CHATFIELD;-Sussex-- London
 MORGAN;-Blaenavon-Abersychan
 FISHER;- Berkshire.
 BLOMFIELD-BLOOMFIELD-BLUMFIELD;-Suffolk.
DOVE. Essex-London
YOUNG-Berkshire
ARDEN.
PINEGAR-COLLIER-HUGHES-JEFFERIES-HUNT-MOSS-FRY

Offline durhamgirl73

  • RootsChat Veteran
  • *****
  • Posts: 635
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Ancestry removing matches less than 8cM
« Reply #106 on: Wednesday 12 August 20 14:16 BST (UK) »
 ;D

Offline jillruss

  • RootsChat Marquessate
  • *******
  • Posts: 4,824
  • Poppy
    • View Profile
Re: Ancestry removing matches less than 8cM
« Reply #107 on: Wednesday 12 August 20 16:07 BST (UK) »
How many of you are considering suing Ancestry for repetitive stress syndrome?  :(
HELP!!!

 BATHSHEBA BOOTHROYD bn c. 1802 W. Yorks.

Baptism nowhere to be found. Possibly in a nonconformist church near ALMONDBURY or HUDDERSFIELD.