-
Notifications
You must be signed in to change notification settings - Fork 61
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
Issue1287 DHW model #1355
Issue1287 DHW model #1355
Conversation
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.
@lucasverleyen thanks for refactoring this model. I've focused on the implementation of PartialTap
for now. Please have a look at my remarks and use that feedback in the other models as well if possible. When that's done, I'll do a second review.
@louisher thanks a lot for the review. I have implemented and resolved all of your suggestions, except 1. @jelgerjansen can you give your opinion? |
@lucasverleyen I did some quick checks with a new implementation for the mass flow calculation. The old implementation gives small but unrealistic results around the transition are (m>m_set, blue curve below). The simulation results below have the a constant |
@jelgerjansen I fully agree with your suggestion! It is indeed more elegant and easier to interpret. |
…ion for all component declarations
…rprofiles" to "DHW"
@jelgerjansen all comments have been addressed. Unit tests pass. If you agree with the implementation of the discomfort calculation in the Tap.mo example, this pull request is ready to be merged. |
Fixes #1287
Issues as described in #1287 have been addressed. The unit test for the old example has been removed and two new unit tests have been added for the two new examples covering the two DHW tap models. The reference results can be found in #1287 .