-
Notifications
You must be signed in to change notification settings - Fork 397
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
Corrected MultiSpeed DX Cooling Coil sizing variable names and capacity reporting issues #7495
Conversation
This is ready for review. |
@Myoldmopar @rraustad Note that I have merged in issue #7381 to this branch. |
Putting this as milestone 9.2 for now since it doesn't appear at first glance to change I/O in a structural manner, but I need to look at the details before making a final decision on that. We'll be freezing the code next week so it may be too late anyway, but if it is clean it would be nice to drop it in. |
Unlikely to get this reviewed before we make final cutoff tomorrow afternoon. I'm going to shift the milestone back to future. |
@Myoldmopar working on it now. |
@Myoldmopar Merged in develop and run the unit test suite. All happy. |
The multi-speed DX cooling coil capacity sizing related report variable names were modified for consistency. Also the design rated capacity at lower speeds are now corrected, the lower speed design cooling capacity are fraction of the design capacity at maximum speed, instead of the user specified maximum speed capacity. |
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.
- Tested this vs develop and saw the expected changes using multispeed.idf as-is (moved to v9.2).
- The name re-ordering in the sizing labels warrants an entry in \src\Transition\OutputRulesFiles\OutputChanges9-2-0-to-9-3-0.md
- Added sizing objects to the defect file and expected to see a reported "Design Size . . . " for every "User-Specified . . .". This was true for all except "Speed 2 Gross Rated Heating Capacity", the design size output is missing for this one. See After-multispeed-AddSizing.eio
- Also made a fully autosized version of the defect file and compared to the hard-sized file with sizing. I was surprised that the Coil:Cooling:DX:MultiSpeed, ASHP CLG COIL, Design Size Speed 2 Gross Rated Total Cooling Capacity was not the same in both files. So maybe that's because the capacity design size is being calculated based on the hard airflow rate? So, I made the airflow rate and the shr autosize in both files and the design gross cooling capacity is still different between the two. Is it broken, or am I missing something? Compare the eio output for After-multispeed-AddSizing-AllAutosize vs After-multispeed-AddSizing-AutoSizeSHRAndAirFlow.
Test files attached: 7477-MulitSpeedDX.zip
"Added sizing objects to the defect file and expected to see a reported "Design Size . . . " for every "User-Specified . . .". This was true for all except "Speed 2 Gross Rated Heating Capacity", the design size output is missing for this one. See After-multispeed-AddSizing.eio" @mjwitte I moved the cooling capacity sizing calc to Requestsizing() function. I think, this function does not report the design capacity (may be any design variable) unless the user specified value is different from the design value by more than 10%. This is a quick reply to item 3. |
@Nigusse I may be wrong, but my understanding is that both values should always be reported, but the >10% difference triggers a warning (with DisplayExtraWarnings?). |
If not autosized, and difference is greater than 0.1, both are reported, otherwise only user specified is reported.
|
@rraustad @Nigusse I didn't realize the reporting was suppressed for <10% difference. So, OK, if I change that to exceed 10% then I see design reported for every user value. So, that part's ok. Any thoughts on the other question about fully autosized capacity being different from the design values reported when user-specified? |
@mjwitte @rraustad The main reason why these two defect files show design size cooling capacity difference is due to differences in sizing method. When it is fully auto-sized, the capacity determined using the RequestSizing() function from the parent object (UnitarySystem) and is set for the DX coil. When there is hard sizing value specified for the DX coil capacity, the design capacity is determined using the autosizing calculation in the DXCoil object. These two sizing methods are slightly different. The RequestSizing() function accounts for fan heat effect in the sizing calculation, while the other is not. I think the way forward in resolving this problem is to use the RequestSizing() in both places. I think, this defect must have been there longer. |
@mjwitte As you have pointed out partial autosizing of multi-speed DX coils fields has been broken. I have found partial autosizing problem for Rated Total Cooling/Heating Capacity, Rated Air Flow Rates, Rated Sensible Heat Ratio, Evaporative Condenser Air Flow Rate, etc. All capacity and flow rate related sizing variables were broken or did not work in the first place when there is partial autosizing. Fixing these issues has broken else where, so reverted some of the changes I made. The remaining issues will be addressed after reviewing the this push, perhaps this issue should be divided into multiple bug issues. |
This fix resolves the mismatch between design size values when fully and partially autosized. |
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.
@Nigusse Thanks for addressing all of the comments. Output looks exactly as expected now. Merging in develop for one more CI round, then this can drop in.
Pull request overview
Fixes #7477. This fixes inconsistent reporting in multi-speed DX cooling and heating coils:
Work Checklist
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.
Review Checklist
This will not be exhaustively relevant to every PR.