Skip to content

[Tracking] libdedx health review — correctness, API hygiene, docs & ecosystem (web + Python) #108

Open
0 of 9 issues completed

Description

@grzanka

libdedx health-review epic

A full read-through of libdedx (source, headers, embedded data, tests, CI, Python binding, docs).

Verdict: the repo is in good shape. It configures and builds cleanly with CMake; all 27 ctests pass, including physics reference-value tests against NIST PSTAR/ASTAR and ICRU/MSTAR at a 0.5 % relative tolerance. CI is solid (Linux + Windows build/test, Valgrind leak check, coverage, clang-format, clang-tidy, Python tests on 3.9/3.13, docs). Stopping-power data is embedded into headers (no runtime file deps), and the public headers are well Doxygen-documented.

So no emergency refactor is required to trust the numbers. This is a parent tracking issue: the work is broken into focused child issues, each with its own context and acceptance criteria. Priorities reflect the stated goals — correct physics first, then API hygiene, then explaining purpose/role, then the web + Python ecosystem.

Verification: cmake -S . -B build && cmake --build build && ctest --test-dir build → 27/27 passed (Linux, gcc).

P0 — Correctness & trust

P1 — API hygiene & robustness

P2 — Documentation: purpose & role

P3 — Ecosystem: web frontend & Python wrapper

Backlog — future physics


New child issues (#109–#117) were created by an automated health review (Claude Code); pre-existing issues are linked, not re-parented unless noted.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions