Skip to content

remove: findMaxValue, dead code with no real callers and three confirmed bugs - #465

Merged
edkerk merged 1 commit into
develop4from
remove/find-max-value-dead-code
Aug 31, 2026
Merged

remove: findMaxValue, dead code with no real callers and three confirmed bugs#465
edkerk merged 1 commit into
develop4from
remove/find-max-value-dead-code

Conversation

@edkerk

@edkerk edkerk commented Aug 30, 2026

Copy link
Copy Markdown
Member

Summary

findMaxValue.m has never had a caller anywhere in the GECKO tree, and has three real bugs (confirmed by tracing both sides against the actual BRENDA data format both toolboxes now load — see raven-gecko-parity#81):

  • A stale 'EC' prefix means BRENDA matching can never succeed at all, wildcarded or not.
  • A broken wildcard slice compounds it independently.
  • A 0-vs-0 tie is mislabeled as a genuine 'SA*Mw' result instead of an empty match.

geckopy's find_max_value already gets all three right, so fixing dead code wasn't worth it — removed instead. Also drops its VerificationMatrix.tsv row.

Fixes raven-gecko-parity#81

Test plan

  • geckoCoreFunctionTests: 51 passed, 0 failed (RAVEN develop3 on path, glpk solver)

…med bugs

findMaxValue.m has never had a caller anywhere in the GECKO tree, and has
three real bugs: a stale 'EC' prefix plus a broken wildcard slice mean
BRENDA matching can never succeed at all (wildcarded or not), and a
0-vs-0 tie is mislabeled as a genuine 'SA*Mw' result instead of an empty
match. geckopy's find_max_value already gets all three right, so this is
one-sided dead weight rather than a real port target.

raven-gecko-parity#81
@github-actions

Copy link
Copy Markdown

Unit test results

51 tests   51 ✅  10s ⏱️
 1 suites   0 💤
 1 files     0 ❌

Results for commit 39d5dac.

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