lonelyjoeparker / qmul-genome-convergence-pipeline

API and binaries for phylogenomic analyses, particularly comparison of input trees/alignments (CONTEXT) and detecting genomic convergence
4 stars 2 forks source link

ResultsPrinterSimple - output hard to understand #20

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
The order and meaning of the columns is opaque, e.g.:
The outputs.txt file gives, in order:
<ol>
    <li>locus</li>
    <li>ensembl_URL</li>
    <li>shortcode</li>
    <li>description</li>
    <li>homog</li>
    <li>mode</li>
    <li>missingData</li>
    <li>lnl (species tree)</li>
    <li>length (species tree)</li>
    <li>model alpha</li>
    <li>numberOfTaxa</li>
    <li>numberOfSites</li>
    <li>preferredTopology</li>
</ol>
Then, it gives (replicates for each (n) trees):
<ul>
    <li>d_lnL_H(n)</li>
    <li>dSSLS_H(n)</li>
    <li>tSSLS_H(n)</li>
    <li>numThresh_H(n)</li>
</ul>
So for instance, if there were two alternative trees, H1 and H2 (three trees 
total, including H0, the null tree), the columns would read:
<pre>locus
ensembl_URL
shortcode
description
homog
mode
missingData
lnl (species tree)
length (species tree)
model alpha
numberOfTaxa
numberOfSites
preferredTopology
d_lnL_H1
d_lnL_H2
dSSLS_H1
dSSLS_H2
tSSLS_H1
tSSLS_H2
numThresh_H1
numThresh_H2</pre>

Original issue reported on code.google.com by joeparke...@gmail.com on 4 Nov 2013 at 1:53