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.

Sign up for GitHub

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

Jump to bottom

Change composition rules for Decision #39

Closed
matthewcrews opened this issue May 29, 2020 · 1 comment · Fixed by #41
Closed

Change composition rules for Decision #39

matthewcrews opened this issue May 29, 2020 · 1 comment · Fixed by #41
Labels
enhancement New feature or request

Comments

@matthewcrews
Copy link
Collaborator

Right now it is clunky to get the result from the Solution type since the values for the Decisions are in a Map<DecisionName,float. While the reasoning for this was to ease the composition for the model, it makes actually extracting the results clunky.

I propose to make modeling slightly more complex but to dramatically ease the extraction of results by not have the create Decision functions return LinearExpression.
@matthewcrews matthewcrews added the enhancement New feature or request label May 29, 2020
@matthewcrews
Copy link
Collaborator Author

Might as well see if we can create a meaningful DecisionBuilder

This was referenced May 29, 2020
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Document domain fslaborg/flips
1 participant
@matthewcrews