-
Notifications
You must be signed in to change notification settings - Fork 390
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
Fix Thermal Comfort zone temperature and humidity lag #8572
Fix Thermal Comfort zone temperature and humidity lag #8572
Conversation
…e variables refractoring.
New code changes are applied. Hopefully this should solve the increased counts of psychometric RH out of bound warnings. |
The psychometric relative humidity ratio out of bound warnings are finally gone--this is good as these warnings are not much expected. |
For the next reviewer: For example, looking at the absolute csv diffs in the regression test for RadHiTempElecTermReheat.idf (CI test results link), This is how develop performs here: As can be observed, the effect of the large jump in temperature on PMV happened one timestep later in the develop branch while it occurred in the same timestep in this branch. Similar big PMV diffs were observed in other regression tests, but could be justified with the temperature changes. Looks good! |
The Linux failed tests results are unrelated, but the diffs are present. Would be good to get another set of CI results again. @jmythms thanks for the results comparison, that helps a lot. @mjwitte do you have anything further on this before it gets in line for final review? Anything else you know you'd like to see from @jcyuan2020 ? |
src/EnergyPlus/HVACManager.cc
Outdated
state.dataHeatBalFanSys->ZTAVComf = state.dataHeatBalFanSys->ZTAV; | ||
state.dataHeatBalFanSys->ZoneAirHumRatAvgComf = state.dataHeatBalFanSys->ZoneAirHumRatAvg; | ||
// state.dataHeatBalFanSys->ZTAVComf = state.dataHeatBalFanSys->ZTAV; | ||
// state.dataHeatBalFanSys->ZoneAirHumRatAvgComf = state.dataHeatBalFanSys->ZoneAirHumRatAvg; |
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.
@jcyuan2020 These lines should be deleted instead of commented, but otherwise, I'm good with this.
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.
@mjwitte The redundant commented code lines are now removed.
…nges from both plus some modifications.
@@ -491,6 +489,9 @@ void ManageHVAC(EnergyPlusData &state) | |||
FirstTimeStepSysFlag = false; | |||
} // system time step loop (loops once if no downstepping) | |||
|
|||
state.dataHeatBalFanSys->ZTAVComf = state.dataHeatBalFanSys->ZTAV; | |||
state.dataHeatBalFanSys->ZoneAirHumRatAvgComf = state.dataHeatBalFanSys->ZoneAirHumRatAvg; | |||
|
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.
A small change to make such an impact. But it seems reasonable, and analysis of the diffs shows better results. This is fine.
EXPECT_NEAR(state->dataThermalComforts->ThermalComfortData(1).FangerPMV, -5.5896341565108720, 0.001); | ||
|
||
EXPECT_NEAR(state->dataThermalComforts->ThermalComfortData(1).FangerPPD, 100.0, 0.001); | ||
} |
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.
OK
Pulled in latest develop here and built and ran tests fine. Code changes look good. Merging. Thanks @jcyuan2020 ! |
Pull request overview
vs. the original results before the fix:
(See #8516 as well)
uncomfortable hours
diffs (e.g. based on ASHRAE Standard 55), such as:These diffs could be expected as the PMV values would slightly change after the zone temperature and humidity corrections in the current PR.
Since the uncomfortable hours are based on computed thermal comfort values (such as PMVs), a graphical comparison of the newly computed PMVs vs. the original PMVs is demonstrated in the following example:
Additional diff comparisons:
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.