Unit Commitment on PGLib-UC Against HiGHS Better / equal / worse instance counts against HiGHS on the official model.Full result, charts and conditions ↗
THE PRODUCT, IN PRACTICE
Commit and dispatch generators with certified objectives
Schedule generator commitment and dispatch on power-system models with certified objectives. It is a newer Garmo Solvers module from the October 2026 benchmark campaign, outside the 1.0.2 release. Results are checked against the original input; the measured result below states where it is ahead and where it is not.
BUILT FOR
Power-system operators, market analysts and planning teams with unit-commitment workloads.
CHALLENGES → PRODUCT RESPONSE
The problem you face. What the product changes.
YOUR CHALLENGEWITH UNIT COMMITMENT
01
The problem needs the right operation
A unit-commitment model in the PGLib-UC format.
Schedule generator commitment and dispatch on power-system models with certified objectives.
02
A result must answer the original question
An answer detached from its original constraints or input is difficult to rely on.
The suite rechecks the answer against the original input and identifies the applicable result state.
03
The comparison needs a defined scope
A capability or benchmark result is not a universal promise for a different workload.
Evaluate the selected input, resource budget, complete cost and required certificate against your baseline.
WHAT YOU GET
A defined capability. A useful result.
01
Selected solving capability
Schedule generator commitment and dispatch on power-system models with certified objectives.
02
Original-input result
A commitment and dispatch schedule; the objective is certified by re-solving the official model with the commitment fixed.
03
Common access
Run it as garmo uc or through the garmo-mcp server; headless execution fits scripts and automated workflows.
04
Checked result
Every reported objective is certified on the official model, with the lower bound stating the remaining gap.
GARMO SOLVERS / MEASURED RESULT
Measured: 11/5/6 vs HiGHS
On 22 PGLib-UC instances at 600 s: 11 wins, 5 ties and 6 losses against HiGHS on the official MIP at 1 core; 13/4/5 at 16 cores. On the California 2014 cases HiGHS finds no solution in 600 s; this module certifies 48,233 against a bound of 48,226. On the FERC instances neither solver finds a solution.
Source: Garmo Labs benchmark campaign, October 2026. Results apply to the stated inputs, hardware and conditions; they are not universal competitor rankings.
A customer has a supported model and wants an accepted result without adopting every other module.
Illustrative customer use—not a new benchmark or completed customer deployment.
01→
Provide the original input and define the useful outcome.
02→
Run the selected module under its supported resource and interface scope.
03→
Review the returned answer, original-input checks and completion state.
FIT & ACCEPTANCE
Start with the task. Agree the useful outcome.
What you bring
A unit-commitment model in the PGLib-UC format.
What a useful evaluation measures
+Accepted original-model result
+Appropriate certificate or disclosed uncertified state
+Total time, memory and operating cost
Delivery
License the selected capability, commission an implementation, or agree an operated service. Infrastructure and additional engineering are specified separately.
QUESTIONS BEFORE BUYING
A clear scope. A clear relationship.
What is the important boundary?−
A certified objective for a returned schedule is not a global-optimality proof; the reported lower bound states the remaining gap.
How is it priced?+
No new standalone price is supplied for this product; request a scoped proposal. The platform plans buy qualified workflows and capacity, not a second charge every time a compatible method is selected. Existing bundle inclusions do not expand automatically.
How do we get access?+
Available through garmo CLI and garmo-mcp, including headless execution. Product-specific inputs, runtime dependencies, budgets and result checks remain explicit.
PUT THE PRODUCT TO WORK
Tell us what needs to improve.
Bring a task, an accepted outcome and the environment in which the product needs to work.
Select the capability you need directly or include its compatible role in a qualified platform workflow. Production scope identifies release, environment, capacity and support; a product count is not an entitlement.
