timeLimit Parameter Ignored in pulp.FSCIP_CMD Solver
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 432
- PR merge metrics
- No merged PRs in 30d
Description
Details for the issue
--------------------
#### What did you do?
I attempted to use the timeLimit parameter with the pulp.FSCIP_CMD solver to restrict the optimization time for solving a linear programming problem. The parameter was set as an argument while initializing the FSCIP_CMD solver instance.
#### What did you expect to see?
I expected the solver to halt the optimization process when the specified time limit was reached, thereby respecting the time constraint set by timeLimit.
#### What did you see instead?
Despite specifying the timeLimit parameter, the solver seems to ignore this constraint and continues the optimization process beyond the set time limit. The optimization completes, but it does so in a time frame that exceeds the specified limit, indicating that the timeLimit parameter is not being effectively enforced or recognized by the solver.
Useful extra information
-------------------------
In pulp.SCIP_CMD, the parameter is fine as expected.
#### What operating system are you using?
- [ ] Windows: ( _version:_ ___ )
- [x] Linux: ( _distro:_ ___ )
- [ ] Mac OS: ( _version:_ ___ )
- [ ] Other: ___
#### I'm using python version:
- [ ] 2.7
- [ ] 3.4
- [ ] 3.5
- [ ] 3.6
- [x] Other: 3.10
#### I installed PuLP via:
- [ ] pypi (python -m pip install pulp)
- [x] github (python -m pip install -U git+https://github.com/coin-or/pulp)
- [ ] Other: ___ (conda?)
#### Did you also
- [ ] Tried out the latest github version: https://github.com/coin-or/pulp
- [x] Searched for an existing similar issue: https://github.com/coin-or/pulp/issues?utf8=%E2%9C%93&q=is%3Aissue%20
Contributor guide
Research direction
Start by comparing how timeLimit is handled in the pulp.FSCIP_CMD solver with the working pulp.SCIP_CMD implementation. Verify that the configured limit reaches the FSCIP solver, then confirm with a Linux Python 3.10 run that optimization stops within the requested limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100