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

Revise the naming convention for everything (e.g., p_*) #123

Closed
Tracked by #61
abelsiqueira opened this issue Sep 27, 2023 · 0 comments · Fixed by #139
Closed
Tracked by #61

Revise the naming convention for everything (e.g., p_*) #123

abelsiqueira opened this issue Sep 27, 2023 · 0 comments · Fixed by #139
Assignees
Labels
Type: improvement Better way of doing something Zone: data & import Interfacing between database and Julia Zone: optimisation model Improvements or changes to the optimisation model (e.g., objective function, variables, constraints)

Comments

@abelsiqueira
Copy link
Member

abelsiqueira commented Sep 27, 2023

Since we are using params and sets, we don't need to prefix with p_ and s_.

@datejada datejada added Type: improvement Better way of doing something Zone: optimisation model Improvements or changes to the optimisation model (e.g., objective function, variables, constraints) Zone: data & import Interfacing between database and Julia labels Sep 27, 2023
@datejada datejada mentioned this issue Oct 4, 2023
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: improvement Better way of doing something Zone: data & import Interfacing between database and Julia Zone: optimisation model Improvements or changes to the optimisation model (e.g., objective function, variables, constraints)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants