DNAda
DNAda is a web application that integrates the j5 DNA assembly software with robotic liquid handlers.
Background
J5 is a powerful DNA assembly software that can be used to design and optimize DNA assembly protocols. However, it is not directly compatible with robotic liquid handlers. DNAda is a web/command-line application that integrates j5 with robotic liquid handlers by converting a j5 assembly design into a series of liquid handler compatible instructions. This enables a user without progamming experience to design DNA assembly protocols on a user-friendly canvas, DeviceEditor, and then convert the design using J5 and subsequently DNAda into a series of instructions that can be executed on a liquid handler.
CLI Installation
Note, it is highly recommended to use a virtual environment to install the dependencies.
For example,
wget "https://github.com/conda-forge/miniforge/releases/latest/download/Mambaforge-$(uname)-$(uname -m).sh"
bash Mambaforge-$(uname)-$(uname -m).sh
source ~/mambaforge/bin/activate
mamba create -y -n dnada
conda activate dnada
mamba install -y python==3.11
pip install dnada
Alternatively, setup from the source code by running
git clone https://github.com/JBEI/dnada.git
cd dnada/backend/app
python setup.py install
Note, there is currently a bug in autoprotocol-python. To temporarily resolve this bug until it gets patched, identify the location of the autoprotocol library identified in your virtual environment and apply the fix-oligosynthesizeolig-serialization.patch file. For example,
cd ~/mambaforge/envs/dnada/lib/python3.11/site-packages/
patch -p1 < ~/dnada/backend/app/fix-oligosynthesizeoligo-serialization.patch
Quick Start
There is a sample J5 design file available in the examples/ directory in the github repo.
After installing the DNAda CLI through pip or github, to run DNAda on that design file,
execute:
cd dnada/examples
dnada_cli example_j5_output.zip
After a few seconds you should see a new .zip archive generated with the
name automation_instructions.zip.
Metadata
Release files for dnada 0.1.2
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 |
|---|---|---|---|---|
| dnada-0.1.2.tar.gz | 133.2 kB | Without provenance | Details for dnada-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dnada-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for dnada-0.1.2-py3-none-any.whl |
Total release size: 335.6 kB
Release files / dnada-0.1.2.tar.gz
| Download URL | dnada-0.1.2.tar.gz |
|---|---|
| Size | 133.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c13732fe9f51a656f60a7a2a37e715ed9f2d96685bf5477806294a90d743387
|
|
BLAKE2b-256 checksum How to use checksums |
ee8fea8596a9a8ab848a8565e2caee232a7677bf9c64b79925e0a2b4236aa7a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / dnada-0.1.2-py3-none-any.whl
| Download URL | dnada-0.1.2-py3-none-any.whl |
|---|---|
| Size | 202.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
68e317b51d1788ccc9e1ad45da8fa21ce247cd8e65314be2bca6fa0ace7b6ed8
|
|
BLAKE2b-256 checksum How to use checksums |
d7059224728b6885ee2507cec55680ee111e1d52a7d7aeff32a4a0916bee8b03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for dnada 0.1.2
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.