freshcrate
Home > Developer Tools > spacy-loggers

spacy-loggers

Logging utilities for SpaCy

Description

<a href="https://explosion.ai"><img src="https://explosion.ai/assets/img/logo.svg" width="125" height="125" align="right" /></a> # spacy-loggers: Logging utilities for spaCy [![PyPi Version](https://img.shields.io/pypi/v/spacy-loggers.svg?style=flat-square&logo=pypi&logoColor=white)](https://pypi.python.org/pypi/spacy-loggers) Starting with spaCy v3.2, alternate loggers are moved into a separate package so that they can be added and updated independently from the core spaCy library. `spacy-loggers` currently provides loggers for: - [Weights & Biases](https://www.wandb.com) - [MLflow](https://www.mlflow.org/) - [ClearML](https://www.clear.ml/) - [PyTorch](https://pytorch.org/) - [CuPy](https://github.com/cupy/cupy) `spacy-loggers` also provides additional utility loggers to facilitate interoperation between individual loggers. If you'd like to add a new logger or logging option, please submit a PR to this repo! ## Setup and installation `spacy-loggers` should be installed automatically with spaCy v3.2+, so you usually don't need to install it separately. You can install it with `pip` or from the conda channel `conda-forge`: ```bash pip install spacy-loggers ``` ```bash conda install -c conda-forge spacy-loggers ``` # Loggers ## WandbLogger ### Installation This logger requires `wandb` to be installed and configured: ```bash pip install wandb wandb login ``` ### Usage `spacy.WandbLogger.v5` is a logger that sends the results of each training step to the dashboard of the [Weights & Biases](https://www.wandb.com/) tool. To use this logger, Weights & Biases should be installed, and you should be logged in. The logger will send the full config file to W&B, as well as various system information such as memory utilization, network traffic, disk IO, GPU statistics, etc. This will also include information such as your hostname and operating system, as well as the location of your Python executable. `spacy.WandbLogger.v4` and below automatically call the [default console logger](https://spacy.io/api/top-level#ConsoleLogger). However, starting with `spacy.WandbLogger.v5`, console logging must be activated through the use of the [ChainLogger](#chainlogger). This allows the user to configure the console logger's parameters according to their preferences. **Note** that by default, the full (interpolated) [training config](https://spacy.io/usage/training#config) is sent over to the W&B dashboard. If you prefer to **exclude certain information** such as path names, you can list those fields in "dot notation" in the `remove_config_values` parameter. These fields will then be removed from the config before uploading, but will otherwise remain in the config file stored on your local system. ### Example config ```ini [training.logger] @loggers = "spacy.WandbLogger.v5" project_name = "monitor_spacy_training" remove_config_values = ["paths.train", "paths.dev", "corpora.train.path", "corpora.dev.path"] log_dataset_dir = "corpus" model_log_interval = 1000 ``` | Name | Type | Description | | ---------------------- | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `project_name` | `str` | The name of the project in the Weights & Biases interface. The project will be created automatically if it doesn't exist yet. | | `remove_config_values` | `List[str]` | A list of values to exclude from the config before it is uploaded to W&B (default: `[]`). | | `model_log_interval` | `Optional[int]` | Steps to wait between logging model checkpoints to the W&B dasboard (default: `None`). Added in `spacy.WandbLogger.v2`. | | `log_dataset_dir` | `Optional[str]` | Directory containing the dataset to be logged and versioned as a W&B artifact (default: `None`). Added in `spacy.WandbLogger.v2`. | | `entity` | `Optional[str]` | An entity is a username or team name where you're sending runs. If you don't specify an entity, the run will be sent to your default entity, which is usually your username (default: `None`). Added in `spacy.WandbLogger.v3`. | | `run_name` | `Optional[str]`

Release History

VersionChangesUrgencyDate
1.0.5Imported from PyPI (1.0.5)Low4/21/2026
v1.0.5* Add `ChainLogger.v1`, `PyTorchLogger.v1` and `LookupLogger.v1` (#19). * Add `CupyLogger.v1` (#24). * Add `WandbLogger.v5` (#21). * Add `ClearMLLogger.v2` (#22). * Add `MLflowLogger.v2` (#23). Low9/11/2023
v1.0.4- Add `spacy.ClearMLLogger.v1` (#12). - Update types (#16). Thanks to @thepycoder for the contribution!Low12/8/2022
v1.0.3- Add `spacy.MLflowLogger.v1` Thanks to @snosrap for the contribution!Low7/14/2022
v1.0.2* Add `spacy.WandbLogger.v4` with the additional settings `log_best_dir` and `log_latest_dir`. Thanks to @Zatteliet for the contribution!Low4/1/2022

Dependencies & License Audit

Loading dependencies...

Similar Packages

azure-coreMicrosoft Azure Core Library for Pythonazure-template_0.1.0b6187637
azure-mgmt-coreMicrosoft Azure Management Core Library for Pythonazure-template_0.1.0b6187637
azure-monitor-opentelemetry-exporterMicrosoft Azure Monitor Opentelemetry Exporter Client Library for Pythonazure-template_0.1.0b6187637
azure-servicebusMicrosoft Azure Service Bus Client Library for Pythonazure-template_0.1.0b6187637
azure-monitor-opentelemetryMicrosoft Azure Monitor Opentelemetry Distro Client Library for Pythonazure-template_0.1.0b6187637