ForwardTranslate to new E+ SpaceLoad Instances + Definitions (opt-out possible)

[jmarrec]

Pull request overview

• E+ gained new Space Load Instances + Definition pairs, eg ElectricEquipment:Instance and ElectricEquipment:Definition
  • cf #11614 - Implement SpaceLoad Instance + Definition objects EnergyPlus#11752

Behavior is that it will now by default translate to these new object pairs. But you can opt-out

• There is a new CLI flag

          --space-load-instances, --no-space-load-instances{false} 
                                   Translate SpaceLoads (People, Lights, ElectricEquipment, etc) to
                                   the E+ Instance / Definition object pairs [Default: True]

• A matching key in WorkflowJSON: no_space_load_instances

  • OSW Schema addition in Add new no_space_load_instances key in ft_options OpenStudio-workflow-gem#160

• A matching method ForwardTranslator::setExcludeSpaceLoadInstances(bool)

---

OpenStudio-resources

• Add an ENV Variable to force space load instances translation or not OpenStudio-resources#234

• I need to run the full regression tests suite at:

• develop

• this PR with USE_SPACE_LOAD_INSTANCES=false

• this PR with USE_SPACE_LOAD_INSTANCES=true

and confirm there are no failing tests and no EUI deviations.

Pull Request Author

• Model API Changes / Additions
• Any new or modified fields have been implemented in the EnergyPlus ForwardTranslator (and ReverseTranslator as appropriate)
• Model API methods are tested (in src/model/test)
• EnergyPlus ForwardTranslator Tests (in src/energyplus/Test)
• If a new object or method, added a test in NREL/OpenStudio-resources: Add Link
• If needed, added VersionTranslation rules for the objects (src/osversion/VersionTranslator.cpp)
• Verified that C# bindings built fine on Windows, partial classes used as needed, etc.
• All new and existing tests passes
• If methods have been deprecated, update rest of code to use the new methods

Labels:

• If change to an IDD file, add the label IDDChange
• If breaking existing API, add the label APIChange
• If deemed ready, add label Pull Request - Ready for CI so that CI builds your PR

Review Checklist

This will not be exhaustively relevant to every PR.

• Perform a Code Review on GitHub
• Code Style, strip trailing whitespace, etc.
• All related changes have been implemented: model changes, model tests, FT changes, FT tests, VersionTranslation, OS App
• Labeling is ok
• 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

[github-actions]

🧪 Test Results Dashboard

Summary

Metric	Value
Total Tests	0
Passed	0
Failed	0
Errors	0
Skipped	0
Success Rate	0.0%
Generated	2026-09-10 11:47:43 UTC

❌ Significant Test Failures

📊 Test Run Information

Run	XML File	Status
-	No XML files found	❌ Missing