3. GS Amplicon Variant Analyzer Command Line Interface
:
3.5 Creating and Computing a Project with the AVA-CLI
: 3.5.12 Reporting
3.5.12
Reporting
After your Project has finished computing you can open it with the GUI to explore the results and alignments. As usual, the Variants Frequency Table on the main Variants Tab of the GUI can be manually exported by clicking on the “text file” button located next to it. The structure of this exported file is in the same two-dimensional geometry (Variants as the rows and Samples as the columns) as the table displayed in the GUI itself. Because of the two-dimensional structure, this format is not particularly amenable to high-throughput processing as one might want to do following a project Computation. The same information can also be generated in an automated fashion, and in a more useful linear form, using the “report variantHits” command from the CLI (see section
3.4.12.2
for the usage statement and output format). Although the GUI allows you to apply various filters to the data before exporting Sample-Variant data, the CLI currently only supports a bulk report of all the Variant statistics. You can generate the report in either tab-separated value (tsv) or comma-separated value (csv) formats. The report only includes Variants that are officially part of the Project,
i.e.
specifically defined Variants, or auto-detected Variants that were “loaded” using the “computation loadDetectedVariants” command (see section
3.5.11.3
). If you have any unloaded automatically detected Variants, they will not be included in the output unless you use the “computation loadDetectedVariants” command prior to using “report variantHits.”
With the CLI-generated report in hand you can do your own customized processing of the reported Variant frequencies. One suggestion would be to apply filter criteria on the reported data to highlight Variants with the most believable support; users can then focus on these “best candidates” and verify them by examination of the alignments in the GUI.