Some help can be obtained with virmet <subcommand> -h or simply virmet -h:
virmet -h
usage: virmet <command> [options]
positional arguments:
{fetch,update,index,wolfpack,covplot}
available sub-commands
fetch download databases
update update viral database
index index genomes
wolfpack analyze a Miseq run
covplot create coverage plot
options:
-h, --help show this help message and exit
-v, --version show program's version number and exit
Run virmet subcommand -h for more help.
Installation
Bioconda
VirMet is available through Bioconda, a channel
for the conda package manager. Once
conda is installed and the
channels are set up,
conda install virmet installs the package with all its dependencies.
Preparation
VirMet contains programs to download and index the genome sequences,
instructions here.
Running a virus scan
Once the fetch and index subcommands have ben run and the databases are downloaded and indexed, users can
use Wolfpack, the main subcommand of VirMet.
A very simple way to use Wolfpack is the following:
virmet wolfpack --run path_to_run_directory
With that, sequencing reads are filtered (quality-control), decontaminated, and finally blasted against a (large)
set of viral sequences.
Virmet Wolfpack provides several outputs that can be found in the
output folder virmet_output_RUN_NAME, located at the current working directory.
For example, if users have a directory named Exp01 with files:
and run virmet wolfpack --run Exp01, their results will
appear into virmet_output_Exp01.
The most important output files are:
Orgs_species_found.csv: table showing the viral organisms identified per
FASTQ file as well as the read counts matching each organism.
It looks as follows:
species: scientific name of the species corresponding to the database sequence. accn: accession number of the viral species corresponding to the database sequence. reads: number of reads assigned to this specific sequence. stitle: title of the sequence in the database (fasta header). ssciname: scientific name of the sequence. covered_region: number of nucleotides covered by at least one read. seq_len: length of the sequence. sample: name of the FASTQ file that lead to the results. run: name of the sequencing run or main folder.
Run_reads_summary.tsv: summary of all reads analyzed per sample, showing the
number of reads passing each step of the pipeline (e.g., QC, decontamination),
and the number of reads matching the human, bovine, bacterial, fungal and
viral database.
It looks as follows:
In addition to these main outputs, Wolfpack creates inside
virmet_output_RUN_NAME a subdirectory for each sample (FASTQ file).
There, users can find these additional files:
Unique.tsv.gz
Viral_reads.fastq.gz
Undetermined_reads.fastq.gz
Orgs_list.tsv
Stats.tsv
Fastp.html
Folders named as viral organisms
Other.err
Files orgs_list.tsv and stats.tsv report the main output of the tool for
each sample. They are the same as Orgs_species_found.csv and Run_reads_summary.tsv,
respectively, but containing information only of one sample. Therefore, the
last two columns (sample and run) are missing.
The unique.tsv.gz reports all BLAST hits to the viral database. These are
not the same as in orgs_list.tsv because VirMet further filters the
BLAST hits (unique.tsv.gz) to ensure that only those with ≥75% pident and
≥75% qcov are ultimately considered viral reads for diagnosis.
As the names say, viral_reads.fastq.gz and undetermined_reads.fastq.gz
contain, respectively, reads identified as of viral origin and reads not
matching any of the considered genomes.
Finally, fastp.html shows the quality-control statistics and information
about the QC-filtering step.
In the decontamination step, reads are aligned against the human genome first,
those matching are discarded while those not matching are aligned against
the bovine genome, and so on. In each step, some files ending with .err
are generated, and they can be used for inspection, if needed. However, they
do not provide valuable information for the users (unless there is any error)
and can be removed if desired.
Besides all these files, Wolfpack automatically creates (unless disabled with
--nocovplot) a few folders with the names of viral organisms. Such folders
contain the coverage plots of the viral assignments, named Viral_organism_coverage.pdf.
It is recommended to manually have a look at them before a final viral diagnosis.
Overall, users can expect the following structure for the outputs:
VirMet
VirMet is a software designed to help users running viral metagenomics (mNGS) experiments.
For full Documentation, please Read the Docs.
VirMet is called with a command-subcommand syntax. All the possible subcommands are:
fetch: download all databasesupdate: update viral databaseindex: index all genomeswolfpack: analyze a Miseq run or filecovplot: plot coverage for a specific organismSome help can be obtained with
virmet <subcommand> -hor simplyvirmet -h:Run
virmet subcommand -hfor more help.Installation
Bioconda
VirMet is available through Bioconda, a channel for the conda package manager. Once conda is installed and the channels are set up,
conda install virmetinstalls the package with all its dependencies.Preparation
VirMet contains programs to download and index the genome sequences, instructions here.
Running a virus scan
Once the
fetchandindexsubcommands have ben run and the databases are downloaded and indexed, users can useWolfpack, the main subcommand of VirMet.A very simple way to use Wolfpack is the following:
virmet wolfpack --run path_to_run_directoryWith that, sequencing reads are filtered (quality-control), decontaminated, and finally blasted against a (large) set of viral sequences.
Virmet Wolfpack provides several outputs that can be found in the output folder
virmet_output_RUN_NAME, located at the current working directory.For example, if users have a directory named
Exp01with files:and run
virmet wolfpack --run Exp01, their results will appear intovirmet_output_Exp01.The most important output files are:
with each column meaning:
species: scientific name of the species corresponding to the database sequence.accn: accession number of the viral species corresponding to the database sequence.reads: number of reads assigned to this specific sequence.stitle: title of the sequence in the database (fasta header).ssciname: scientific name of the sequence.covered_region: number of nucleotides covered by at least one read.seq_len: length of the sequence.sample: name of the FASTQ file that lead to the results.run: name of the sequencing run or main folder.In addition to these main outputs, Wolfpack creates inside
virmet_output_RUN_NAMEa subdirectory for each sample (FASTQ file). There, users can find these additional files:Files
orgs_list.tsvandstats.tsvreport the main output of the tool for each sample. They are the same asOrgs_species_found.csvandRun_reads_summary.tsv, respectively, but containing information only of one sample. Therefore, the last two columns (sample and run) are missing.The
unique.tsv.gzreports all BLAST hits to the viral database. These are not the same as inorgs_list.tsvbecause VirMet further filters the BLAST hits (unique.tsv.gz) to ensure that only those with ≥75% pident and ≥75% qcov are ultimately considered viral reads for diagnosis.As the names say,
viral_reads.fastq.gzandundetermined_reads.fastq.gzcontain, respectively, reads identified as of viral origin and reads not matching any of the considered genomes.Finally,
fastp.htmlshows the quality-control statistics and information about the QC-filtering step.In the decontamination step, reads are aligned against the human genome first, those matching are discarded while those not matching are aligned against the bovine genome, and so on. In each step, some files ending with .err are generated, and they can be used for inspection, if needed. However, they do not provide valuable information for the users (unless there is any error) and can be removed if desired.
Besides all these files, Wolfpack automatically creates (unless disabled with
--nocovplot) a few folders with the names of viral organisms. Such folders contain the coverage plots of the viral assignments, namedViral_organism_coverage.pdf. It is recommended to manually have a look at them before a final viral diagnosis.Overall, users can expect the following structure for the outputs:
Please, see VirMet Documentation for a more extensive explanation on how to use
fetch,index,wolfpackandcovplotsubcommands.