Description Usage Arguments Details Value
This runs it in a directory and the output from stdout goes into a big file spip_out.txt in that directory. Currently this is pretty bare bones.
1 2 3 4 5 6 7 |
pars |
A named list of parameter values. |
dir |
The directory to run it in. Defaults to a temp directory, which will be unique every time it is run. |
spip_seeds |
a vector of two positive integers. These get written to the
file spip_seeds, which is used by spip to seed its random number generator. By
default, R supplies these two integers from its own random number generator. This
way reproducible results from spip can be obtained by calling |
num_pops |
the number of demes that are being simulated. This is still being implemented... |
allele_freqs |
a list of allele frequencies provided if you want
to simulate unlinked genotypes for the sampled individuals. The default
is simply a single locus with two alleles at frequencies 0.5, 0.5, which
is provided because spip has to be given some allele frequencies if sampling
is to be carried out. Note that a user-specified value to this option should
only be given if you want to actually simulate some genetic data from the
sampled individuals. The length of the list should be the number of loci
desired, and the length of each element should be the number of alleles.
For examples for three loci with 2, 3, and 4 equifrequent alleles, respectively,
you would provide |
This creates a temporary directory and runs spip in that directory, redirecting stdout and stderr to files. It then processes the output using awk to create a collection of files. If spip throws an error, the contents of stderr are written to the screen to notify the user of how to correct their input.
For a full example of its use see the Vignette:
vignette("species_1_simulation", package = "CKMRpop")
.
Returns the path to the temporary directory were spip
was run and where the
processed output files can be found to be read in using slurp_spip()
.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.