Jambe
using the command java Jambe
leads to various output files.
Of main interest for the pruning option
is file
resultsAllTopos.out.
This file contains all the topology strings written
out during the MCMC simulations, for various window
positions.
The probabilistic divergence measures can be
computed from resultsAllTopos.out
with class JambeAnalyseTopos;
just give the command
java JambeAnalyseTopos.
If you want to apply the simple
pruning option described
here
,
all you need to do is create a
file called
prune.in
with a single integer number.
This number specifies the total number of
different topologies to which the original
posterior distribution is pruned down.
Next, give the command java JambeAnalyseTopos,
as usual.
The package contains two further classes for pruning options, which are described below.
prune_taxum.in
with a single integer number: the number
of the taxum to be removed.
Next, copy or move your file
resultsAllTopos.out
to file
resultsAllTopos.bak.
Finally, give the command
java PruneTaxum > resultsAllTopos.out.
File resultsAllTopos.out
no longer contains the taxum specified in
prune_taxum.in.
However, as a consequence of string manipulations
performed by the program, different topology strings
may actually encode the same topology.
In order to rectify this shortcoming, an
invocation of
PruneInput is required,
which merges topology strings that encode
the same topology.
An example of a full application is given
below.
PruneInput has various
applications.
resultsAllTopos.out
from strings to integers
so as to allow reading in files where the
program might crash otherwise due to exhausted memory.
Application:
cp resultsAllTopos.out resultsAllTopos.bak
java PruneInput > xxx
mv xxx resultsAllTopos.out
java JambeAnalyseTopos
If you directory contains the optional
file
prune_input_format,
this file needs to contain one integer number:
the number "1".
Note that the application of this pruning option
rules out any further pruning of taxa and posterior
distributions.
prune_input_thesh.in with a single
integer number: the value of the threshold.
The program can write out topology strings (for option 2)
or integer codes (for option 1). The default setting is integer codes.
If you want to use the other option, generate
a file called prune_input_format.in
with a single zero in it.
The output topo strings from the MCMC simulation
have to be kept in file resultsAllTopos.bak.
Standalone invocation:
java PruneInput > name_of_output_file.
Questions you have to ask yourself:
resultsALlTopos.out
so as to prevent a memory overflow?
If yes, either edit file
prune_input_format.in
so that it contains the (single) integer number
"1", or delete this file.
prune_input_format.in
so that it contains the (single) integer number
"0".
prune_input_thresh.in
with a single integer number:
the minimum RF distance required for
treating two tree topologies as different.
Topologies whose RF distance falls below that
threshold are merged.
If you don't want to use this option,
either delete file
prune_input_thresh.in,
or set its integer to "1".
Jambe
are saved in file resultsAllTopos.out.
Proceed as follows.
First, create file
prune_taxum.in, whose single
integer number defines the taxum to be removed.
Unless you are running into memory problems,
you may want to create a file called
prune_taxum_format.in
with a single integer number "0"; this
keeps the topology strings rather than replace them
by integers.
Next, give the following commands:
mv resultsAllTopos.out resultsAllTopos.bak
java PruneTaxum > resultsAllTopos.out
java PruneInput > xxx
mv xxx resultsAllTopos.out
java JambeAnalyseTopos
prune_taxum.in,
prune_input_format.in and
prune_input_thresh.in are set correctly.
Typical mistakes are:
Back to my homepage