Skip to content

Refactor and enhance documentation throughout the codebase #29

Open

Description

@johnh2o2

Update and improve all documentation for cuvarbase, including docstrings, the README, and usage examples. Ensure all public functions and classes have clear docstrings, and that the README accurately reflects current capabilities and installation instructions. Add or update example notebooks or scripts for users.

Activity

  1. johnh2o2 commented on Jun 12, 2026

    @johnh2o2
    OwnerAuthor

    v1.0 status. Delivered under this umbrella in the packed release:

    • PDM: full Sphinx page (docs/source/pdm.rst) + API docs (community PR PDM refactorization and kernel speedup #62)
    • Sphinx autodoc now covers every post-0.2.6 module (bls_frequencies, cufinufft_backend, the experimental TLS modules, the memory/base subpackages)
    • Power-spectrum convention sections in bls.rst/lomb.rst (Document + maybe add some flexibility for powerspectrum convention #17)
    • README significance pass + benchmark docs (docs/BENCHMARK_RESULTS.md), with claims either traced to repo data or rephrased
    • Docstring corrections wherever the audit found claims contradicting behavior (TLS limits, cuFINUFFT backend, batch BLS, pinned-memory naming, FAP heuristics)

    Deferred (v1.1): the all-public-API docstring audit and updated example notebooks. Leaving open for those.

  2. johnh2o2 commented on Sep 28, 2026

    @johnh2o2
    OwnerAuthor

    Release triage for PR #69 (cuvarbase 1.0.1, source 6b6c48945160).

    This issue remains open and is listed as related follow-up in PR #69; it is intentionally excluded from automatic closure.

    The source has updated guides, release/migration notes, examples and corrections to numerical/performance claims. The owner’s June 12 comment left the complete public-API docstring audit and refreshed notebooks open. The current suite still records the known PDM notebook string-escape warning as a strict expected failure. Remaining: finish the full public-API documentation audit and update/validate the notebooks, including that known warning.

    Evidence: API documentation index · known PDM notebook warning tracked by a strict expected failure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions