Miroslav Simko <ms@iolabs.ch> 2026-09-02T08:58:10+02:00
Commit #62 ยท 3 snippets
guardrails/__init__.py | 2 +- guardrails/config.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
| 3 | Mirrors the config convention used by the iolabs point-cloud packages | 3 | Mirrors the config convention used by the iolabs point-cloud packages |
| 4 | (``iolabs_point_cloud_segmentation_trajectory`` etc.): the package owns a | 4 | (``iolabs_point_cloud_segmentation_trajectory`` etc.): the package owns a |
| 5 | ``guardrails.default.json`` algorithm config, and a typed params object | 5 | ``guardrails.default.json`` algorithm config, and a typed params object |
| 6 | (:class:`DetectorConfig`) is loaded from it at CLI start. Runtime overrides are | 6 | (:class:`DetectorConfig`) is loaded from it at CLI start. Runtime overrides are |
| 7 | applied through repeatable ``--set PATH=VALUE`` flags, never repo-local JSON. | 7 | applied through repeatable ``--set KEY=VALUE`` flags, never repo-local JSON. |
| 8 | ``config.py`` is the loader/schema: the pydantic model field set is the schema | 8 | ``config.py`` is the loader/schema: the pydantic model field set is the schema |
| 9 | and every field default is kept identical to ``guardrails.default.json`` | 9 | and every field default is kept identical to ``guardrails.default.json`` |
| 10 | (guarded by a unit test), so ``DetectorConfig()`` and ``load_config()`` agree. | 10 | (guarded by a unit test), so ``DetectorConfig()`` and ``load_config()`` agree. |
| 11 | 11 |
| 1 | """Classical geometric guardrail detection for MLS point clouds.""" | 1 | """Classical geometric guardrail detection for MLS point clouds.""" |
| 2 | 2 | ||
| 3 | __version__ = "0.1.0" | 3 | __version__ = "0.2.1" |
| 4 | 4 |
| 3 | Mirrors the config convention used by the iolabs point-cloud packages | 3 | Mirrors the config convention used by the iolabs point-cloud packages |
| 4 | (``iolabs_point_cloud_segmentation_trajectory`` etc.): the package owns a | 4 | (``iolabs_point_cloud_segmentation_trajectory`` etc.): the package owns a |
| 5 | ``guardrails.default.json`` algorithm config, and a typed params object | 5 | ``guardrails.default.json`` algorithm config, and a typed params object |
| 6 | (:class:`DetectorConfig`) is loaded from it at CLI start. Runtime overrides are | 6 | (:class:`DetectorConfig`) is loaded from it at CLI start. Runtime overrides are |
| 7 | applied through repeatable ``--set PATH=VALUE`` flags, never repo-local JSON. | 7 | applied through repeatable ``--set KEY=VALUE`` flags, never repo-local JSON. |
| 8 | ``config.py`` is the loader/schema: the pydantic model field set is the schema | 8 | ``config.py`` is the loader/schema: the pydantic model field set is the schema |
| 9 | and every field default is kept identical to ``guardrails.default.json`` | 9 | and every field default is kept identical to ``guardrails.default.json`` |
| 10 | (guarded by a unit test), so ``DetectorConfig()`` and ``load_config()`` agree. | 10 | (guarded by a unit test), so ``DetectorConfig()`` and ``load_config()`` agree. |
| 11 | 11 |
nullconfig sections fall back to section defaults (pre-migration behaviour), re-validation instead ofmodel_copy(update=), doc/test parity with the packaged JSON.