Skip to content

Trim docs and comments to current-state-only prose - #716

Merged
edkerk merged 2 commits into
develop3from
docs/trim-to-current-state
Aug 29, 2026
Merged

Trim docs and comments to current-state-only prose#716
edkerk merged 2 commits into
develop3from
docs/trim-to-current-state

Conversation

@edkerk

@edkerk edkerk commented Aug 28, 2026

Copy link
Copy Markdown
Member

Summary

Full-codebase pass over help blocks, inline comments, and top-level docs (229 .m files + 7 markdown files reviewed; 49 changed). Cut:

  • Historical narrative: "previously X, now Y", dated asides, version/PR-era commentary.
  • General hedging and padding: "in order to", "generally", speculative TODO-style asides.
  • Redundant restatement (a help-block sentence repeating the H1 description, etc.).

Kept as-is:

  • Every load-bearing rationale: MILP formulations, numerical-tolerance gotchas, platform/solver limitations, correctness warnings.
  • All parameter/return documentation and examples.
  • Files that were already terse (most of analysis/, gapfilling/, solver/, etc. — left untouched).

Generated documentation (doc/), vendored third-party code (software/), license text, and the changelog were out of scope entirely.

Comments and docstrings only — no functional code touched (verified: every changed line in every file is either inside a %-comment or a trailing comment on an otherwise-unchanged code line).

Test plan

  • testing/function_tests/* full suite — 298 passed, 0 failed, 8 filtered (pre-existing environment gates: missing quadprog/network data/Parallel Computing Toolbox branches, unrelated to this change)
  • Diffed every changed file for non-comment lines — confirmed zero functional code changes

Help blocks, inline comments, and top-level docs across the codebase
described how things got here instead of just what's true now:
version/PR history, "previously X now Y" narration, dated asides,
migration-era provenance notes, and general hedging/AI-speak padding.

Cut all of that. Kept every load-bearing rationale (MILP formulations,
numerical gotchas, platform/solver limitations, correctness warnings)
and all parameter/return documentation as-is. Left already-terse files
untouched.

Comments and docstrings only; no functional code changed.
@github-actions

github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown

Function test results

303 tests   276 ✅  1m 7s ⏱️
 25 suites   27 💤
  1 files      0 ❌

Results for commit ec06919.

♻️ This comment has been updated with latest results.

Reviewed every help-block against end-user usefulness: does it say what
the function produces, and does it explain what each non-obvious
parameter controls, without narrating internal algorithm steps.

Fixes a few inaccuracies found along the way: ftINITFillGaps documented
a parameter that doesn't exist in its signature, groupRxnScores had the
groupIds convention backwards, and haveFlux's documented cutOff default
didn't match the code.
@edkerk
edkerk merged commit 8d650f1 into develop3 Aug 29, 2026
4 checks passed
@edkerk
edkerk deleted the docs/trim-to-current-state branch August 29, 2026 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant