Week 6 - Abstract Model Refactoring, Unified Testing & CI Setup

In the past week, my main focus was on refactoring the model layer, improving test coverage, and streamlining project automation.

Progress:

  • New Abstract Model Class:
    Introduced AbstractLPModel as the new central class to dynamically manage variables, constraints, and all model metadata. Instead of fixed arrays, the class uses flexible lists and maps. The final model is only constructed when calling build().

  • Consistent Mapping & ID Tracking:
    Implemented clear mapping from names to indices for all variables and constraints, preventing duplicate IDs and making debugging easier.

  • Unit Tests for Model Abstraction:
    Added a new test class (AbstractLPModelTest) covering variable/constraint addition, the build process, and redundancy cases. Exception handling for duplicate names is implemented and tested.

  • CI/CD Pipeline:
    Set up a GitHub Actions workflow that automatically builds and tests every commit and pull request. Errors are shown directly in the PR for quick feedback.

  • Unified Adapter Tests:
    Standardized all LP test cases so that CommonsMath and OjAlgo adapters are tested on exactly the same features (bounds, minimization/maximization, error handling).

  • Code Quality:
    Improved JavaDocs and ensured clean, consistent code for all model, adapter, and test classes.

  • Project Structure:
    Maintained clear separation of main and test code, stable Maven/Java environment, and consistent use of feature branches.

  • Improved Logging and Error Handling:
    The model now supports optional debug logging. With debugging enabled, all key operations (adding variables, constraints, and building the model) provide log output. In addition, the model now uses a “fail fast” approach: if you try to add a duplicate variable or constraint, an error is thrown and logged immediately. This makes debugging and testing much more straightforward compared to traditional APIs.

Next Steps:

  • Refactor the solver adapters so they accept only the finalized model object.

  • (Optional) Extend redundancy tests for intentional duplicate variable/constraint names.

  • Expand the README and developer documentation.

  • If the new interface is approved by the mentors, begin integration of CommonsMathSolver, OjAlgoSolver and the additional solvers GLPK, CBC, and 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