euler-eval 2.22.0__tar.gz → 2.26.0__tar.gz

euler_eval-2.26.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Daniel Rothenpieler
+
+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.

euler_eval-2.26.0/PKG-INFO

@@ -0,0 +1,237 @@
+Metadata-Version: 2.4
+Name: euler-eval
+Version: 2.26.0
+Summary: Evaluation toolkit for depth, RGB, ray and 3D point-map predictions
+Author-email: Daniel Rothenpieler <rothenpielerdaniel@gmail.com>
+License: MIT
+Project-URL: Homepage, https://github.com/d-rothen/euler-eval
+Project-URL: Repository, https://github.com/d-rothen/euler-eval
+Project-URL: Issues, https://github.com/d-rothen/euler-eval/issues
+Project-URL: Documentation, https://github.com/d-rothen/euler-eval/tree/main/docs
+Keywords: depth,depth-estimation,evaluation,metrics,benchmark,computer-vision,point-cloud,lidar,3d
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Scientific/Engineering :: Image Processing
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: numpy>=1.21.0
+Requires-Dist: scipy>=1.7.0
+Requires-Dist: Pillow>=8.0.0
+Requires-Dist: torch>=1.9.0
+Requires-Dist: torchvision>=0.10.0
+Requires-Dist: opencv-python-headless>=4.5.0
+Requires-Dist: lpips>=0.1.4
+Requires-Dist: torchmetrics>=1.0
+Requires-Dist: tqdm>=4.62.0
+Requires-Dist: euler-loading>=2.15
+Requires-Dist: ds-crawler>=2.10
+Requires-Dist: euler-metric-naming>=0.2
+Provides-Extra: logging
+Requires-Dist: euler-train>=2.11; extra == "logging"
+Provides-Extra: fid
+Requires-Dist: clean-fid>=0.1.35; extra == "fid"
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0.0; extra == "dev"
+Requires-Dist: pytest-cov>=3.0.0; extra == "dev"
+Requires-Dist: black>=22.0.0; extra == "dev"
+Requires-Dist: ruff>=0.2; extra == "dev"
+Dynamic: license-file
+
+<!-- euler header — shared across the euler packages.
+     Per package, change only: the <h1>, the tagline, and the badge URLs. -->
+<p align="center">
+  <img src="https://files.chronodle.com/icons/euler.svg" alt="euler" width="96" height="96">
+</p>
+
+<h1 align="center">euler-eval</h1>
+
+<p align="center">
+  <em>Score depth, RGB, ray and 3D point-map predictions against the same ground truth — from one JSON config.</em>
+</p>
+
+<p align="center">
+  <a href="https://pypi.org/project/euler-eval/"><img alt="PyPI" src="https://img.shields.io/pypi/v/euler-eval.svg"></a>
+  <a href="https://pypi.org/project/euler-eval/"><img alt="Python versions" src="https://img.shields.io/pypi/pyversions/euler-eval.svg"></a>
+  <a href="LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/license-MIT-blue.svg"></a>
+  <a href="https://github.com/d-rothen/euler-eval/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/d-rothen/euler-eval/actions/workflows/ci.yml/badge.svg"></a>
+</p>
+
+---
+
+Comparing predictions to ground truth is rarely one line of code. The files have
+to be paired, the ground truth may be radial where the prediction is planar, the
+model may only be correct up to scale, and every modality wants a different
+metric set.
+
+euler-eval takes a JSON config naming the ground truth and one or more
+prediction datasets, and writes an `eval.json` per modality: files paired by ID,
+decoded from dataset metadata rather than convention, aligned when the
+prediction is not metric, and scored with the metric set that modality deserves.
+
+```mermaid
+flowchart LR
+    C["ds-crawler<br/><i>indexes files</i>"] --> H["dataset-head.json<br/><i>euler-dataset-contract</i>"]
+    H --> L["euler-loading<br/><i>pairs GT + prediction by ID</i>"]
+    L --> E["euler-eval<br/><b>scores the pair</b>"]
+    E --> J["eval.json<br/><i>per modality, per dataset</i>"]
+    E -.->|optional| T["euler-train<br/><i>experiment logging</i>"]
+```
+
+It is the consuming end of that pipeline and does none of the earlier steps
+itself: a path in the config is a
+[euler-loading](https://github.com/d-rothen/euler-loading) path, and how to
+decode it — loader, units, radial or planar depth, point-cloud column layout —
+is read from the dataset's own index. Metric keys are built with
+[euler-metric-naming](https://github.com/d-rothen/euler-metric-naming), so every
+result is self-describing to downstream tools.
+
+## Install
+
+```bash
+pip install euler-eval                  # core
+pip install "euler-eval[fid]"           # + clean-fid RGB FID backend
+pip install "euler-eval[logging]"       # + euler-train experiment logging
+```
+
+Python 3.9 or newer. CUDA is used automatically when available, and every metric
+also runs on CPU.
+
+## Quick start
+
+Describe the ground truth and what to score against it:
+
+```json
+{
+  "gt": {
+    "rgb":   { "path": "/data/gt/rgb" },
+    "depth": { "path": "/data/gt/depth" }
+  },
+  "datasets": [
+    {
+      "name": "model_a",
+      "rgb":   { "path": "/data/model_a/rgb" },
+      "depth": { "path": "/data/model_a/depth" }
+    }
+  ]
+}
+```
+
+```bash
+euler-eval config.json --batch-size 32
+```
+
+Ground truth and prediction files are matched by ID rather than by directory
+order, so an incomplete prediction set scores the frames it does have instead of
+silently comparing the wrong pairs. Results are written next to each prediction
+modality:
+
+```json
+{
+  "depth": {
+    "eval": {
+      "metric": {
+        "standard": {
+          "image_mean": { "absrel": 0.081, "rmse": 3.42, "delta1": 0.93 }
+        }
+      }
+    }
+  }
+}
+```
+
+Every path accepts euler-loading's inline selectors, so splits and archives need
+no extra plumbing — `"/data/muses.zip:test#scope=rgb"` reads the `test` split
+straight out of the archive. Full schema: [Configuration](docs/configuration.md).
+
+## What it evaluates
+
+| Modality | Config key | Scored against | Headline metrics |
+|---|---|---|---|
+| **Depth** | `depth`, `relative_depth`, `affine_depth` | dense GT depth | `absrel`…`delta3`, PSNR/SSIM/LPIPS/FID/KID, surface-normal consistency, depth-edge F1 |
+| **Sparse depth** | `depth` + `gt.sparse_depth` | a LiDAR-style point cloud, projected into the prediction plane | pointwise depth metrics at projected points, plus directed 3D completeness |
+| **RGB** | `rgb` | GT RGB | PSNR, SSIM, LPIPS, FID, SCE, edge F1, tail errors, HF energy ratio, depth-binned photometric error; optional NIQE/FADE dehazing metrics |
+| **Rays** | `rays` | GT ray direction map | ρ_A (angular-accuracy AUC), angular error, threshold percentages |
+| **Points-3D** | `points_3d` | GT point map, or GT depth unprojected on the fly | 3D EPE/RMSE/δ, radial-vs-lateral decomposition, true-3D normals and edge F1, Chamfer / F-score |
+
+A run evaluates whichever modalities are configured on both sides; a depth-only
+prediction is a perfectly ordinary run. The full inventory, with the key each
+metric is written under, is in [Metrics](docs/metrics.md).
+
+## What you get
+
+| | |
+|---|---|
+| **ID-based pairing** | GT and prediction frames are matched by file ID and hierarchy, not by filename luck. Calibration and pose files are matched by tree position and shared. |
+| **Metadata-driven decoding** | Radial vs planar depth, value ranges, point-cloud column layout and loader choice all come from the dataset index — no per-dataset flags. |
+| **Honest spaces** | Relative models are scored `native` *and* `metric` (after scale/shift or a similarity gauge), so a scale failure never reads as a geometry failure. |
+| **Benchmark depth bins** | `--benchmark-depth-range MIN MAX` adds near/mid/far bins in square-root depth space, additive to the regular metrics. |
+| **Sky masking** | `--mask-sky` drops sky pixels using GT segmentation — from the metrics *and* from the alignment fit. |
+| **Per-file + aggregate** | Dataset-level numbers plus per-image metrics in dataset-hierarchy order, in the same file. |
+| **Sanity checks** | Results are validated against configurable thresholds; implausible ranges, degenerate inputs and scale mismatches are reported instead of quietly scored. |
+| **Structured metric names** | Each result carries a `metricSet` envelope declaring its namespace, axes, units and metric directions. |
+| **Composable domains** | `--domain dehazing` supplements the stable core set with prediction-only NIQE and FADE; the registry is ready for additional domains. |
+| **euler-train logging** | Optional: register each evaluation in an experiment run with full package provenance. |
+
+## In-training validation
+
+The same depth-metric semantics are available for in-memory predictions, so a
+training loop's validation numbers match what the CLI reports later — against
+dense *or* sparse ground truth, without writing predictions to disk:
+
+```python
+from euler_eval import DepthValidationAggregator, evaluate_sparse_depth_sample
+
+aggregator = DepthValidationAggregator()
+for sample in val_dataset:
+    result = evaluate_sparse_depth_sample(
+        model(sample["rgb"]),        # (H, W) metres
+        sample["sparse_depth"],      # (N, C>=3) lidar points
+        intrinsics,
+        lidar_to_camera,
+        alignment="none",            # "affine" for relative depth
+    )
+    aggregator.update(result)
+
+aggregator.summary()["standard"]["image_mean"]["absrel"]
+```
+
+Multi-process runs reduce sufficient statistics rather than averages — see
+[In-training validation](docs/validation.md).
+
+## Documentation
+
+| Guide | Covers |
+|---|---|
+| [Configuration](docs/configuration.md) | The config file, `gt` and `datasets`, paths and selectors, sparse-depth and points-3d ground truth, euler-train logging |
+| [CLI reference](docs/cli.md) | Every flag, worked examples, device selection, offline cache warmup |
+| [Spaces & alignment](docs/alignment.md) | `native` vs `metric`, depth affine fitting, points-3d gauge alignment, benchmark depth bins |
+| [Metrics](docs/metrics.md) | The full metric inventory per modality |
+| [Results & output](docs/output.md) | Anatomy of `eval.json`, per-file metrics, the sanity-check report |
+| [In-training validation](docs/validation.md) | The programmatic API for scoring in-memory predictions |
+
+Start with [the concepts page](docs/README.md) for how the pieces fit together.
+
+## Development
+
+```bash
+git clone https://github.com/d-rothen/euler-eval.git
+cd euler-eval
+uv sync --extra dev     # or: pip install -e ".[dev]"
+uv run pytest
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the test layout and release process.
+
+## License
+
+[MIT](LICENSE) © Daniel Rothenpieler

euler_eval-2.26.0/README.md

@@ -0,0 +1,188 @@
+<!-- euler header — shared across the euler packages.
+     Per package, change only: the <h1>, the tagline, and the badge URLs. -->
+<p align="center">
+  <img src="https://files.chronodle.com/icons/euler.svg" alt="euler" width="96" height="96">
+</p>
+
+<h1 align="center">euler-eval</h1>
+
+<p align="center">
+  <em>Score depth, RGB, ray and 3D point-map predictions against the same ground truth — from one JSON config.</em>
+</p>
+
+<p align="center">
+  <a href="https://pypi.org/project/euler-eval/"><img alt="PyPI" src="https://img.shields.io/pypi/v/euler-eval.svg"></a>
+  <a href="https://pypi.org/project/euler-eval/"><img alt="Python versions" src="https://img.shields.io/pypi/pyversions/euler-eval.svg"></a>
+  <a href="LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/license-MIT-blue.svg"></a>
+  <a href="https://github.com/d-rothen/euler-eval/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/d-rothen/euler-eval/actions/workflows/ci.yml/badge.svg"></a>
+</p>
+
+---
+
+Comparing predictions to ground truth is rarely one line of code. The files have
+to be paired, the ground truth may be radial where the prediction is planar, the
+model may only be correct up to scale, and every modality wants a different
+metric set.
+
+euler-eval takes a JSON config naming the ground truth and one or more
+prediction datasets, and writes an `eval.json` per modality: files paired by ID,
+decoded from dataset metadata rather than convention, aligned when the
+prediction is not metric, and scored with the metric set that modality deserves.
+
+```mermaid
+flowchart LR
+    C["ds-crawler<br/><i>indexes files</i>"] --> H["dataset-head.json<br/><i>euler-dataset-contract</i>"]
+    H --> L["euler-loading<br/><i>pairs GT + prediction by ID</i>"]
+    L --> E["euler-eval<br/><b>scores the pair</b>"]
+    E --> J["eval.json<br/><i>per modality, per dataset</i>"]
+    E -.->|optional| T["euler-train<br/><i>experiment logging</i>"]
+```
+
+It is the consuming end of that pipeline and does none of the earlier steps
+itself: a path in the config is a
+[euler-loading](https://github.com/d-rothen/euler-loading) path, and how to
+decode it — loader, units, radial or planar depth, point-cloud column layout —
+is read from the dataset's own index. Metric keys are built with
+[euler-metric-naming](https://github.com/d-rothen/euler-metric-naming), so every
+result is self-describing to downstream tools.
+
+## Install
+
+```bash
+pip install euler-eval                  # core
+pip install "euler-eval[fid]"           # + clean-fid RGB FID backend
+pip install "euler-eval[logging]"       # + euler-train experiment logging
+```
+
+Python 3.9 or newer. CUDA is used automatically when available, and every metric
+also runs on CPU.
+
+## Quick start
+
+Describe the ground truth and what to score against it:
+
+```json
+{
+  "gt": {
+    "rgb":   { "path": "/data/gt/rgb" },
+    "depth": { "path": "/data/gt/depth" }
+  },
+  "datasets": [
+    {
+      "name": "model_a",
+      "rgb":   { "path": "/data/model_a/rgb" },
+      "depth": { "path": "/data/model_a/depth" }
+    }
+  ]
+}
+```
+
+```bash
+euler-eval config.json --batch-size 32
+```
+
+Ground truth and prediction files are matched by ID rather than by directory
+order, so an incomplete prediction set scores the frames it does have instead of
+silently comparing the wrong pairs. Results are written next to each prediction
+modality:
+
+```json
+{
+  "depth": {
+    "eval": {
+      "metric": {
+        "standard": {
+          "image_mean": { "absrel": 0.081, "rmse": 3.42, "delta1": 0.93 }
+        }
+      }
+    }
+  }
+}
+```
+
+Every path accepts euler-loading's inline selectors, so splits and archives need
+no extra plumbing — `"/data/muses.zip:test#scope=rgb"` reads the `test` split
+straight out of the archive. Full schema: [Configuration](docs/configuration.md).
+
+## What it evaluates
+
+| Modality | Config key | Scored against | Headline metrics |
+|---|---|---|---|
+| **Depth** | `depth`, `relative_depth`, `affine_depth` | dense GT depth | `absrel`…`delta3`, PSNR/SSIM/LPIPS/FID/KID, surface-normal consistency, depth-edge F1 |
+| **Sparse depth** | `depth` + `gt.sparse_depth` | a LiDAR-style point cloud, projected into the prediction plane | pointwise depth metrics at projected points, plus directed 3D completeness |
+| **RGB** | `rgb` | GT RGB | PSNR, SSIM, LPIPS, FID, SCE, edge F1, tail errors, HF energy ratio, depth-binned photometric error; optional NIQE/FADE dehazing metrics |
+| **Rays** | `rays` | GT ray direction map | ρ_A (angular-accuracy AUC), angular error, threshold percentages |
+| **Points-3D** | `points_3d` | GT point map, or GT depth unprojected on the fly | 3D EPE/RMSE/δ, radial-vs-lateral decomposition, true-3D normals and edge F1, Chamfer / F-score |
+
+A run evaluates whichever modalities are configured on both sides; a depth-only
+prediction is a perfectly ordinary run. The full inventory, with the key each
+metric is written under, is in [Metrics](docs/metrics.md).
+
+## What you get
+
+| | |
+|---|---|
+| **ID-based pairing** | GT and prediction frames are matched by file ID and hierarchy, not by filename luck. Calibration and pose files are matched by tree position and shared. |
+| **Metadata-driven decoding** | Radial vs planar depth, value ranges, point-cloud column layout and loader choice all come from the dataset index — no per-dataset flags. |
+| **Honest spaces** | Relative models are scored `native` *and* `metric` (after scale/shift or a similarity gauge), so a scale failure never reads as a geometry failure. |
+| **Benchmark depth bins** | `--benchmark-depth-range MIN MAX` adds near/mid/far bins in square-root depth space, additive to the regular metrics. |
+| **Sky masking** | `--mask-sky` drops sky pixels using GT segmentation — from the metrics *and* from the alignment fit. |
+| **Per-file + aggregate** | Dataset-level numbers plus per-image metrics in dataset-hierarchy order, in the same file. |
+| **Sanity checks** | Results are validated against configurable thresholds; implausible ranges, degenerate inputs and scale mismatches are reported instead of quietly scored. |
+| **Structured metric names** | Each result carries a `metricSet` envelope declaring its namespace, axes, units and metric directions. |
+| **Composable domains** | `--domain dehazing` supplements the stable core set with prediction-only NIQE and FADE; the registry is ready for additional domains. |
+| **euler-train logging** | Optional: register each evaluation in an experiment run with full package provenance. |
+
+## In-training validation
+
+The same depth-metric semantics are available for in-memory predictions, so a
+training loop's validation numbers match what the CLI reports later — against
+dense *or* sparse ground truth, without writing predictions to disk:
+
+```python
+from euler_eval import DepthValidationAggregator, evaluate_sparse_depth_sample
+
+aggregator = DepthValidationAggregator()
+for sample in val_dataset:
+    result = evaluate_sparse_depth_sample(
+        model(sample["rgb"]),        # (H, W) metres
+        sample["sparse_depth"],      # (N, C>=3) lidar points
+        intrinsics,
+        lidar_to_camera,
+        alignment="none",            # "affine" for relative depth
+    )
+    aggregator.update(result)
+
+aggregator.summary()["standard"]["image_mean"]["absrel"]
+```
+
+Multi-process runs reduce sufficient statistics rather than averages — see
+[In-training validation](docs/validation.md).
+
+## Documentation
+
+| Guide | Covers |
+|---|---|
+| [Configuration](docs/configuration.md) | The config file, `gt` and `datasets`, paths and selectors, sparse-depth and points-3d ground truth, euler-train logging |
+| [CLI reference](docs/cli.md) | Every flag, worked examples, device selection, offline cache warmup |
+| [Spaces & alignment](docs/alignment.md) | `native` vs `metric`, depth affine fitting, points-3d gauge alignment, benchmark depth bins |
+| [Metrics](docs/metrics.md) | The full metric inventory per modality |
+| [Results & output](docs/output.md) | Anatomy of `eval.json`, per-file metrics, the sanity-check report |
+| [In-training validation](docs/validation.md) | The programmatic API for scoring in-memory predictions |
+
+Start with [the concepts page](docs/README.md) for how the pieces fit together.
+
+## Development
+
+```bash
+git clone https://github.com/d-rothen/euler-eval.git
+cd euler-eval
+uv sync --extra dev     # or: pip install -e ".[dev]"
+uv run pytest
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the test layout and release process.
+
+## License
+
+[MIT](LICENSE) © Daniel Rothenpieler

euler_eval-2.26.0/euler_eval/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,83 @@
+# Third-party notices
+
+`euler-eval` bundles the pristine natural-scene model parameters from the NIQE
+software release and the foggy/fog-free model parameters from the FADE software
+release. These assets and the corresponding metric implementations are based on
+software published by the Laboratory for Image and Video Engineering (LIVE).
+
+## NIQE software release
+
+-----------COPYRIGHT NOTICE STARTS WITH THIS LINE------------
+
+Copyright (c) 2011 The University of Texas at Austin
+
+All rights reserved.
+
+Permission is hereby granted, without written agreement and without license or
+royalty fees, to use, copy, modify, and distribute this code (the source files)
+and its documentation for any purpose, provided that the copyright notice in
+its entirety appear in all copies of this code, and the original source of this
+code, Laboratory for Image and Video Engineering (LIVE,
+http://live.ece.utexas.edu) and Center for Perceptual Systems (CPS,
+http://www.cps.utexas.edu) at the University of Texas at Austin (UT Austin,
+http://www.utexas.edu), is acknowledged in any publication that reports
+research using this code. The research is to be cited in the bibliography as:
+
+1) A. Mittal, R. Soundararajan and A. C. Bovik, "NIQE Software Release",
+URL: http://live.ece.utexas.edu/research/quality/niqe.zip, 2012.
+
+2) A. Mittal, R. Soundararajan and A. C. Bovik, "Making a Completely Blind
+Image Quality Analyzer", submitted to IEEE Signal Processing Letters, 2012.
+
+IN NO EVENT SHALL THE UNIVERSITY OF TEXAS AT AUSTIN BE LIABLE TO ANY PARTY FOR
+DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF
+THE USE OF THIS DATABASE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF TEXAS
+AT AUSTIN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+THE UNIVERSITY OF TEXAS AT AUSTIN SPECIFICALLY DISCLAIMS ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS FOR A PARTICULAR PURPOSE. THE DATABASE PROVIDED HEREUNDER IS ON AN "AS
+IS" BASIS, AND THE UNIVERSITY OF TEXAS AT AUSTIN HAS NO OBLIGATION TO PROVIDE
+MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
+
+-----------COPYRIGHT NOTICE ENDS WITH THIS LINE------------
+
+## FADE software release
+
+-----------COPYRIGHT NOTICE STARTS WITH THIS LINE------------
+
+Copyright (c) 2015 The University of Texas at Austin
+
+All rights reserved.
+
+Permission is hereby granted, without written agreement and without license or
+royalty fees, to use, copy, modify, and distribute this code (the source files)
+and its documentation for any purpose, provided that the copyright notice in
+its entirety appear in all copies of this code, and the original source of this
+code, Laboratory for Image and Video Engineering (LIVE,
+http://live.ece.utexas.edu) at The University of Texas at Austin (UT Austin,
+http://www.utexas.edu), is acknowledged in any publication that reports
+research using this code. The research is to be cited in the bibliography as:
+
+1. L. K. Choi, J. You, and A. C. Bovik, "Referenceless Prediction of
+Perceptual Fog Density and Perceptual Image Defogging," IEEE Transactions on
+Image Processing, to appear (2015).
+
+2. L. K. Choi, J. You, and A. C. Bovik, "Referenceless perceptual fog density
+prediction model," in Proc. SPIE Human Vis. Electron. Imag., Feb. 2014, 90140H.
+
+3. L. K. Choi, J. You, and A. C. Bovik, "FADE Software Release,"
+URL: http://live.ece.utexas.edu/research/fog/FADE_release.zip, 2015
+
+IN NO EVENT SHALL THE UNIVERSITY OF TEXAS AT AUSTIN BE LIABLE TO ANY PARTY FOR
+DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF
+THE USE OF THIS DATABASE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF TEXAS
+AT AUSTIN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+THE UNIVERSITY OF TEXAS AT AUSTIN SPECIFICALLY DISCLAIMS ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS FOR A PARTICULAR PURPOSE. THE DATABASE PROVIDED HEREUNDER IS ON AN "AS
+IS" BASIS, AND THE UNIVERSITY OF TEXAS AT AUSTIN HAS NO OBLIGATION TO PROVIDE
+MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
+
+-----------COPYRIGHT NOTICE ENDS WITH THIS LINE------------

{euler_eval-2.22.0 → euler_eval-2.26.0}/euler_eval/__init__.py

@@ -18,6 +18,8 @@ from __future__ import annotations
 from typing import TYPE_CHECKING
 
 _VALIDATION_EXPORTS = (
+    "BENCHMARK_DEPTH_BIN_NAMES",
+    "DepthBenchmarkEvaluation",
     "DepthSampleEvaluation",
     "DepthValidationAggregator",
     "VALIDATION_ALIGNMENT_MODES",
@@ -39,7 +41,9 @@ if TYPE_CHECKING:  # pragma: no cover - static import surface for type checkers
         get_sample_pointcloud_to_camera_extrinsics,
     )
     from .validation import (  # noqa: F401
+        BENCHMARK_DEPTH_BIN_NAMES,
         VALIDATION_ALIGNMENT_MODES,
+        DepthBenchmarkEvaluation,
         DepthSampleEvaluation,
         DepthValidationAggregator,
         build_validation_gt_dataset,