The simple-image-debayer library allows you to debayer images in a directory. It uses OpenCV for the debayering underneath the hood.
Changelog
0.0.4 (2020-06-04)
added option –ignore_errors to keep debayering images despite errors
added option –delete to delete input file when successfully debayered
outputting total processing time now at the end
split code into more fine-grained methods to make it easier to use the tool as Python library
0.0.3 (2020-05-25)
outputting now the time left for processing the remainder of the images as well
0.0.2 (2020-05-25)
–output_dir parameter gets used now
0.0.1 (2020-05-25)
initial release
1 maintainer
Metadata
1 maintainer
Release files for simple-image-debayer 0.0.4
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 | |
|---|---|---|---|---|
| simple-image-debayer-0.0.4.tar.gz | 5.3 kB | Without provenance | Details |
Release files / simple-image-debayer-0.0.4.tar.gz
| Download URL | simple-image-debayer-0.0.4.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
554e5d50f445b223ea38e49bafeefb6256007912eb9dd321a6831d7ff832eecd
|
|
BLAKE2b-256 checksum How to use checksums |
71ea64226a18aa624b480b6c218eed5b9d943a4cd4fce1e64cfce1cc769face2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.4.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.5
|
Security for simple-image-debayer 0.0.4
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.
