Neptune + LightGBM Integration
Experiment tracking, model registry, data versioning, and live model monitoring for LightGBM trained models.
What will you get with this integration?
- Log, display, organize, and compare ML experiments in a single place
- Version, store, manage, and query trained models, and model building metadata
- Record and monitor model training, evaluation, or production runs live
What will be logged to Neptune?
- training and validation metrics,
- parameters,
- feature names, num_features, and num_rows for the train set,
- hardware consumption (CPU, GPU, memory),
- stdout and stderr logs,
- training code and Git commit information,
- other metadata
Resources
- Documentation
- Code example on GitHub
- Example of a run logged in the Neptune app
- Run example in Google Colab
Example
# On the command line:
pip install neptune-lightgbm
# In Python:
import lightgbm as lgb
import neptune
from neptune.integrations.lightgbm import NeptuneCallback
# Start a run
run = neptune.init_run(
project="common/lightgbm-integration",
api_token=neptune.ANONYMOUS_API_TOKEN,
)
# Create a NeptuneCallback instance
neptune_callback = NeptuneCallback(run=run)
# Prepare datasets
...
lgb_train = lgb.Dataset(X_train, y_train)
# Define model parameters
params = {
"boosting_type": "gbdt",
"objective": "multiclass",
"num_class": 10,
...
}
# Train the model
gbm = lgb.train(
params,
lgb_train,
callbacks=[neptune_callback],
)
Support
If you got stuck or simply want to talk to us, here are your options:
- Check our FAQ page
- You can submit bug reports, feature requests, or contributions directly to the repository.
- Chat! When in the Neptune application click on the blue message icon in the bottom-right corner and send a message. A real person will talk to you ASAP (typically very ASAP),
- You can just shoot us an email at support@neptune.ai
1 maintainer
Metadata
1 maintainer
Release files for neptune-lightgbm 2.0.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 |
|---|---|---|---|---|
| neptune_lightgbm-2.0.0.tar.gz | 10.9 kB | Without provenance | Details for neptune_lightgbm-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| neptune_lightgbm-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for neptune_lightgbm-2.0.0-py3-none-any.whl |
Total release size: 23.3 kB
Release files / neptune_lightgbm-2.0.0.tar.gz
| Download URL | neptune_lightgbm-2.0.0.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52e0f2f1df57c0fae5b10d50c5f8e4264457f740ac8e04b3b97d2cae49c8629a
|
|
BLAKE2b-256 checksum How to use checksums |
24208e12db5d9b599986450a2155581dfd42241ecfd29d353adf6099968560ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / neptune_lightgbm-2.0.0-py3-none-any.whl
| Download URL | neptune_lightgbm-2.0.0-py3-none-any.whl |
|---|---|
| Size | 12.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1413068c34c1fd534b89b407e8da27485401d5ae3e2bb21f683153b72c5a53df
|
|
BLAKE2b-256 checksum How to use checksums |
296ba5c4f0fc4e011fe70c0eddb23486e477945cc4984ddaebc1e261ad074e6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for neptune-lightgbm 2.0.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.
