allow constant in objective cost function #539
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #236
Changes proposed in this Pull Request
Allow the objective cost function to contain a constant. While the constant is not needed for optimization, it can make life easier in some cases (see linked issue for discussion).
It was previously forbidden to have a constant in the objective cost function, I assume this is because most solvers expect the ocf to only contain variables.
To get around this without having to touch too many different parts of code, I allowed the objective function itself to have a constant, but added some special logic to deal with constants in a decorator for Model.solve.
Before solving, the constant part is removed, after solving it is added again.
Checklist
doc.doc/release_notes.rstof the upcoming release is included.