Skip to content

fix(trace): invert ConvergenceRate so higher means faster - #23

Open
MrBeldum wants to merge 2 commits into
loop-eng:mainfrom
MrBeldum:fix/1-convergence-rate-semantics
Open

fix(trace): invert ConvergenceRate so higher means faster#23
MrBeldum wants to merge 2 commits into
loop-eng:mainfrom
MrBeldum:fix/1-convergence-rate-semantics

Conversation

@MrBeldum

Copy link
Copy Markdown

Summary

computeSummary set ConvergenceRate = firstSuccess / totalIterations, so succeeding on iteration 1 scored lower than succeeding late.

Invert per #1: 1.0 - (firstSuccess-1)/totalIterations so first-try = 1.0 and last-try ≈ 0. Unchanged when there is no successful verification (stays 0).

Fixes #1

Test plan

  • go test ./internal/trace/ -count=1
  • Regression: first-try > last-try; no-success stays 0

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.

ConvergenceRate has inverted semantics

1 participant