Pull request overview

• Fixes SetupOutputVariables.csv is reporting unused reports and comments #11086

Description of the purpose of this PR

It was noted that in the SetupOutputVariables.csv file that is generated by a python script has a slight issue. When the scrip runs, it looks for all occurrences of "SetupOutputVariable" in the EnergyPlus code and then reports that to the .csv file. Unfortunately, there are several cases where the call to SetupOutputVariable has been commented out. The python script still logs those even though they are no longer valid calls. The solution here was to adjust the name of the call in the comment lines (added spaces between them) so that they are not logged by the python script. In addition, any place where an in-line comment was in the middle of a call to SetupOutputVariable there were also issues that resulted in the log in SetupOutputVariables.csv having additional problems. These have been corrected as well. No unit test were added or needed as per @Myoldmopar.

Pull Request Author

• Title of PR should be user-synopsis style (clearly understandable in a standalone changelog context)
• Label the PR with at least one of: Defect, Refactoring, NewFeature, Performance, and/or DoNoPublish
• [na] Pull requests that impact EnergyPlus code must also include unit tests to cover enhancement or defect repair
• Author should provide a "walkthrough" of relevant code changes using a GitHub code review comment process
• If any diffs are expected, author must demonstrate they are justified using plots and descriptions
• If changes fix a defect, the fix should be demonstrated in plots and descriptions
• If any defect files are updated to a more recent version, upload new versions here or on DevSupport
• If IDD requires transition, transition source, rules, ExpandObjects, and IDFs must be updated, and add IDDChange label
• If structural output changes, add to output rules file and add OutputChange label
• If adding/removing any LaTeX docs or figures, update that document's CMakeLists file dependencies

Reviewer

• Perform a Code Review on GitHub
• If branch is behind develop, merge develop and build locally to check for side effects of the merge
• If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
• If feature, test running new feature, try creative ways to break it
• CI status: all green or justified
• Check that performance is not impacted (CI Linux results include performance check)
• Run Unit Test(s) locally
• Check any new function arguments for performance impacts
• Verify IDF naming conventions and styles, memos and notes and defaults
• If new idf included, locally check the err file and other outputs