Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate objective deactivation #22

Open
npaterakis opened this issue Feb 24, 2024 · 0 comments
Open

Automate objective deactivation #22

npaterakis opened this issue Feb 24, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@npaterakis
Copy link
Collaborator

Currently the user has to deactivate the objective functions in obj_list before returning their pyomo model. If it is forgotten, an error will be raised as soon as a model instance has to be solved. The error message is quite intuitive (Solver interface does not support multiple objectives). However, I think this should be easy to automate for a neater user workflow:

  • Add a new method in the Model class
  • Call it at the beggining of the solve method in the PyAugmecon class

The models in the tests directory would have to be updated, but I don't expect an error if the user deactivates the objective functions anyway.

@npaterakis npaterakis added the enhancement New feature or request label Feb 24, 2024
@npaterakis npaterakis self-assigned this Feb 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant