Go Back   Family Tree DNA Forums > Paternal Lineages (Y-DNA) > BIG Y and SNP Discovery

BIG Y and SNP Discovery This area is for talk about BIG Y results.

Reply
 
Thread Tools Display Modes
  #1  
Old 13th August 2017, 02:54 AM
sputnik sputnik is offline
FTDNA Customer
 
Join Date: Jan 2015
Posts: 1
STR reporting from BIGY

Hi, I notice if I upload my BigY results to YFull for analysis, they report on 500 STRs, but FTDNA does not seem to report these results.
As the information is clearly in the data, why do I have to do a Y111 test if I want to search YDNA matches at that level, when those STRs are already tested in the BigY data. Or am I missing something here?
Reply With Quote
  #2  
Old 14th August 2017, 04:41 AM
T E Peterman T E Peterman is offline
FTDNA Customer
 
Join Date: Sep 2004
Posts: 1,573
Some people just do a y-12, order Big Y, request the BAM, upload to yfull & then get access to all of those other str marker reads.

If you do this, you will get the numbers, but unless you get these markers from Family Tree DNA & have them in the database, they will have no matching value or TIP value.

Timothy Peterman
Reply With Quote
  #3  
Old 14th August 2017, 06:28 AM
Alhan Alhan is offline
FTDNA Customer
 
Join Date: Mar 2017
Posts: 2
Quote:
Originally Posted by sputnik View Post
Hi, I notice if I upload my BigY results to YFull for analysis, they report on 500 STRs, but FTDNA does not seem to report these results.
As the information is clearly in the data, why do I have to do a Y111 test if I want to search YDNA matches at that level, when those STRs are already tested in the BigY data. Or am I missing something here?
Same question here.
I wonder if that's a technical issue or marketing technique?

I'm still waiting for my BigY results. Thus, I don't know what I will have in terms of raw marker results in BigY pack. And Yfull is another question mark. If as a result of Yfull a list of markers with relevant values,
Should I prepare huge excel files copied from the Projects??
Reply With Quote
  #4  
Old 14th August 2017, 10:26 AM
John McCoy John McCoy is offline
FTDNA Customer
 
Join Date: Nov 2013
Posts: 516
Do I recall some past discussion about how often YFull (using Big Y BAM file) and FTDNA (using direct STR testing) disagree on the scoring of particular STR's? I don't remember what the conclusion was.

YFull does report how well your STRs match with other customers in its own database. However, I think the YFull haplotree is far more important, because it places you far more precisely in the haplotree than STR scoring ever could.
Reply With Quote
  #5  
Old 14th August 2017, 11:01 AM
MMaddi MMaddi is offline
yDNA: R-CTS2509; mtDNA: T2e
 
Join Date: Jul 2005
Location: Houston, TX
Posts: 3,376
Quote:
Originally Posted by John McCoy View Post
Do I recall some past discussion about how often YFull (using Big Y BAM file) and FTDNA (using direct STR testing) disagree on the scoring of particular STR's? I don't remember what the conclusion was.
You're correct. I don't know the details, but there are cases where FTDNA and YFull counts for specific markers may disagree. This is probably one reason why FTDNA does not use the STR results from Big Y tests for matching purposes.

I think this is related to the testing technology. FTDNA uses standard Sanger sequencing for getting STR results. Since Big Y is a Next Generation Sequencing (NGS) test, a different technology is involved. One problem with NGS testing being used for STR results is that the current read length is not long enough to accurately get results for STRs with a large number of repeats. Perhaps when NGS testing is able to use longer read lengths, that will cease to be a problem.
Reply With Quote
  #6  
Old 14th August 2017, 12:51 PM
JSW JSW is offline
FTDNA Customer
 
Join Date: Apr 2003
Location: San Antonio, TX
Posts: 301
MMaddi wrote " One problem with NGS testing being used for STR results is that the current read length is not long enough to accurately get results for STRs with a large number of repeats. Perhaps when NGS testing is able to use longer read lengths, that will cease to be a problem. "

I agree with that I have looked at my BAM file in detail
and extracting an STR is a non trivial process.
The fact that YFull gets as many right as they do is
a (good) surprise to me.
It is more than a problem of just how to score an STR
the NGS data just does not give results that are a
accurate as Sanger.
Reply With Quote
  #7  
Old 28th August 2017, 11:21 AM
rrrobins rrrobins is offline
FTDNA Customer
 
Join Date: Apr 2017
Posts: 4
I found one STR value (DYS388) that FTDNA had at 12 and YFull placed at 13. I am reasonably certain that FTDNA has it right based on comparison with all my Y and Big Y matches.

Also several STRs from my Y-111 test had no value shown on YFull or were shown with a gray background, which I suspect means low confidence. Basically they are different tests and both are useful.
Reply With Quote
Reply

Bookmarks


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
FamilyTree bug reporting? Saffi Features Requests & Bug Reports Area 0 10th April 2017 08:57 AM
Big Y results and Haplotree POS/NEG reporting gthompsonft BIG Y and SNP Discovery 0 2nd May 2014 07:28 PM
E3b reporting new Deep SNP Results 4/20/07 Bill Harvey Paternal Lineage (Y-DNA STR) Advanced 3 2nd May 2007 09:15 AM
Haplogroup Reporting WHTurner DNA and Genealogy for Beginners 1 11th July 2005 09:59 PM
split reporting D3569 Group Administrators - Advanced Chat 0 12th March 2004 10:33 AM


All times are GMT -5. The time now is 01:47 PM.


Family Tree DNA - World Headquarters

1445 North Loop West, Suite 820
Houston, Texas 77008, USA

Phone: (713) 868-1438 | Fax: (832) 201-7147
Copyright 2001-2010 Genealogy by Genetics, Ltd.
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.