[](https://travis-ci.org/eclarke/swga)
[](https://coveralls.io/github/eclarke/swga)
## Introduction
This is an easy-to-use, start-to-end package for finding sets of primers that selectively amplify a particular genome (the "foreground" genome) over a background genome. For instance, we can design a set of primers that amplify a parasite's genome in a sample that is overwhelmingly composed of host DNA.
You can run SWGA on hardware ranging from a Mac laptop to a high-end server.
## Features:
- Counts all the possible primers in a size range in both genomes
- Filters primers based on:
- foreground and background genome binding rates
- melting temperatures (with a built-in melt temp calculator that accounts for mono- and divalent cation solutions!)
- Possible homodimerization
- Finds primer sets containing primers that are compatible with each other using graph theory (largest clique formation). The process ensures:
- No primer in a set is a heterodimer
- Even binding site spacing in foreground genome
- Low total binding to background genome
- Score each set based on certain binding metrics and allows exploration of high-scoring sets via output to common formats.
## Installation
Follow the installation instructions [here](https://github.com/eclarke/swga/wiki/Installation)
## Using SWGA
Follow the guide on our Wiki/[Quick Start](https://github.com/eclarke/swga/wiki/Quick-Start) to get started!
## Updates
New features and bugfixes are released all the time. To update, simply follow steps 3-5 on the [installation instructions](https://github.com/eclarke/swga/wiki/Installation).
## 3rd-party code
SWGA incorporates code from other open-source projects:
- `cliquer`, a clique-finding library by Sampo Niskanen and Patric Ostergard
- http://users.aalto.fi/~pat/cliquer.html
- `DSK`, a disk-based kmer-counting tool by G. Rizk
- http://minia.genouest.org/dsk/
- Citation: (Rizk, G., Lavenier, D. and Chikhi, R. DSK: k-mer counting with very low memory usage, Bioinformatics, 2013.)
Cliquer is copyright © 2002 Sampo Niskanen, Patric Östergård. and licensed under the GPL.
DSK is licensed under the CeCILL license, which can be found in src/dsk/LICENSE, and is GPL compatible.
Metadata
Release files for swga 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| swga-0.4.0.tar.gz | 28.7 kB | Without provenance | Details for swga-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| swga-0.4.0-py2-none-any.whl | Python 2 | none | any | Details for swga-0.4.0-py2-none-any.whl |
Total release size: 218.6 kB
Release files / swga-0.4.0.tar.gz
| Download URL | swga-0.4.0.tar.gz |
|---|---|
| Size | 28.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80d7ea746cebb3037980858342eb4d3635b4baf64cdeef58ef4ac7de847d8192
|
|
BLAKE2b-256 checksum How to use checksums |
eca25f594f6d0ee78220650e8514c3b82a50e4e4a02eebf859dc4c3a2510f956
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / swga-0.4.0-py2-none-any.whl
| Download URL | swga-0.4.0-py2-none-any.whl |
|---|---|
| Size | 189.9 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
661a9f61063e323c67e4bee79ee37566a2768607bc19432e62d9a97569ae7d47
|
|
BLAKE2b-256 checksum How to use checksums |
c385dd0928f98600f66cd7e00dc697c54be956afd45a35c26d78bcf98da9543b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for swga 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.