-
Notifications
You must be signed in to change notification settings - Fork 392
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
Add warnings/errors for unreasonable DHW temperatures for WaterUse:Equipment #8808
Conversation
…water temperature.
…-waterusetemp-error
All diffs are due to situations where the target water temperature is unachievable due to the hot water temperature, or the hot water temperature is below the cold water temperature. Not sure if these should be investigated in the models to eliminate these warnings. |
this->HWTempErrIndex, | ||
this->HotTemp, | ||
this->HotTemp); | ||
} |
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.
Catches when Cold water temp is > available Hot water temp and throws one time and recurring warning error message.
this->TargetTempErrIndex, | ||
this->HotTemp, | ||
this->ColdTemp); | ||
} |
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.
Catches when Target water temp is > available Hot water temp and throws one time and recurring warning error message.
this->TargetTempErrIndex, | ||
this->HotTemp, | ||
this->ColdTemp); | ||
} |
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.
Catches when Target water temp is < available Cold water temp and throws one time and recurring warning error message.
}); | ||
|
||
EXPECT_TRUE(compare_err_stream(error_string3, true)); | ||
} |
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 unit test demonstrates the three conditions where throwing warning error message is warranted. Update the branch, built and ran the unit test locally. Also ran the unit test suite locally and all passed.
Now there are 35 example files that throw warning error message because they are caught by the fix. But these are expected error messages unless we want to modify the example files to eliminate the warning error. @Myoldmopar |
If the warning error message is a concern another alternative is to not report the warning error message unless "DisplayExtraWarnings" variable is set to true. |
@matthew-larson @Nigusse Ultimately, we want to fix these so the example files deliver the requested target temp without warnings. I would not hide these under "DisplayExtraWarnings". That could happen here or as a sperate defect/PR. These are are all good warnings that indicate the target temp won't be met, and why. Do we have a warning that checks the supply temp vs target temp directly and warns that it didn't deliver? Or would that even be useful? If all of these checks pass, are there other things that could prevent the target temp from being met? |
@mjwitte @Nigusse I ended up not doing a check for supply temp vs target temp as this would involve whole different part of the code and I thought would probably be better as a separate issue/pull request. This could probably go along with DHW heating capacity checks which could be the other reason that the target temp wouldn't be reached. I can go ahead and create another issue/pull request to fix the example files so we can push this one through sooner than later without me holding it up. |
@mjwitte @matthew-larson I suspect sometimes the available capacity and demand mismatch may lead to hot water temperature to drop below the target temperature. But these needs to investigate case by case. I think removing the error message from the example files should be handled in a separate issue. |
@mjwitte I was making comment but ended up closing the issue. That was inadvertent. |
I looked at a couple of example files trying to understand the source and causes of the warning messages. For instance, the example file ReportHeatEmission_RefFSRestaurant.idf has a total of 41 warning massages and these messages occur during warmup period only. There are also two other observations I made:
@matthew-larson please add timestamp reporting function |
// print error for variables of hot water temperature | ||
++this->HWTempErrorCount; | ||
if (this->HWTempErrorCount < 2) { | ||
ShowWarningError(state, "CalcEquipmentFlowRates: Hot water temperature is less than the cold water temperature"); |
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.
Add this ShowContinueErrorTimeStamp(state, "");
here
// print error for variables of target water temperature | ||
++this->TargetTempErrorCount; | ||
if (this->TargetTempErrorCount < 2) { | ||
ShowWarningError(state, "CalcEquipmentFlowRates: Target water temperature is greater than the hot water temperature"); |
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.
Add this ShowContinueErrorTimeStamp(state, "");
here
// print error for variables of target water temperature | ||
++this->TargetTempErrorCount; | ||
if (this->TargetTempErrorCount < 2) { | ||
ShowWarningError(state, "CalcEquipmentFlowRates: Target water temperature is less than the cold water temperature"); |
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.
Add this ShowContinueErrorTimeStamp(state, "");
here
Thanks @Nigusse for your review. I went ahead and added the |
I'll pull and test this locally. |
Builds and passes locally with develop pulled in. Regressions locally are exactly what it was showing the last time Decent ran. Merging, thanks @matthew-larson and @Nigusse! |
Thanks @Myoldmopar! |
Pull request overview
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.