|
22 | 22 | /**
|
23 | 23 | * <p>
|
24 | 24 | * Create a single bundle (JSON) file for one or more related inputs, for use as input to a GATK tool.
|
25 |
| - * <h2>Bundle Structure</h2> |
| 25 | + * <h3>Bundle File Structure</h3> |
26 | 26 | * A bundle is a JSON file that contains references to one or more related resources (i.e., a VCF file
|
27 | 27 | * and it's associated index file, or a .fasta reference file and it's associated index and dictionary files).
|
28 | 28 | * Bundle files can be supplied as inputs for many GATK tools. The primary advantage to using a bundle input
|
|
34 | 34 | * Each resource in a bundle has an associated content type, which is a string that identifies the type of data
|
35 | 35 | * in that resource. One resource in the bundle is always designated as the "primary" resource, which determines
|
36 | 36 | * the type of the bundle.
|
37 |
| - * |
38 |
| - * <p>An example bundle JSON file is show below. The bundle has 3 resources, with content types |
| 37 | + *<p> |
| 38 | + * An example bundle JSON file is show below. The bundle has 3 resources, with content types |
39 | 39 | * "HAPLOID_REFERENCE", "REFERENCE_DICTIONARY", and "REFERENCE_INDEX" respectively, with the "HAPLOID_REFERENCE"
|
40 | 40 | * resource designated as the primary resource. This bundle is a reference bundle, and can be used as an
|
41 | 41 | * input where ever a reference argument is required.
|
|
51 | 51 | * "primary": "HAPLOID_REFERENCE"
|
52 | 52 | * }
|
53 | 53 | * </pre>
|
54 |
| - * <h2>Using CreateBundle</h2> |
| 54 | + * <h3>Using CreateBundle</h3> |
55 | 55 | * <p>
|
56 | 56 | * CreateBundle requires at least one primary resource input. One or more optional secondary resource inputs
|
57 | 57 | * may also be supplied.
|
|
79 | 79 | * <p>
|
80 | 80 | * Bundle output file names must end with the suffix ".json".
|
81 | 81 | * <p>
|
82 |
| - * <h2>Standard Content Types</h2> |
| 82 | + * <h3>Standard Content Types</h3> |
83 | 83 | * In general, bundle content types can be any string, but many tools expect bundles to use standard, well known
|
84 | 84 | * content types that are pre-defined, such as content types for a VCF, a VCF index, a .fasta file, or a reference
|
85 | 85 | * dictionary file. The common well known content types are:
|
|
88 | 88 | * <li>"CT_VARIANT_CONTEXTS": a VCF file</li>
|
89 | 89 | * <li>"CT_VARIANTS_INDEX": a VCF index file</li>
|
90 | 90 | * </ul>
|
91 |
| - * <h4>Standard Reference Content Types</h4> |
| 91 | + * <h4>Standard Reference Content Types:</h4> |
92 | 92 | * <ul>
|
93 | 93 | * <li>"CT_HAPLOID_REFERENCE": a fasta reference file</li>
|
94 | 94 | * <li>"CT_HAPLOID_REFERENCE_INDEX": a fasta index file</li>
|
95 | 95 | * <li>"CT_HAPLOID_REFERENCE_DICTIONARY": a fasta dictionary file</li>
|
96 | 96 | * </ul><p>
|
97 |
| - * <h2>Standard Secondary Resources</h2> |
98 |
| - * <h3>For VCFS, the standard (inferred) secondary resources are:</h3> |
| 97 | + * <h3>Standard Secondary Resources</h3> |
| 98 | + * <h4>VCF standard secondary resources:</h4> |
99 | 99 | * <ul>
|
100 | 100 | * <li>an index file</li>
|
101 | 101 | * </ul>
|
102 |
| - *<h3>For references, the standard secondary resources are:</h3> |
| 102 | + *<h4> FASTA reference standard secondary resources:</h4> |
103 | 103 | * <ul>
|
104 | 104 | * <li>an index file</li>
|
105 | 105 | *<li>a dictionary file</li>
|
106 | 106 | * </ul>
|
107 |
| - * <h3>Common bundle creation examples:</h3> |
| 107 | + * <h3>Bundle Creation Examples</h3> |
108 | 108 | * </p>
|
109 |
| - * <h3>VCF Bundle Examples</h3> |
| 109 | + * <h4>VCF Bundle Examples</h4> |
110 | 110 | * <p>
|
111 | 111 | * 1) Create a resource bundle for a VCF from just the VCF, letting the tool resolve the secondary (index) resource by
|
112 | 112 | * automatically finding the sibling index file, and letting the tool determine the content types. If the sibling index
|
|
150 | 150 | * --secondary:CT_VARIANTS_INDEX some/other/path/to/vcd.idx \
|
151 | 151 | * --output mybundle.json
|
152 | 152 | * </pre><p>
|
153 |
| - *<h3>Reference Bundle Examples</h3> |
| 153 | + *<h4>Reference Bundle Examples</h4> |
154 | 154 | *<p>
|
155 | 155 | * 1) Create a resource bundle for a reference from just the .fasta, letting the tool resolve the secondary
|
156 | 156 | * (index and dictionary) resource by automatically finding the sibling files, and determining the content types.
|
|
179 | 179 | * --secondary:CT_HAPLOID_REFERENCE_INDEX some/other/path/to/my.fai \
|
180 | 180 | * --secondary:CT_HAPLOID_REFERENCE_DICTIONARY some/other/path/to/my.dict \
|
181 | 181 | * --output mybundle.json
|
182 |
| - * </pre><p> |
| 182 | + * </pre> |
183 | 183 | * 4) Create a resource bundle for a fasta, but specify the fasta, index and dictionary resources and the content
|
184 | 184 | * types explicitly. The resulting bundle will contain the fasta, index and dictionary resources:
|
185 | 185 | * <pre>
|
|
188 | 188 | * --secondary:CT_HAPLOID_REFERENCE_INDEX some/other/path/to/my.fai \
|
189 | 189 | * --secondary:CT_HAPLOID_REFERENCE_DICTIONARY some/other/path/to/my.dict \
|
190 | 190 | * --output mybundle.json
|
191 |
| - * </pre><p> |
| 191 | + * </pre> |
192 | 192 | */
|
193 | 193 | @DocumentedFeature
|
194 | 194 | @CommandLineProgramProperties(
|
|
0 commit comments