pinda
Pip-INstallable Dockerized Applications
pinda is designed to deliver dockerized versions of software packages that have a user interface that is as identical as possible to what would be available if the package was installed in the conventional way.
For example, to install Gromacs version 2018:
% pinda install gromacs 2018
Once the installation is complete, you will find the 'gmx' command in your path.
Installation:
Easiest via pip:
% pip install pinda
Usage:
To see a list of packages available via pinda:
% pinda list
amber 16 Amber and AmberTools version 16
amber 18 Amber and AmberTools version 18
ambertools 16 AmberTools version 16
ambertools 18 AmberTools version 18
* gromacs 2018 Gromacs version 2018
gromacs 2018-cuda Gromacs version 2018 with CUDA support
* obabel 2.4.1 Open Babel version 2.4.1
vina 1.1.2 AutoDock Vina and selected AutoDock Tools
%
Packages that you have already installed are asterisked.
NOTE: Because of license restrictions you may find that you can't actually run certain packages (e.g. Amber) - see here for some help on this.
To install a package:
% pinda install ambertools 18
%
To uninstall a package:
% pinda uninstall obabel 2.4.1
%
Limitations:
You need to have Docker installed on your machine. The containerised versions of the applications can only 'see' files that are in the directory a command in invoked from, or a subdirectory of this, so for example:
% gmx mdrun -s bpti.tpr # This is fine
% gmx mdrun -s ../bpti.tpr # This won't work
Author:
Charlie Laughton charles.laughton@nottingham.ac.uk
License:
BSD 3-clause
Metadata
Release files for pinda 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 |
|---|---|---|---|---|
| pinda-0.1.1.tar.gz | 6.6 kB | Without provenance | Details for pinda-0.1.1.tar.gz |
Release files / pinda-0.1.1.tar.gz
| Download URL | pinda-0.1.1.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3695d0756e87793a297eb02d76e63f303b7c28d94dfb8f59020de1248a726d9
|
|
BLAKE2b-256 checksum How to use checksums |
3a08193a358a205362a21b87083d7d9d4632e9ea0130ab80bbb6e0d560ca4559
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/39.2.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.6.5
|
Security for pinda 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.