-
Notifications
You must be signed in to change notification settings - Fork 18
Feat: set OptSolvX
as default LP backend; add SBML-FBC→LP bridge prototype
#90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
xts-Michi
wants to merge
22
commits into
draeger-lab:master
Choose a base branch
from
xts-Michi:feat/optsolvx-default
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… ctor) and changed the pom OptSolvX verison to java 8
…nds, S·v=0, objective) into OptSolvX
…ective tests using jdk 8 artifact
…e FbaToOptSolvX preview
draeger
requested changes
Aug 21, 2025
<groupId>org.optsolvx</groupId> | ||
<artifactId>optsolvx</artifactId> | ||
<version>0.1.0-SNAPSHOT</version> | ||
</dependency> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please place a local lib file of OptSolvX and use a local dependency for the time being, until we have it in MavenCentral.
…oting note (JDK ≥17)
…lues), ignore boundary/no-participation species, and multi-species cases with minimal SBML builders
…refs) — OptSolvX is now the sole LP solver
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Switch FBA to OptSolvX by default, introduce an initial SBML-FBC→LP bridge, fix dependency/classpath issues for modern JDKs, and remove the legacy SCPSolver/GLPK backend.
What changed since the last review
NewGLPKSolver
and SCPSolver test (SCPSolverIssue
); no SCPSolver/GLPK deps remain in code or POM.BridgeConstraintTests
) and minor perf tidy-ups in the bridge (cached SBML lists, pre-sized maps).getActiveObjective()
in FBA for API/test compatibility.Key changes
1) Default backend = OptSolvX
OptSolvXSolverAdapter
.2) SBML-FBC → LP bridge (prototype)
FbaToOptSolvX
maps:Small perf pass: cache SBML lists, pre-size maps.
3) Dependency / classpath
org.apache.commons:commons-math:2.2
for legacy ODE API (Math2) next tocommons-math3:3.6.1
.xercesImpl
,xml-apis
,xalan
) to avoid JAXP conflicts with modern JDKs (Log4j2 config now clean).4) Cleanup: remove SCPSolver/GLPK
src/test/scripts/**
still references old GLPK jars only for the historic wrapper; it’s inert for Maven builds and can be pruned later.5) Tests & layout
Bridge smoke/objective:
BridgeSmokeTest
,BridgeObjectiveTest
.New:
BridgeConstraintTests
checking S·v=0 at coefficient level:Tests live under
src/test/java/org/simulator/optsolvx
.6) Docs / build hygiene
How to test
Typical runtime (E. coli core):
Compatibility
getActiveObjective()
restored; tests depending on it pass.Follow-ups