This repository has been archived by the owner on Dec 7, 2021. It is now read-only.
Add validation of sizes of arguments of OptimizationResults and unit tests #1167
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.
Summary
OptimizationResult
newly introducedvariables
class variables in #1122.But, there is not enough check of arguments. So I added a check of sizes of
OptimizationResult._x
andOptimizationResult._variables
.I fix bugs of generation of
OptimizationResult
detected by this check.#1131 modifies the way to interpret
OptimizationResult
so thatOptimizationResult
becomes read-only.But, some
interpret
did not treatvariables
correctly. I notice that there is no unit test aboutOptimizationResult.variable_names
andOptimizationResult.variables_dict
.So I added some relevant unit tests.
Details and comments