1 file was added to this release more than 14 days after its initial publication. Inspect the release files before installing.
Calibration
This is a simple tool that constructs a calibration curve using known x and y values from standards, and backout the x value for an unknown based on its measured y signal.
Features
Given x and y, creates calibration curve and finds linear portion and limits of linearity
Given y of an unknown, interpolates to find x
Computes interpolation error
Development
Development requires Docker and Make on your host system. Everything else is taken care of inside the Docker container.
Spin up your container using the provided docker-compose.yml file and Makefile by running make image. This creates an image with a correct git configuration for your user, which makes it easy to release. All of the commands you should need to run are defined the Makefile as targets. All of the targets except for image, are meant to be run inside the Docker container, but can be run from the host machine by having -ext appended to them. For example, to run tests, you could either call make test from a shell inside the container, or make test-ext from the host.
Dependencies are managed through the conda tool and defined in environment.yml. All new dependencies must be specified with a version, for a reproducible build environment.
All pull requests are run through the Travis CI process specified in .travis.yml and must pass all tests before being accepted.
Deployment
Deployment of tagged commits happens to PyPI automatically via Travis CI. To bump and deploy a new version directly, you must have access to write to the master branch. Run make bump/[foo]-ext, where [foo] is major, minor, or patch. Then git push origin --tags master. If you do not have access to the master branch, do the same thing, but in a separate branch, and make a pull request.
Release files for calibrate 0.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release files before installing.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| calibrate-0.10.0.tar.gz | 6.0 kB | Without provenance | Details for calibrate-0.10.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| calibrate-0.10.0-py2-none-any.whl | Python 2 | none | any | Details for calibrate-0.10.0-py2-none-any.whl |
Total release size: 13.5 kB
Release files / calibrate-0.10.0.tar.gz
| Download URL | calibrate-0.10.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5a637ce77e285b9a47d5de79d6bb9b1dce0df1e60eb27cdf1eda1e89c32c8e1
|
|
BLAKE2b-256 checksum How to use checksums |
97cccde2e4cf13f0d36b5a4098be4aa84e016ff049a69bc18ad417250bef23b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / calibrate-0.10.0-py2-none-any.whl
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | calibrate-0.10.0-py2-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
7cf8c012f197876b7c95f4b168013bef5a29f4bd6a69f16c2266074f43ee18bf
|
|
BLAKE2b-256 checksum How to use checksums |
ea5fcad6a63b0dae44edb88685217fc2ee41aba3b10667cba6baab1c9cd121ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for calibrate 0.10.0
Upload timing
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
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.
