jump-dev / jump-dev/open-energy-modeling-benchmarks
LP capacity expansion problem benchmark
- Dominant language
- MATLAB
- Stars
- 27
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I have a .lp file generated from Pyomo (using openTEPES - https://github.com/IIT-EnergySystemModels/openTEPES/) that is an order of magnitude slower than a commercial solver, and was wondering if it'd be useful to include as a benchmark.
I've attached the file here (20mb zipped, 425mb unzipped): [run1-lp-file.zip](https://github.com/user-attachments/files/17088472/run1-lp-file.zip)
It takes roughly 60 minutes to run on a Mac with HiGHS. On Windows, this hangs indefinitely. I left it running for a few hours and then killed the process, I believe the hanging is related to this issue: https://github.com/ERGO-Code/HiGHS/issues/1044.
With a commercial solver, this lp file solves in a few minutes.
fwiw there's a smaller problem with the same formulation (i.e. same constraints but over fewer time periods - 1 week instead of 1 year) that you can run in a few minutes with HiGHS here: https://github.com/IIT-EnergySystemModels/openTEPES/blob/6f70339e11daaea3f372c06e035dd9a021b6d4b1/tests/test_run.py
Contributor guide
No contributing guide indexed for this repository
Research direction
Download and inspect the attached run1-lp-file.zip, then compare it with the smaller openTEPES example linked in tests/test_run.py. Check how this repository records benchmarks and whether the large LP file can be added with reproducible HiGHS runtime expectations. Done means the capacity-expansion case is included as a usable benchmark with its solver behavior documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100