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

Project itz fixes v2 (Klaas) to master #1379

Open
wants to merge 291 commits into
base: stack_effect_project_itz_master
Choose a base branch
from

Conversation

jelgerjansen
Copy link
Contributor

@kldjonge I merged your changes into the project_itz_fixes_v2 branch of the open-ideas repo (via PR #1376). I'll use this branch to fix typos and update the reference results. If you want to change something, please pull the latest changes of the project_itz_fixes_v2 to your local branch and later create a PR to merge your changes into this branch.

If everything appears to be fine, we can merge in the stack_effect_project_itz_master branch, after which we can merge to the master branch.

@Mathadon FYI

kldjonge and others added 30 commits April 21, 2022 12:44
Changes of master were not correctly merged
Not really a clean implementation at this point.
Derived Habs to be able to easily check the model after translation
Changed the default to handle floors and ceilings as airtight
When an opening is horizontal, no different flows are expected due to the lack of stack effect, thus simplifying to less compartments is logical.

Can this be 1?
commit 121cb9c
Merge: 06aa135 a681abf
Author: kldjonge <[email protected]>
Date:   Mon Aug 29 09:00:13 2022 +0200

    Merge branch 'open-ideas:master' into master

commit a681abf
Author: Filip Jorissen <[email protected]>
Date:   Sat Aug 27 16:04:04 2022 +0200

    default value for epsSw_shading in IDEAS//Buildings/Components/Shading/Interfaces/PartialShading.mo
jelgerjansen and others added 22 commits October 30, 2024 11:16
This caused errors irrelevant to the model example
Model intended to show flow difference for seemingly similar models for large horizontal openings. Model adapted to highlight differences more. Documentation added.
This is cleaner as part of the multizone package
.mos files, revision notes and finished two examples
…to avoid unspecified initial condition warning
@jelgerjansen
Copy link
Contributor Author

@kldjonge I had to modify the initialization of LargeHorizontalOpening due to warnings while unit testing (e.g. https://github.com/open-ideas/IDEAS/actions/runs/11597200022/job/32290133284).

This led to slightly different reference results (below is a comparison between your initial model and my updated model). Could you verify whether this is still OK?
IDEAS_Airflow_Multizone_Validation_LargeHorizontalOpening
IDEAS_Airflow_Multizone_Validation_LargeHorizontalOpening_Statistics

Furthermore, I also get a similar warning for AirflowBoxModel: https://github.com/open-ideas/IDEAS/actions/runs/11614092887/job/32341474696, I presume by switching to 'DynamicFreeInitial' for the energy dynamics of the zone. Could you please fix this issue?

@kldjonge
Copy link
Contributor

Still okay! Results make sense given that the different initialisation dynamics.

As previous I can not reproduce the issue in Dymola 2024x , but I now avoided the use of 'DynamicsFreeInitial'. I will make a new pull-request from my fork to project_itz_fixes_v2.

@jelgerjansen
Copy link
Contributor Author

There was still an issue with SingleZoneResidentialHydronicHeatPump (overspecified initial pressure condition in evaporator), probably due to changes in the IDEAS.Fluid.Sources.OutsideAir model. I solved this by setting the HP energyDynamics to DynamicFreeInitial (commit 6f55c89) and adding some initial equations. @kldjonge @Mathadon could you please verify that these initial equations are somewhat logical (I think they are as the reference results are the same). However it's maybe not that important as we'll remove this model from the library in the future (see ibpsa/project1-boptest#681)

If this is OK for both of you, I'll do a final review (mainly focussing on documentation and revision notes), and then we can merge this PR. A next and final step is then to merge these changes to the actual master branch.

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.

4 participants