MLPet
Preprocessing tools for Petrophysics ML projects at Eureka
Installation
-
Install the package by running the following (requires python 3.8 or later)
pip install mlpet
Quick start
-
Short example for pre-processing data prior to making a regression model:
from mlpet.Datasets.shear import Sheardata # Instantiate an empty dataset object using the example settings and mappings provided ds = Sheardata( settings="support/settings_shear.yaml", mappings="support/mappings.yaml", folder_path="support/") # Populate the dataset with data from a file # (support for multiple file formats and direct cdf data collection exists) ds.load_from_pickle("support/data/shear.pkl") # The original data will be kept in ds.df_original and will remain unchanged print(ds.df_original.head()) # Split the data into train-validation sets df_train_original, df_valid_original, valid_wells = ds.train_test_split( df=ds.df_original, test_size=0.3) # Preprocess the data for training df_train, train_key_wells, feats = ds.preprocess(df_train_original) # Preprocecss accepts some keyword arguments related to various steps # (e.g. the key wells used for normalizing curves such as GR) df_valid, valid_key_wells, _ = ds.preprocess( df_valid_original, _normalize_curves={'key_wells':train_key_wells})
The procedure will be exactly the same for the lithology class. The only difference will be in the "settings". For a full list of possible settings keys see the documentation for the main Dataset class. Make sure that the curve names are consistent with those in the dataset. The mappings will NOT be applied during the load data step.
API Documentation
Full API documentaion of the package can be found under docs/
For developers
-
to update the API documentation, from the root directory of the project run
pip install pdoc pdoc --docformat google -o docs mlpet
Metadata
Release files for MLPet 0.0.7.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 |
|---|---|---|---|---|
| MLPet-0.0.7.1.tar.gz | 19.7 kB | Without provenance | Details for MLPet-0.0.7.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| MLPet-0.0.7.1-py3-none-any.whl | Python 3 | none | any | Details for MLPet-0.0.7.1-py3-none-any.whl |
Total release size: 42.0 kB
Release files / MLPet-0.0.7.1.tar.gz
| Download URL | MLPet-0.0.7.1.tar.gz |
|---|---|
| Size | 19.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a84c8a3d299c3b377ec739a089bf748913377c101c925a72fa98c6cbbf16b33
|
|
BLAKE2b-256 checksum How to use checksums |
889e8928ea129e8de2c8ac349881d83a67cdb64ae774d2fb9bab2db11fb30d5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7
|
Release files / MLPet-0.0.7.1-py3-none-any.whl
| Download URL | MLPet-0.0.7.1-py3-none-any.whl |
|---|---|
| Size | 22.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c3288d0aabbc1a94e6054ab763f176a0e4c4834aa1a3bac24916eb52a913980
|
|
BLAKE2b-256 checksum How to use checksums |
459cbce89f15e8149d17182d8498bea39c5e60f3bce3cd1a5de0dbd371819a74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7
|
Security for MLPet 0.0.7.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.