-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix water coil user-specified sizing and Component Sizing Summary table for fan coils #7988
Conversation
…-chwcoil-sizingtable
…es change the calculated cooling coil capacity.
…-chwcoil-sizingtable
…-chwcoil-sizingtable
…-chwcoil-sizingtable
…-chwcoil-sizingtable
…-chwcoil-sizingtable
…ue to sizing calulcation now being based on user-specified design flow rates.
…-chwcoil-sizingtable
} else { | ||
DataAirFlowUsedForSizing = TempSize; // many autosized inputs use the design (autosized) air volume flow rate, save this value | ||
DataFlowUsedForSizing = TempSize; | ||
} |
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.
This first change looks OK to me.
src/EnergyPlus/WaterCoils.cc
Outdated
@@ -2233,9 +2244,19 @@ namespace WaterCoils { | |||
TempSize = AutoSize; | |||
RequestSizing(state, CompType, CompName, CoolingCapacitySizing, SizingString, TempSize, bPRINT, RoutineName); | |||
DataCapacityUsedForSizing = TempSize; | |||
TempSize = WaterCoil(CoilNum).MaxWaterVolFlowRate; | |||
TempSize = AutoSize; |
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.
This second change always autosizes the HW coil water flow rate. What if the coil input is hard-sized? And the coil is on the main branch. I am on the fence whether this is OK for zone equipment, but if the fan coil HW flow rate is hard-sized or autosized then that flow rate will be used in the HW coil, even if the HW coil hard-sized the HW flow rate. This is an input over-specification problem and this does correct that. Do all other zone equipment also pass the ZoneEqSizing data, I assume they do, so again this is probably OK.
src/EnergyPlus/WaterCoils.cc
Outdated
@@ -2579,7 +2600,7 @@ namespace WaterCoils { | |||
|
|||
FieldNum = 2; // N2 , \field Maximum Water Flow Rate | |||
SizingString = WaterCoilNumericFields(CoilNum).FieldNames(FieldNum) + " [m3/s]"; | |||
TempSize = WaterCoil(CoilNum).MaxWaterVolFlowRate; | |||
TempSize = AutoSize; |
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.
Same comment as above for always autosizing the HW flow rate whether or not the HW coil input is hard-sized.
It is interesting that only the fan coil example files show diff's. However, there may not be example files where a water coil on the main branch is hard-sized. I think a quick test of 5ZoneAirCooled using hard-sized water flow rates for the main branch coils would show any problems. Also, what if a test file is completely hard-sized? And there are no sizing objects? That file would fail with a warning to add sizing objects. And users would say "huh". |
The fan coil was already passing the information. For some reason the water coil was not picking that information up in RequestSizing.
I think if you step through the sizing of a fan coil's water coil, by stepping into RequestSizing, you will see where the problem lies. |
Thanks @rraustad, I'll go back and step through the sizing portion and see if I can find the disconnect. |
…-chwcoil-sizingtable
…-chwcoil-sizingtable
@matthew-larson @lgentile it has been 28 days since this pull request was last updated. |
@rraustad I ended up removing the changes related to the water flow rates for this pull request. I felt that I was getting beyond the scope of these issues which are addressing the design air flow rates and need to spend more time investigating RequestSizing for the water flow rates as you recommended previously. Thanks again for your assistance with this. Let me know if you have any additional comments regarding this pull request. |
Well, the logic here looks better. Good thing this is in water coils, because I have removed RequestSizing in the Autosizing Library branch. Can you paste in the eio diff's from a defect file so I have a reference for what you think is the correct result? And tell me what defect file or example file you used. |
I used the _FanCoilHybridVentAFN.idf testfile to show the effect. The ZoneHVAC:FourPipeFanCoil object is autosized to a Design Size Maximum Supply Air Flow of 0.21702 m3/s. The Coil:Cooling:Water associated with the fan coil specifies a Design Size Design Air Flow Rate of 0.21702 m3/s but a User-Specified Design Air Flow Rate of 0.12390 m3/s, which is used for the sizing of the coil, leaving the coil undersized compared to the fan coil specifications. After the fix, the Coil:Cooling:Water gets a User-Specified Design Air Flow Rate of 0.21702 m3/s to match the size determined by the ZoneHVAC:FourPipeFanCoil object. You can see the change in Nominal Total Capacity of the cooling coil and other design parameters below (before on left, after on right): I also tested when the Maximum Supply Air Flow Rate for the ZoneHVAC:FourPipeFanCoil object is hard-sized to 0.2 m3/s instead of autosized. Originally, hard-sizing this has no effect on the Coil:Cooling:Water Nominal Total Capacity as it still uses the User-Specified Design Air Flow Rate of 0.12390 m3/s. After the fix, the Coil:Cooling:Water gets a User-Specified Design Air Flow Rate of 0.2 m3/s to match the size determined by the ZoneHVAC:FourPipeFanCoil object and increases the Nominal Total Capacity. Same before and after comparison with the hard-sized flow rate shown below: Let me know if you need any other info/results or have any additional or followup questions. |
Well, this goes to what the user intended. What if the user wanted to under (or over) size the cooling coil? With these changes there is no way to size a coil different from the fan coil size. Using the autosize method, all inputs should be autosized. If a user specifies a hard-size then E+ uses that information, regardless of result. |
I see what you mean, I need to address the ability to hard-size the water coil to be different than the fan coil. I'll spend more time on this, thanks. |
…-chwcoil-sizingtable
…-chwcoil-sizingtable
I made a number of updates to get the eio results to reflect what I believe we want to see based on different scenarios of autosizing and hardsizing the fan coil and cooling coil inputs. Below is a table showing the eio results for the ZoneHVAC:FourPipeFanCoil Maximum Supply Air Flow Rate and Coil:Cooling:Water Design Air Flow Rate using the same test file (_FanCoilHybridVentAFN.idf). The warnings and failed regressions tests are all due to the Coil:Cooling:Water now reporting 'Design Size Design Air Flow Rate' instead of 'User-Specified Design Air Flow Rate' when the coil is connected to a fan coil which are both autosized for air flow rate, which I think is appropriate. There is an error added to the results for '_FanCoilHybridVentAFN.idf' due to the change in the Coil:Cooling:Water air flow rate but wanted to get this all reviewed before addressing this if needed. |
WaterCoil(WhichCoil).DesAirVolFlowRate = CoilDesFlow; | ||
} else { | ||
WaterCoil(WhichCoil).DesAirVolFlowRate = CoilDesFlow; | ||
//WaterCoil(WhichCoil).DesAirVolFlowRate = CoilDesFlow; |
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.
I guess the design air vol flow rate will just stay at zero for this case?
I've got no problem with this. I think all the review comments have been addressed. CI results look OK given the expected string change. I built locally with develop and ran tests and everything is still fine. I'm inclined to merge but will hold for a while to see if anyone has more thoughts. |
Merging. Thanks @matthew-larson for the fix and @rraustad for looking at the changes multiple times. |
Pull request overview
Before:

After:

Pull Request Author
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.
Reviewer
This will not be exhaustively relevant to every PR.