Skip to content

Commit ebe0fc1

Browse files
committed
FIx up javadoc.
1 parent 0071d9f commit ebe0fc1

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

src/main/java/org/broadinstitute/hellbender/tools/CreateBundle.java

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@
2222
/**
2323
* <p>
2424
* 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>
2626
* A bundle is a JSON file that contains references to one or more related resources (i.e., a VCF file
2727
* and it's associated index file, or a .fasta reference file and it's associated index and dictionary files).
2828
* Bundle files can be supplied as inputs for many GATK tools. The primary advantage to using a bundle input
@@ -34,8 +34,8 @@
3434
* Each resource in a bundle has an associated content type, which is a string that identifies the type of data
3535
* in that resource. One resource in the bundle is always designated as the "primary" resource, which determines
3636
* 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
3939
* "HAPLOID_REFERENCE", "REFERENCE_DICTIONARY", and "REFERENCE_INDEX" respectively, with the "HAPLOID_REFERENCE"
4040
* resource designated as the primary resource. This bundle is a reference bundle, and can be used as an
4141
* input where ever a reference argument is required.
@@ -51,7 +51,7 @@
5151
* "primary": "HAPLOID_REFERENCE"
5252
* }
5353
* </pre>
54-
* <h2>Using CreateBundle</h2>
54+
* <h3>Using CreateBundle</h3>
5555
* <p>
5656
* CreateBundle requires at least one primary resource input. One or more optional secondary resource inputs
5757
* may also be supplied.
@@ -79,7 +79,7 @@
7979
* <p>
8080
* Bundle output file names must end with the suffix ".json".
8181
* <p>
82-
* <h2>Standard Content Types</h2>
82+
* <h3>Standard Content Types</h3>
8383
* In general, bundle content types can be any string, but many tools expect bundles to use standard, well known
8484
* content types that are pre-defined, such as content types for a VCF, a VCF index, a .fasta file, or a reference
8585
* dictionary file. The common well known content types are:
@@ -88,25 +88,25 @@
8888
* <li>"CT_VARIANT_CONTEXTS": a VCF file</li>
8989
* <li>"CT_VARIANTS_INDEX": a VCF index file</li>
9090
* </ul>
91-
* <h4>Standard Reference Content Types</h4>
91+
* <h4>Standard Reference Content Types:</h4>
9292
* <ul>
9393
* <li>"CT_HAPLOID_REFERENCE": a fasta reference file</li>
9494
* <li>"CT_HAPLOID_REFERENCE_INDEX": a fasta index file</li>
9595
* <li>"CT_HAPLOID_REFERENCE_DICTIONARY": a fasta dictionary file</li>
9696
* </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>
9999
* <ul>
100100
* <li>an index file</li>
101101
* </ul>
102-
*<h3>For references, the standard secondary resources are:</h3>
102+
*<h4> FASTA reference standard secondary resources:</h4>
103103
* <ul>
104104
* <li>an index file</li>
105105
*<li>a dictionary file</li>
106106
* </ul>
107-
* <h3>Common bundle creation examples:</h3>
107+
* <h3>Bundle Creation Examples</h3>
108108
* </p>
109-
* <h3>VCF Bundle Examples</h3>
109+
* <h4>VCF Bundle Examples</h4>
110110
* <p>
111111
* 1) Create a resource bundle for a VCF from just the VCF, letting the tool resolve the secondary (index) resource by
112112
* automatically finding the sibling index file, and letting the tool determine the content types. If the sibling index
@@ -150,7 +150,7 @@
150150
* --secondary:CT_VARIANTS_INDEX some/other/path/to/vcd.idx \
151151
* --output mybundle.json
152152
* </pre><p>
153-
*<h3>Reference Bundle Examples</h3>
153+
*<h4>Reference Bundle Examples</h4>
154154
*<p>
155155
* 1) Create a resource bundle for a reference from just the .fasta, letting the tool resolve the secondary
156156
* (index and dictionary) resource by automatically finding the sibling files, and determining the content types.
@@ -179,7 +179,7 @@
179179
* --secondary:CT_HAPLOID_REFERENCE_INDEX some/other/path/to/my.fai \
180180
* --secondary:CT_HAPLOID_REFERENCE_DICTIONARY some/other/path/to/my.dict \
181181
* --output mybundle.json
182-
* </pre><p>
182+
* </pre>
183183
* 4) Create a resource bundle for a fasta, but specify the fasta, index and dictionary resources and the content
184184
* types explicitly. The resulting bundle will contain the fasta, index and dictionary resources:
185185
* <pre>
@@ -188,7 +188,7 @@
188188
* --secondary:CT_HAPLOID_REFERENCE_INDEX some/other/path/to/my.fai \
189189
* --secondary:CT_HAPLOID_REFERENCE_DICTIONARY some/other/path/to/my.dict \
190190
* --output mybundle.json
191-
* </pre><p>
191+
* </pre>
192192
*/
193193
@DocumentedFeature
194194
@CommandLineProgramProperties(

0 commit comments

Comments
 (0)