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

Check if user-provided model component names conflict with pyaugmecon-added component names #23

Open
npaterakis opened this issue Feb 24, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@npaterakis
Copy link
Collaborator

Method convert_prob in class Model modifies the user-provided pyomo model by adding new components.
If the model of interest contains a component with the same name as one of the components that are added by the convert_prob method it will be "overwritten" resulting in errors that are hard to trace.

Thus, there are some reserved component names against which the component names in the user-provided model must be checked and, in case of conflict, guide the user to fix them.

@wouterbles I already have a solution for this. It appears that there are only 4 components ({'Os', 'Slack', 'e', 'con_list'}) added to the model, but it would be good to rename them first.

@npaterakis npaterakis added the enhancement New feature or request label Feb 24, 2024
@npaterakis npaterakis self-assigned this Feb 24, 2024
@npaterakis
Copy link
Collaborator Author

A (temporary) solution was included in 1.0.8. However, it still makes sense to rename the reserved component names.

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