AMIMSpy
Python package for processing acoustic mist ionization mass spectrometry-based metabolomics and lipidomics data
Documentation: https://amimspy.readthedocs.io/en/latest
Source: https://github.com/computational-metabolomics/amimspy
Bug reports: https://github.com/computational-metabolomics/amimspy/issues
Installation
See the Installation page of the online documentation.
Bug reports
Please report any bugs that you find here. Or fork the repository on GitHub and create a pull request (PR). We welcome all contributions, and we will help you to make the PR if you are new to git.
Credits
- Developers and contributers
Matthew Smith (mjs708@student.bham.ac.uk) - University of Birmingham (UK)
Ralf J. M. Weber (r.j.weber@bham.ac.uk) - University of Birmingham (UK)
- AMIMSpy acknowledges support from the following funders:
BBSRC and Waters Corporation for an iCASE PhD studentship.
License
AMIMSpy is licensed under the GNU General Public License v3.0 (see LICENSE file for licensing information). Copyright © 2020 Matthew Smith, Ralf Weber
Metadata
Release files for amimspy 0.1.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 |
|---|---|---|---|---|
| amimspy-0.1.0.tar.gz | 6.6 MB | Without provenance | Details for amimspy-0.1.0.tar.gz |
Release files / amimspy-0.1.0.tar.gz
| Download URL | amimspy-0.1.0.tar.gz |
|---|---|
| Size | 6.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73a64c643d8262517e3648439740c24d3a96f64c9ed4b75417561efe64ab8536
|
|
BLAKE2b-256 checksum How to use checksums |
b64ead0a61dace14a9e16e6501c4637fc1e230da89051ee8b8307dcb5e8e9d0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.8
|
Security for amimspy 0.1.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.