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

Consider adding a replicate index to all variables #44

Closed
ccoffrin opened this issue Nov 16, 2016 · 3 comments
Closed

Consider adding a replicate index to all variables #44

ccoffrin opened this issue Nov 16, 2016 · 3 comments

Comments

@ccoffrin
Copy link
Member

To more readily support multi-time models.

@ccoffrin
Copy link
Member Author

from @rb004f, "More generally we'd also want to index by scenario, or perhaps other reasons"

Good point! It should be a fairly general way to include multiple network copies in one JuMP model. The constraints you add to link those variables together would differ based on these different applications.

@ccoffrin ccoffrin changed the title Consider adding time index to all variables Consider adding a replicate index to all variables Jun 28, 2017
@ccoffrin
Copy link
Member Author

ccoffrin commented Aug 5, 2017

To enable this we need to, move all variable constructors to JuMP anonymous variables and add our own methods for organizing and looking up these variables. This will also will resolve the issue of how to have two Infrastructure Models in one JuMP model.

@ccoffrin
Copy link
Member Author

ccoffrin commented Aug 5, 2017

Proposal, pm.var[:p] for looking up variables. We can also considering adding getvar and getref methods for handling various default cases (e.g. with and without variable lookup)

@ccoffrin ccoffrin added this to the Release v0.5 milestone Aug 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant