-
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
Remove dead code #10794
Remove dead code #10794
Conversation
@@ -915,12 +915,6 @@ void PullCompInterconnectTrigger(EnergyPlusData &state, | |||
// First store the current check in a single variable instead of array for readability | |||
CurCriteria = state.dataPlantUtilities->CriteriaChecks(UniqueCriteriaCheckIndex); | |||
|
|||
// Check to make sure we didn't reuse the index in multiple components | |||
if (CurCriteria.CallingCompLoopNum != plantLoc.loopNum || CurCriteria.CallingCompLoopSideNum != plantLoc.loopSideNum || |
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.
Would it be useful to change this into an assert
?
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'm not sure,. I think this is the type of thing that should only be done once in the simulation, just not sure where to do that. Maybe move this code up into the if (UniqueCriteriaCheckIndex <= 0)
block? I would think those 4 Nums would always be non-zero but this code would be better served there than here (and with the assert).
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 other thing that could be improved is that BranchNum and CompNum are not used. Those could be removed.
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 seems simple enough. I'll double check it is still happy with today's develop and get this in.
Yeah it's all happy. The doc/build failures are not related. This is good to go. Thanks @rraustad |
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.