-
Notifications
You must be signed in to change notification settings - Fork 401
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
LowTempRadiantSystem - Fix minor bug #8463
Conversation
@@ -698,7 +698,7 @@ namespace LowTempRadiantSystem { | |||
} | |||
} else if (UtilityRoutines::SameString(Alphas(12), "CapacityPerFloorArea")) { | |||
thisRadSys.CoolingCapMethod = CapacityPerFloorArea; | |||
if (!lNumericBlanks(9)) { | |||
if (!lNumericBlanks(11)) { |
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.
Interesting that this wasn't causing any issues. And interesting that no unit test caught this. @RKStrand could you give a quick thumbs up/down on this?
@jmythms it would be really great to integrate testing of this in a unit test. Is there an existing unit test that handles input processing of this that you could modify or mimic? (Hint: there must be one because several lines of code around this line you changed are indeed covered by unit test.)
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.
Thank you for the review! Working on the unit test now.
While working on this, I also just came across this line, which I am not sure should have been
if (thisRadSys.ScaledCoolingCapacity <= 0.0) {
instead of
if (thisRadSys.CoolingCapMethod <= 0.0) {
.
I think this second change would generate the error message intended:
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.
@Myoldmopar I would agree that this is a bug that needs to be fixed. It should be changed as @jmythms is suggesting.
My guess (and it's just a guess because I don't think I was the one to add all of the sizing mods that did things on a floor area, etc. basis) is that there simply isn't a test that exercises all of the potential options for both correct and incorrect input for low temperature radiant systems. Is there one for a different input object like baseboards or something similar, maybe and if so, it would be good to implement such a unit testing scheme here.
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.
@jmythms Yes, I agree with your second recommended change also. It should not be looking at CoolingCapMethod but ScaledCoolingCapacity.
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.
Thank you!
@jmythms let me know if you need anything on this. It's just a bug fix, so there's no urgency to get it in, but I am trying to get the PR list down and this would be a quick fix. I already pulled in develop and ran tests locally. |
Sorry, I got sidetracked with the other projects, will get this ready quick. |
@Myoldmopar This is ready for review, can you take a look please? |
This looks ready to go. Thanks for adding the unit test. I'm going to do a quick build of this with develop pulled in just to make sure nothing happened with the unit test. Then I'll merge. Thanks @jmythms |
Thanks very much @Myoldmopar |
Built with develop pulled in locally, no issues. Ran unit tests serially then the whole test suite in parallel, all passing. Merging. |
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.