Double Match Triangulator Version History
Version 5.2.1, 12 Jul 2023
- The method of retrieving file information from open files added in 5.2 caused other problems, so now a message is given to warn when a segment match file is open for editing.
Version 5.2, 20 Jun 2023
- DMT now does one extra bit of painting. When two people triangulate with Person A and both have MRCAs that are not "R" and one is longer than the other, then the segment with shorter MRCA can be painted to one generation more along the line of the longer MRCA. That can be done because a valid segment cannot change parent part of the way through its match with Person A.
- DMT now will retrieve the file information it needs from segment files that you may have open without giving an I/O error.
- GEDmatch files which have matches with people who have a null name (i.e. they weren't assigned a name in GEDmatch and only have a kit number) would incorrectly become Person B if their first match occurs before the first Person B match in Person A's file. This problem has been fixed.
- The error message stating there was an invalid MRCA in the People file was listing the incorrect person. This is now fixed.
- The error message stating "Min Triang cannot be larger than Min Single" sometimes incorrectly was appearing for some large values of Min Triang or Min Single. Fixed.
- Fixed a couple of small memory leaks.
Version 5.1.1, 16 Jan 2023 - File changes in Folder
- If Folder B is selected, DMT will now look for the files in Folder B when the Run button is pressed. Previously, they were only found when Folder B was checkmarked or changed. Now any files changes to Folder B from the folder since your last run will be picked up for your next run.
- One-to-one files now can be in the folder containing File A, the folder containing File B (if File B is selected), or Folder B (if Folder B is selected) optionally with subfolders.
- Messages in the log file about one-to-one files included now list the full file path rather than just the filename.
Version 5.1, 12 Dec 2022 - Improve Efficiency of GEDmatch 1-1 processing
- The processing of GEDmatch one-to-one files included an extra unneeded loop. This was causing a major slowdown in GEDmatch processing when there were more than a few one-to-one files. This has been fixed.
Version 5.0.7, 27 Oct 2022 - Fix for GEDmatch 1-1 download (one more time)
- Copying a GEDmatch's One-to-One page from Firefox or sometimes from Google Chrome adds a blank line to the beginning of the clipboard text, causing DMT not to recognize it. This is now fixed.
- DMT will now let you know if there are no segments in the One-to-One results rather than just saying "Problem reading GEDmatch data".
Version 5.0.6, 8 Oct 2022 - Fix for GEDmatch 1-1 download (again)
- GEDmatch changed their One-to-One page again. This time they added three columns to their report in both their Classic and their New view. DMT now handles this.
Version 5.0.5, 20 Sep 2022 - Fix for GEDmatch 1-1 download
- GEDmatch changed their One-to-One page in their Classic view. They simply changed the capitalization of One-to-One in their heading. As a result, the DMT "Saving GEDmatch 1-1" button was no longer accepting the copied page from the clipboard. This has now been fixed. This was not a problem for GEDmatch's New view.
Version 5.0.4, 20 Sep 2022 - Fix no chromosomes in a segment
- Fixed a pesky error that was hard to track down. In a combined run, when there were no segments for a chromosome, DMT would produce a "One range has the top bigger than the bottom" error. This would happen with MyHeritage files which don't include the X chromosome, and for GEDmatch files where the X-DNA match file was not downloaded.
Version 5.0.3, 18 Aug 2022 - Fix and Improvement
- Triangulation group boundaries were not being calculated correctly for one-to-one runs. This bug was added in version 5.0.0. Now fixed.
- A Missing AB match where Person C is a sibling of Person A is now treated as an inferral where an inferral is possible. If the sibling were on the same parent as Person B, then it would be a triangulation. But since this is a Missing AB match, the sibling match with A must be on the opposite parent as the sibling match with Person B. Thus an Inferral of Person B's ancestral path is possible.
Version 5.0.2, 16 Jul 2022 - Fix for GEDmatch.
- For GEDmatch files, DMT was not detecting a match between A and B when Person A's segment match file did not match Person B, but Person B's segment match file matched Person A. This was due to GEDmatch not including the name of the person in the file and I had neglected to add the necessary code to handle this case. Now fixed.
Version 5.0.1, 16 Jun 2022 - Fixes for GEDmatch, DNA Painter and version check.
- The "Save GEDmatch 1-1" button did not work with the new web layout at GEDmatch. This has been fixed.
- DMT's DNA Painter file stopped being accepted at DNA Painter. This has been fixed.
- Unfortunately in Version 5.0, the checking for a new version was not working, so the auto-update feature from within DMT in 5.0 was not accessible. If you have Version 5.0, then to update to a new version, you'll have to go to the website and download and install the new version. Doing so will overwrite 5.0 with 5.0.1 (or later) and DMT will remember your licence info and settings.
Version 5.0, 17 May 2022 - Algorithm Change allowing Triangulations on Both Parents
- Different triangulations on the same segment for Persons A and B are now allowed to occur on both parents. This is a major change in the 5.0 version. Previously, all triangulations competed for the parental side they were on, based on the original idea that one B person (other than siblings) generally triangulate on a segment through just one parent.
- This allows triangulations without an MRCA to be assigned to the parent with known triangulations on that segment. If neither or both parents have triangulations anywhere along the segment, then the segment is placed in the Unassigned parent group.
- Single matches without an MRCA denoting the parent now are assigned to the parent without known triangulations on that segment. If neither or both parents have triangulations, the segment is placed in the Unassigned parent group.
- Allowing triangulations on both parents now results in much more useful information to be displayed when B is a sibling of A. Previously for siblings, only C people with MRCAs and inferrals were shown. Now over segments where triangulations for the sibling occur for just one parent, the other triangulating and non-triangulating segments can have their parent group assigned.
- A new status of "MRCAs differ" is assigned to triangulating segments where Person B and Person C both have MRCAs that indicate they are from opposite parents. These segments will be included in the Unknown parent section. This can validly happen if Person C is related to person A through both parents, or it may be the case of A, B and C matching on different parents, e.g. A's father matches B's father, A's mother matches C's father, and B's mother matches C's mother.
- The Ancestral path at every Mbp is now determined first using ancestral paths of all triangulations and will only use single matches if there are no triangulations. Previously, triangulations and single matches were applied equally. This was changed because with the new algorithm, triangulations now invalidate single matches.
- Triangulation groups are now determined only from the triangulating section of a segment rather than from full AC segment as they were before.
- Grandparent extensions are now done by comparing the grandparent assigned at every Mbp within a triangulation group. The grandparent assigned to the most Mbp locations is now used to extend the ancestral path at each Mbp in the triangulation group. Grandparents now nicely extend just to triangulation group boundaries, rather than partly through triangulations groups as they did previously.
- Triangulation groups are now assigned to segments that triangulate based on just the part of the segment that triangulates rather than their full segment length.
- A new status has been added called "MRCA Bad on X". This indicates for a segment on the X chromosome that either (a) there is "FF" somewhere in the MRCA for Person C, or (b) the MRCA for person C starts with "F" when Person A is male. The first is not possible because the X cannot be passed down from a male to a male, and the second is not possible because a male gets his one X from his mother. In both cases, the MRCA will not be used with that segment..
- When the People file is first created for a male with one X chromosome, the X chromosome is now initially marked U (undefined) rather than M (mother). This puts all people initially in cluster U ordered by highest to lowest total cM which makes it easier to find the people to assign MRCAs.
- With the triangulations now allowed on both parents, Base AB matches would now possibly be included on both the F and M side or maybe the U side making them harder to find. After some thinking, I decided to not show the Base AB matches as their own lines in the output. So the status "Base AB" no longer exists. Instead, the start position, end position and cM of the A-B segment is now shown on each line. Even though they repeat a lot, there is now less searching to find the A-B match information. They are included in columns O, P and Q after the point where the frame freezes, so they hide when you scroll right.
- The AB start and end positions are highlighted if they are at (i.e. define) the beginning or end of a triangulation. Along with the Start-AC, End-AC, Start-BC and End-BC values, it's now easy to see which of the 3 matches define the start and end points of the triangulation.
- Similarly, the AB cM value is highlighted if both Start-AB and End-AB delimit the triangulation. Like the CM-AC and CM-BC values, CM-AB will give the length of the triangulation if both its start and end is highlighted.
- Inferred matches are now treated as small segments if they are smaller than Min Single. If so, they are given the status of "Small Inferred" and are placed in the X (excluded) section.
- Missing AB and Missing BC matches now must have their AC segment be larger than Min Single. If less, they will be treated as Small AC match since the AC match may be false.
- When one or both parents are in the Segment Match file, the parent(s) that match each AB segment now help to define the parental side of the ancestral path of all triangulations.
- The Combined results no longer is determined internally by repainting and re-analyzing all the segments. Instead, it now uses a consensus of the Ancestral Paths from each of the A versus B runs.
- In the Combined results file, the AC Consensus line is no longer produced. Instead, each segment match of a person has all its A-B runs grouped together and all are given the same Triangulation Group and Ancestral Path. The matches will be placed in the F, M or U parent sections as appropriate. If the Ancestral Path is different than it was in the A versus B run, then it will be appended with the word "was" followed by original value, e.g. FF was F.
- For a combined run, the largest invalid segments are no longer shown in the log file. Those tended to just be the largest segments smaller than Min Single which wasn't useful.
- DMT will no longer allow a run when the user's Min Triang setting is larger than Min Single.
- A single match file now ends with "_single.xlsx" to differentiate it from a combined result file and to emphasize that it is based on single matches rather than double matches. This also prevents it from being overwritten by a Combine All Results run.
- The log filename no longer includes a datestamp. It now includes the name(s) of the file(s) used follow by "_log.txt", "_single_log.txt", "_all_doubles_log.txt" or "_combined_log.txt" depending on the type of run done. Older log files are now overwritten when the same run is repeated. This results in fewer log files and the log file for a specific run will be easier to find.
- When the mouse is over one of the three "..." buttons, a hint box shows up displaying what the button does, e.g. "Select the Person A file".
- Bugfix: When the start of an AB segment had a very small overlap with the end of an AC segment, an overlap between that AB segment and the next AC segment for that person was being missed. This was more likely to occur when comparing siblings. But even with siblings, it only seemed to miss about 14 matches out of 50,000. This is now fixed.
- Bugfix: When two AB segments match two BC segments and the two segments both match different parts of an AC segment, the second triangulation was sometimes not included. This is now fixed.
- Bugfix: The number of people with the same name as someone else has been corrected in the log file. It previously was listing the total number of overlapping segments found, rather than the number of people.
- Reviewed and updated as necessary both the help file and the website.
Version 4.3.1, 02 Sep 2021 - Fixes
- Fixed a problem in a Combine All run where there's an extra Single AC match that is not needed because other statuses for that match are available. When that extra match was the final line of a chromosome, then DMT would give an Argument out of range error and abort.
Version 4.3, 26 Aug 2021 - New Family Tree DNA format supported
- Family Tree DNA's new segment file format is now supported. The file no longer contains the tester's
name, so the user must now manually add to cell G1 of the file the tester's name as it is used in other people's match files. New format Family Tree DNA files may be used with the previous format, but since the company also changed their matching algorithm, the segment matches have changed, and results from a person's old file will differ from their new file.
- The Ancestral Path in Combine All reports for Single AC matches has been fixed. It was picking the Ancestral Path as determined from the first B file read. But now it is calculated correctly from the consensus path of all the Ancestral Paths determined from all the B files.
- DMT now only displays the Single AC match in Combine All reports if there are no better statuses for that match (e.g. Triangulation, Missing AB, Missing BC) or if there is an Ancestral Path determined for it.
- DMT now only displays the Small AC match in Combine All reports if there are no better statuses for that match (e.g. Triangulation, Missing AB, Missing BC). Note: Small AC matches never have an Ancestral Path determined for them.
- Base AB matches in A-B runs are now displayed as Single AC or Small AC matches in the Combine All run. Previously they were displayed as Full Triangulation if they had a triangulation somewhere over them, or as a Single AC if they didn't. Their display as Full Triangulation is not needed because all the individual triangulations are shown in the Combine All run, and was somewhat confusing.
- Fixed it so that the "Run" button will be enabled after the user corrects a problem with File B in an A-B run.
- Previously, when there were A-B matches in both File A and File B, DMT compared segment matches in the two files and only used the ones that were the same. Now the matches between Person A and Person B will all be taken from Person A's match file. If that file has none (because it is older and Person B hadn't tested yet), then they will all be taken from Person B's file. DMT's log file will warn you if the matches of Person B in Person A's file differ from the matches of Person A in Person B's file and will display both sets of matches so you can compare them.
Version 4.2, 10 May 2021 - Check for new version, web update, and misc fixes
- Replace the link to the website with a check for a new version. Clicking on the link will go to the website and check a small file containing the latest version number and compare it to your version. A new window will open giving telling you if you have the latest version available or if there's a new one. If there is a new one, you can press an update button which will download the latest version and run the installation for you, which avoids all Microsoft's download warnings.
- The web update window gives you the option to check automatically for new versions. If you select this option, then DMT will check for a new version once when you start DMT.
- The limit for base addresses on chromosome 21 was increased from 46999999 to 48999999. This fixes the drawing of the triangulation group boundaries for chr 21 segments with endpoints higher than 46 Mbp.
- Default Min Triang and Min Single values changed from 8 and 12 cM to 7 and 15 cM, which are more generally accepted limits for almost-always valid triangulations and almost-always valid single matches.
- DMT's window now opens where you last had it open on your screen.
- The File A, File B and Folder B dropdown boxes now change size fully when the width of DMT's window is changed. Previously they only changed to half of difference.
- The default A or B directory was not getting updated when a file with the same name in a different directory was opened. Now fixed.
- Fixed bug in Combine All run when both of Person A's parents are included as Person B files. DMT sometimes was not assigning any ancestral groups to either parent.
Version 4.1, 28 Apr 2021 - Refinements to the algorithms and GEDmatch fixes
- Long segments extending into a grandparent ancestral path were incorrectly being assigned the grandparent path when they should be assigned just the parent path. This was due to the removal of the grandparent extension algorithm in 4.0 which was no longer thought to be needed. The algorithm was added back into 4.1 to handle this correctly.
- Triangulating segments where Person B is a sibling of Person A (MRCA = 'R' and shared cM is between 2300 and 3300) are not painted as "triangulated" so that triangulating segments on the same region won't be assigned to just one parent, when it could be either. And then non-triangulating segments in the same region won't be assigning to the other parent, when it also could be either.
- To correctly respect the horizon effect, inferred segments now must be at least 3 cM greater than the minimum triangulation length. This will prevent most cases of false inferrals where an AC match that is under the minimum length does exist.
- The grandparent implied by inferrals was being painted on the segment. This sometimes incorrectly changed the ancestral path assigned to triangulated segments. Inferred grandparents are no longer painted to the segments. Inferrals are now only applied after the ancestral path is determined, and now the inferrals can only extend or initially assign the path, but not change it.
- Inferred matches were not being painted in combined runs at Mbp locations that did not have at least one grandparent as an AC Consensus. Some inferred matches were not being shown. This is now fixed.
- Inferred matches were not being applied to Mbps where no ancestral path assigned from matches. Now they are.
- The handling of GEDmatch One-to-one files now adds the names of the one-to-one matches to the people file.
- GEDmatch One-to-one files will be used for Person B if the other person is also a Person A match.
- The folder where a GEDmatch One-to-one file will be saved will now defaults to be Folder B rather than the last place a One-to-one file was saved.
- For GEDmatch files, Person A's name will now be taken from a one-to-one files.
- The People file will now be recreated in any run whenever the number of people matching Person A gets increased or decreased. This could happen because a new segment match file for Person A is downloaded or new GEDmatch One-to-one files are downloaded. Person A's sex and their assigned MRCAs will be saved from the previous file and included in the new file. A sneaky way to force recreation of the People file is to delete a few people who don't have an MRCA assigned and do a run.
- The limit for base addresses on chromosome 1 was increased from 247999999 to 249999999. This fixes the drawing of the triangulation group boundaries for chr 1 segments with endpoints higher than 248 Mbp.
- File A and File B were being locked by DMT even when they were not being used. That is now fixed. This bug got into version 4.0
- Files are now read even if they have illegal Unicode characters which some MyHeritage segment files have without crashing.
- Files that have a Byte Order Mark (BOM) at the beginning are now read correctly. Normally, segment match files will not have a BOM unless they are manually edited and saved with some text editors.
Version 4.0, 22 Feb 2021 - Improved ancestral group assignment
- Now handles the new format of GEDmatch's segment file, which they changed about Nov 28, 2020.
- Now handles the slight change in GEDmatch's one-to-one comparison report, which they changed about Nov 25, 2020.
- DMT 4.0 no longer supports the older format MyHeritage segment match files prior to May 2019. The newer MyHeritage files include an ID number that identifies the match person uniquely. This eliminates problems with people having the same name. With the new files, you will need to you re-create your old People file because of the IDs now added to the names. DMT will pop up a message box to warn you if you need to do this.
- DMT no longer needs a segment overlap to detect multiple people with the same name. If the name is found a second time in the file, it is considered to be a repeat. This is only a problem for FTDNA and 23andMe, since GEDmatch and MyHeritage include unique IDs in their segment match files.
- DMT better checks to ensure segment match files are correctly formatted. This should allow DMT to report a file format as invalid if it is changed by a vendor, rather than causing the DMT to crash.
- There is no a drop down box where you can specify Person A as: "Male (1 X)" or "Female (2 X)", so that the X chromosome will be presented correctly, as just the mother for males, or mother and father for females.
- For "Male (1 X)", any X chromosome ancestral paths starting with "F" (father) or containing "FF" (e.g. "MFF") will be not be considered possible. Any relatives matching on the X who have one of an MRCA on one of those impossible paths will be assigned an ancestral path that other matches assign to the segment.
- Matches smaller than the minimum triangulation length for person A are no longer included in the analysis. To handle the horizon effect, DMT now requires segments 3 cM greater than the minimum triangulation length rather than segments 2 cM smaller to denote Missing AB and Missing BC matches. As a result, some smaller Missing AB and Missing BC matches will be treated as Small AC matches which is better to do than being wrong about a small triangulation which was possible using the 2 cM smaller criteria.
- When the MRCAs of Persons B and C are on opposite parents, they will no longer be used in calculating the ancestral path of a triangulation.
- Removed DMT's detection of siblings and automatic setting of the MRCA to "R". Noting that someone is a sibling was used to prevent grandparent extensions for sibling matches. But now, user entry of the "R" as the MRCA will do that instead. The "R" is entered for anyone sharing having both parents of Person A as their ancestor.
- DMT no longer does grandparent extensions on segments. That mostly happens on its own and didn't really add much.
- Removed the iterations that were usign the calculated ancestral paths as the MRCA. It was a nice idea, i.e. basically to assume that the calculated ancestral paths of each person are correct and running DMT again using them as the MRCA. But doing so changed some of the segment assignments, making it much harder to trace the reason why you might have a conflict. I decided it was better to not iterate so that the result would be based just on the MRCAs supplied. This iteration can still be donee manually if desired, by copying the ancestral paths to the MRCAs in the People file and running DMT again.
- Fixed a bug that was slowing Excel file creation by a factor of 10. What was taking 10 seconds to create the file now takes 1 second. This bug was in the program since version 3.0 (October 2019)
- When running just File A alone after running some other run without closing DMT, the MRCA of Person B from the previous run was not cleared out sometimes causing some incorrect ancestral path assignments. This has been fixed.
- When Folder B and its subfolders (if selected) have quite a few segment match files, there can be a slight delay while the files are checked. DMT now issues a message that this is being done and to wait.
- Fixed a problem where duplicates from Person B's file sometimes were be added to the People file and might cause a different person to be marked with the duplicate prefix: ##
- Help file has been reviewed, revised and brought up-to-date.
Version 3.1.3, 29 Jan 2020
- Allowed DMT to accept chromosome '98' as the X chromosome which can be found in some Family Tree DNA project data.
- DMT now checks that the chromosome number is valid, which prevents DMT from crashing when an illegal chromosome number is in the segment match file.
Version 3.1.2, 21 Jan 2020
- Fixed the display of Base A-B segments in a combined run. They were always showing as single matches, but when they triangulate, they should show as Full Triangulation.
- Improve the handling of the horizon effect by restricting just B-C segment matches to the Min Triang value and allowing smaller A-C and A-B matches.
- Improve some of the data displayed and data descriptions in the log file.
- Allow Person A and B to be processed if only one file has matches to the other. Previously, matches both ways was required which won't happen when one of the files was downloaded before the other persons test results were available.
- MyHeritage Matches Shared Segment files are now filtered only by their English filename to help prevent the more severe problem of people selecting their MyHeritage Matches List file by mistake.
- If running only File A, then messages say that instead of "using 0 Person B Files"
- The Min Single label now shows as dark grey instead of red when values of 10 cM or 12 cM are selected, since 85% of single matches 10 cM or more should be valid.
- The display of the number of inferred segments on the People page is now right justified rather than center justified.
- If you have the DMT or People file open when DMT is trying to save it, DMT will now prompt you to close the file.
Version 3.1.1, 24 Oct 2019
- A-B matches that are only in file A or only in file B will now be accepted for GEDmatch files, because the GEDmatch ID is unique and guarantees that we have the correct kit.
- GEDmatch file lines with a comma in the Test Company field will now be accepted.
- Indicate "MH Not Shared Segm" instead of "Invalid Input File" when a MyHeritage Match List file is selected instead of a MyHeritage Shared Segment file. DMT can't filter the Match List files out because their filenames cannot be distinguished with only English words. MyHeritage changes filenames depending on your Windows language.
Version 3.1, 16 Oct 2019 - Improved algorithms
- Improvements to the grandparent extension algorithm.
- Small improvements to the calculation of triangulation group boundaries.
- In a Combine All Files run:
- Corrects a few matches that were not being assigned an AC Consensus.
- Corrects a few assignments of AC No Parents when there is a parent.
- Fixed bug in 32-bit version of DMT that caused crash when writing files.
- Fixed bug that prevented loading of the B match statistics for a Compare Two Files run.
- When using 23andMe DNAGedcom FIA Input files:
- Fixed incorrect filename given to People file.
- Now detects the same person's name correctly.
- Now handles the DNAGedcom bug that sometimes excludes the first name when it is only 1 character.
- Person B columns are now included in the people file in alphabetical order, rather than reverse alphabetical order.
- Tuning: Increased the internal minimum overlap DMT uses to 1.5 Mbp, previously 1.0 Mbp to reduce the effect of by chance overlap at either end of a match.
Version 3.0.1, 3 Oct 2019 - Important Bug Fix
- The People file was not being created correctly the first time. Now fixed.
(Murphy's law: 2 lines were out of place in the program)
Version 3.0, 1 Oct 2019 - Automates chromosome mapping.
- An MRCA (Most Recent Common Ancestor) column has been added to the People file, allowing you to enter the MRCA for each person that you know.
- The process of segment matching and assignment of ancestral paths to segments and matches is now automated in an expert-system manner that mimics what a person would do map their chromosomes.
- You can now select the minimum cM of the matches that you want DMT to include in its analysis.
- You can now run DMT with only Person A to get the listing of Person A's matches and people.
- DMT now handles all the new segment match file formats from the various companies.
- The Map page, People page and Log file all have extensive revisions.
- DMT outputs a dnapainter csv file that can be uploaded to www.dnapainter.com.
- Now uses conditional formatting extensively in the Excel files, so most of the formatting should move when the data is copied and pasted or sorted.
- Now can filter all matches to a minimum cM.
- Calculates and uses all inferred matches
- Clusters people into their primary ancestral lines.
- Does parental filtering if one or both parents have DNA tested.
Version 2.9.5, 8 Jan 2019 - Additional fix needed to handle new Family Tree DNA format.
Version 2.9.4, 20 Dec 2018 - Various fixes and changes to allow DMT to work with changed file formats, including:
- Changes Family Tree DNA made in October 2018 to their Chromosome Browser Results file are now handled.
- Changes GEDmatch made to their Genesis Matching Segment Search report (adding a checkmark column) are now handled.
- 2.1.1 only fixed 23andMe names when comparing 2 files. Now it is also fixed for multiple files
- A case of incorrect warnings of mismatches between Person A and Person B is no longer displayed.
- 23andMe people who are not sharing are now included on the People page and marked as **not sharing**.
- GEDmatch puts an asterisk (*) before alias names, and now DMT will find Person A and B in each other's files properly if either one has an alias name.
- Names with a space before it now will match to the same name without a space before it.
- Prevent a crash when reading in numbers that contain commas.
- Fixed crash when attempting to create a new folder during a save of a GEDmatch file.
- Fixed display of cM on people page for the Base AB person when that A is in B's file but B is not in A's file.
- Fixed detection of MyHeritage files in Folder B.
- Fixed problems reading in the chromosome when the value is X and has a space before it.
Versions 2.9.1 to 2.9.3 - These were 3 private builds for users who encountered the file change problems that are now fixed in 2.9.4
Version 2.1.1, 28 Mar 2018 - Correction to reading match files when Windows Region Number settings are not comma for thousands and/or period for decimal point (e.g. non-English based Windows). The name of the tester in the 23andMe Relatives Download file name no longer has to have its case (capitals and small letters) changed to be the same as what's used in the match files.
Version 2.1, 7 Mar 2018 - Reads the new segment match files from MyHeritage DNA that they now let you download.
Version 2.0.2, 18 Feb 2018 - Fix for some 23andMe files that caused error when loading. 23andMe included lines with no segment match information that need to be ignored.
Version 2.0.1, 8 Feb 2018 - Did not realize that different web browsers copy to the clipboard differently. The "Save GEDmatch" button now should work for any web browser.
Version 2.0, 6 Feb 2018 - New Excel engine no longer needs Excel installed. Now reads 23andMe and GEDmatch data directly. Includes a helper to download GEDmatch data. Missing AB regions now displayed distinctly from triangulations. Combined files displayed by AC match. Lots more.
Version 1.5.1, 17 Jul 2017 - List people by highest largest cM instead of by highest total cM. Display an error when CBR file contains invalid Hex '00' character. Fix the file processing and display after the same file is set as both File a and File b. Fix crash when running By Chromosome Files.
Version 1.5, 22 Mar 2017 - Now requires purchase of license for full display. Without license, DMT now hides most of the Person c names. Fixed bug that would crash program in no By Chromosome files matched. Fixed By Chromosome People b columns whose values were inflated because the a-b match was inadvertently included. Updated install program to follow changes to
Microsoft's desktop applications guideline.
Version 1.4.1, 16 Feb 2017 - Now checks that at least Excel 2007 is installed and if not, only produces .csv file. Fix to prevent crash that sometimes happened during By Chromosome runs when there are only a few double matches on a chromosome.
Version 1.4, 20 Jan 2017 - Now works if either File a or b was downloaded before the other person's results came in. Prevents the same person from being used twice. Excludes non-matches from By Chromosome analysis. Better handling of duplicate segments in CBR files. Improvements to People page. Several minor fixes and improvements. Updated help file.
Version 1.3, 12 Dec 2016 - Improved output on People page including some color coding to ease interpretation. Implemented the idea of
Theorem 1 so Triangulation Groups are now determined independently of Double Match Groups. Updated help file.
Version 1.2, 21 Nov 2016 - Now can work if only Person a has b matches or Person b has a matches, which might occur if one file was downloaded before the other's test results were in. Excludes duplicate or overlapping segments in CBR files and prefixes such people with ##. The People page and file now include just the Person c matches with Person a.
Version 1.1.99, 18 Oct 2016 - Identifies Double Match Groups. Allows combination of multiple runs by Chromosome. Improved People Page/File.
Version 1.1, 27 Aug 2016 - Cursor now changes when running. Does not try to create Excel files on computers without Excel (so it won't hang) and creates csv files instead. Eliminated folders for Person a.
Version 1.0.1, 20 Aug 2016 - Fixed possible freezing on some computers when running.
Version 1.0, 18 Aug 2016 - Initial Release.
Version 0.99.1, 04 Aug 2016 - Private Beta.
Version 0.99, 03 Aug 2016 - Private Beta.