Thursday, 6 February 2020

The finding of an ancestor and a nickname

It is a pleasure to introduce this guest blog post by my project co-administrator, Jamee Ryan Carlin. Using newly available online records, Jamee was able to trace her Ryan ancestral line back to Tipperary in the early 1800s and discovered additional clues that may help focus further research.

The finding of an ancestor and a nickname
by Jamee Ryan Carlin

It all started with a piece of paper signed by a parish priest in 1935. Without it, I could not have identified my great grandfather’s brothers and sisters, nor where they lived. It was very frustrating, my great grandparents were only 3 times removed from our generation

All I knew for sure was that my great grandfather’s name was Laurence (Lawrence) Ryan, his parents were John Ryan and Mary Gleeson of County Tipperary and he had siblings. Anyone familiar with the Ryans of Tipperary knows there were many John Ryans and Mary Gleesons and that in the mid-1800s there were almost as many Ryans in Tipperary as there were in the rest of Ireland combined. 

Lawrence Ryan and his Grandchildren

In 1935, my great grandfather, aged 94 and unsure of the date of his baptism, wrote the parish of Ballinahinch where he was baptized. He received a note back, on lined paper, with a seal and signature from the parish priest stating he was baptized on 29 June 1843 in the Ballinahinch Catholic Church. This paper was unearthed and shared by one of my cousins in the early 2000s and after years of picking other’s brains, I finally had my first solid clue. 

In 1989, the same cousin wrote the Nenagh District Heritage Society. The Society confirmed there was a Laurence Ryan born of John Ryan and Mary Gleason and baptized in 1843. In addition, they stated, he had a brother named Owen, baptized 1845 with the address listed as Ballikinlalee. Furthermore, there was a Laurence Ryan in the Ballikinlalee Tithe Applotment List, ca. 1828 who, the society conjectured, may have been his grandfather, since it was the practice to name the first born after the father’s father. 

This was all the information the society had at the time and I did not see this document until late 2019 when a first cousin, once removed, received a copy, contacted me and shared it. By then I knew that Laurence Ryan was not the firstborn nor was he only one of two children but one of five or six, maybe more. And possibly, just possibly, there were some half-siblings. Ah … the wonders of modern technology!

The note from the Parish Priest in 1935 (also called Laurence Ryan)

Once vital information became available online for use in genealogy, facilitating research, I discovered that Laurence’s parents John Ryan and Mary Gleeson married on 7 Feb 1836 in Newport Parish, County Tipperary. Their witnesses were Tim Ryan and Patrick Hogan. I also discovered that Laurence’s (b. 1843) siblings were: Patrick (b. 1837), Timothy (b. 1838), Patrick (b. 1839, indicating the first Patrick had died prior to the second), Margaret (b. 1844) and Owen (b. 1845). Owen’s baptism record was a key find as it noted the Ryan’s address in County Tipperary, Ballikinlalee, a little townland located about 22km SW of Nenagh.

In 1845, a Valuation Office House Book for Ballykinlalee listed a John Ryan (Mathew), lot 10, Patrick Ryan (Mathew), Lot 8 in addition to a Michael Ryan, (Long), lot 6. The Poor Law Union Burial Rate Books of 22 Feb. 1845 also listed these individuals in addition to a Timothy Ryan, Laurence Ryan and a William Gleeson who, hopefully, will tie into my search for Mary Gleeson, John’s wife. Another exciting discovery is the presence of a John McNamara, lot 7. One of the sponsors for John’s son Patrick (b. 1829) was an “Ony” McNamara.

House Book 1845 (Valuation Office)

The House Valuation in Ballykinlalee was performed on Thursday, 30 Oct. 1845, only three days prior to the baptism of John’s youngest son Owen on Sunday, 2 Nov 1845. The hand written records included another piece of critical information, our Ryan family nickname. This discovery was only recent and very exciting. As noted above, John Ryan was listed with the nickname of Mathew (Matt).

Quick reviews of the Poor Law Union Burial Rate Books of 1946 and 1847 confirm John Ryan’s continued presence in Ballykinlalee but he disappears from the records in 1848. Working backwards, John appears in the Tithe Applotment records of 1837, holding land in common with Timothy Ryan (also noted in the Poor Rate Book of 1845). The 1837 record includes Laurence Ryan and William Gleeson. A John Ryan also appears in the 1827 Tithe Applotment records with a Laurence, Samuel and an unnamed Ryan.

While researching other records I located traces of Ryans in Ballykinlalee, back to at least 1641. In 1641, Connor & Owen, “O’Mulryan[s] (Ryan[s]) of Owney and Owneybeg, Barony of Owney and Ara” Parish of Kilcomenty are noted as proprietors of land in “Ballykinloghlogh” with a grant being given to a Henry Prittie and John Wood for much of the acreage. 1 A later accounting entry in the 1886 Calendar of Treasury Books included the notation regarding “part of the lands of Ballykinloghie” which had been granted on “16 Jun 1666 to Pat. Allen, gent.” 2

I hope someday, with the aid of DNA and haplogroups to be able to determine if the seventeenth century Ryans in Ballykinlalee were distant ancestors but for now I am so very happy to have made the breakthrough noted above and am looking forward to learning more and especially being able to devote more time to my great great grandmother, Mary Gleeson.
Jamee Ryan Carlin
Feb 2020

Sources 
1. (Citation: “Records of Four Tipperary Septs: the O'Kennedys, O'Dwyers, O'Mulryans, O'Meaghers”, Dr. Martin Callanan, L.R.C.P. & S.I, (O'Gorman Printinghouse, 1938), out of print. http://www.igp- web.com/tipperary/septs/omulryans.htm {accessed 19 Sep 1919].)

2. (Citation: ‘Entry Book: February 1686,1-5’, in Calendar of Treasury Books, Volume 8, 1685-1689, ed. William A Shaw (London, 1923), pp. 546-572. British History Online http://www.british-history.ac.uk/cal-treasury-books/vol8/pp546-572 [accessed 19 Sep 1919].)





Thursday, 8 August 2019

Uploading your new Big Y-700 results

The Big Y test changed to a completely new technology earlier this year. It now covers 50% more of the Y chromosome than previously. And so it is anticipated that the new test will discover additional SNP markers that the old technology did not detect. Furthermore, the new SNPs should be able to more accurately date the various branching points on the Tree of Mankind.

It also gives us approximately 700 STR markers whereas the previous test only gave approximately 500 STRs. As a result, the old test is called the Big Y-500 and the new one is called the Big Y-700. Going forward, all new Big Y orders will use this new technology.

For those who did the old test, it is possible to upgrade from the Big Y-500 to the Big Y-700. There are several people within the project who have done this upgrade. But for everyone who does the new test, or upgrades from the old version to the new version, it is essential that you upload a copy of your results to the Big Tree so that we can get some essential additional analyses. You will find instructions for doing so on the Big Tree website here and on the Y-DNA Data Warehouse website here but I include a briefer summary below.


What do you get from your Results?

Your results should be analysed within a week or two and you can check them by navigating to your particular portion of the Big Tree. For members of Ryan Group 2 (for example), your Terminal SNP is M756 and you will find this branch on the Big Tree here (see screenshot below). The diagram nicely illustrates your placement on the Tree of Mankind and the surnames of the people sitting on neighbouring branches to your own. This information can be very useful for determining the geographic origins of your particular direct male line and for determining if your name is associated with an Ancient Irish Clan.

Project Administrators can use programmes like the SAPP tool to generate Mutation History Trees and determine the likely branching structure of your particular "genetic family" from the time of surname origins up to the present day. This process can also help identify which Ryan's are more closely related to you and which are more distantly related. It is also possible to date the branching points within the Mutation History Tree using SNP data as well as STR data. This process is likely to become more accurate with the advent of the new Big Y-700 data and the identification of new SNPs. It is anticipated that the new data will reduce the number of "years per SNP" from about 130 to about 80 years per SNP. You can read more about this here.

You can also click on your surname above your kit number for an analysis of your Unique / Private SNPs. These may prove useful in the future for defining new downstream branches in the Mutation History Tree and for dating new branching points. But this very much depends on new people joining the project and undertaking Big Y-700 testing (so that we can compare apples with apples). And as this is a new test, it is likely that we will have to wait some time before we begin to see real benefits from it.







Creating a Link to your Big Y results

In order to create a downloadable link to your Big Y results, first log in to your FTDNA account and go to your Big Y Results page ...



Then click on the blue Download Raw Data button ...



Then you need to create a link to two separate files - your VCF file and your BAM file. The VCF file is used for placing you on The Big Tree. The BAM file is used for high-end technical analysis by the folks at the Y-DNA Data Warehouse. You can see some of the results so far on their Coverage Page here (and if you like you can search for kits by surname, including your own).




1) to create a link to your VCF file, right click on the green Download VCF button, and then click on "Copy link" from the drop-down menu. You will later paste this link into the the "Download URL" box on the Submission Form.
Alternatively you can simply (left) click on the green Download VCF button and this downloads a 10 MB file to your computer. This can then be directly uploaded via the Submission Form below. However it is preferable (and less problematic) to generate a link instead.
2) to create a link to your BAM file, click on the green Generate BAM button. You will then get a message that "Your Big Y BAM file is currently being generated" (see below). This generates a very large BAM file ... but it takes several days to prepare so you will have to come back to this page in a few days time! Put a reminder in your diary / calendar!



Uploading your VCF file

Having created the first link (to your VCF file) and copied it, click here to go to the Y-DNA Data Warehouse and fill in the form with your standard information - email, kit number, surname of your paternal MDKA (Most Distant Known Ancestor), and (most importantly) the link to your file - you do this by pasting the link you copied earlier into the "Download URL" box underneath the heading "Raw Data Upload" at the bottom of the page.


If you want to upload the actual file itself (rather than a link), click on the blue Direct tab under "Raw Data Upload" and then click on the "Choose File" button and attach the file from where you downloaded it onto your computer (on my laptop, the "Choose File" button appears to be slightly hidden under some text but it works if you click on the start of the text). 


Don't forget to tick the checkbox to confirm you agree with the Data Policy and then click the blue Submit button.



Uploading your BAM file

Several days later, come back to this same place to get a link to your newly generated BAM file. So, navigate to your Big Y Results page, and after clicking on the blue Download Raw Data button, you will find that the BAM file has been generated. DO NOT DOWNLOAD IT - you don't need to and it is way too big. Instead, click on the green Share BAM button and then the green Copy button in order to copy a link to your BAM file. You will share this link in the next step.



Then go to the Y-DNA Data Warehouse and fill in the same form as before BUT ...

  1. select Other for the Testing Lab
  2. enter your Kit ID Number 
  3. leave everything else on its default setting
  4. paste the link to the BAM file in the "Download URL" box underneath the heading "Raw Data Upload"
  5. tick the checkbox to confirm you agree with the Data Policy and then click the blue Submit button




Maurice Gleeson
Aug 2019



Tuesday, 4 June 2019

Birth of a new Genetic Family - Group 10

A new project member recently joined the Ryan DNA Project (CR-5799). He does not have any Ryan's among his list of matches but he does match another Ryan within the project (SR-3236) at a Genetic Distance of 7/37 (i.e. 7 steps away from an exact match). These two people also share a number of STR marker values in common, creating a relatively Unique STR Pattern (USP) compared to other project members. And on this basis I have decided to group them together.

Arrows indicate the Unique STR Pattern for this group

How old is the new group?
Even though they are genetically related to each other (probably within the last 1000 years or so), their common ancestor could have lived back in the 1600s or earlier (i.e. it is a distant connection). The TiP Report predicts an approximate 50% probability that they share a common ancestor within the last 14 generations (i.e. born about 1530 AD) and an approximate 95% probability within the last 24 generations (i.e. about 1230 AD). More accurate predictions could be achieved by testing to a higher number of STR markers (e.g. Y-DNA-111) but there would still be a range of about +/- 300 years on either side of the midpoint estimate. In other words, these estimates will always be crude (from a genealogical perspective).

However, given that the connection is so far back, and they both carry the same Ryan surname, this group could represent a relatively ancient Ryan subgroup, that has been around for many hundred years, but which does not have many surviving descendants.

Where did they come from?
There is no information available about the MDKA (Most Distant Known Ancestor) for either project member so there are no clues from either individual's genealogical data. We may find clues among the surnames of their matches, or from the terminal SNP markers of their matches.

Matches' Surnames
CR-5799 has 16 matches (at the 37 marker level of comparison) and they have the following surnames: Burns, Coleman, Coulson (x2), Ford, Hagan, Healy, Jackson, Johnson, Lewis, Mason Minett, Pemberton, Potteet, Smith, Williams

SR-3236 has 13 matches (at the 37 marker level of comparison) and they have the following surnames: Creswick (x3), Eason (x3), Easton, Evans, Hayes, Hobson, Paige, Pelsue, Ratcliffe

There are both English & Irish names among these matches so this suggests an origin in either Britain or Ireland within the last 1000 years (our timeframe of interest).

Matches' Terminal SNPs
Here is a list of the most relevant Terminal SNPs of the matches of each of the members. This information may help place them on the Tree of Mankind and this in turn may allow us to identify a likely origin for this particular group.

At the 37-marker level of comparison: CR-5799 ... L21; SR-3236 ... U106, S25007

At the 25-marker level of comparison (most frequent SNPs only - numbers in brackets are number of times each SNP appears):
  • CR-5799 (570 matches) ... L20 (3), L21 (2), L48 (5), L513 (2), U106 (3), U152 (4), U198 (2), Y34483 (4), Z156 (2), Z16532 (3), Z18 (2), Z195 (2), Z9 (2)
  • SR-3236 (191 matches) ... BY32442 (3), BY34891 (2), L21 (2), S25007 (2), S7432 (2), U106 (2)
Below are the SNP Progressions for these most frequent SNP markers. A SNP Progression is simply the sequence of SNP markers that characterise each branching point on the Tree of Mankind, starting at the level of the Haplogroup (R in this case) and progressing all the way "downstream" to the Terminal SNP.  Comparing SNP Progressions helps us see exactly where each terminal SNP sits on the Tree of Mankind relative to all the other SNPs:
  • L21 (2) ... ... R-P312/S116 > Z290 > L21
  • L513 (2) ... .. R- P312/S116 > Z290 > L21 > DF13 > L513
  • Z16532 (3) ... R-P312/S116 > Z290 > L21/S145 > DF13 > DF21/S192 > FGC3213 > Z16532
  • Y34483 (4) ... R-P312/S116 > Z290 > L21 S145 > DF13 > DF21/S192 > FGC3213 > Z16532 > Y34485 > Y34483
  • BY34891 (2) ... R-P312/S116 > Z290 > L21 S145 > DF13 > FGC11134 > A353 > Z16250 > A114 > CTS4466/S1136 > S1115 > A541 > S1121 > Z16251 > A159 > Z17981 > A923 > BY21614 > BY30545 > BY34891
  • L20 (3) ...  R-P312/S116 > Z40481 > ZZ11 > U152/S28 > L2/S139 > Z367/S255 > L20/S144
  • U152 (4) ... R-P312/S116 > Z40481 > ZZ11 > U152
  • Z195 (2) ...  R-P312/S116 > Z40481 > ZZ11 > DF27/S250 > Z195/S355
  • S7432 (2) ... R-P312/S116 > Z40481 > ZZ11 > DF27/S250 > ZZ12 > ZZ41 > S7432
  • U106 (3) ... R-U106/S21
  • S25007 (2) ... R-U106/S21 > ...
  • Z18 (2) ... ...   R-U106/S21 > Z2265 > Z18
  • Z156 (2) ... ...  R-U106/S21 > Z2265 > Z381/S263 > S264/Z156
  • U198 (2) ... ...  R-U106/S21 > Z2265 > Z381/S263 > Z301/S499 > S1688 > U198
  • L48 (5) ... ... ... R-U106/S21 > Z2265 > Z381/S263 > Z301/S499 > L48
  • Z9 (2) ... ... ... .. R-U106/S21 > Z2265 > Z381/S263 > Z301/S499 > L48 > Z9
  • BY32442 (3) ... R-U106/S21 > Z2265 > Z381 S263 > Z301/S499 > L48 > Z9 > Z30/S271 > Z2 > ~22277095-G-A > S16218 > b38:7436045AT>A > BY32442

Simply ordering the SNP Progressions in this way allows us to see that the matches of these two group members sit on very distinct branches of the Tree of Mankind (some separated by tens of thousands of years) indicating that a lot of them are "chance matches" that just happen to have similar STR genetic signatures. Thus we cannot reliably predict on which branch of the Tree of Mankind this group is likely to sit. In order to clarify this, one or both group members would need to undertake the Big Y test.

Conclusions
Even though the two members of this group are not close matches to each other (GD 7/37), their Unique STR Pattern suggests that they can be appropriately grouped together and that they share a common ancestor some time in the past several hundred years (probably pre-1600s). For now, we are none the wiser as to where this particular genetic group originated, but hopefully, as more people join the project and are a match to this new group, their origins will become more clear.

Both members should join the relevant Haplogroup & Geographic Projects and seek further advice from the Admins of those projects. For now, until Big Y data is available, only topline recommendations can be made re potentially relevant projects:

Options for these project members would be to upgrade to Y-DNA-111 and do the Big Y test. This would help confirm that they are appropriately grouped together and would help isolate on which particular branch of the Tree of Mankind they sit. This in turn could give clues as to their origins.

Maurice Gleeson
June 2019




Wednesday, 15 May 2019

What can Y-DNA Results tell us?

Most people who join surname projects (like the Ryan DNA Project) start off with the Y-DNA-37 marker test. This tests 37 STR markers, and you can later upgrade to 67 or 111 STR markers. Some people also do SNP marker testing, either via a special "SNP Pack" or the Big Y test. So there are two types of DNA markers - STR markers and SNP markers. You can read more about them here.

Each type of marker gives different kinds of information. The SNP markers help define the exact location that someone sits on the Tree of Mankind, whilst the STR markers give an indication of how closely two people are related within the last several hundred years. Both types of marker can provide crucial information that helps the interpretation of the overall data and allows us to draw specific conclusions about each of the genetic groups within the project.

But DNA data is not the only type of data that we analyse. We also analyse the direct male line pedigrees that project members have provided, and in particular the birth location of each MDKA (Most Distant Known Ancestor).

On an individual level, a simple Y-DNA-37 test may help you identify people to whom you are closely related. An exact match at 37 markers (i.e. no mutations; Genetic Distance = 0/37) suggests that you and the other person have a 50% chance of being related on your direct male line within 5 generations and a 95% chance of being related within 8 generations. The probabilities are even stronger for an exact match at 67 markers (50% probability within 3 generations, 95% probability within 5 generations) and 111 markers (3rd cousins or closer). Thus your own individual Y-DNA results can help you with your personal family tree research.

But you get additional value from your Y-DNA results by joining DNA projects - surname projects, haplogroup projects & geographic projects. And at this project level, your Y-DNA results can tell us a lot about the deeper origins of your specific genetic group. Here's how ...

In most projects, distinct genetic groups can be identified from the DNA data. These are groups of people who all share a broadly similar genetic signature, suggesting that they all descended from the same common ancestor some time in the last 1000 years or so (i.e. "within a genealogical timeframe", or "since the advent of surnames"). The key questions that we can ask about any genetic group within a project are:
  • Where are they from?
  • How old is the group?
  • Is the group associated with a specific Irish "clan"?

And as the Y-DNA database has grown, various DNA projects have indeed been able to identify the genetic signatures of specific Irish "clans", thus connecting people with their deeper Irish roots and a history that few may have imagined.

Brian Boru (941-1014), High King of Ireland 

One of the earliest examples of this is the O'Brien DNA Project. The Administrators of this project worked closely with Haplogroup Project Administrators to identify a specific signature for the "tribe" of the Dal gCais (pronounced Doll Gash), one of whose most famous descendants was Brian Boru, 1st High King of Ireland, who was killed at the Battle of Clontarf in 1014. [1] The evidence collected in support of this conclusion (that a specific signature is that of the Dal gCais) includes the following:
  • a specific Y-DNA signature (called the Irish Type III STR signature, which is associated with the L226 SNP marker) is in turn associated with: 
  1. a surplus of Dal Cassian surnames (e.g. O'Brien, Casey, McGrath, Hogan, etc)
  2. the clan territories of the Dal gCais (centred around Clare & Limerick)


Distribution of L226 is strongest in Dal gCais territories

So Y-DNA results can help you identify matches with whom you share a fairly recent common ancestor (on your direct male line) and can link you up to the deeper origins of your surname and where it came from.

We will see in subsequent posts if the deeper origins of the various groups within the Ryan DNA Project are coming close to identifying specific DNA signatures of specific Ryan "clans".

Maurice Gleeson
May 2019
References:
[1] Dennis M Wright, 2009. A Set of Distinctive Marker Values defines a Y-STR Signature for Gaelic Dalcassian families. Journal of Genetic Genealogy, 5(1):1-7. Available at http://www.jogg.info/pages/51/files/Wright.pdf





Tuesday, 27 November 2018

Birth of a New Genetic Family - Group 9

As more people test their Y-DNA and join the FTDNA database, people who have been in the Ungrouped section of the project will suddenly find that they have a new close match and this instantly creates a new genetic family. This has just happened in the Ryan DNA Project and as a result a new genetic family has been born.

Just today, a new project member (JR-7435)* joined the project and he was an instant match to an existing project member (PAR-2453) in the Ungrouped section. In fact, when comparing this new member's 67-marker profile against everyone else's in the FTDNA database, he has 3 matches: a Rowan (with a Genetic Distance of 4/67), a Ryan (GD 5/67) and a Loftus (GD 7/67). So it looks like this provides a direct genetic link between the Ryan surname and the Rowan surname.

* this is the members initials and the last 4 digits of his kit number

The new member has 3 matches at the 67-marker level of comparison

When we decrease the comparison level to the 37-marker level, the new member has the following matches:
  • Ryan x1
  • Rowan x3
  • Mulvihill / Melville x5

So this begs a few questions:
  1. is the genetic connection between the Ryan's and the Rowan's a "true match" or a "false match" (due to Convergence)?
  2. same question for the Ryan / Rowan surname and the Mulvihill surname - is it a true match? (i.e. is the connection within the last few hundred years)
  3. if it is a true match, which came first: the Mulvihill chicken or the Ryan / Rowan egg? Was there some sort of a Surname or DNA Switch (SDS) somewhere along the direct male line of these genetically matching individuals?

The answer to the first and second question is: yes, this is very likely to be a true match. The Rowan individual has the terminal SNP marker DF17, whilst the Ryan individual has the terminal SNP marker FGC14115. If we look at where these sit on the Tree of Mankind, we find out that they are on the same branch, with DF17 being upstream (toward the past) and FGC14115 being downstream (toward the present). This gives us a SNP Progression as follows (note: the SNP Progression is the series of SNP markers that characterise each branching point on the Tree of Mankind from the major haplogroup level down to the sub-branch on which the individual sits):
  • R-P312/S116 > Z40481 > ZZ11 > DF27/S250 > Z195/S355 > Z272 > BY907 (aka DF17) > FGC14113 > ~22264668-T-C > FGC14126 > FGC14124 > FGC14117 > FGC14115

This is illustrated in the diagram below from The Big Tree. The yellow circles mark the locations of DF17 and FGC14115. Note that there is also a Mulvihill sitting below FGC14115, and this strongly supports the notion that the genetic match between the Mulvihill's and the Ryan / Rowan surname is in fact a "true match". So that just leaves us with the question: which came first? Did the Rowan's become Mulvihill's and Ryan's? or were the Ryan's the progenitors? or were the Mulvihill's the father of them all?

The position of FGC14115 in relation to DF17 on the Tree of Mankind

The Rowan matches are not in the Ryan project so I invited them all to join. One of the Mulvihill matches (N1993) has done the Big Y test so I have invited him to join too (for comparison purposes). The existing project member (PAR-2453) has already done the Big Y test and I will ask him to upload it to the Big Tree (instructions here) so that we can get some additional (free) analyses that will further elucidate the relationship between the Ryan and Mulvihill surnames.

A close up of the branch on which the members of Group 9 sit

The Mulvihill individual on the Big Tree (see close up above) has 5 unique SNPs (not shared with anyone else in the database), which (crudely) represents about 500-750 years of time. This suggests that the Mulvihill line branched away from FGC14115 about 1200 to 1450 AD (very approximately). When project member PAR-2453 uploads his Big Y data to the Big Tree, it is likely that some or all of these 5 unique SNPs will form a new branch below FGC14115 ... and below this new branch, we will find both Mulvihill N1993 and PAR-2453, each perhaps with 2 or 3 unique SNP markers of their own.

This may also give us an idea of when the split between the Ryan and Mulvihill surname took place, and by extension, which came first: the chicken or the egg.


Where do they come from?

Unfortunately not many people include the birth location of their MDKA (Most Distant Known Ancestor) in their profile so it is not easy to see from what county in Ireland people originated. This is essential information to include and I encourage all project members to amend their profiles to include this information. You can read about how to do it here. PAR-2453 has included this information (mega-brownie points) and we can see that his ancestors came from Kilkenny. Among his matches, one Mulvihill has origins in Longford, another in Limerick, but the rest have no MDKA data.

There is a Mulvihill DNA Project and on reviewing their public DNA Results Page, there is a suggestion that the particular branch of the Mulvihill's who are FGC14115+ comes from North Kerry (although unfortunately, individual MDKA data is not displayed). There is also a Rowan DNA Project but their public DNA Results Page does not offer any insights (again, sadly, no MDKA information is displayed).

Surname Distribution Maps indicate two hotspots for the Mulvihill surname in the mid-1800s ... Longford and Clare / Limerick. Either of these two places could indicate the genetic origin of this group of related surnames. The map for the Rowan surname shows a less localised distribution for that particular surname and offers no additional clues.


Surname Distribution Maps based on Griffiths Valuation
(from www.johngrenham.com)

It would be interesting to see if the Admins of the Rowan and Mulvihill DNA Projects have any further insights to offer as to the likely origins of this group.

Watch this space for further updates.

Maurice Gleeson
Nov 2018




Tuesday, 13 November 2018

FTDNA Thanksgiving Sale

There are some incredible discounts in the current FTDNA Sale which lasts from now until Nov 22nd. And there will probably be a Christmas Sale after that. So now is the time to start thinking about getting that upgrade or that extra kit.

Below are the sale prices and they are the lowest I have ever seen.
Y37 for just $99 ...
Family Finder for just $49 ...
and $100-140 off Big Y upgrades.

This feels more like Crazy Eddie's Second Hand Car Deals!

If you have any questions about your own particular situation, just drop me an email.

Maurice Gleeson
Nov 2018





Wednesday, 27 June 2018

New Results & Next Steps for Group 7

The DNA results of a new member of the Ryan Project have recently come back from the lab and this has allowed us to add several new members to Group 7 of the DNA Project.

Who does the new member match?

The new member (B346403) has 1 match at 37 markers (another Ryan) and 56 at the 25-marker level, including a second Ryan (310545). The first match is currently Ungrouped but the second match (310545) belongs to Group 7 which has the following SNP Progression (ie the SNPs that define each branching point down to where he sits on the Tree of Mankind):
  • R-P312/S116 > Z290 > L21/S145 > DF13 > L513/S215/DF1 > S6365 > Z16361 > Z16372 > Z18080/BY184 > Z18079/BY182

Looking at the terminal SNPs of the new member's matches at the 25-marker level (and assessing where these fall on the Tree of Mankind), gives us the following info:
  • BY11277 … below BY182 thus: BY182 > M2775 > ZS5207 > BY11277
  • BY182 (member 310545)
  • BY184 … 1 step above BY182
  • BY20805 … a chance match with a SNP Progression thus: U106 … > Z301 > L48 … >Z30 … > Z2 > Z7 > Z8 > FGC5264 > BY20805 (i.e. a completely different branch)
  • BY42404 … 2 steps below BY182 (Nicholson)
  • L513 x2 … the subclade SNP
  • M2775 … 1 step below BY182 (Nicholson)
  • Z25289 x3 … another completely different branch below Z30
  • ZS5210 … 1 step below BY182 (Nicholson)

This indicates that most of the new member's 25-marker matches (who have SNP data) fall on or below the BY182 branch of the Tree of Mankind (as does member 310545) and so I am reasonably confident that the new member does too. As a result, I have placed him and the first Ryan match (previously Ungrouped) in the same group as 310545 (i.e. Group 7). You can see this on the DNA Results page here.

The DNA results for Group 7 (this group has 4 members but one member has his results settings set to default and therefore they are not displayed - see how to change this in the Next Steps section below)

We could check that this placement of the new member is correct by doing the Big Y test ($650) or the cheaper R-S6365 SNP Pack ($119 - see SNPs covered at the end of this post) or the single SNP BY182 ($39). However, the Big Y is the preferred test in this situation as it will help identify branches “downstream” of BY182 and will eventually identify if there is a Ryan-specific branch for this particular genetic group. 

Where does Group 7 sit on the Tree of Mankind?

You can see a diagram of the BY182 portion of the Tree of Mankind below (which is taken from here … http://www.ytree.net/DisplayTree.php?blockID=510&star=false). Based on the number of SNPs in the Nicholson blocks, BY182 is (very) approximately 2250 years old. The Group 7 Ryan’s lie somewhere below this … and a lot can happen in 2250 years! Hence Big Y testing of two group members would be very informative and would probably identify several “more downstream” branches for this Ryan group below BY182.

The Big Tree's version of the Tree of Mankind showing the BY182 branch in the middle

The R-L513 & Subclades project provides a little bit more detail than the Big Tree diagram above. The Ryan portion is in the middle of the large circular blob on the right, above the blue (Nicholson) oval. 

Mike Walsh's diagram of the L513 branch of the Tree of Mankind

All members of the Ryan project should join the relevant Haplogroup projects and for Group 7 members, the relevant project is the R-L513 & Subclades project.

Where is Group 7 from?

Only one of the members in Group 7 has indicated the exact birth location of their MDKA (Most Distant Known Ancestor) and this is Cork, Ireland … so this is one clue to where this group possibly originated. 

Another clue to the origin of this genetic group could potentially be gleaned from the surnames on the neighbouring branches of the Tree of Mankind, and from the close matches identified by the relevant Haplogroup Project (in this case the R-L513 & Subclades project). These include the surnames indicated below. Note that the O’Brien individual gives Kerry as his MDKA’s birth location (Kerry is the neighbouring county to Cork).

BY182+ individuals, as identified by the R-L513 & Subclades project.

Unfortunately, Surname Distribution maps for each of these names do not suggest a specific most likely location for the origins of this group of Ryan’s. You can see a selection of these maps at the end of this post.

All project members should fill in their own MDKA info on their FTDNA Genealogy page using the following format (see item 2 here for instructions - http://ryandnaproject.blogspot.com/p/getting-most-out-of-your-dna-test.html):
  • James RYAN b1835 Shallee, Tipp d1879 Longstone, Tipp m Kathy BURKE
Having this information is essential for determining where the various genetic groups in the project originated.

How closely related is the new member to his closest matches?

The new project member has a Genetic Distance (GD) of 4/37 to his first Ryan match (i.e. 4 steps away from an exact match) and a GD of 5/37 to 310545  Consequently, the TiP Report tool predicts he and the first Ryan match share a common Ryan ancestor about 6 generations ago (90% Confidence Interval 1-14 gens) and he & 310545 share one about 8 generations ago (90% CI 3-18 gens). 

These TMRCA estimates (i.e. Time to Most recent Common Ancestor) translate into a birth year for the common ancestor of about 1770 (1580-1920) and 1710 (1410-1860) with both matches respectively. Note the wide range around the mid-point estimates - these indicate how inexact these TMRCA estimates actually are and (in general) they should never be relied upon. Also of note, the mid-point estimates (1770 & 1710) are probably beyond the reach of documentary records.

Next Steps for Group 7

All members should update their MDKA information as indicated above. Having the birth location of the MDKA for each member of the project is essential.

At least two members of the group should undertake Big Y testing. This will help firmly identify on which downstream branch of the Tree of Mankind these Ryans sit.

All project members are encouraged to allow their results to be displayed on the public DNA Results page here. This allows you to see your results without having to log in to your account. To allow public sharing, simply follow these steps:
  • log in to your FTDNA account, 
  • hover over your name in the top right, 
  • click on Privacy & Sharing, 
  • scroll down to Project Sharing, 
  • and tick the "Opt in to Sharing" box beside the first option "Group Project Profile". These results are pseudonymised (i.e. your name is not displayed) and so your identity is kept private.

Maurice Gleeson
June 2018


The SNP markers covered by the S6365 SNP pack are indicated below. The ones of relevance to Group 7 are highlighted in yellow.

SNP PackR1b - S6365 SNP Pack 
Includes the following SNPs on the haplotree:
CTS3087, BY182, BY404, Z16372, Z16377, Z16383, BY16, FGC11788, Z16386, Z17801, Z17807, Z16390, Z16392, Z16395, BY359, BY360, L1333, BY17, BY553, BY554, ZW02, ZW04, BY3092, Z17909, Z16400, Z16403, CTS11744, CTS6621, M2775, BY416, BY184, BY2745, S6365, Z16409, Z16404, BY402, Z16407, Z17624, Z17626, Z17627, Z17628, BY390, FGC32363, BY3150, BY3151, BY3153, FGC11791, BY2926, S8120, BY4794, BY11261, BY11267, BY11262, BY11269, FGC31789, FGC31790, Z16410, Z16416, Z16405, Z16408, Z16402, Z16411, Z16412, ZW01, ZW09, FGC46414, FGC46415, FGC46416, FGC46420, S8124, BY11253, Z17629, FGC13421, FGC13422, BY11289, Z17630, FGC13411, CTS750, Z16362, Z16365, Z16366, Z16371, BY11280, A11235, CTS10651, BY392, BY393, BY394, F2338, ZS5209, ZS5211, ZS5213, BY11266, BY11264, BY11274, BY11279, BY11271, BY11252, BY11257, FGC34075, FGC34076, ZW05, BY11255, FGC36485, FGC36487, ZW22, ZW23, BY11281, FGC31837, FGC31841, ZW15, ZW14, BY11285, BY361, BY362, BY363, BY364, FGC11827, Z16387, Z16388, Z16389, Z16396, FGC32640, BY11283, BY11259, BY11287, Z17805, Z17806, Z17808, Z17809, Z17810, BY2863, Z16374, Z16376, Z16380, Z16381, Z16373, BY11251, BY11273, BY405, BY407, BY408, BY11277, BY11278, BY11276, BY11282, BY11256, BY11260, BY11272, BY11284, BY11286, BY11290, BY11291, BY11263, BY11270, BY391, ZW10, ZW11, BY11265, BY11254, FGC32195, FGC32196

Includes the following SNPs that are NOT on the haplotree:
Z16363, BY11258, BY11268, BY11275, FGC31902


Surname Distribution maps of the close genetic cousins to the Group 7 Ryan's are below. These are from http://forebears.co.uk/surnames. There is no definite pattern that emerges from these maps to suggest a place of origin for the Ryan's of Group 7.







Extensive Lineages of Group 2 – new results & status update

We have made some additional progress since our last update on the Extensive Lineages of Group 2 . We previously identified several promine...