Pull request overview

OK, this continues the ground heat exchanger modeling improvements. This one is about adding the ability to design and size the borehole field itself. Lots of caveats in here, and plenty of things needed for error handling, much improved documentation, more tests, double checking my flag usages, improvements to the required input configuration to make it work, etc. I'm pushing it tonight to see how GHA feels about it, and then I'll go from there tomorrow, including plenty of walkthrough.

Notable TO-DO:

• Need to verify the loads are coming out as expected, and match the load sign convention for GHEDesigner
• If we add an input field to the new :Sizing object that references the name of a SizingPeriod:WeatherFIleDays object, we could make the whole sizing/load operation much more flexible and robust.
• Needs documentaiton updates in the engineering reference - probably a good time to go over the whole GLHE section.
• Verify transition code changes work by pulling a 25.1 file, transitioning it, and running it in 25.2
• Add outputs to the EIO file for the borehole field. Maybe a list of borehole X, Y coordinates?

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