dazzdb 1.0+git20220426.8a55f0e-1 source package in Ubuntu

Changelog

dazzdb (1.0+git20220426.8a55f0e-1) unstable; urgency=medium

  * Team upload.
  * New upstream version
  * Standards-Version: 4.6.1 (routine-update)
  * Refresh append-cflags.patch.
  * Refresh compiler-flags.patch.
  * Remove cross.patch: not relevant with last refresh of compiler-flags.patch.

 -- Étienne Mollier <email address hidden>  Wed, 08 Jun 2022 23:11:40 +0200

Upload details

Uploaded by:
Debian Med
Uploaded to:
Sid
Original maintainer:
Debian Med
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
dazzdb_1.0+git20220426.8a55f0e-1.dsc 2.2 KiB 27e3e3684bc3fc27741fab12aec39b3a3245da46946a97f0a8c89b919c1fba99
dazzdb_1.0+git20220426.8a55f0e.orig.tar.xz 68.7 KiB 5d953e64041fd8d40d8cb91fedb8f55091acd30229956c60aa4a70ab6eb71d50
dazzdb_1.0+git20220426.8a55f0e-1.debian.tar.xz 6.5 KiB 6ed52efb2138483424b0659a6e2cc45c1dc14ab14b1efe07733e4aeaf4a65de2

No changes file available.

Binary packages built by this source

dazzdb: manage nucleotide sequencing read data

 To facilitate the multiple phases of the dazzler assembler, all the read data
 is organized into what is effectively a database of the
 reads and their meta-information. The design goals for this data base
 are as follows:
  * The database stores the source Pacbio read information in such a
    way that it can re-create the original input data, thus permitting
    a user to remove the (effectively redundant) source files. This
    avoids duplicating the same data, once in the source file and once
    in the database.
  * The data base can be built up incrementally, that is new sequence
    data can be added to the data base over time.
  * The data base flexibly allows one to store any meta-data desired for
    reads. This is accomplished with the concept of *tracks* that
    implementors can add as they need them.
  * The data is held in a compressed form equivalent to the .dexta and
    .dexqv files of the data extraction module. Both the .fasta and
    .quiva information for each read is held in the data base and can be
    recreated from it. The .quiva information can be added separately and
    later on if desired.
  * To facilitate job parallel, cluster operation of the phases of the
    assembler, the database has a concept of a *current partitioning* in
    which all the reads that are over a given length and optionally
    unique to a well, are divided up into *blocks* containing roughly a
    given number of bases, except possibly the last block which may have
    a short count. Often programs can be run on blocks or pairs of blocks
    and each such job is reasonably well balanced as the blocks are all
    the same size. One must be careful about changing the partition
    during an assembly as doing so can void the structural validity of
    any interim block-based results.

dazzdb-dbgsym: debug symbols for dazzdb