-
Notifications
You must be signed in to change notification settings - Fork 396
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
1st pass on using air distribution effectiveness in OA calculation #9678
base: develop
Are you sure you want to change the base?
Conversation
src/EnergyPlus/SingleDuct.cc
Outdated
@@ -6355,7 +6360,7 @@ void AirTerminalMixerData::InitATMixer(EnergyPlusData &state, bool const FirstHV | |||
airLoopOAFrac = state.dataAirLoop->AirLoopFlow(this->AirLoopNum).OAFrac; | |||
if (airLoopOAFrac > 0.0) { | |||
vDotOAReq = DataSizing::calcDesignSpecificationOutdoorAir(state, this->OARequirementsPtr, this->ZoneNum, UseOccSchFlag, true); | |||
mDotFromOARequirement = vDotOAReq * state.dataEnvrn->StdRhoAir / airLoopOAFrac; | |||
mDotFromOARequirement = vDotOAReq * state.dataEnvrn->StdRhoAir / (airLoopOAFrac * this->ADEff); |
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.
What should be done here is include ADEff inside calcDesignSpecificationOutdoorAir so other models will also get this update
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 was the change needed to see differences in the simulation results. Without this change there are only diffs in the eio.
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 don't know the best solution, but I don't think we want to be mixing extra functionality into DesignSpecification:OutdoorAir. The issue here is that some of the info is in DesignSpecification:OutdoorAir and some is in DesignSpecification:ZoneAirDistribution. I think these sorts of complexities should be handled at the parent level and these design spec object models should be kept simple, just the dry results please, and let the parents do what they need with the specification.
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.
The ATMixer receives OA from the system. There is no adjustment at the ATMixer. So maybe the system (DOAS) is not providing the correct amount of OA. I'm still looking at that. It appears the TUs do need this adjustment and I will look at that after I figure out if the ATMixer really has an issue.
The first question is should the zone OA quantity be adjusted by zone air distribution effectiveness. I believe the answer is yes but no model is currently doing this. The issue description shows that MinOA is getting adjusted during sizing which makes sense. But without also adjusting the OA quantity during the simulation the zone ADEff is not accounted for. |
src/EnergyPlus/SingleDuct.cc
Outdated
std::min(state.dataSize->ZoneSizingInput(SizingInputNum).ZoneADEffCooling, | ||
state.dataSize->ZoneSizingInput(SizingInputNum).ZoneADEffHeating); | ||
state.dataSingleDuct->SysATMixer(ATMixerNum).DesignPrimaryAirVolRate /= | ||
state.dataSingleDuct->SysATMixer(ATMixerNum).ADEff; |
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 is a one time init in GetATMixers that adjusts the ATMixer primary flow based on zone distribution effectiveness. This is all good except without also adjusting the zone OA calculated during the simulation this one time init only affects the size, not the operating flow rate.
src/EnergyPlus/SingleDuct.hh
Outdated
@@ -323,6 +323,7 @@ namespace SingleDuct { | |||
Real64 DesignPrimaryAirVolRate; // System sizing adjustments, filled from design OA spec using sizing mode flags. | |||
DataZoneEquipment::PerPersonVentRateMode OAPerPersonMode; // mode for how per person rates are determined, DCV or design. | |||
bool printWarning; // flag to print warnings only once | |||
Real64 ADEff = 1.0; |
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 am questioning where this saved data should live. The DesignSpecification:ZoneAirDistribution object name can be entered in the Sizing:Zone object. This object name can also be entered in Controller:MechanicalVentilation. So somewhere this data needs to be saved. Also, there is an effectiveness for both cooling and heating, so using the min of these to determine OA seems wrong. If cooling eff=1 and heating eff=0.8 then OA during heating and cooling should be different.
Interesting, no diffs. What I see in every unit test is this. Same for example files?
|
The first change (lines 6278 - 6282) adjusts the ATMixer DesignPrimaryAirVolRate to match what is reported in the eio. These design flow rates for the ATMixer are not reported to the eio so this was never noticed. 0.1298 + 0.059 + 0.1298 + 0.059 + 0.236 = 0.6136. The second change (line 6363) adjusts the ATMixer's raw OA to include air distribution effectivenss and provides the correct flow rates as seen in this figure. This is all in the parent object so things look good so far. Now on to the TUs. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
3 similar comments
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad how are you feeling about this branch? It's draft, which is fine, I just want to attach a milestone to it if you intend on getting it moving forward sometime. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
1 similar comment
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad it has been 8 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
7 similar comments
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 9 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
1 similar comment
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 9 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 8 days since this pull request was last updated. |
…7-ADEff-issue-with-TUs
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
2 similar comments
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@Myoldmopar @mjwitte I need some help with these steps to move this foward.
|
Some thoughts:
|
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
7 similar comments
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
1 similar comment
@rraustad @Myoldmopar it has been 28 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
3 similar comments
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
@rraustad it has been 8 days since this pull request was last updated. |
@rraustad it has been 7 days since this pull request was last updated. |
1 similar comment
@rraustad it has been 7 days since this pull request was last updated. |
Pull request overview
NOTE: ENHANCEMENTS MUST FOLLOW A SUBMISSION PROCESS INCLUDING A FEATURE PROPOSAL AND DESIGN DOCUMENT PRIOR TO SUBMITTING CODE
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.
ToDo: