Skip to content

Conversation

@joseph-robertson
Copy link
Collaborator

Pull request overview

  • Fixes #ISSUENUMBERHERE (IF THIS IS A DEFECT)

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

@joseph-robertson joseph-robertson self-assigned this Sep 30, 2025
@joseph-robertson joseph-robertson added Pull Request - Ready for CI This pull request if finalized and is ready for continuous integration verification prior to merge. IDDChange labels Sep 30, 2025
@joseph-robertson joseph-robertson mentioned this pull request Sep 30, 2025
26 tasks
@joseph-robertson joseph-robertson marked this pull request as ready for review October 10, 2025 18:44
@ci-commercialbuildings
Copy link
Collaborator

ci-commercialbuildings commented Oct 16, 2025

Copy link
Collaborator

@jmarrec jmarrec left a comment

Choose a reason for hiding this comment

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

I'd make the schedules required, but that's just my personal opinion, I don't really care if you don't want to do it.


And reviewer note: there is no VT needed because fields are just added at the end.

Comment on lines +29890 to +29893
A16, \field Design Specification ZoneHVAC Sizing Object Name
\note Enter the name of a DesignSpecificationZoneHVACSizing object.
\type object-list
\object-list DesignSpecificationZoneHVACSizingName
Copy link
Collaborator

Choose a reason for hiding this comment

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

So this is just a reservation because we don't have this object right?

why don't we have it? Isn't it weird that no one asked for it? It was added in E+ V8-2-0

Copy link
Collaborator

Choose a reason for hiding this comment

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

@joseph-robertson I'd like your opinion here please (I'm about to merge anyways)

Comment on lines +29894 to +29901
A17, \field Heating Fuel Efficiency Schedule Name
\type object-list
\object-list ScheduleNames
\note Reference heating fuel efficiency value for converting heating
\note ideal loads into fuel energy consumption.
\note The minimum schedule value must be greater than 0.0. The maximum value
\note depends on the technology, and can exceed 1.0.
\note If blank, heating fuel efficiency value is always 1.0.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
A17, \field Heating Fuel Efficiency Schedule Name
\type object-list
\object-list ScheduleNames
\note Reference heating fuel efficiency value for converting heating
\note ideal loads into fuel energy consumption.
\note The minimum schedule value must be greater than 0.0. The maximum value
\note depends on the technology, and can exceed 1.0.
\note If blank, heating fuel efficiency value is always 1.0.
A17, \field Heating Fuel Efficiency Schedule Name
\type object-list
\object-list ScheduleNames
\required-field
\note Reference heating fuel efficiency value for converting heating
\note ideal loads into fuel energy consumption.
\note The minimum schedule value must be greater than 0.0. The maximum value
\note depends on the technology, and can exceed 1.0.
\note Defaults to always 1.0.

\key DistrictCooling
\key DistrictHeatingWater
\key DistrictHeatingSteam
\required-field
Copy link
Collaborator

Choose a reason for hiding this comment

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

Ok E+ IDD has DistrictHeatingWater as default

Comment on lines +29918 to +29925
A19, \field Cooling Fuel Efficiency Schedule Name
\type object-list
\object-list ScheduleNames
\note Reference cooling fuel efficiency value for converting cooling
\note ideal loads into fuel energy consumption.
\note The minimum schedule value must be greater than 0.0. The maximum value
\note depends on the technology, and can exceed 1.0.
\note If blank, cooling fuel efficiency value is always 1.0.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same idea, required, default to always On


std::string heatingFuelType() const;

boost::optional<Schedule> coolingFuelEfficiencySchedule() const;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same here


bool setHeatingFuelEfficiencySchedule(Schedule& heatingFuelEfficiencySchedule);

void resetHeatingFuelEfficiencySchedule();
Copy link
Collaborator

Choose a reason for hiding this comment

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

And no reset for either heating or cooling sch

Comment on lines +935 to +939
bool ok = true;
ok = setHeatingFuelType("DistrictHeatingWater");
OS_ASSERT(ok);
ok = setCoolingFuelType("DistrictCooling");
OS_ASSERT(ok);
Copy link
Collaborator

Choose a reason for hiding this comment

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

That is Ok per E+ IDD.

I'd make the Heating/Cooling Fuel Efficiency schedule default to alwaysOnContinuous

Comment on lines +507 to +508
{"ZoneHVACIdealLoadsAirSystem", "Heating Fuel Efficiency", "heatingFuelEfficiencySchedule", true, "", OptionalDouble(), OptionalDouble()},
{"ZoneHVACIdealLoadsAirSystem", "Cooling Fuel Efficiency", "coolingFuelEfficiencySchedule", true, "", OptionalDouble(), OptionalDouble()},
Copy link
Collaborator

Choose a reason for hiding this comment

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

continus = true, seems about right!

Copy link
Collaborator

Choose a reason for hiding this comment

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

thanks for this

Base automatically changed from v25.2.0-IOFreeze to develop October 20, 2025 12:08
@jmarrec
Copy link
Collaborator

jmarrec commented Oct 22, 2025

Ok I'm going to ignore the fact that I'd like the schedules required, the object has an optional Availability Schedule already, so at least it's somewhat consistent.

@jmarrec jmarrec merged commit adf7263 into develop Oct 22, 2025
0 of 4 checks passed
@jmarrec jmarrec deleted the v25.2.0-IOFreeze-ideal branch October 22, 2025 10:44
\minimum 0.0
\maximum 1.0
\default 0.65
A16, \field Design Specification ZoneHVAC Sizing Object Name
Copy link
Collaborator

Choose a reason for hiding this comment

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

I had missed the fact that the field above is broken

-  N11; \field Latent Heat Recovery Effectiveness
+  N11, \field Latent Heat Recovery Effectiveness

Copy link
Collaborator

Choose a reason for hiding this comment

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

Hotfixed on develop on 1a3696b

jmarrec added a commit that referenced this pull request Oct 23, 2025
Hotfix #5487 - Translate the Zone DSOA if ZoneHVACIdealLoadsAirSystem has no harcoded DSOA
anchapin pushed a commit that referenced this pull request Nov 30, 2025
anchapin pushed a commit that referenced this pull request Nov 30, 2025
… has no harcoded DSOA

Follow up would be:

* #5504
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

IDDChange Pull Request - Ready for CI This pull request if finalized and is ready for continuous integration verification prior to merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants