Skip to content
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 #10718 - DXCoils StandardRatings OutputReportPredefined::addFootNoteSubTable produces invalid XML #10860

Open
wants to merge 9 commits into
base: develop
Choose a base branch
from

Conversation

jmarrec
Copy link
Contributor

@jmarrec jmarrec commented Dec 17, 2024

Pull request overview

Pull Request Author

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

  • 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
  • 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

This will not be exhaustively relevant to every PR.

  • 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

@jmarrec jmarrec added the Defect Includes code to repair a defect in EnergyPlus label Dec 17, 2024
@jmarrec jmarrec self-assigned this Dec 17, 2024
@jmarrec jmarrec force-pushed the 10718_StandardRatingsXML branch from 7ac4834 to 5374b1b Compare December 17, 2024 14:29
@jmarrec
Copy link
Contributor Author

jmarrec commented Dec 17, 2024

@nrel-bot-2c
Copy link

@jmarrec it has been 7 days since this pull request was last updated.

@nrel-bot-2
Copy link

@jmarrec it has been 8 days since this pull request was last updated.

@jmarrec jmarrec marked this pull request as ready for review January 6, 2025 08:32
Copy link
Member

@Myoldmopar Myoldmopar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an interesting set of changes. Ultimately I guess you are just collecting a few repeated strings into one location (great!!) and then doing some work to make sure it is valid output. You went above and beyond to bring the pytest work to the core CMakeLists scope and built some great tests to exercise your changes. I'm very happy with this. Any thoughts @JasonGlazer ?

@Myoldmopar
Copy link
Member

I'm pushing a fix to the license year for the 2 new python files, but this appears ready anytime unless anyone has comments or objections.

@JasonGlazer
Copy link
Contributor

The footnotes now have HTML in them. I wonder if they work with plain text tables and CSV tables? (or did they never work for those?)

@jmarrec
Copy link
Contributor Author

jmarrec commented Jan 14, 2025

The footnotes now have HTML in them. I wonder if they work with plain text tables and CSV tables? (or did they never work for those?)

@JasonGlazer

Take DXCoilSystemAuto.idf, modify the OutputControl:Table:Style

diff --git a/testfiles/DXCoilSystemAuto.idf b/testfiles/DXCoilSystemAuto.idf
index 398ea60ae8..94b4da3978 100644
--- a/testfiles/DXCoilSystemAuto.idf
+++ b/testfiles/DXCoilSystemAuto.idf
@@ -1859,7 +1859,7 @@
   Output:Constructions,Constructions;
 
   OutputControl:Table:Style,
-    HTML;                    !- Column Separator
+    All;                     !- Column Separator
 
   Output:Table:SummaryReports,
     AllSummary;              !- Report 1 Name

and here it is, with develop

Screenshot from 2025-01-14 11-10-31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Defect Includes code to repair a defect in EnergyPlus
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CoilCoolingDX.cc OutputReportPredefined::addFootNoteSubTable produces invalid XML
5 participants