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

[TASK] Choose solver for Pyomo dispatcher #96

Closed
10 tasks done
PaulTalbot-INL opened this issue Aug 12, 2021 · 0 comments · Fixed by #97
Closed
10 tasks done

[TASK] Choose solver for Pyomo dispatcher #96

PaulTalbot-INL opened this issue Aug 12, 2021 · 0 comments · Fixed by #97
Labels
priority-normal tasks that may be time sensitive, but are not necessarily critical task Feature requests

Comments

@PaulTalbot-INL
Copy link
Collaborator

PaulTalbot-INL commented Aug 12, 2021 •
edited by dylanjm
Loading

Issue Description

Right now the solver used in the pyomo_dispatch is determined based on the OS without user input.

It would be nice to give optional flexibility to the user.

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@PaulTalbot-INL PaulTalbot-INL added task Feature requests priority-normal tasks that may be time sensitive, but are not necessarily critical labels Aug 12, 2021
@PaulTalbot-INL PaulTalbot-INL mentioned this issue Aug 12, 2021
Merged
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority-normal tasks that may be time sensitive, but are not necessarily critical task Feature requests
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Pyomo solver option PaulTalbot-INL/HERON
1 participant
@PaulTalbot-INL