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

Specify the domain of decommission variables #846

Merged
merged 6 commits into from
Oct 14, 2024

Conversation

gnawin
Copy link
Member

@gnawin gnawin commented Oct 8, 2024

Pull request details

Describe the changes made in this pull request

List of related issues or pull requests

Closes #828

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

@gnawin
Copy link
Member Author

gnawin commented Oct 8, 2024

@abelsiqueira @datejada It is more or less straightforward to do this for the decommission variable of the compact method, so I did this before the refactor.

The simple method is a bit more complex because it is indexed differently, i.e., not using an indice set yet, but it will be the same idea (and the conditions are very similar as well). Since we'll refactor, I did not do it for the simple method and rather do it in the factor.

Copy link

codecov bot commented Oct 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.90%. Comparing base (250318e) to head (e24557a).
Report is 18 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #846   +/-   ##
=======================================
  Coverage   99.90%   99.90%           
=======================================
  Files          20       20           
  Lines        1017     1021    +4     
=======================================
+ Hits         1016     1020    +4     
  Misses          1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@gnawin
Copy link
Member Author

gnawin commented Oct 8, 2024

@abelsiqueira both the link and the codecov/project fails are confusing to me, could you have a look? Thanks!

@gnawin gnawin marked this pull request as draft October 8, 2024 08:51
@abelsiqueira
Copy link
Member

For completeness, repeating some thigns from the chat here.

The link check failure is probably due to changes in the treatment of automated link checkers by the end points. Recommended solution is to ignore at the moment, and check after we apply Bestie (#676). If the error persists we can add it to the ignore list. This is safe to do for this website at least. We can think again for the others.
On a side note, it is actually possible to add it to the ignore list at .markdown-link-check.json right now, but we would need to go check how to run it locally

The Codecov error is probably because version "1" points to "1.11" now (JuliaLang/www.julialang.org#2160) and that affected how the coverage is processed.
Possible solutions:

  • Set a range of acceptable coverage instead of the 100% goal - it will be harder and harder to keep it at 100%, so this might be an incentive and the right time to do it
  • Change the for and remove the intermediary variable constraints_files.

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.

LGTM

@gnawin
Copy link
Member Author

gnawin commented Oct 8, 2024

For completeness, repeating some thigns from the chat here.

The link check failure is probably due to changes in the treatment of automated link checkers by the end points. Recommended solution is to ignore at the moment, and check after we apply Bestie (#676). If the error persists we can add it to the ignore list. This is safe to do for this website at least. We can think again for the others. On a side note, it is actually possible to add it to the ignore list at .markdown-link-check.json right now, but we would need to go check how to run it locally

The Codecov error is probably because version "1" points to "1.11" now (JuliaLang/www.julialang.org#2160) and that affected how the coverage is processed. Possible solutions:

  • Set a range of acceptable coverage instead of the 100% goal - it will be harder and harder to keep it at 100%, so this might be an incentive and the right time to do it
  • Change the for and remove the intermediary variable constraints_files.

Edit: I will not search for a temp solution for now, because in the afternoon @datejada will apply Bestie with @abelsiqueira and will try to address this issue and the codecov issue.

After some searching, it seems that I have to use an inline comment, but it does not work

<!-- markdownlint-disable-next-line -->
[Visit this link](https://code.visualstudio.com)

Is this what I should do?

@gnawin gnawin marked this pull request as ready for review October 8, 2024 10:21
@gnawin gnawin requested a review from datejada October 8, 2024 10:21
@gnawin gnawin merged commit d732a4a into TulipaEnergy:main Oct 14, 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
2 participants