Package: kaptive-example
Source: kaptive
Version: 2.0.8-1build1
Architecture: all
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
Installed-Size: 6328
Enhances: kaptive
Section: science
Priority: optional
Multi-Arch: foreign
Homepage: https://github.com/katholt/Kaptive
Description: example data for kaptive for Klebsiella genome assemblies
 Kaptive reports information about K and O types for Klebsiella genome
 assemblies.
 .
 Given a novel genome and a database of known loci (K or O), Kaptive will
 help a user to decide whether their sample has a known or novel locus.
 It carries out the following for each input assembly:
 .
  * BLAST for all known locus nucleotide sequences (using blastn) to
    identify the best match ('best' defined as having the highest
    coverage).
  * Extract the region(s) of the assembly which correspond to the BLAST
    hits (i.e. the locus sequence in the assembly) and save it to a
    FASTA file.
  * BLAST for all known locus genes (using tblastn) to identify which
    expected genes (genes in the best matching locus) are present/missing
    and whether any unexpected genes (genes from other loci) are present.
  * Output a summary to a table file.
 .
 In cases where your input assembly closely matches a known locus,
 Kaptive should make that obvious. When your assembly has a novel type,
 that too should be clear. However, Kaptive cannot reliably extract or
 annotate locus sequences for totally novel types - if it indicates a
 novel locus is present then extracting and annotating the sequence is up
 to you! Very poor assemblies can confound the results, so be sure to
 closely examine any case where the locus sequence in your assembly is
 broken into multiple pieces.
 .
 This package contains some example data.
