Micral (MICROstructure anALysis) - core module
Description :
The aim is to gather information about microstructure. It provide raw infomation.
Installation :
pip install micral_core
Usage :
In a python file or directly in the interpreter, type :
import micral_core print(micral_core.analyse(<your image>))
Where <your image> is the name of the image to analyse (with extension (ie jpg, png, bmp etc…)) The output is an unique value.
It’s also possible to send multiple image at once : in that case, provide a list of name : <your image> = [<image1>, <image2>, …] And the return will be also a list of all the results
Note that the image must be in the same directory than the python file (or in the current directory of the command)
1 maintainer
Metadata
1 maintainer
Release files for micral-core 2.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 | |
|---|---|---|---|---|
| micral_core-2.0.tar.gz | 2.1 kB | Without provenance | Details |
Release files / micral_core-2.0.tar.gz
| Download URL | micral_core-2.0.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10735b8119ec5a766aa73c4796c878ce36bef4b2f6d01c014f31a518f3d827e8
|
|
BLAKE2b-256 checksum How to use checksums |
fb47d0960f6d8bc1208bb081cd66dca8ff471d61d309a2cc26c951e1f98d714b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/39.2.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.6.6
|
Security for micral-core 2.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.
