A catalog can be built from any set of samples processed by the ustacks or pstacks programs. It will create a set of consensus loci, merging alleles together. In the case of a genetic cross, a catalog would be constructed from the parents of the cross to create a set of all possible alleles expected in the progeny of the cross.

Program Options

cstacks -P in_path -M popmap [-n num_mismatches] [-p num_threads]
cstacks -s sample1_path [-s sample2_path ...] -o path [-n num_mismatches] [-p num_threads]

Gapped assembly options:

Advanced options:

Example Usage

  1. Here we specify the output directory to write the catalog, and then each sample we want to add to the catalog (one -s option for each sample). Here we are allowing up to four, fixed nucleotide differences between loci that we are trying to incorporate into the catalog and we are using 15 threads to speed up the sequence-matching process between loci:

    % cstacks -o ./stacks -s ./stacks/f0_male -s ./stacks/f0_female -n 4 -p 15

  2. Here we specify the directory containing all our Stacks output files from ustacks, and then provide a population map, which contains all of the individual samples we want to add to the catalog within it (see the manual for information on population maps):

    % cstacks -P ./stacks -M ./popmap -n 4 -p 15

  3. In this example, we start with a pre-existing catalog to which we want to add additional samples, and we want to allow/incorporate gaps between the sample and catalog loci:

    % cstacks -b 1 -o ./stacks --catalog ./stacks/catalog -s ./stacks/sample_37 -s ./stacks/sample_38 -s ./stacks/sample_39 -n 4 -p 12

Other Pipeline Programs

Raw reads


Execution control

Utility programs