rapmap 0.4.0+dfsg-2 source package in Ubuntu

Changelog

rapmap (0.4.0+dfsg-2) unstable; urgency=medium

  * Set NO_NATIVE_ARCH=true
    Closes: #847084
  * Do not try downloading libjemalloc
    Closes: #847083
  * debhelper 10
  * d/watch: version=4
  * hardening=+all

 -- Andreas Tille <email address hidden>  Mon, 05 Dec 2016 16:32:20 +0100

Upload details

Uploaded by:
Debian Med on 2016-12-05
Uploaded to:
Sid
Original maintainer:
Debian Med
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Bionic release on 2017-10-24 universe misc
Artful release on 2017-04-20 universe misc
Zesty release on 2016-12-06 universe misc

Downloads

File Size SHA-256 Checksum
rapmap_0.4.0+dfsg-2.dsc 2.0 KiB b5002f9914faae198e92a3b3212d2fbb40c20beb6a02878cfb726aab66af4671
rapmap_0.4.0+dfsg.orig.tar.xz 199.5 KiB 09ad5c892d1be2c683bb143e03eac977e5c3448cb10bf883e7c8f514fb981267
rapmap_0.4.0+dfsg-2.debian.tar.xz 7.4 KiB 6141378e5f86b22e3b8e3c85d98ed37fc2ccec94f74d7b201d961a98efab0ff8

Available diffs

No changes file available.

Binary packages built by this source

rapmap: rapid sensitive and accurate DNA read mapping via quasi-mapping

 RapMap is a testing ground for ideas in quasi-mapping / (lightweight /
 pseudo) transcriptome alignment. That means that, at this point, it is
 somewhat experimental. The develop branch will have the latest
 improvements and additions, but is not guaranteed to be stable between
 commits. Breaking changes to the master branch will be accompanied by a
 tag to the version before the breaking change. Currently, RapMap is a
 stand-alone quasi-mapper that can be used with other tools. It is also
 being used as part of Sailfish and Salmon. Eventually, the hope is to
 create and stabilize an API so that it can be used as a library from
 other tools.
 .
 Quasi-mapping / (lightweight / pseudo)-alignment is the term that is
 used here for the type of information required for certain tasks (e.g.
 transcript quantification) that is less "heavyweight" than what is
 provided by traditional alignment. For example, one may only need to
 know the transcripts / contigs to which a read aligns and, perhaps, the
 position within those transcripts rather than the optimal alignment and
 base-for-base CIGAR string that aligns the read and substring of the
 transcript. For details on RapMap (quasi-mapping in particular), please
 check out the associated paper. Note: RapMap implements both quasi-
 mapping and pseudo-alignment (originally introduced in Bray et al.
 2016), these two are not the same thing. They are distinct concepts, and
 RapMap simply happens to implement algorithms for computing both.

rapmap-dbgsym: debug symbols for package rapmap

 RapMap is a testing ground for ideas in quasi-mapping / (lightweight /
 pseudo) transcriptome alignment. That means that, at this point, it is
 somewhat experimental. The develop branch will have the latest
 improvements and additions, but is not guaranteed to be stable between
 commits. Breaking changes to the master branch will be accompanied by a
 tag to the version before the breaking change. Currently, RapMap is a
 stand-alone quasi-mapper that can be used with other tools. It is also
 being used as part of Sailfish and Salmon. Eventually, the hope is to
 create and stabilize an API so that it can be used as a library from
 other tools.
 .
 Quasi-mapping / (lightweight / pseudo)-alignment is the term that is
 used here for the type of information required for certain tasks (e.g.
 transcript quantification) that is less "heavyweight" than what is
 provided by traditional alignment. For example, one may only need to
 know the transcripts / contigs to which a read aligns and, perhaps, the
 position within those transcripts rather than the optimal alignment and
 base-for-base CIGAR string that aligns the read and substring of the
 transcript. For details on RapMap (quasi-mapping in particular), please
 check out the associated paper. Note: RapMap implements both quasi-
 mapping and pseudo-alignment (originally introduced in Bray et al.
 2016), these two are not the same thing. They are distinct concepts, and
 RapMap simply happens to implement algorithms for computing both.