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

Bugs for the models in cooling capacity calculator model #3146

Closed
lambtt opened this issue Nov 8, 2022 · 4 comments · Fixed by #3147
Closed

Bugs for the models in cooling capacity calculator model #3146

lambtt opened this issue Nov 8, 2022 · 4 comments · Fixed by #3147

Comments

@lambtt
Copy link

lambtt commented Nov 8, 2022

Describe the bug
Model 1. Buildings.Fluid.HeatExchangers.DXCoils.BaseClasses.CoolingCapacityWaterCooled
Model 2. Buildings.Fluid.HeatExchangers.DXCoils.BaseClasses.PartialCoolingCapacity
Some codes for these two models seem to have problems.
Screenshots
For Model 1, it seems the water mass flow, ffCon should have been used in Cooling capacity modification factor as a function of water flow fraction at the condenser, but it didn't. And it seems the ffConMin should be replaced with ffConMax.

Snipaste_2022-11-08_10-26-41

For Model 2, it seems there is the same issue as Model 1.

Snipaste_2022-11-08_10-30-01
Snipaste_2022-11-08_10-30-41

Version

  • Modelica Buildings Library: [9.0.0]
  • Modelica simulation environment: Dymola 2023
  • Operating system: Windows 10

Additional context
I did the curve fitting (different temperatures and different flow rates) for the heat pump in our lab and found the results could not be matched. I copied Models 1 and 2 and modified the codes. Finally, the results could be matched.

The performance curve (Buildings.Fluid.HeatExchangers.DXCoils.WaterCooled.Examples.PerformanceCurves.Curve_I) in Example (Buildings.Fluid.HeatExchangers.DXCoils.WaterCooled.Examples.VariableSpeed) uses a constant modification factor for capFunFF, capFunFFCon, EIRFunFF, and EIRFunFFCon. I'm wondering if maybe that's the reason the bugs above didn't come up in the Example.

Snipaste_2022-11-08_10-32-40

@mwetter
Copy link
Member

mwetter commented Nov 8, 2022

Thanks for reporting. I will correct it on branch issue3065_dxCoilsPerformance

@lambtt
Copy link
Author

lambtt commented Nov 8, 2022

Thanks for reporting. I will correct it on branch issue3065_dxCoilsPerformance

Thank you for your attention, Michael! We will keep following it! @mingzhe37

@mwetter
Copy link
Member

mwetter commented Nov 8, 2022

@lambtt : Can you please check if #3147 addresses the issue.
Thanks.

@lambtt
Copy link
Author

lambtt commented Nov 8, 2022

@mwetter : Michael, I have checked the code change and left a comment #3147 (comment). Hope it helps!

mwetter added a commit that referenced this issue Nov 10, 2022
mwetter added a commit that referenced this issue Nov 10, 2022
mwetter added a commit that referenced this issue Nov 10, 2022
mwetter added a commit that referenced this issue Nov 10, 2022
mwetter added a commit that referenced this issue Nov 10, 2022
* Corrected function argument to ffCon

For #3146
mwetter added a commit that referenced this issue Nov 23, 2022
mwetter added a commit that referenced this issue Nov 23, 2022
* Corrected function argument to ffCon

For #3146

* Corrected function argument to ffCon

For #3146

* Updated reference results

* Initialized variable Done in gFunction
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 a pull request may close this issue.

2 participants