The applications listed here are available for use in the Discovery Environment and are documented in: Discovery Environment Manual.

Discovery Environment Applications List

The box below searches only this space.
To search the entire iPlant wiki, enter your query in the box at the upper right.

Maintenance: Tues, 28 Jan 2020


Discovery Environment         8:00am to 5:00pm MST
The Discovery Environment will be unavailable while patches and updates are applied.
        ** Currently running analyses will be terminated. Please plan accordingly.

Data Store                    8:00am to 5:00pm MST
The Data Store will be unavailable during the maintenance period.
Data Commons                  8:00am to 5:00pm MST
The Data Commons will be unavailable during the maintenance period.
Atmosphere and Cloud Services 8:00am to 5:00pm MST
Marana Cloud: Atmosphere instances in the Marana Cloud will be operational; however, you will not be able to use the Data Store within your instance, and you may not be able to access the Atmosphere web interface.
User Portal                   8:00am to 5:00pm MST
The User Portal,, will be unavailable while we perform maintenance and updates.
Agave/Science API             8:00am to 5:00pm MST
The Agave/Science API will be unavailable during this maintenance period.
DNA Subway                    8:00am to 5:00pm MST
DNA Subway will be unavailable during this maintenance period.
The following services will NOT be affected by the maintenance: CyVerse Wiki and JIRA

Keep up to date with our maintenance schedules on the CyVerse public calendar
Check your local timezone here 
Please contact for any questions, or concerns.






Skip to end of metadata
Go to start of metadata

The QuickStart tutorial provides an introduction to basic DE functionality and navigation.

Please work through the tutorial and use the intercom button on the bottom right of this page if you have any questions.

Rationale and background: 

VIBRANT is a tool for automated recovery and annotation of bacterial and archaeal viruses, determination of genome completeness, and characterization of virome function from metagenomic assemblies. VIBRANT uses neural networks of protein annotation signatures and genomic features to maximize the identification of highly diverse partial or complete viral genomes as well as excise integrated proviruses.

  • Uses neural network machine learning of protein annotation signatures
  • Assigns novel 'v-score' for determining the virus-like nature of all annotations
  • Determines genome completeness
  • Characterizes virome function by metabolic analysis
  • Identifies auxiliary metabolic genes (AMGs)
  • Excises integrated viral genomes from host scaffolds
  • Performs well in diverse environments
  • Recovers novel and abundant viral genomes
  • Built for dsDNA, ssDNA and RNA viruses

VIBRANT uses three databases for identifying viruses and characterizing virome metabolic potential:


  1. A CyVerse account. (Register for a CyVerse account here -

  2. Input

    1. Input fasta file

  3. Parameters
    1. Format of input {prot,nucl} [default="nucl"]
    2. Number of parallel VIBRANT runs, each occupies 1 CPU [default=1, max of 1 CPU per scaffold]
    3. Length in basepairs to limit input sequences. Default is 1000, can increase but not decrease

    4. Number of ORFs per scaffold to limit input sequences. Default is 4, can increase but not decrease

    5. virome. Use this setting if the dataset is known to be comprised mainly of viruses. More sensitive to viruses, less sensitive to false identifications [default=off]
    6. no_plot. suppress the generation of summary plots [default=off]

Test/sample data:

The test data are provided for testing VIBRANT-1.0.1 is in here - /iplant/home/shared/iplantcollaborative/example_data/vibrant

Use the following inputs/outputs and parameters for VIBRANT-1.0.1

  1. Input 

    1. Input fasta file: /iplant/home/shared/iplantcollaborative/example_data/vibrant/example_data/mixed_example.fasta

  2. Parameters
    1. Format of input: Nucleotide
    2. Number of parallel VIBRANT runs: 1
    3. Length in basepairs to limit input sequences: 1000

    4. Number of ORFs per scaffold to limit input sequences: 4

Leave the rest of the two as defaults

Output Reports:

After successful completion of the run, expect the following files as output:

  1. VIBRANT_log_mixed_example.log

  2. mixed_example.faa

  3. mixed_example.ffn

  4. mixed_example.gff

  5. VIBRANT_HMM_tables_parsed_mixed_example

  6. VIBRANT_HMM_tables_unformatted_mixed_example

  7. VIBRANT_figures_mixed_example

  8. VIBRANT_phages_mixed_example

  9. VIBRANT_results_mixed_example

For more detailed information about these outputs, please refer to this link -







  • No labels