Skip to content

Repo completion — v0.2.0 hardening, program README sync, design cleanup #17

Description

@rosspeili

Context

Individual feature issues (#1#16) can merge incrementally. This wrap-up issue tracks everything needed to call spintronic-qrc code-complete at the same bar as spinq-vqe v0.1.2:

  • All 6 notebooks executed with committed outputs
  • benchmarks/ scripts runnable
  • Tests green on default [dev] and optional extras documented
  • pyproject.toml version bump
  • Program-level Spintronics/README.md status updated from Not started to complete/in-progress with validated result
  • Stale docs removed (scaffold language, wrong docstring DOIs)

User owns git tags and GitHub releases — do not create tags in this issue.

Goal

Single consolidation PR that brings the repo to v0.2.0 (or agreed version) with no loose ends.

Checklist

Code and tests

  • pytest spintronic-qrc/tests/ -v — all pass on [dev]
  • Document optional test commands:
    pip install -e "./spintronic-qrc[open,dev]" && pytest ...
    pip install -e "./spintronic-qrc[crossval,dev]" && pytest ...
  • ruff check src/ tests/ — clean or documented ignores
  • init.py all exports match public API in docs/api.md
  • Fix stale docstring DOIs (e.g. reservoir.py still cites wrong Dambre IEEE TNN — use Sci. Rep. 10.1038/srep00514)

Notebooks and outputs

  • All 6 notebooks in notebooks/ execute top-to-bottom
  • figures/*.png committed (6 minimum from notebook plan)
  • data/*.csv committed from notebooks + benchmarks/

Benchmarks

  • python benchmarks/run_all.py --quick passes in CI-smoke time
  • Full benchmark run documented in benchmarks/README.md with expected runtime

Documentation

Program integration

Update Spintronics/README.md (parent program repo) sections:

Section Change
Section 10 repo table spintronic-qrc: Not started -> Complete (v0.2.0) or In progress with NARMA baseline
Section 12 execution order Repo 2 status updated
spintronic-qbench activation NARMA-10 QRC baseline: mark done if Issue #4 shipped

Add one-line validated result (e.g. NARMA-10 test_nmse QRC vs ESN) in Repo 2 subsection.

Only edit parent README if this issue explicitly includes program repo — assignee confirms scope.

GitHub repo card (manual, document in PR)

Reminder for maintainer (not automated):

  • Description, topics, website already suggested in prior session
  • Create release v0.2.0 when ready (user action)

Acceptance criteria

  • Version 0.2.0 in pyproject.toml and CITATION.cff
  • CHANGELOG [0.2.0] entry complete
  • Full pytest [dev] green
  • run_all.py --quick green
  • No .gitkeep-only directories that should have content (notebooks/, benchmarks/, data/, figures/)
  • OVERVIEW deliverables all checked except paper if still draft
  • Parent Spintronics/README.md updated OR separate follow-up issue linked

Files likely touched

  • pyproject.toml
  • CITATION.cff
  • CHANGELOG.md
  • OVERVIEW.md (final pass)
  • README.md
  • docs/testing.md
  • Spintronics/README.md (parent, if in scope)
  • Various docstring DOI fixes

Depends on

Blocks

  • Program Repo 3 (mtj-quantum-noise) start with QRC baseline confirmed
  • spintronic-qbench QRC task ingestion
  • Public v0.2.0 GitHub release (user-owned)

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions