Date   
Re: New Big-Y files needed

Thomas Goff
 

Hi again, thanks for the tutorial.

I had a few reasons to try the others --

23andme: Jokingly, for several years my wife and I have disputed who had more Neanderthal DNA. She is from Eastern Europe and my maternal line is Portuguese, so with remains found in Croatia and the Iberian peninsula, we had a friendly competition. We put to rest that she indeed does have more variants, 287 and 271 for me. Over 300 is considered high and 23andme highest results were 397. However, not sure I really came out ahead in this? LOL  It also provides some health traits that I'm still looking in to. Another interesting difference I liked was the ancestry timeline. See the link provided if your interested.

AncestryDNA: It was only $54 on black Friday and I'm hoping its ethnicity estimate provides more insight than the others.

I came across this article on the differences between all the DNA studies.










On Monday, January 8, 2018, 11:11:03 AM EST, Jared Smith <jared@...> wrote:


I'd certainly recommend that anyone that has done autosomal testing to
upload their results to GedMatch.com. This site provides a great way
to find matches from all of the major testing companies. If you've not
used it, I wrote a tutorial that may be helpful -
http://smithplanet.com/stuff/gedmatch.htm

It would be a good idea to check your GedMatch one-to-many list for
the surnames of folks in this group. It's most likely that our shared
direct male line ancestors are too far back to have shared autosomal
DNA from them, but it's possible we're related in other ways.

Thanks,

Jared


On Mon, Jan 8, 2018 at 9:03 AM, Thomas Goff <thomasgoff94@...> wrote:
> Thanks, sounds good.
>
> btw, forgot to mention. I took advantage of some sales on other DNA testing.
> My 23andme test are in and waiting for Ancestry.com results.  Let me know if
> you are interested with these results.
>
> Best,
> Tom
>
> On Monday, January 8, 2018, 10:20:48 AM EST, Jared Smith
> <jared@...> wrote:
>
>
> Thomas -
>
> That is correct. This is only for those that have done the Big-Y test. If
> any new SNP testing looks viable for you after the analysis, I'll certainly
> let you know.
>
> Thanks,
>
> Jared
>
>



Re: New Big-Y files needed

Charles Thomas
 

Hello Jared, Thomas, and everyone,

I've found the Matching Segment Search very helpful at Gedmatch.com. It's available via the Tier 1 utilities which requires a $10 fee for one month's access. It's helpful in finding others who match at the same segment and therefore have a shared ancestor/ancestral couple. It can be tricky, however, determining which match is from which copy (maternal or paternal) of the particular chromosome unless one has a parent whose results can be "phased" against your own.

Best wishes for the new year,

Charles Thomas




From: Z16357@groups.io <Z16357@groups.io> on behalf of Jared Smith <jared@...>
Sent: Monday, January 8, 2018 10:10 AM
To: Z16357@groups.io
Subject: Re: [Z16357] New Big-Y files needed
 
I'd certainly recommend that anyone that has done autosomal testing to
upload their results to GedMatch.com. This site provides a great way
to find matches from all of the major testing companies. If you've not
used it, I wrote a tutorial that may be helpful -
http://smithplanet.com/stuff/gedmatch.htm
smithplanet.com
Genetic Genealogy using GEDmatch An Absolute Beginners Guide. by Jared Smith. Please contact me if you have any corrections or clarifications. Overview



It would be a good idea to check your GedMatch one-to-many list for
the surnames of folks in this group. It's most likely that our shared
direct male line ancestors are too far back to have shared autosomal
DNA from them, but it's possible we're related in other ways.

Thanks,

Jared


On Mon, Jan 8, 2018 at 9:03 AM, Thomas Goff <thomasgoff94@...> wrote:
> Thanks, sounds good.
>
> btw, forgot to mention. I took advantage of some sales on other DNA testing.
> My 23andme test are in and waiting for Ancestry.com results.  Let me know if
> you are interested with these results.
>
> Best,
> Tom
>
> On Monday, January 8, 2018, 10:20:48 AM EST, Jared Smith
> <jared@...> wrote:
>
>
> Thomas -
>
> That is correct. This is only for those that have done the Big-Y test. If
> any new SNP testing looks viable for you after the analysis, I'll certainly
> let you know.
>
> Thanks,
>
> Jared
>
>



Re: New Big-Y files needed

Jared Smith
 

I'd certainly recommend that anyone that has done autosomal testing to
upload their results to GedMatch.com. This site provides a great way
to find matches from all of the major testing companies. If you've not
used it, I wrote a tutorial that may be helpful -
http://smithplanet.com/stuff/gedmatch.htm

It would be a good idea to check your GedMatch one-to-many list for
the surnames of folks in this group. It's most likely that our shared
direct male line ancestors are too far back to have shared autosomal
DNA from them, but it's possible we're related in other ways.

Thanks,

Jared

On Mon, Jan 8, 2018 at 9:03 AM, Thomas Goff <thomasgoff94@...> wrote:
Thanks, sounds good.

btw, forgot to mention. I took advantage of some sales on other DNA testing.
My 23andme test are in and waiting for Ancestry.com results. Let me know if
you are interested with these results.

Best,
Tom

On Monday, January 8, 2018, 10:20:48 AM EST, Jared Smith
<jared@...> wrote:


Thomas -

That is correct. This is only for those that have done the Big-Y test. If
any new SNP testing looks viable for you after the analysis, I'll certainly
let you know.

Thanks,

Jared

Re: New Big-Y files needed

Thomas Goff
 

Thanks, sounds good.

btw, forgot to mention. I took advantage of some sales on other DNA testing. My 23andme test are in and waiting for Ancestry.com results.  Let me know if you are interested with these results.

Best,
Tom 

On Monday, January 8, 2018, 10:20:48 AM EST, Jared Smith <jared@...> wrote:


Thomas -

That is correct. This is only for those that have done the Big-Y test. If any new SNP testing looks viable for you after the analysis, I'll certainly let you know.

Thanks,

Jared

Re: New Big-Y files needed

Jared Smith
 

Thomas -

That is correct. This is only for those that have done the Big-Y test. If any new SNP testing looks viable for you after the analysis, I'll certainly let you know.

Thanks,

Jared

Re: New Big-Y files needed

Thomas Goff
 

Hello Jared,

Happy new year and hope you are well!


It looks like the link you sent are for those who have done the Big-Y test. I haven't taken Big-Y, but I have attached an image of what is available for my download. Please let me know if any of these are useful.

Thanks,
Tom


Inline image


On Sunday, January 7, 2018, 7:01:29 PM EST, Jared Smith <jared@...> wrote:


Hi all! I hope you had a wonderful holiday season and I wish you all
the best in this new year!

I'm still in need of quite a few new Build 38 files to update my
analysis. I've received Raw Data files for the following:
- J Hartley
- C Hays
- Bennett

I know there were some difficulties with the file size of the Raw Data
file, which is the critical one for my analysis. Fortunately, I've
discovered a much easier way to get the Raw Data file that doesn't
involve you downloading it at all:

1. Log in to familytreedna.com
2. Go to https://www.familytreedna.com/my/big-y (or click MyFTDNA...
Big-Y... Matches)
3. Select the "Download Raw Data" button near the top right of the screen.
4. Right-click on the green "Download VCF" (NOT "Download BAM") button
at the bottom of the screen, and select "Copy Link Address". This menu
options might also be called "Copy Link Location" or similar,
depending on the browser you're using.
5. Reply to this message (or a private e-mail just to me, if you
prefer) and paste (Control or Command + V) in the long web site
address, then send to me.

It would be very helpful for our project if you could send this to me.

I also strongly encourage you to share your Raw Data file to the new
Y-DNA Data Warehouse. This will allow other researchers to analyze the
data to help build our tree. Instructions are at
http://haplogroup-r.org/instructions.html You use the same copied Link
Address as above, so it's very easy to submit.

Thanks,

Jared

On Mon, Nov 20, 2017 at 1:39 PM, Joel Hartley <joel@...> wrote:
> Hi James,
>
>
>
> I guess I’m underutilizing this:
>
>
>
>
>
>
> Hope you get it (and that it is the right file).
>
>
>
> Joel
>
>
>
> From: Z16357@groups.io [mailto:Z16357@groups.io] On Behalf Of James Bennett
> Sent: Monday, November 20, 2017 11:23 AM
> Subject: Re: [Z16357] New Big-Y files needed
>
>
>
> Joel,
>
>
>
> If by "Microsoft Cloud" you mean "One Drive", I believe if you store the
> file on your local OneDrive folder, you can "right-click" the file and chose
> "Share a OneDrive link".  That will but a link in your clipboard that you
> can paste into the e-mail.
>
>
>
> HTH,
>
> James
>
>
>
> On Sun, Nov 19, 2017 at 5:59 PM, Joel Hartley <joel@...> wrote:
>
> Yes, still no luck with the VCF. Any suggestions? I have used the Cloud
> through Microsoft, but only on a limited basis and am not very familiar with
> it. I also have my own website, but not sure how to share files with you.
>
>
>
> Joel
>
>
>
> From: Z16357@groups.io [mailto:Z16357@groups.io] On Behalf Of Jared Smith
> Sent: Tuesday, November 14, 2017 10:44 PM
> Subject: [Z16357] New Big-Y files needed
>
>
>
> Hello fellow Z16357 cousins! Things have been relatively quiet around here -
> no new matches in quite some time. Now's a great time to recruit those STR
> matches of ours = Big-Y is on sale for $475.
>
>
>
> For Big-Y customers, you've probably seen that FTDNA has made notable
> updates to their Big-Y tools. There are some nice improvements (though still
> some issues they are working through).
>
>
>
> FTDNA has also moved to a new Y-DNA reference - hg19 to hg38. At it's most
> basic level, this is an adjustment of the numeric values that are used to
> represent different 'markers' on the Y-chromosome. Z16357, for example, is a
> G to T allele change at position 22,512,912 when using the older hg19
> reference, but it's G to T at position 20,351,026 using the hg38 reference.
> So all of the SNP and variant numbering at http://dna.smithplanet.com/snp
> will need to be updated. The new reference provides us some opportunity to
> find new shared or novel variants.
>
>
> To update my research and reference numbers, I need your updated FTDNA
> Results and VCF files.
>
>
>
> Please take a few moments to download and e-mail them to me. This will be
> incredibly helpful to our research.
>
>
>
> 1. Log in to FTDNA.
>
>
> 3. Click "Export Results" at the top right and save the .csv file
>
> 4. Click "Download Raw Data" at the top right.
>
> 5. Click "Download VCF" at the bottom and save the .zip file.
>
> 6. Attach both the .csv and .zip files to a new e-mail and send to me
> off-list - jared@...
>
>
>
> Once I have everyone's updated results, I'll analyze them, update the web
> site, and let you know if I find anything interesting.
>
>
>
> Thanks!
>
>
>
> Jared Smith
>
>
>
>
>
>


Re: New Big-Y files needed

Jared Smith
 

Hi all! I hope you had a wonderful holiday season and I wish you all
the best in this new year!

I'm still in need of quite a few new Build 38 files to update my
analysis. I've received Raw Data files for the following:
- J Hartley
- C Hays
- Bennett

I know there were some difficulties with the file size of the Raw Data
file, which is the critical one for my analysis. Fortunately, I've
discovered a much easier way to get the Raw Data file that doesn't
involve you downloading it at all:

1. Log in to familytreedna.com
2. Go to https://www.familytreedna.com/my/big-y (or click MyFTDNA...
Big-Y... Matches)
3. Select the "Download Raw Data" button near the top right of the screen.
4. Right-click on the green "Download VCF" (NOT "Download BAM") button
at the bottom of the screen, and select "Copy Link Address". This menu
options might also be called "Copy Link Location" or similar,
depending on the browser you're using.
5. Reply to this message (or a private e-mail just to me, if you
prefer) and paste (Control or Command + V) in the long web site
address, then send to me.

It would be very helpful for our project if you could send this to me.

I also strongly encourage you to share your Raw Data file to the new
Y-DNA Data Warehouse. This will allow other researchers to analyze the
data to help build our tree. Instructions are at
http://haplogroup-r.org/instructions.html You use the same copied Link
Address as above, so it's very easy to submit.

Thanks,

Jared

On Mon, Nov 20, 2017 at 1:39 PM, Joel Hartley <joel@...> wrote:
Hi James,



I guess I’m underutilizing this:



https://1drv.ms/u/s!AgUuC5wLrF2Ogy40BVWOsivXYYgD



Hope you get it (and that it is the right file).



Joel



From: Z16357@groups.io [mailto:Z16357@groups.io] On Behalf Of James Bennett
Sent: Monday, November 20, 2017 11:23 AM
To: Z16357@groups.io
Subject: Re: [Z16357] New Big-Y files needed



Joel,



If by "Microsoft Cloud" you mean "One Drive", I believe if you store the
file on your local OneDrive folder, you can "right-click" the file and chose
"Share a OneDrive link". That will but a link in your clipboard that you
can paste into the e-mail.



HTH,

James



On Sun, Nov 19, 2017 at 5:59 PM, Joel Hartley <joel@...> wrote:

Yes, still no luck with the VCF. Any suggestions? I have used the Cloud
through Microsoft, but only on a limited basis and am not very familiar with
it. I also have my own website, but not sure how to share files with you.



Joel



From: Z16357@groups.io [mailto:Z16357@groups.io] On Behalf Of Jared Smith
Sent: Tuesday, November 14, 2017 10:44 PM
To: Z16357@groups.io
Subject: [Z16357] New Big-Y files needed



Hello fellow Z16357 cousins! Things have been relatively quiet around here -
no new matches in quite some time. Now's a great time to recruit those STR
matches of ours = Big-Y is on sale for $475.



For Big-Y customers, you've probably seen that FTDNA has made notable
updates to their Big-Y tools. There are some nice improvements (though still
some issues they are working through).



FTDNA has also moved to a new Y-DNA reference - hg19 to hg38. At it's most
basic level, this is an adjustment of the numeric values that are used to
represent different 'markers' on the Y-chromosome. Z16357, for example, is a
G to T allele change at position 22,512,912 when using the older hg19
reference, but it's G to T at position 20,351,026 using the hg38 reference.
So all of the SNP and variant numbering at http://dna.smithplanet.com/snp
will need to be updated. The new reference provides us some opportunity to
find new shared or novel variants.


To update my research and reference numbers, I need your updated FTDNA
Results and VCF files.



Please take a few moments to download and e-mail them to me. This will be
incredibly helpful to our research.



1. Log in to FTDNA.

2. Go to https://www.familytreedna.com/my/big-y

3. Click "Export Results" at the top right and save the .csv file

4. Click "Download Raw Data" at the top right.

5. Click "Download VCF" at the bottom and save the .zip file.

6. Attach both the .csv and .zip files to a new e-mail and send to me
off-list - jared@...



Once I have everyone's updated results, I'll analyze them, update the web
site, and let you know if I find anything interesting.



Thanks!



Jared Smith





Re: Big Y build 38

Charles Thomas
 

Thank you for the link, James!

Charles




From: Z16357@groups.io <Z16357@groups.io> on behalf of James Bennett <james@...>
Sent: Sunday, December 10, 2017 11:06 AM
To: Z16357@groups.io
Subject: [Z16357] Big Y build 38
 
Here is an interesting article on how to leverage the new FtDNA tools.  Of course, I will need to read it multiple time for it to sink in at all.  :)

James

Big Y build 38

James Bennett
 

Here is an interesting article on how to leverage the new FtDNA tools.  Of course, I will need to read it multiple time for it to sink in at all.  :)

James

Re: New Big-Y files needed

Joel Hartley
 

Hi James,

 

I guess I’m underutilizing this:

 

https://1drv.ms/u/s!AgUuC5wLrF2Ogy40BVWOsivXYYgD

 

Hope you get it (and that it is the right file).

 

Joel

 

From: Z16357@groups.io [mailto:Z16357@groups.io] On Behalf Of James Bennett
Sent: Monday, November 20, 2017 11:23 AM
To: Z16357@groups.io
Subject: Re: [Z16357] New Big-Y files needed

 

Joel,

 

If by "Microsoft Cloud" you mean "One Drive", I believe if you store the file on your local OneDrive folder, you can "right-click" the file and chose "Share a OneDrive link".  That will but a link in your clipboard that you can paste into the e-mail.

 

HTH,

James

 

On Sun, Nov 19, 2017 at 5:59 PM, Joel Hartley <joel@...> wrote:

Yes, still no luck with the VCF. Any suggestions? I have used the Cloud through Microsoft, but only on a limited basis and am not very familiar with it. I also have my own website, but not sure how to share files with you.

 

Joel

 

From: Z16357@groups.io [mailto:Z16357@groups.io] On Behalf Of Jared Smith
Sent: Tuesday, November 14, 2017 10:44 PM
To: Z16357@groups.io
Subject: [Z16357] New Big-Y files needed

 

Hello fellow Z16357 cousins! Things have been relatively quiet around here - no new matches in quite some time. Now's a great time to recruit those STR matches of ours = Big-Y is on sale for $475.

 

For Big-Y customers, you've probably seen that FTDNA has made notable updates to their Big-Y tools. There are some nice improvements (though still some issues they are working through).

 

FTDNA has also moved to a new Y-DNA reference - hg19 to hg38. At it's most basic level, this is an adjustment of the numeric values that are used to represent different 'markers' on the Y-chromosome. Z16357, for example, is a G to T allele change at position 22,512,912 when using the older hg19 reference, but it's G to T at position 20,351,026 using the hg38 reference. So all of the SNP and variant numbering at http://dna.smithplanet.com/snp will need to be updated. The new reference provides us some opportunity to find new shared or novel variants.


To update my research and reference numbers, I need your updated FTDNA Results and VCF files.

 

Please take a few moments to download and e-mail them to me. This will be incredibly helpful to our research.

 

1. Log in to FTDNA.

3. Click "Export Results" at the top right and save the .csv file

4. Click "Download Raw Data" at the top right.

5. Click "Download VCF" at the bottom and save the .zip file.

6. Attach both the .csv and .zip files to a new e-mail and send to me off-list - jared@...

 

Once I have everyone's updated results, I'll analyze them, update the web site, and let you know if I find anything interesting.

 

Thanks!

 

Jared Smith

 

 

Re: New Big-Y files needed

James Bennett
 

Joel,

If by "Microsoft Cloud" you mean "One Drive", I believe if you store the file on your local OneDrive folder, you can "right-click" the file and chose "Share a OneDrive link".  That will but a link in your clipboard that you can paste into the e-mail.

HTH,
James

On Sun, Nov 19, 2017 at 5:59 PM, Joel Hartley <joel@...> wrote:

Yes, still no luck with the VCF. Any suggestions? I have used the Cloud through Microsoft, but only on a limited basis and am not very familiar with it. I also have my own website, but not sure how to share files with you.

 

Joel

 

From: Z16357@groups.io [mailto:Z16357@groups.io] On Behalf Of Jared Smith
Sent: Tuesday, November 14, 2017 10:44 PM
To: Z16357@groups.io
Subject: [Z16357] New Big-Y files needed

 

Hello fellow Z16357 cousins! Things have been relatively quiet around here - no new matches in quite some time. Now's a great time to recruit those STR matches of ours = Big-Y is on sale for $475.

 

For Big-Y customers, you've probably seen that FTDNA has made notable updates to their Big-Y tools. There are some nice improvements (though still some issues they are working through).

 

FTDNA has also moved to a new Y-DNA reference - hg19 to hg38. At it's most basic level, this is an adjustment of the numeric values that are used to represent different 'markers' on the Y-chromosome. Z16357, for example, is a G to T allele change at position 22,512,912 when using the older hg19 reference, but it's G to T at position 20,351,026 using the hg38 reference. So all of the SNP and variant numbering at http://dna.smithplanet.com/snp will need to be updated. The new reference provides us some opportunity to find new shared or novel variants.


To update my research and reference numbers, I need your updated FTDNA Results and VCF files.

 

Please take a few moments to download and e-mail them to me. This will be incredibly helpful to our research.

 

1. Log in to FTDNA.

3. Click "Export Results" at the top right and save the .csv file

4. Click "Download Raw Data" at the top right.

5. Click "Download VCF" at the bottom and save the .zip file.

6. Attach both the .csv and .zip files to a new e-mail and send to me off-list - jared@...

 

Once I have everyone's updated results, I'll analyze them, update the web site, and let you know if I find anything interesting.

 

Thanks!

 

Jared Smith

 


Re: New Big-Y files needed

Joel Hartley
 

Yes, still no luck with the VCF. Any suggestions? I have used the Cloud through Microsoft, but only on a limited basis and am not very familiar with it. I also have my own website, but not sure how to share files with you.

 

Joel

 

From: Z16357@groups.io [mailto:Z16357@groups.io] On Behalf Of Jared Smith
Sent: Tuesday, November 14, 2017 10:44 PM
To: Z16357@groups.io
Subject: [Z16357] New Big-Y files needed

 

Hello fellow Z16357 cousins! Things have been relatively quiet around here - no new matches in quite some time. Now's a great time to recruit those STR matches of ours = Big-Y is on sale for $475.

 

For Big-Y customers, you've probably seen that FTDNA has made notable updates to their Big-Y tools. There are some nice improvements (though still some issues they are working through).

 

FTDNA has also moved to a new Y-DNA reference - hg19 to hg38. At it's most basic level, this is an adjustment of the numeric values that are used to represent different 'markers' on the Y-chromosome. Z16357, for example, is a G to T allele change at position 22,512,912 when using the older hg19 reference, but it's G to T at position 20,351,026 using the hg38 reference. So all of the SNP and variant numbering at http://dna.smithplanet.com/snp will need to be updated. The new reference provides us some opportunity to find new shared or novel variants.


To update my research and reference numbers, I need your updated FTDNA Results and VCF files.

 

Please take a few moments to download and e-mail them to me. This will be incredibly helpful to our research.

 

1. Log in to FTDNA.

3. Click "Export Results" at the top right and save the .csv file

4. Click "Download Raw Data" at the top right.

5. Click "Download VCF" at the bottom and save the .zip file.

6. Attach both the .csv and .zip files to a new e-mail and send to me off-list - jared@...

 

Once I have everyone's updated results, I'll analyze them, update the web site, and let you know if I find anything interesting.

 

Thanks!

 

Jared Smith

 

Re: New Big-Y files needed

Joel Hartley
 

Hi Jared,

 

Thanks for the email and thanks for your analyses.

 

The other file was too big. I’ll try in a separate email, but the message told me to put it in a shared location.

 

Joel

 

 

From: Z16357@groups.io [mailto:Z16357@groups.io] On Behalf Of Jared Smith
Sent: Tuesday, November 14, 2017 10:44 PM
To: Z16357@groups.io
Subject: [Z16357] New Big-Y files needed

 

Hello fellow Z16357 cousins! Things have been relatively quiet around here - no new matches in quite some time. Now's a great time to recruit those STR matches of ours = Big-Y is on sale for $475.

 

For Big-Y customers, you've probably seen that FTDNA has made notable updates to their Big-Y tools. There are some nice improvements (though still some issues they are working through).

 

FTDNA has also moved to a new Y-DNA reference - hg19 to hg38. At it's most basic level, this is an adjustment of the numeric values that are used to represent different 'markers' on the Y-chromosome. Z16357, for example, is a G to T allele change at position 22,512,912 when using the older hg19 reference, but it's G to T at position 20,351,026 using the hg38 reference. So all of the SNP and variant numbering at http://dna.smithplanet.com/snp will need to be updated. The new reference provides us some opportunity to find new shared or novel variants.


To update my research and reference numbers, I need your updated FTDNA Results and VCF files.

 

Please take a few moments to download and e-mail them to me. This will be incredibly helpful to our research.

 

1. Log in to FTDNA.

3. Click "Export Results" at the top right and save the .csv file

4. Click "Download Raw Data" at the top right.

5. Click "Download VCF" at the bottom and save the .zip file.

6. Attach both the .csv and .zip files to a new e-mail and send to me off-list - jared@...

 

Once I have everyone's updated results, I'll analyze them, update the web site, and let you know if I find anything interesting.

 

Thanks!

 

Jared Smith

 

New Big-Y files needed

Jared Smith
 

Hello fellow Z16357 cousins! Things have been relatively quiet around here - no new matches in quite some time. Now's a great time to recruit those STR matches of ours = Big-Y is on sale for $475.

For Big-Y customers, you've probably seen that FTDNA has made notable updates to their Big-Y tools. There are some nice improvements (though still some issues they are working through).

FTDNA has also moved to a new Y-DNA reference - hg19 to hg38. At it's most basic level, this is an adjustment of the numeric values that are used to represent different 'markers' on the Y-chromosome. Z16357, for example, is a G to T allele change at position 22,512,912 when using the older hg19 reference, but it's G to T at position 20,351,026 using the hg38 reference. So all of the SNP and variant numbering at http://dna.smithplanet.com/snp will need to be updated. The new reference provides us some opportunity to find new shared or novel variants.

To update my research and reference numbers, I need your updated FTDNA Results and VCF files.

Please take a few moments to download and e-mail them to me. This will be incredibly helpful to our research.

1. Log in to FTDNA.
3. Click "Export Results" at the top right and save the .csv file
4. Click "Download Raw Data" at the top right.
5. Click "Download VCF" at the bottom and save the .zip file.
6. Attach both the .csv and .zip files to a new e-mail and send to me off-list - jared@...

Once I have everyone's updated results, I'll analyze them, update the web site, and let you know if I find anything interesting.

Thanks!

Jared Smith

Re: New aging estimates

Joel Hartley
 

I forgot to mention – I checked the L513 Yahoo Forum and didn’t see mention of this study. I would have thought that it would have been big news there.

 

Joel

 

From: Z16357@groups.io [mailto:Z16357@groups.io] On Behalf Of Jared Smith
Sent: Monday, July 24, 2017 11:10 AM
To: Z16357@groups.io
Subject: [Z16357] New aging estimates

 

Iain McDonald has just published a new project analyzing all of the P312 Big-Y results. P312 is much older than our Z16357. The general heredity is P312 > L21/Z290 > L513 > S5668 > Z16357.

 

He places the 95% reliability date of Z16357 being formed 2528BC — 1177BC with a central date of 1873BC. This is quite a bit older than the estimates I've been using. I generally run two sets - one at 1000BC and one at 500BC.

 

He places Z17911 as formed 310BC — 713AD with a central date of 252AD. This is also quite a bit older than the 1000AD date I've calculated.

 

As for our more recent haplogroups, his estimates are only slightly older than mine.

 

Of note is that he did not include our recent Smith BY19970 data. If he had, I think this would have pushed his dates a bit more recent.

 

Does this mean that his estimates are right and mine wrong? We all perform mathematical analysis within certain constraints and assumptions. And the variability is notable. He certainly applies a strong methodology.

 

You can check out Iain's excellent work at http://www.jb.man.ac.uk/~mcdonald/genetics.html

 

Jared

Re: New aging estimates

Joel Hartley
 

Thanks Jared,

 

I don’t have a lot of backup, but I have thought that perhaps some of your dates were too recent. I’m guessing the truth could be in the middle between you and McDonald. My thought was that the trend has been that some of our SNPs could be more recent than previously thought. My recollection was that this applied to the L513 SNPs in general, but I’m not sure. A third opinion would be the YFull YTree update which should be coming out shortly. Dating can be one of the more fascinating aspects of YDNA.

 

Joel

 

From: Z16357@groups.io [mailto:Z16357@groups.io] On Behalf Of Jared Smith
Sent: Monday, July 24, 2017 11:10 AM
To: Z16357@groups.io
Subject: [Z16357] New aging estimates

 

Iain McDonald has just published a new project analyzing all of the P312 Big-Y results. P312 is much older than our Z16357. The general heredity is P312 > L21/Z290 > L513 > S5668 > Z16357.

 

He places the 95% reliability date of Z16357 being formed 2528BC — 1177BC with a central date of 1873BC. This is quite a bit older than the estimates I've been using. I generally run two sets - one at 1000BC and one at 500BC.

 

He places Z17911 as formed 310BC — 713AD with a central date of 252AD. This is also quite a bit older than the 1000AD date I've calculated.

 

As for our more recent haplogroups, his estimates are only slightly older than mine.

 

Of note is that he did not include our recent Smith BY19970 data. If he had, I think this would have pushed his dates a bit more recent.

 

Does this mean that his estimates are right and mine wrong? We all perform mathematical analysis within certain constraints and assumptions. And the variability is notable. He certainly applies a strong methodology.

 

You can check out Iain's excellent work at http://www.jb.man.ac.uk/~mcdonald/genetics.html

 

Jared

Re: New aging estimates

Charles Thomas
 

Thanks for the notification, Jared. Yes, great work Iain McDonald is doing. I wonder, however, why he doesn't use the widely accepted BCE/CE dating standard rather than the old BC/AD. It's not a big thing but it would seem more scientific to me to use BCE/CE.

Charles Thomas


From: Z16357@groups.io <Z16357@groups.io> on behalf of Jared Smith <jared@...>
Sent: Monday, July 24, 2017 10:09 AM
To: Z16357@groups.io
Subject: [Z16357] New aging estimates
 
Iain McDonald has just published a new project analyzing all of the P312 Big-Y results. P312 is much older than our Z16357. The general heredity is P312 > L21/Z290 > L513 > S5668 > Z16357.

He places the 95% reliability date of Z16357 being formed 2528BC — 1177BC with a central date of 1873BC. This is quite a bit older than the estimates I've been using. I generally run two sets - one at 1000BC and one at 500BC.

He places Z17911 as formed 310BC — 713AD with a central date of 252AD. This is also quite a bit older than the 1000AD date I've calculated.

As for our more recent haplogroups, his estimates are only slightly older than mine.

Of note is that he did not include our recent Smith BY19970 data. If he had, I think this would have pushed his dates a bit more recent.

Does this mean that his estimates are right and mine wrong? We all perform mathematical analysis within certain constraints and assumptions. And the variability is notable. He certainly applies a strong methodology.

You can check out Iain's excellent work at http://www.jb.man.ac.uk/~mcdonald/genetics.html

www.jb.man.ac.uk
I have a side interest in genetic genealogy, for which I am Honorary Research Fellow in Genenealogy, Paleography and Heraldry at the Centre for Lifelong Learning at ...



Jared

New aging estimates

Jared Smith
 

Iain McDonald has just published a new project analyzing all of the P312 Big-Y results. P312 is much older than our Z16357. The general heredity is P312 > L21/Z290 > L513 > S5668 > Z16357.

He places the 95% reliability date of Z16357 being formed 2528BC — 1177BC with a central date of 1873BC. This is quite a bit older than the estimates I've been using. I generally run two sets - one at 1000BC and one at 500BC.

He places Z17911 as formed 310BC — 713AD with a central date of 252AD. This is also quite a bit older than the 1000AD date I've calculated.

As for our more recent haplogroups, his estimates are only slightly older than mine.

Of note is that he did not include our recent Smith BY19970 data. If he had, I think this would have pushed his dates a bit more recent.

Does this mean that his estimates are right and mine wrong? We all perform mathematical analysis within certain constraints and assumptions. And the variability is notable. He certainly applies a strong methodology.

You can check out Iain's excellent work at http://www.jb.man.ac.uk/~mcdonald/genetics.html

Jared

Re: New major Smith branch!

Jared Smith
 

FTDNA has now had these Smith SNPs named. The new haplogroup label is R-BY19970. The FTDNA tree has been updated, as well as the terminal SNP identifier for Sylvia's and Lenita's kits. I've also updated my charts at http://dna.smithplanet.com/snp

Jared


On Tue, Jun 13, 2017 at 10:40 PM, Jared Smith <jared@...> wrote:
We have a new, significant branching under Z16357. Up to this point Sylvia Smith was the only person truly at Z16357 - meaning that her kit had tested positive for Z16357, but for no shared SNPs downstream from there. If we think of Z16357 as the trunk or base of our part of the tree, there has thus far been only one branch (Z16343) coming from that trunk, which then split into two sub-branches (Z17911 and Z16854), which split into the various sub-sub-branches below them.

The Big-Y results for Lenita's brother (Leonard Ellwin Smith) are in and they create a 2nd major branch from the Z16357 trunk for Lenita and Sylvia. This Smith branch is VERY long - extending from a common (yet unknown) Smith ancestor that lived a few hundred years ago all the way back to Z16357 (probably 2500 years ago or so). It's pretty incredible to think that nobody else on this family line has done DNA testing to this level yet.

To avoid potential confusion, while my surname is Smith, it's only coincidental - this new Smith line and my Smith line below Z17911 are very distant - connecting at Z16357 around 2500 years ago.

I've updated my charts at http://dna.smithplanet.com/snp so you can see the new branching.

Lenita and Sylvia share 24 SNPs/variants. This represents around 2000 years of their family line with no known branching. This new branch has yet to be named - but I suspect that FTDNA will submit these 24 shared SNPs for naming - and one of them will be chosen as the designator for this branch of the tree.

Sylvia has the following 4 novel variants (meaning mutations that are unique to her, so they occurred more recently than Lenita's and Sylvia's common ancestor):
14703381-T-A
21734697-A-G
22102505-G-T
23817871-G-A

Lenita has the following 3 novel variants:
7676708-T-A
15315228-G-A
19139648-C-T

If I apply my aging methodology, this would suggest that their common Smith ancestor was born between 333 and 383 years ago (sometime in the mid- to late-1600s). However, these two Smiths have fewer variants/mutations (28 and 27) than is the average for our group (35.2), so this might suggest that their common ancestor is a bit more distant than this. But these are just VERY rough estimates, so their ancestor could also be more recent. As we get more Smith testers, this will be refined.

This is a very notable addition to our tree! Thank you Sylvia and Lenita for investing in Big-Y! We're trying to identify other distant Smith cousins to take Big-Y to help us better define this new Smith branch.

Thanks,

Jared Smith



New major Smith branch!

Jared Smith
 

We have a new, significant branching under Z16357. Up to this point Sylvia Smith was the only person truly at Z16357 - meaning that her kit had tested positive for Z16357, but for no shared SNPs downstream from there. If we think of Z16357 as the trunk or base of our part of the tree, there has thus far been only one branch (Z16343) coming from that trunk, which then split into two sub-branches (Z17911 and Z16854), which split into the various sub-sub-branches below them.

The Big-Y results for Lenita's brother (Leonard Ellwin Smith) are in and they create a 2nd major branch from the Z16357 trunk for Lenita and Sylvia. This Smith branch is VERY long - extending from a common (yet unknown) Smith ancestor that lived a few hundred years ago all the way back to Z16357 (probably 2500 years ago or so). It's pretty incredible to think that nobody else on this family line has done DNA testing to this level yet.

To avoid potential confusion, while my surname is Smith, it's only coincidental - this new Smith line and my Smith line below Z17911 are very distant - connecting at Z16357 around 2500 years ago.

I've updated my charts at http://dna.smithplanet.com/snp so you can see the new branching.

Lenita and Sylvia share 24 SNPs/variants. This represents around 2000 years of their family line with no known branching. This new branch has yet to be named - but I suspect that FTDNA will submit these 24 shared SNPs for naming - and one of them will be chosen as the designator for this branch of the tree.

Sylvia has the following 4 novel variants (meaning mutations that are unique to her, so they occurred more recently than Lenita's and Sylvia's common ancestor):
14703381-T-A
21734697-A-G
22102505-G-T
23817871-G-A

Lenita has the following 3 novel variants:
7676708-T-A
15315228-G-A
19139648-C-T

If I apply my aging methodology, this would suggest that their common Smith ancestor was born between 333 and 383 years ago (sometime in the mid- to late-1600s). However, these two Smiths have fewer variants/mutations (28 and 27) than is the average for our group (35.2), so this might suggest that their common ancestor is a bit more distant than this. But these are just VERY rough estimates, so their ancestor could also be more recent. As we get more Smith testers, this will be refined.

This is a very notable addition to our tree! Thank you Sylvia and Lenita for investing in Big-Y! We're trying to identify other distant Smith cousins to take Big-Y to help us better define this new Smith branch.

Thanks,

Jared Smith