-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add ramping and unit commitment basic constraints #726
Conversation
ec71469
to
110b75b
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #726 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 17 18 +1
Lines 755 842 +87
=========================================
+ Hits 755 842 +87 ☔ View full report in Codecov by Sentry. |
@clizbe, the latest changes in the main branch conflict with your changes here for this development. They should be easy to resolve, but if you need some guidance or help, please let @abelsiqueira or me know. |
ca69549
to
1a0ba6e
Compare
1a0ba6e
to
ab441c7
Compare
@datejada I think I rebased correctly. |
I got you! No worries 😉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. I've made some comments in various places.
I see there are no changes to the tests (not the test data). Is that expected? The coverage passed, so the constrains are supposed to be generated. I imagine there is no easy way to test this, so I will leave to your decision.
Co-authored-by: Abel Soares Siqueira <nepper271@gmail.com>
Correct! The constraints are tested through the case study. It is not a bulletproof way to do it, but we need to come up with something simple to test the functions that creates the constraints that do not depend on the case studies. I will make an issue for that because we would like to be sure we test and get what we want. This might be a good thing to do after the refactoring. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Pull request details
Describe the changes made in this pull request
List of related issues or pull requests
Closes #724
Collaboration confirmation
As a contributor I confirm