Neptune + Keras integration
Experiment tracking for Keras-trained models.
What will you get with this integration?
- Log, organize, visualize, and compare ML experiments in a single place
- Monitor model training live
- Version and query production-ready models and associated metadata (e.g., datasets)
- Collaborate with the team and across the organization
What will be logged to Neptune?
- hyperparameters for every run,
- learning curves for losses and metrics during training,
- hardware consumption and stdout/stderr output during training,
- TensorFlow tensors as images to see model predictions live,
- training code and Git commit information,
- model weights,
- other metadata
Example charts in the Neptune UI with logged accuracy and loss
Resources
Example
On the command line:
pip install neptune-tensorflow-keras
In Python:
import neptune
from neptune.integrations.tensorflow_keras import NeptuneCallback
from neptune import ANONYMOUS_API_TOKEN
# Start a run
run = neptune.init_run(
project="common/tf-keras-integration",
api_token=ANONYMOUS_API_TOKEN,
)
# Create a NeptuneCallback instance
neptune_cbk = NeptuneCallback(run=run, base_namespace="metrics")
# Pass the callback to model.fit()
model.fit(
x_train,
y_train,
epochs=5,
batch_size=64,
callbacks=[neptune_cbk],
)
# Stop the run
run.stop()
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
Metadata
Release files for neptune-tensorflow-keras 2.2.2
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_tensorflow_keras-2.2.2.tar.gz | 10.7 kB | Without provenance | Details for neptune_tensorflow_keras-2.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| neptune_tensorflow_keras-2.2.2-py3-none-any.whl | Python 3 | none | any | Details for neptune_tensorflow_keras-2.2.2-py3-none-any.whl |
Total release size: 23.1 kB
Release files / neptune_tensorflow_keras-2.2.2.tar.gz
| Download URL | neptune_tensorflow_keras-2.2.2.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1c22e277e363888b7bc2778d73a86af193fb22ea439178822c70785b629faa7
|
|
BLAKE2b-256 checksum How to use checksums |
c98673d975bd66c1390c0832f8229eac6ec50f111fe17005182fd5d7da7a7645
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.18
|
Release files / neptune_tensorflow_keras-2.2.2-py3-none-any.whl
| Download URL | neptune_tensorflow_keras-2.2.2-py3-none-any.whl |
|---|---|
| Size | 12.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
73f98a608a9645aff4283d18cdfc8e1c04874fe8226df3b0cc8f8883cb2d1835
|
|
BLAKE2b-256 checksum How to use checksums |
7de43ae76fbf870e47e070ad0faa58380d80bb176c8dddd92b7a3bdb97b7ce4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.18
|
Security for neptune-tensorflow-keras 2.2.2
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.