Week 7 - Model Refinement, Code Cleanup, and Solver Integration

In the past week, my main focus was on refining the model abstraction, further cleaning the codebase, and once again, integrate the CommonsMathSolver into the solver interface.

Progress:

  • Model Refinement with Built Flag:
    Added a built flag to AbstractLPModel to clearly indicate when the model is finalized. After calling build(), the flag is set to true. Any subsequent changes reset the flag to false until the model is rebuilt. This mechanism ensures clarity about the model's state throughout its lifecycle.

  • Utility for Constraint Indices:
    Implemented a utility method that retrieves the index of a given constraint within the model. This allows adapters or other classes easy access to constraint indices without redundant logic.

  • Continuous Integration Improvements:
    Ensured the CI pipeline via GitHub Actions runs all unit tests smoothly and without errors, providing instant feedback on new code contributions and pull requests.

  • Explicit Double Types in Tests:
    Added the explicit type suffix (d) to all double literals within unit tests, clearly marking them as doubles and improving readability.

  • Extracted Optimization Goal Enum:
    Moved the optimization goal (MAXIMIZE/MINIMIZE) enum into a dedicated file, following best Java architecture practices. This enhances reusability across classes and avoids tight coupling.

  • Mapping Index Logic Relocated to Model:
    Removed the direct handling of indices from variables and constraints, centralizing the mapping logic within the model itself. This reduces complexity in the solver adapters.

  • Enhanced Future-Proof Logging:
    Replaced fixed logging strings with dynamically generated class names and used Java's MessageFormat for constructing log messages. This approach is flexible and robust, reducing maintenance if class or method names change in the future.

  • CommonsMathSolver Integration:
    Successfully integrated the CommonsMathSolver into the unified solver interface (ILPSolver). The solver is now fully operational and demonstrated via the SolverDemo class.

Next Steps:

  • Review the correctness and suitability of the model’s built-flag mechanism in further Unit tests.

  • Reuse the unit tests from the old Interface for the SimplexSolver and import them into the new interface.

  • Integrate the current Interface into SBSCL to test if the integration was done correctly.

  • If possible, expand the documentation (README, developer docs).

  • If the first solver works in SBSCL, continue with the integration of the remaining solver adapters (OjAlgo, GLPK, CBC, SCIP).

That's it for this week, see you next week!

Project Details:

Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

OptSolvX in SBSCL: A Solver-Agnostic LP Core (GSoC 2025 Final Report)

Bild
Enhancing the Systems Biology Simulation Core Library (SBSCL) with a Solver-Agnostic Framework for Constraint-Based Simulation and Analysis National Resource of Network Biology (NRNB) Google Summer of Code 2025 Final Report Name Michael Gaas Mentors           Prof. Dr. Andreas Dräger, Matthias König Overview This work modernizes constraint-based simulation in the Systems Biology Simulation Core Library (SBSCL) by introducing a solver-agnostic linear programming (LP) core (OptSolvX), a thin integration layer within SBSCL, and a bridge from SBML/FBC to linear programs. The objective is to restore robust, portable Flux Balance Analysis (FBA) on current platforms, including ARM-based systems, while preserving SBSCL’s public API and keeping solver-specific concerns decoupled from biological model handling. Implementation Summary OptSolvX provides a minimal, solver-agnostic LP domain model with AbstractLPModel, Variable, Constraint, OptimizationDirection,...
Mehr anzeigen

Week 2 – Community Bonding Wrap-Up

Community Bonding Period - Getting Ready for SBSCL The community bonding period is coming to an end, and the actual coding phase is about to begin. Over the past two weeks, I've spent my time getting familiar with the Systems Biology Simulation Core Library (SBSCL) and preparing for my GSoC project. During this initial phase, I focused on understanding how SBSCL uses SBML (Systems Biology Markup Language) to simulate biological models. My primary interest was in constraint-based simulations, particularly Flux Balance Analysis (FBA). My project aims at enhancing SBSCL by developing a solver-agnostic framework, ensuring compatibility with different solvers and hardware platforms, including newer ARM-based systems like Apple's M-series processors. I gained deeper insight into FBA as a computational method used to calculate the optimal flow of metabolites through metabolic networks to achieve specific biological goals, such as maximizing biomass or minimizing nutrient usage. Howeve...
Mehr anzeigen

Week 5 - Unit Testing, OjAlgo Integration, and Code Cleanup

In the past week, my primary goal was enhancing the test infrastructure, finishing the integration of the second solver, OjAlgo, and maintaining overall code quality and clarity. Progress: Unit Tests for CommonsMathSolver Implemented unit tests covering maximization, minimization, variable bounds, equality constraints, unsolvable and unbounded LP scenarios, and precision checks. Standardized test logic and provided clear comments aligned with Commons Math documentation and architecture. Test Environment Stabilization Fully synchronized Maven and IntelliJ configurations, eliminating issues with dependencies (JUnit, etc.) and resolving ClassNotFoundException permanently. Cleaned up the project structure by separating test and main code, removing obsolete files, and ignoring IDE-specific files ( .idea , .iml ) from version control. Development of Second Solver Adapter ( OjAlgoSolver ) Created a new adapter implementation to the ILPSolver   interface. S...
Mehr anzeigen