views-hydranet 0.1.0__tar.gz

views_hydranet-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Simon Polichinel von der Maase
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

views_hydranet-0.1.0/PKG-INFO

@@ -0,0 +1,211 @@
+Metadata-Version: 2.4
+Name: views-hydranet
+Version: 0.1.0
+Summary: views-hydranet is a package that contains modeling procedure, evaluation and forecasting using HydraNet implemented in PyTorch
+License: MIT
+License-File: LICENSE
+Author: Dylan
+Author-email: 52908667+smellycloud@users.noreply.github.com
+Requires-Python: >=3.11,<3.15
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Provides-Extra: viz
+Requires-Dist: matplotlib (>=3.8,<4) ; extra == "viz"
+Requires-Dist: torch (>=2.2.1,<3.0.0)
+Requires-Dist: views-frames (>=1.10.2,<2)
+Requires-Dist: views-pipeline-core (>=3.0.0,<4.0.0)
+Project-URL: Changelog, https://github.com/views-platform/views-hydranet/releases
+Project-URL: Homepage, https://github.com/views-platform/views-hydranet
+Project-URL: Issues, https://github.com/views-platform/views-hydranet/issues
+Project-URL: Repository, https://github.com/views-platform/views-hydranet
+Description-Content-Type: text/markdown
+
+<div style="width: 100%; max-width: 1500px; height: 400px; overflow: hidden; position: relative;">
+  <img src="https://github.com/user-attachments/assets/1ec9e217-508d-4b10-a41a-08dface269c7" alt="VIEWS Twitter Header" style="position: absolute; top: -50px; width: 100%; height: auto;">
+</div>
+
+
+# **HydraNet**: Spatiotemporal Conflict Forecasting Model 👾  
+
+> **Part of the [VIEWS Platform](https://github.com/views-platform) ecosystem for large-scale conflict forecasting.**
+
+---
+
+## 📚 Table of Contents  
+
+1. [Overview](#overview)  
+2. [Role in the VIEWS Pipeline](#role-in-the-views-pipeline)  
+3. [Features](#features)  
+4. [Installation](#installation)  
+5. [Usage](#usage)  
+6. [Configuration & Stability](#configuration--stability)
+7. [Architecture](#architecture)  
+8. [Project Structure](#project-structure)  
+9. [Contributing](#contributing)  
+10. [License](#license)  
+11. [Acknowledgements](#acknowledgements)  
+
+---
+
+## 🧠 Overview  
+
+**HydraNet** is an advanced machine learning model designed for **spatiotemporal forecasting of violent conflict** at high granularity. It predicts three types of violence—state-based, non-state-based, and one-sided—by solving regression and classification tasks concurrently.  
+
+The model provides:  
+- **Probabilistic Outputs**: Enables uncertainty quantification through posterior distributions.  
+- **Temporospatial Learning**: Leverages convolutional layers for spatial dependencies and LSTMs for temporal patterns.  
+- **Multi-Tasking**: Simultaneously predicts probabilities and magnitudes of conflict.  
+
+HydraNet is **FAIR-compliant** (Findable, Accessible, Interoperable, Reusable), ensuring transparency and ease of use for researchers and policymakers.  
+
+---
+
+## 🌍 Role in the VIEWS Pipeline  
+
+HydraNet is a core component of the **Violence & Impacts Early Warning System (VIEWS)** pipeline, working alongside other repositories:  
+
+- **[views-pipeline-core](https://github.com/views-platform/views-pipeline-core):** Manages data ingestion, preprocessing, and pipeline orchestration.  
+- **[views-models](https://github.com/views-platform/views-models):** Provides interfaces to train, test, and deploy HydraNet.  
+- **[views-evaluation](https://github.com/views-platform/views-evaluation):** Evaluates model predictions and performs calibration tasks.  
+- **[docs](https://github.com/views-platform/docs):** Organization/pipeline level documentation.
+
+### Integration Workflow  
+
+HydraNet fits into the VIEWS pipeline as follows:  
+1. **Data Input:** Preprocessed PRIO grid-cell-level conflict data is retrieved from **views-pipeline-core**.  
+2. **Model Execution:** HydraNet generates probabilistic forecasts for multiple violence types across a 36-month horizon.  
+3. **Evaluation and Calibration:** Outputs are passed to **views-evaluation** for ensembling and alignment with other models.  
+
+---
+
+## ✨ Features  
+
+- **Multi-Task Learning:** Simultaneous prediction of probabilities and magnitudes for three conflict types.  
+- **Uncertainty Quantification:** Generates posterior distributions for robust decision-making.  
+- **Hybrid Architecture:** Combines CNNs for spatial dependencies, LSTMs for temporal patterns, and U-net for precision.  
+- **Minimal Manual Engineering:** Relies solely on past conflict history, simplifying input requirements.  
+- **Scalable Design:** Adaptable for new features and forecasting tasks.  
+
+---
+
+## ⚙️ Installation  
+
+### Prerequisites  
+
+- Python >= 3.8  
+- GPU support recommended (e.g., NVIDIA CUDA).   
+
+### Steps  
+
+See the organization/pipeline level [docs](https://github.com/views-platform/docs)  
+
+---
+
+## 🚀 Usage  
+
+### 1. Run Training Locally  
+
+See the organization/pipeline level [docs](https://github.com/views-platform/docs)  
+
+### 2. Use in the VIEWS Pipeline  
+
+HydraNet seamlessly integrates into the broader VIEWS pipeline. After training and prediction, the outputs can be passed into the **views-evaluation** repository for further analysis and calibration.  
+
+---
+
+## ⚙️ Configuration & Stability
+
+HydraNet uses a **Strict Handshake** protocol to ensure production predictability. All hyperparameters are validated against a Pydantic schema (`HydraNetConfig`) at the start of every task.
+
+- **Fail-Fast:** If a required field is missing or a value is invalid (e.g., a typo in `transform`), the program will halt immediately with a detailed error report.
+- **Safe-Mode:** The system uses internal state protection to ensure that critical paths (like model saving and data loading) are robust against partial initializations or mocked environments.
+
+### Feature Lifecycle (ADR 046)
+HydraNet employs a **Symmetric Feature Lifecycle** governed by an "Instructional Blueprint."
+- **Transformations:** Mathematical scaling (e.g., `log1p`) applied to raw inputs.
+- **Derivations:** Manufacturing instructions for targets (e.g., `binary` thresholding) applied consistently during training and evaluation.
+- **Handshake:** The model manager "sanctifies" ground-truth data for evaluation, ensuring that targets like `by_sb_best` are derived on-the-fly and bit-perfect with training logic.
+
+### Prediction Output Format (ADR 047)
+HydraNet adopts the **PredictionFrame** interface mandated by `views-pipeline-core` (ADR-033).
+
+- **What:** `_evaluate_model_artifact()` returns `dict[str, list[PredictionFrame]]` and `_forecast_model_artifact()` returns `dict[str, PredictionFrame]` — one entry per target signal.
+- **Why:** Target-keyed output enables multi-target dispatch, enforces a validated `(N, S)` shape contract, and unlocks automatic parity auditing between the PF and legacy DataFrame paths.
+- **How:** The config declares `"prediction_format": "prediction_frame"`. The manager converts its internal DataFrames via `_to_pf_dict()` before returning. The upstream pipeline reads the flag and routes through `PredictionFrameDispatcher`.
+- **Guide:** See [`reports/guides/prediction_frame.md`](reports/guides/prediction_frame.md) for a self-contained implementation guide, including how to adopt this pattern in other model repos.
+
+---
+
+## 🏗 Architecture  
+
+HydraNet employs a **probabilistic recurrent U-net** architecture optimized for spatiotemporal conflict forecasting.  
+
+### Key Components  
+
+- **CNNs (Convolutional Neural Networks):** Capture intricate spatial patterns in grid-cell data.  
+- **LSTMs (Long Short-Term Memory networks):** Model temporal dependencies and trends.  
+- **Dropout Layers:** Enable Monte Carlo sampling to quantify model uncertainty.  
+- **Multi-Decoder Design:** Outputs six distinct forecasts (probabilities and magnitudes for three violence types).  
+
+### Workflow  
+
+1. **Input:** Historical conflict fatalities categorized as state-based, non-state, and one-sided.  
+2. **Data Processing:** Converts historical data into z-stacks of monthly grids with three channels (one for each violence type).  
+3. **Prediction:** Generates six outputs: probabilities and magnitudes for each type of violence.  
+
+For a detailed explanation of the architecture, refer to the **[HydraNet Paper](link-to-paper)**.  
+
+---
+
+## 🗂 Project Structure  
+
+```plaintext
+views_hydranet/
+├── README.md            # Documentation
+├── tests                # Unit and integration tests
+├── views_hydranet       # Main source code
+│   ├── architecture     # Model definitions (CNN + LSTM + U-net)
+│   ├── evaluate         # Evaluation scripts
+│   ├── forecast         # Forecasting utilities
+│   ├── manager          # Workflow management
+│   ├── train            # Training logic
+│   ├── utils            # Helper functions (logging, metrics, etc.)
+│   ├── __init__.py      # Package initialization
+├── .gitignore           # Git ignore rules
+├── pyproject.toml       # Poetry project file
+├── poetry.lock          # Dependency lock file
+```  
+
+---
+
+## 🤝 Contributing  
+
+We welcome contributions to HydraNet! Please follow the contribution guidelines outlined in the [organization-level documentation](https://github.com/views-platform/docs).  
+
+---
+
+## 📜 License  
+
+...
+
+---
+
+## 💬 Acknowledgements  
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/views-platform/docs/main/images/views_funders.png" alt="Views Funders" width="80%">
+</p>
+
+HydraNet builds upon:  
+
+- [UCDP Georeferenced Event Dataset (GED)](https://ucdp.uu.se/) for conflict data.  
+- [PRIO Grid](https://grid.prio.org/#/) for spatial resolution.  
+- Concepts from Hegre et al. (2019), Hegre et al. (2021), and Vesco et al. (2022).  
+- Funding from the **European Research Council** and the **Danish Research Council**.  
+
+Special thanks to the **VIEWS MD&D Team** for their collaboration, guidance, and efforts.  
+

views_hydranet-0.1.0/README.md

@@ -0,0 +1,184 @@
+<div style="width: 100%; max-width: 1500px; height: 400px; overflow: hidden; position: relative;">
+  <img src="https://github.com/user-attachments/assets/1ec9e217-508d-4b10-a41a-08dface269c7" alt="VIEWS Twitter Header" style="position: absolute; top: -50px; width: 100%; height: auto;">
+</div>
+
+
+# **HydraNet**: Spatiotemporal Conflict Forecasting Model 👾  
+
+> **Part of the [VIEWS Platform](https://github.com/views-platform) ecosystem for large-scale conflict forecasting.**
+
+---
+
+## 📚 Table of Contents  
+
+1. [Overview](#overview)  
+2. [Role in the VIEWS Pipeline](#role-in-the-views-pipeline)  
+3. [Features](#features)  
+4. [Installation](#installation)  
+5. [Usage](#usage)  
+6. [Configuration & Stability](#configuration--stability)
+7. [Architecture](#architecture)  
+8. [Project Structure](#project-structure)  
+9. [Contributing](#contributing)  
+10. [License](#license)  
+11. [Acknowledgements](#acknowledgements)  
+
+---
+
+## 🧠 Overview  
+
+**HydraNet** is an advanced machine learning model designed for **spatiotemporal forecasting of violent conflict** at high granularity. It predicts three types of violence—state-based, non-state-based, and one-sided—by solving regression and classification tasks concurrently.  
+
+The model provides:  
+- **Probabilistic Outputs**: Enables uncertainty quantification through posterior distributions.  
+- **Temporospatial Learning**: Leverages convolutional layers for spatial dependencies and LSTMs for temporal patterns.  
+- **Multi-Tasking**: Simultaneously predicts probabilities and magnitudes of conflict.  
+
+HydraNet is **FAIR-compliant** (Findable, Accessible, Interoperable, Reusable), ensuring transparency and ease of use for researchers and policymakers.  
+
+---
+
+## 🌍 Role in the VIEWS Pipeline  
+
+HydraNet is a core component of the **Violence & Impacts Early Warning System (VIEWS)** pipeline, working alongside other repositories:  
+
+- **[views-pipeline-core](https://github.com/views-platform/views-pipeline-core):** Manages data ingestion, preprocessing, and pipeline orchestration.  
+- **[views-models](https://github.com/views-platform/views-models):** Provides interfaces to train, test, and deploy HydraNet.  
+- **[views-evaluation](https://github.com/views-platform/views-evaluation):** Evaluates model predictions and performs calibration tasks.  
+- **[docs](https://github.com/views-platform/docs):** Organization/pipeline level documentation.
+
+### Integration Workflow  
+
+HydraNet fits into the VIEWS pipeline as follows:  
+1. **Data Input:** Preprocessed PRIO grid-cell-level conflict data is retrieved from **views-pipeline-core**.  
+2. **Model Execution:** HydraNet generates probabilistic forecasts for multiple violence types across a 36-month horizon.  
+3. **Evaluation and Calibration:** Outputs are passed to **views-evaluation** for ensembling and alignment with other models.  
+
+---
+
+## ✨ Features  
+
+- **Multi-Task Learning:** Simultaneous prediction of probabilities and magnitudes for three conflict types.  
+- **Uncertainty Quantification:** Generates posterior distributions for robust decision-making.  
+- **Hybrid Architecture:** Combines CNNs for spatial dependencies, LSTMs for temporal patterns, and U-net for precision.  
+- **Minimal Manual Engineering:** Relies solely on past conflict history, simplifying input requirements.  
+- **Scalable Design:** Adaptable for new features and forecasting tasks.  
+
+---
+
+## ⚙️ Installation  
+
+### Prerequisites  
+
+- Python >= 3.8  
+- GPU support recommended (e.g., NVIDIA CUDA).   
+
+### Steps  
+
+See the organization/pipeline level [docs](https://github.com/views-platform/docs)  
+
+---
+
+## 🚀 Usage  
+
+### 1. Run Training Locally  
+
+See the organization/pipeline level [docs](https://github.com/views-platform/docs)  
+
+### 2. Use in the VIEWS Pipeline  
+
+HydraNet seamlessly integrates into the broader VIEWS pipeline. After training and prediction, the outputs can be passed into the **views-evaluation** repository for further analysis and calibration.  
+
+---
+
+## ⚙️ Configuration & Stability
+
+HydraNet uses a **Strict Handshake** protocol to ensure production predictability. All hyperparameters are validated against a Pydantic schema (`HydraNetConfig`) at the start of every task.
+
+- **Fail-Fast:** If a required field is missing or a value is invalid (e.g., a typo in `transform`), the program will halt immediately with a detailed error report.
+- **Safe-Mode:** The system uses internal state protection to ensure that critical paths (like model saving and data loading) are robust against partial initializations or mocked environments.
+
+### Feature Lifecycle (ADR 046)
+HydraNet employs a **Symmetric Feature Lifecycle** governed by an "Instructional Blueprint."
+- **Transformations:** Mathematical scaling (e.g., `log1p`) applied to raw inputs.
+- **Derivations:** Manufacturing instructions for targets (e.g., `binary` thresholding) applied consistently during training and evaluation.
+- **Handshake:** The model manager "sanctifies" ground-truth data for evaluation, ensuring that targets like `by_sb_best` are derived on-the-fly and bit-perfect with training logic.
+
+### Prediction Output Format (ADR 047)
+HydraNet adopts the **PredictionFrame** interface mandated by `views-pipeline-core` (ADR-033).
+
+- **What:** `_evaluate_model_artifact()` returns `dict[str, list[PredictionFrame]]` and `_forecast_model_artifact()` returns `dict[str, PredictionFrame]` — one entry per target signal.
+- **Why:** Target-keyed output enables multi-target dispatch, enforces a validated `(N, S)` shape contract, and unlocks automatic parity auditing between the PF and legacy DataFrame paths.
+- **How:** The config declares `"prediction_format": "prediction_frame"`. The manager converts its internal DataFrames via `_to_pf_dict()` before returning. The upstream pipeline reads the flag and routes through `PredictionFrameDispatcher`.
+- **Guide:** See [`reports/guides/prediction_frame.md`](reports/guides/prediction_frame.md) for a self-contained implementation guide, including how to adopt this pattern in other model repos.
+
+---
+
+## 🏗 Architecture  
+
+HydraNet employs a **probabilistic recurrent U-net** architecture optimized for spatiotemporal conflict forecasting.  
+
+### Key Components  
+
+- **CNNs (Convolutional Neural Networks):** Capture intricate spatial patterns in grid-cell data.  
+- **LSTMs (Long Short-Term Memory networks):** Model temporal dependencies and trends.  
+- **Dropout Layers:** Enable Monte Carlo sampling to quantify model uncertainty.  
+- **Multi-Decoder Design:** Outputs six distinct forecasts (probabilities and magnitudes for three violence types).  
+
+### Workflow  
+
+1. **Input:** Historical conflict fatalities categorized as state-based, non-state, and one-sided.  
+2. **Data Processing:** Converts historical data into z-stacks of monthly grids with three channels (one for each violence type).  
+3. **Prediction:** Generates six outputs: probabilities and magnitudes for each type of violence.  
+
+For a detailed explanation of the architecture, refer to the **[HydraNet Paper](link-to-paper)**.  
+
+---
+
+## 🗂 Project Structure  
+
+```plaintext
+views_hydranet/
+├── README.md            # Documentation
+├── tests                # Unit and integration tests
+├── views_hydranet       # Main source code
+│   ├── architecture     # Model definitions (CNN + LSTM + U-net)
+│   ├── evaluate         # Evaluation scripts
+│   ├── forecast         # Forecasting utilities
+│   ├── manager          # Workflow management
+│   ├── train            # Training logic
+│   ├── utils            # Helper functions (logging, metrics, etc.)
+│   ├── __init__.py      # Package initialization
+├── .gitignore           # Git ignore rules
+├── pyproject.toml       # Poetry project file
+├── poetry.lock          # Dependency lock file
+```  
+
+---
+
+## 🤝 Contributing  
+
+We welcome contributions to HydraNet! Please follow the contribution guidelines outlined in the [organization-level documentation](https://github.com/views-platform/docs).  
+
+---
+
+## 📜 License  
+
+...
+
+---
+
+## 💬 Acknowledgements  
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/views-platform/docs/main/images/views_funders.png" alt="Views Funders" width="80%">
+</p>
+
+HydraNet builds upon:  
+
+- [UCDP Georeferenced Event Dataset (GED)](https://ucdp.uu.se/) for conflict data.  
+- [PRIO Grid](https://grid.prio.org/#/) for spatial resolution.  
+- Concepts from Hegre et al. (2019), Hegre et al. (2021), and Vesco et al. (2022).  
+- Funding from the **European Research Council** and the **Danish Research Council**.  
+
+Special thanks to the **VIEWS MD&D Team** for their collaboration, guidance, and efforts.  

views_hydranet-0.1.0/pyproject.toml

@@ -0,0 +1,58 @@
+[project]
+name = "views-hydranet"
+version = "0.1.0"
+description = "views-hydranet is a package that contains modeling procedure, evaluation and forecasting using HydraNet implemented in PyTorch"
+authors = [
+    {name = "Dylan",email = "52908667+smellycloud@users.noreply.github.com"}
+]
+license = {text = "MIT"}
+readme = "README.md"
+requires-python = ">=3.11,<3.15"
+dependencies = [
+    "views-pipeline-core (>=3.0.0,<4.0.0)",
+    "views-frames (>=1.10.2,<2)",
+    "torch>=2.2.1,<3.0.0"
+]
+
+# issue #215: matplotlib is imported lazily by VisualDiagnostics (optional plotting stack). Declare it
+# as an OPTIONAL extra so models that enable diagnostics (diagnostic_visualizations=True) can pin it via
+# `views-hydranet[viz]`; the default headless run path needs no plotting stack.
+[project.urls]
+Homepage = "https://github.com/views-platform/views-hydranet"
+Repository = "https://github.com/views-platform/views-hydranet"
+Issues = "https://github.com/views-platform/views-hydranet/issues"
+Changelog = "https://github.com/views-platform/views-hydranet/releases"
+
+[project.optional-dependencies]
+viz = ["matplotlib>=3.8,<4"]
+
+[build-system]
+requires = ["poetry-core>=2.0.0,<3.0.0"]
+build-backend = "poetry.core.masonry.api"
+
+[tool.poetry.group.dev.dependencies]
+ruff = ">=0.14.14,<0.15.0"
+mypy = ">=1.19.1,<2.0.0"
+pytest = "<9.0.0"
+pre-commit = ">=4.5.1,<5.0.0"
+pytest-cov = ">=5.0.0,<6.0.0"
+# #215: the test suite renders diagnostics + imports matplotlib at module top (test_visual_diagnostics,
+# test_memory_fingerprint), and conftest fails the run if collection drops below the min count — so
+# matplotlib must be present in the test env even though it's a runtime-optional 'viz' extra.
+matplotlib = ">=3.8,<4"
+
+
+[tool.ruff]
+line-length = 99
+
+[tool.ruff.lint]
+# Enable Pyflakes (F), pycodestyle errors (E) & warnings (W), and isort (I)
+select = ["E", "F", "W", "I"]
+
+[tool.ruff.format]
+# Use double quotes for strings
+quote-style = "double"
+
+[tool.mypy]
+# Ignore errors from libraries that don't have type hints
+ignore_missing_imports = true

views_hydranet-0.1.0/views_hydranet/__init__.py

@@ -0,0 +1,36 @@
+"""views-hydranet — the HydraNet conflict-forecasting model for the VIEWS platform.
+
+The public API of this package is **`HydranetManager`, and nothing else.**
+
+That is not an aspiration; it is what the consumers do. All eight models in `views-models`
+that constitute the `rusty_bucket` ensemble import exactly one name, and it is this one::
+
+    from views_hydranet import HydranetManager
+
+Everything else — `views_hydranet.utils`, `.train`, `.architectures`, `.distributions`,
+`.infrastructure` — is **internal**. It is importable, because Python has no way to prevent it,
+but it carries no stability promise and may be renamed or moved without a major version bump.
+
+Why this file says so at all: publishing to PyPI makes every module in the wheel reachable by
+strangers, and anything reachable can be depended upon. Without this declaration, all 67 modules
+would look equally official, and #181 — reorganising `utils/`, which is 42 of them — would become
+a breaking change for anyone who had imported from it. With it, that reorganisation stays free.
+
+See `docs/guides/publishing-to-pypi.md`, and #181 / #279.
+
+⚠️ The import below is LAZY, and must stay lazy. `HydranetManager` pulls in torch, and this
+package has two tests — `test_importing_config_initializer_does_not_import_torch` and
+`test_importing_the_registry_does_not_import_torch` — that guarantee the light modules stay light.
+An eager import here breaks both, because importing ANY submodule runs this file first. PEP 562's
+module-level `__getattr__` gives the short public path without that cost.
+"""
+
+__all__ = ["HydranetManager"]
+
+
+def __getattr__(name: str):
+    if name == "HydranetManager":
+        from views_hydranet.manager.hydranet_manager import HydranetManager
+
+        return HydranetManager
+    raise AttributeError(f"module {__name__!r} has no attribute {name!r}")