Optimization direction from config file #62
Merged
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.
User can pick what parameters he wants to optimize + decide if parameter should be maximize or minimize
Description
Added new field in optimization config
.jsonfile, where the end user can specify the objective direction of the optimization loop. Possible to only minimize/maximize.Related Issues
Closes #42
How Has This Been Tested?
We encourage you to keep the code coverage percentage at 90% and above.
have not been included
Testing Environment:
Checklist
Ensure that all the following tasks are completed before submitting your PR:
pyproject.toml, anduv.lockhas been regenerated accordingly.Deployment Notes
Now in configuration.json files other than
"well_placement"field user has to specify"optimization_strategy"like so:{ "well_placement": [], "optimization_parameters": { "optimization_strategy": "maximize" } }