Sanger Sequence Analysis
Semi-automated Sanger sequence analysis for plasmid verification.
This package is the result of an internal hackathon at the Novo Nordisk Foundation Center for Biosustainability and represents our approach to improving the workflow of geneticists who need to verify plasmid constructs by Sanger sequencing.
Getting Started
From a Python environment that has Python 3.6 or later installed you can easily
$ pip install sanger-sequencing
or use pip3 depending on your environment.
When you import the package, two main components are made available to you: a configuration class that you can instantiate to set some global configuration values and a high level analysis interface.
import sanger_sequencing
config = sanger_sequencing.Configuration()
print(config.threshold)
print(config.output)
You can read more about the meaning of those attributes in the configuration documentation. The main entry point for doing any kind of analysis is the sanger_verification function. This function requires three arguments: a template table of what to analyze, a mapping from plasmid identifiers to their sequence records (typically coming from Genbank files), and a mapping from sample identifiers to sequence records (.ab1 files).
You can find the complete documentation at: https://sanger-sequencing.readthedocs.io.
Copyright
Copyright (c) 2018 Novo Nordisk Foundation Center for Biosustainability, Technical University Denmark licensed under the Apache License, Version 2.0
Credits
This package was created using cookiecutter and the DD-DeCaF/cookiecutter-decaf-python project template.
Metadata
Release files for sanger-sequencing 0.1.1
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 |
|---|---|---|---|---|
| sanger-sequencing-0.1.1.tar.gz | 34.3 kB | Without provenance | Details for sanger-sequencing-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sanger_sequencing-0.1.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for sanger_sequencing-0.1.1-py2.py3-none-any.whl |
Total release size: 61.1 kB
Release files / sanger-sequencing-0.1.1.tar.gz
| Download URL | sanger-sequencing-0.1.1.tar.gz |
|---|---|
| Size | 34.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
196d43774fa1a717e2dc50610bf50f388b98af573e6197fde2e20bc3d911a87e
|
|
BLAKE2b-256 checksum How to use checksums |
168f5da948deb808ff0a867adc4f71e8db59ad2ea0934a77a00dedcda1693658
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.1.0 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/3.6.3
|
Release files / sanger_sequencing-0.1.1-py2.py3-none-any.whl
| Download URL | sanger_sequencing-0.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 26.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7bffa82e18f7e7437134df571a87816652e73bf6dbd9b855e2d392e8a2b9051a
|
|
BLAKE2b-256 checksum How to use checksums |
760d0f4a19c09a9ab2cb762db27d122085ef5c315d3b9972f38c7a2200ae3db6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.1.0 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/3.6.3
|
Security for sanger-sequencing 0.1.1
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.