V25.2.0-IOFreeze: new ZoneHVACIdealLoadsAirSystem fields#5487
V25.2.0-IOFreeze: new ZoneHVACIdealLoadsAirSystem fields#5487
Conversation
…previously being translated properly.
|
CI Results for ae5d8e8:
|
| A16, \field Design Specification ZoneHVAC Sizing Object Name | ||
| \note Enter the name of a DesignSpecificationZoneHVACSizing object. | ||
| \type object-list | ||
| \object-list DesignSpecificationZoneHVACSizingName |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
@joseph-robertson I'd like your opinion here please (I'm about to merge anyways)
| 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. |
There was a problem hiding this comment.
| 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 |
There was a problem hiding this comment.
Ok E+ IDD has DistrictHeatingWater as default
| 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. |
There was a problem hiding this comment.
Same idea, required, default to always On
|
|
||
| std::string heatingFuelType() const; | ||
|
|
||
| boost::optional<Schedule> coolingFuelEfficiencySchedule() const; |
|
|
||
| bool setHeatingFuelEfficiencySchedule(Schedule& heatingFuelEfficiencySchedule); | ||
|
|
||
| void resetHeatingFuelEfficiencySchedule(); |
There was a problem hiding this comment.
And no reset for either heating or cooling sch
| bool ok = true; | ||
| ok = setHeatingFuelType("DistrictHeatingWater"); | ||
| OS_ASSERT(ok); | ||
| ok = setCoolingFuelType("DistrictCooling"); | ||
| OS_ASSERT(ok); |
There was a problem hiding this comment.
That is Ok per E+ IDD.
I'd make the Heating/Cooling Fuel Efficiency schedule default to alwaysOnContinuous
| {"ZoneHVACIdealLoadsAirSystem", "Heating Fuel Efficiency", "heatingFuelEfficiencySchedule", true, "", OptionalDouble(), OptionalDouble()}, | ||
| {"ZoneHVACIdealLoadsAirSystem", "Cooling Fuel Efficiency", "coolingFuelEfficiencySchedule", true, "", OptionalDouble(), OptionalDouble()}, |
There was a problem hiding this comment.
continus = true, seems about right!
|
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. |
| \minimum 0.0 | ||
| \maximum 1.0 | ||
| \default 0.65 | ||
| A16, \field Design Specification ZoneHVAC Sizing Object Name |
There was a problem hiding this comment.
I had missed the fact that the field above is broken
- N11; \field Latent Heat Recovery Effectiveness
+ N11, \field Latent Heat Recovery Effectiveness… has no harcoded DSOA Follow up would be: * #5504
Hotfix #5487 - Translate the Zone DSOA if ZoneHVACIdealLoadsAirSystem has no harcoded DSOA
… has no harcoded DSOA Follow up would be: * #5504
Pull request overview
Pull Request Author
src/model/test)src/energyplus/Test)src/osversion/VersionTranslator.cpp)Labels:
IDDChangeAPIChangePull Request - Ready for CIso that CI builds your PRReview Checklist
This will not be exhaustively relevant to every PR.