Skip to content

update to main#266

Closed
PStange wants to merge 535 commits into
next/patchfrom
main
Closed

update to main#266
PStange wants to merge 535 commits into
next/patchfrom
main

Conversation

@PStange
Copy link
Copy Markdown
Collaborator

@PStange PStange commented Jun 4, 2025

No description provided.

FBumann and others added 25 commits March 29, 2025 18:23
Add warning if relative_minimum is used without on_off_parameters
* Bump up python version in tests

* Remove numpy restriction in dependencies
* Bugfix in FlowModel

* Bugfix in OnOffModel

* bugfix in rename from cherry pick

* bugfix in rename from cherry pick

* Add tests of mathematical model for classes

* Bugfix divest effects

* Add lower bound to variable (just for good measure)

* ruff check

* Add pytest mark "slow"

* ruff check

* remove code duplicate

* Bugfix consecutive duration and add tests

* Add test for compute_previous_on_states()

* Add check in compute_previous_on_states() for array size

* Make sure the minimum size is not 0
Add tests for LinearConverter, Storage and Component
Splitup the OnOffModel into smaller Submodels, improving modularity and reusability.
Some variables were renamed slightly
* Bugfix testing fixture

* Bugfix tests and add new tests to check for previous states/flow_rates

* Bugfix tests and add new tests to check for previous states/flow_rates

* Add comment for previous flow_rates

* Add comment for OnOffParameters in Component and LinearConverter
@FBumann
Copy link
Copy Markdown
Member

FBumann commented Jun 4, 2025

Im not sure if the approach with the next/.. branch is needed now as we use pypi.
I simply merge branches into main is sufficient.

@FBumann
Copy link
Copy Markdown
Member

FBumann commented Jun 4, 2025

Not every merge into mein is a release.

@PStange
Copy link
Copy Markdown
Collaborator Author

PStange commented Jun 4, 2025

Ich will doch letztendlich nur diesen Mini-Bug beim Speicherverlust beheben und bin jetzt einfach verwirrt, was denn nun das Vorgehen sein soll. Wenn nicht über next-Branch, dann Branch vom main, dort Bug beheben, wenn Tests durchlaufen, dann Pull-Request per merge in den main? (Felix' Vorschlag)

@FBumann
Copy link
Copy Markdown
Member

FBumann commented Jun 4, 2025

@PStange
Exakt
Neuer branch von Main,bug beheben.
Pull request auf Main.
Dann pull request mergen/annehmen.
Ggf. noch releasenotes erstellen (docs) und Release erstellen (GitHub)

@FBumann FBumann closed this Jun 4, 2025
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.

3 participants