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

Add ramping and unit commitment basic constraints #726

Merged
merged 21 commits into from
Aug 23, 2024

Conversation

clizbe
Copy link
Member

@clizbe clizbe commented Aug 5, 2024

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

  • I read and followed the instructions in README.dev.md
  • The documentation is up to date with the changes introduced in this Pull Request (or NA)
  • Tests are passing
  • Lint is passing

@clizbe clizbe force-pushed the 581_ramping_constraints branch 2 times, most recently from ec71469 to 110b75b Compare August 6, 2024 15:27
Copy link

codecov bot commented Aug 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (a447277) to head (7c5cb20).
Report is 2 commits behind head on main.

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.
📢 Have feedback on the report? Share it here.

@datejada
Copy link
Member

@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.

@clizbe
Copy link
Member Author

clizbe commented Aug 21, 2024

@datejada I think I rebased correctly.
But also I've gotten busy with a lot of other stuff before my vacation. Can we hand off and you continue it? I left a lot of notes in the code, but I can also explain it.

@datejada
Copy link
Member

@datejada I think I rebased correctly. But also I've gotten busy with a lot of other stuff before my vacation. Can we hand off and you continue it? I left a lot of notes in the code, but I can also explain it.

I got you! No worries 😉

@datejada datejada changed the title Add optional ramping constraints Add ramping and unit commitment basic constraints Aug 22, 2024
@datejada datejada marked this pull request as ready for review August 23, 2024 11:52
Copy link
Member

@abelsiqueira abelsiqueira left a 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.

src/input-schemas.jl Show resolved Hide resolved
src/input-schemas.jl Outdated Show resolved Hide resolved
src/constraints/ramping-and-unit-commitment.jl Outdated Show resolved Hide resolved
src/create-model.jl Outdated Show resolved Hide resolved
src/create-model.jl Outdated Show resolved Hide resolved
datejada and others added 2 commits August 23, 2024 15:44
Co-authored-by: Abel Soares Siqueira <nepper271@gmail.com>
@datejada
Copy link
Member

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.

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!

Copy link
Member

@abelsiqueira abelsiqueira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@datejada datejada merged commit d795f54 into TulipaEnergy:main Aug 23, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add optional ramping constraints
3 participants