Announcement

Collapse
No announcement yet.

Lost so many matches

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • efgen
    replied
    Originally posted by 1_mke View Post
    Beating a dead horse here, but I think it is innacurate for FTDNA to claim this FMS thing is a seperate issue.
    I'm sure you already know this, but they meant that the FMS issue was not related to the Build 37 upgrade The FMS issue was reported to IT late Tuesday night and was fixed first thing Wednesday morning, before 9am.

    Originally posted by 1_mke View Post
    It's all the same issue which is that their operations and IT stuff is a mess and clearly poorly run and/or funded. I'm hoping they are either already taking steps to correct these issues or will soon.
    Anyone in Houston looking for a full-time job? FTDNA has job postings for experienced software developers, customer service (information specialists) and several other positions:

    http://www.familytreedna.com/careers.aspx

    Elise

    Leave a comment:


  • Colin
    replied
    After seeing the above i went to my FMS results and 5 had become 3152 or some such, but not the original 5 EXACT matches, they still show among HVR2 matches.

    Leave a comment:


  • 1_mke
    replied
    Beating a dead horse here, but I think it is innacurate for FTDNA to claim this FMS thing is a seperate issue. It's all the same issue which is that their operations and IT stuff is a mess and clearly poorly run and/or funded. I'm hoping they are either already taking steps to correct these issues or will soon.

    Leave a comment:


  • emyr
    replied
    I just talked with a rep and he told me the FMS issues are totally separate from the FF issues. I expressed frustration but it did no good of course. I have purchased 6 FF kits, 1 FMS, and 3 ydna kits. My brother has purchased 2 FF kits and 1 ydna test. I chose testing with ftdna because i believed their product was of the best quality. As I told the rep, I'm beginning to lose my confidence in the quality of their product. I really hope they get things sorted out soon. I don't want to take my business elsewhere, but at some point I will be forced to if this continues.
    Last edited by emyr; 13 March 2013, 08:28 AM.

    Leave a comment:


  • Lincoln
    replied
    Something is happening. I now have a LOT more FMS matches (still have no FF matches- the 30 I had left went way days ago), but sometime today, the FMS matches showed up. I had 5 until this am, now have 21. EDIT: I know this is a FF forum (and thread) but thought this is significant nonetheless. Will post when I get my FF matches back. Am assuming it will take a while.

    Leave a comment:


  • saudi arabia
    replied
    all my matches gone

    i want them back or at least one match

    i dont to be alone

    Leave a comment:


  • janeliz
    replied
    Have lost all my FF matches. None were closer than 3rd, 4th or 5th cousin but no idea if they were too remote to be included in "refined" results or whether they were one of those whose matches were wrongly obliterated. How and when will anyone know which is the case? Will also be interested to know if anyone has had their matches restored.

    Leave a comment:


  • Taz85
    replied
    Down to only 28 matches. At Gedmatch I have 300 or so. Prob close to 2000 at 5cM. I have come to accept the fact that I have very old, rare DNA. I might test somewhere else.

    Leave a comment:


  • jbarry6899
    replied
    Lost so many matches

    Has anyone who lost all of their FF matches had them restored? Mine disappeared last week and as of today are still among the missing.

    Jim

    Leave a comment:


  • Kasandra
    replied
    Originally posted by efgen View Post
    23andMe has been on Build 37 since last October or so. Their transition is what prompted FTDNA to start working on its own transition when it did. Once 23andMe was on Build 37, FTDNA either had to "downgrade" new transfers to Build 36 to make their data compatible with FTDNA's customer data, or they had to convert their own customers to Build 37. They chose the latter since they needed to transition to Build 37 eventually anyway.

    Elise
    The raw data files were converted to build 37 last October but they continue to use build 36 for matching. I've asked the company to make a statement about whether they will remove matches shown to be mismatches once they convert to build 37 and they have refused to do so. Until they make a statement, I will mistrust what will happen (and indeed what is going on now.) Why they would not make the simple public pledge to remove matches that are found to not be matches is beyond me. I have no desire to waste time on matches that aren't real. (not to say I would not stay friends with those I lose!)

    Leave a comment:


  • Odis
    replied
    Time will tell if I will lose matches at 23andme on build 37, but they look to be going for the goal of one million customers and maybe the build 37 is on the back-burner for now..

    Leave a comment:


  • efgen
    replied
    Originally posted by MFWare View Post
    Therefore, it may very well be that there will no significant reduction in the number of matches at 23andMe when it completes its Build 36 to Build 37 transition.
    23andMe has been on Build 37 since last October or so. Their transition is what prompted FTDNA to start working on its own transition when it did. Once 23andMe was on Build 37, FTDNA either had to "downgrade" new transfers to Build 36 to make their data compatible with FTDNA's customer data, or they had to convert their own customers to Build 37. They chose the latter since they needed to transition to Build 37 eventually anyway.

    Elise

    Leave a comment:


  • MFWare
    replied
    Originally posted by Odis View Post
    I have lost matches here from 408 to 302 but it seems I have lost some reliable matches, but I will be satisfied to know the matches are correct and not be chasing false positives, I have over one thousand matches at 23andme but I think some are not correct, I asked them about the build 37, it is not complete there yet, they state some matches will change, but I won't lose any, I'm not buying that, since I lost 25% here..
    Do not assume that one company's product will have the same issues as another company's product. It is interesting to note the differences in my own case between 23andMe data and Family Finder Build 36 data when uploaded to GEDmatch.com. Back in those wonderful days when I had matches in Family Finder, I had only 77 of them. This number was reduced to 49 after with the Build 36 to Build 37 transition. On 23andMe, I have going on 800 matches. On GEDmatch.com, I have a goodly number of matches to my 23andMe data. However, my Family Finder data on GEDmatch.com have matches that go much deeper into the past than my 23andMe data.

    Assuming that these deeper matches are the ones that Build 37 eliminates, it is likely that FT-DNA's update brought it into line with 23andMe. Therefore, it may very well be that there will no significant reduction in the number of matches at 23andMe when it completes its Build 36 to Build 37 transition.

    Leave a comment:


  • chartera
    replied
    Matches still in limbo

    My matches are still gone, posted messages by the feedback twice, first when they disappeared, then after the message, as noted above, was put up.

    Nothing was close, but then again, I have no close matches anywhere. It's disappointing.

    Leave a comment:


  • Odis
    replied
    I have lost matches here from 408 to 302 but it seems I have lost some reliable matches, but I will be satisfied to know the matches are correct and not be chasing false positives, I have over one thousand matches at 23andme but I think some are not correct, I asked them about the build 37, it is not complete there yet, they state some matches will change, but I won't lose any, I'm not buying that, since I lost 25% here..

    Leave a comment:

Working...
X