Available utilities for processing unzipped autosomal files from Family Tree DNA and/or 23andMe:
<ul>
<li><a href="http://www.math.mun.ca/~dapike/FF23utils/roh.php" target="_roh">Search for Runs of Homozygosity (ROHs)</a>
<li><a href="http://www.math.mun.ca/~dapike/FF23utils/het.php" target="_het">Search for Heterozygous Sequences</a>
<li><a href="http://www.math.mun.ca/~dapike/FF23utils/pair-comp.php" target="_pair-comp">Search for Shared DNA Strands in Two Raw Data Files</a>
<li><a href="http://www.math.mun.ca/~dapike/FF23utils/strand.php" target="_strand">Inspect a Shared DNA Strand in Two Raw Data Files</a>
<li><a href="http://www.math.mun.ca/~dapike/FF23utils/trio.php" target="_trio">Inspect Shared DNA Strands in a Trio of Raw Data Files</a>
<li><a href="http://www.math.mun.ca/~dapike/FF23utils/pair-discord.php" target="_pair-discord">Search for Discordant SNPs in Parent-Child Raw Data Files</a>
<li><a href="http://www.math.mun.ca/~dapike/FF23utils/trio-discord.php" target="_trio-discord">Search for Discordant SNPs when given data for child and both parents</a>
<li><a href="http://www.math.mun.ca/~dapike/FF23utils/diffs.php" target="_diffs">Search for Differently Reported SNPs</a>
<li><a href="http://www.math.mun.ca/~dapike/FF23utils/trio-phase.php" target="_trio-phase">Phase a Child when given data for child and both parents </a>
<!--
<li><a href="http://www.math.mun.ca/~dapike/FF23utils/phase-sibs-1parent.php" target="_sibs-phase">Phase Siblings with Data from One Parent </a> (this utility is deprecated; use the 2-parent tool instead)
-->
<li><a href="http://www.math.mun.ca/~dapike/FF23utils/phase-sibs-2parent.php" target="_family-phase">Phase Siblings with Data from Both Parents </a>
</ul>
<p>
These utilities were developed by <a href="/~dapike/" target="_full">David Pike</a>.

<p>
My original motivation for developing these utilities was so that I could privately perform some advanced analysis of autosomal DNA results, with my
objective being to better pursue genealogical research within my own family.  Instead of limiting these utilities to my own personal use, I have made
them available in the hope that they might assist other members of the genetic genealogy community with their own individual research goals.

<p>
Given the do-it-yourself nature of the intended user, the utilities are presented with minimal documentation and without verbose explanation of analysis
results.  Also note that the analysis performed by these utilities is based on my own methodology and implementation,
whereas Family Tree DNA, 23andMe and AncestryDNA
have their own proprietary analysis methodologies.  Differences in methodology may give rise to minor interpretive differences between their analysis and
that performed by my utilities.
<p>
Some other notes about these utilities:
<ul>



<li> They only accept *UNZIPPED* raw data files from either Family Tree DNA's Illumina-based FamilyFinder (.csv files) or 23andMe (.txt files)
     or AncestryDNA (.txt files).


<li> They should work with Chrome, Safari, and some other browsers.
     But they probably will not work with Internet Explorer.
     They should work with Firefox 3.6 Beta or later versions of Firefox
     (<a href="http://www.mozilla.com" target="_new">available from here</a>).
     Earlier versions of Firefox will not work with these utilities.
     Note, however, that some of the utilities are computationally intensive and might run much slower in Firefox
     than in a different browser such as Chrome.

<li> They do their processing on your computer and not mine.
My real point here is that your raw data files are not sent over the internet by these utilities.


<li> No-Calls are reported differently by FTDNA versus 23andMe versus AncestryDNA.
     These utilities convert all No-Called SNPs to question marks.

<li> Utilities that involve the comparison of two or more raw data files do not need the files to all be from one company or to have the same file format.
     <br>
     Nor do the files need to contain the same set of SNPs.
     Only those SNPs that occur in all files being processed will be compared.  All other SNPs will be ignored. 
<br> Synchonisation of SNPs between files is performed based on the position numbers of the SNPs. 
     It is assumed that the files have been pre-sorted to have the SNPs on each chromosome listed in ascending position value.

<li> If you want to trick these utilities into using other text files, then you'll need to conform to one of the following file formats:
     <ul>
     <li> A tab-separated file with an initial line beginning with # and containing the string "23andMe", and no quotes on any data.
          <br>
          Data items should be in order:  RSID, Chromosome Number, SNP Position Number, a single string with both alleles
     <li> A tab-separated file with an initial line beginning with # and containing the string "AncestryDNA", and no quotes on any data.
          <br>
          Data items should be in order:  RSID, Chromosome Number, SNP Position Number, first allele, second allele
     <li> A comma-separated file with each data item enclosed in quotes.
          <br>
          Data items should be in order:  RSID, Chromosome Number, SNP Position Number, a single string with both alleles
     <li> A space-separated file with no quotes on any data.
          <br>
          Data items should be in order:  RSID, Chromosome Number, SNP Position Number, a single string with both alleles
     </ul>
     Any line beginning with the # symbol or containing the string "RSID" will otherwise be ignored.
     <br>
     Note also that if you wish to process files from FTDNA's former Affymetrix-based FamilyFinder then 
     you should translate all instances of "--" to "DD" 
     before subjecting your data to analysis; 
     otherwise the utilities will erroneously treat these deletions as No-Calls.
     Instances of "---" in Affymetrix-based data will still be correctly treated as No-Calls.

<li> If Firefox complains about "A script on this page is causing Mozilla to run slowly" then you might want 
     to configure Firefox to not complain as quickly when a script is running.  
     <a href="http://kb.mozillazine.org/Dom.max_script_run_time">Click here</a> for details about one way to change this Firefox configuration setting.

<li> Javascript source code is contained within the top frame of each individual utility.
     If you want to view how I've implemented things, that's where you'll find the code that I've written.
</ul>

<!--
I do not yet know of a nice way to get javascript code that is embedded in a webpage to write its
output to a file on the user's hard drive.  In most circumstances enabling such functionality would pose a security threat,
but if anybody knows how to let the user specify a target file and provide consent to write to it,
please let me know.
-->