-
Notifications
You must be signed in to change notification settings - Fork 58
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
Stack effect airflow - Project itz fixes #1327
base: stack_effect_project_itz_master
Are you sure you want to change the base?
Stack effect airflow - Project itz fixes #1327
Conversation
Updated master from IDEAS Master
Debugging partial surface, new implementation of stack columns because conditional connections to col models did not work as expected.
Got rid of the unnecessary initial equations
New implementation for the density columns to avoid error due to conditional statements in the column heights
Changed error in input of door component.
… and flow element(s) Assign height difference between meteorological pressure measurements and flow element(s). Also, by default corrects for the windspeed using this height when the TwoPort implementation is used.
cosmetic change
option added to get better default for roofs. This needs to be fine-tuned based on available data.
The problem seems to be that we are externally applying a stack instead of letting the door model handle it. This would have been fine if the model equations were consistent, but they are not: the external pressure column uses The cleanest approach would be to refactor the model such that we used the internal stack computation again. |
@Mathadon the results seem to be better (solid line represents the results of PR #1322, dashed line the results of this PR) When zooming in, both results show exactly the same trend, but there is still a minor offset of about (2e-5 for W1[1], 8e-5 for W7[1], 2e-4 for W10, and 1e-7 for W37). The latter might be due to the change CVal/COpe? |
Isn't the external column their is a door/opening doesn't start on the floor level? (e.g. a large opening between a living room and a kitchen that only starts above the cabinets..). I'm not familiar with the specific changes you made when combining/optimizing the models, but that was the approach before I believe. If I recall correctly, the door model assumes the pressure in the connecor to be the reference at the bottom of the door, so their should be some kind of correction based on the room heights (and preferably the 'starting height' of the door for e.g. modelling a 2-storey hallway with as 1-zone). |
@kldjonge to be clear, the problem that I described is a problem that I created by modifying your implementation. As far as I know, the equations are now again consistent with the old implementation. The way I see it, the external column is now integrated into the door model but I did not look into the model equations in full detail to verify their correctness. Since the implementation is the same as before, it should be equally correct as before and the validation should point out whether or not that the results match contam and thus whether the implementation is correct. |
@jelgerjansen the CVal/COpe should be correct since commit aad7465. Perhaps the remaining differences are because the new implementation effectively disables the cracks when a door is open. In the old implementation both equations would be present at the same time. The underlying assumption was that the crack flow rate is negligible to the flow rate of an open door. Looking at the values of @jelgerjansen would it be possible to send me those two .mat files such that I can compare further? |
At least part of the reason seems to be that the The cause of this change is probably: + setArea(A=A*nWin),
- setArea(A=A_glass*nWin), in the So I think we can accept these changes and move ahead..! @kldjonge @jelgerjansen do you agree? |
Is the difference in ratio |
@jelgerjansen Indeed, the results are affected by all surfaces so the q50 value does not scale proportionally. |
I would propose to update the reference results of the current PR and then run unit tests again for Mathadon#2 to look for new changes. |
I've included an overview of the reference results that show significant changes compared to those of commit . The reference results are those from #1322.
|
…mmented once the validation data is available.
@jelgerjansen commit 07c74e4 fixes a parameter bug that is a possible cause for the remaining changes. I pushed it on branch project_itz_fixes_v2. |
@Mathadon I ran the branch project_itz_fixes_v2, but I ran into an error which I solved in commit 33e525c (see branch origin/project_itz_fixes_v2). |
The deviation of |
For clarity, we still have to cover the comments here: Mathadon#2 |
@jelgerjansen this includes some changes but still requires a master merge