Open JasonGlazer opened 1 year ago
A6 , \field Refrigeration System Working Fluid Type
\note Fluid property data for the refrigerant must be entered.
\note The fluid property data, including the objects:
\note FluidProperties:Name, FluidProperties:Temperatures,
\note FluidProperties:Saturated and FluidProperties:Superheated
\note can be copied from the FluidPropertiesRefData.idf dataset
\required-field
\type object-list
\object-list FluidNames
From helpdesk ticket 16495:
On page 61: talking about 'Shading Calculation Method' it says: "Unlike PolygonClipping, PixelCounting has no limitations related to zone concavity when used with any “FullInterior” solar distribution options (i.e., it can accommodate both concave and convex zones equally)." Therefore, if I would like to include Concave Zones, I would conclude that I should use 'FullInteriorAndExterior' as the value for the SolarDistribution property on the Building object. On page 49: talking about the 'SolarDistribution' property on Building, it says: "If the zone’s surfaces do not enclose a space or if the zone is not convex you should use Solar Distribution = FullExterior instead of FullInteriorAndExterior." This two entries contradict each other. Which is correct?
Chiller:Electric:EIR
still mentions this is not possible. See related comment here.A user (Helpdesk Ticket 16513) pointed out that the following equation in the EcoRoof model is incorrect in Engineering Reference (pp.189, Eq 4.11, v23.2):
The correct form should be "0.9 - 0.7 exp(-0.75 LAI)" instead.
The EnergyPlus source code is checked and the implementation there is correct. This is confirmed to be just a documentation issue.
HeatBalanceSurfaceManager (what's the difference in the last 2 reports?):
state.dataHeatBalFanSys->ZoneHeatIndexHourBinsRepPeriod(ZoneNum, ReportPeriodIdx)[0] += state.dataGlobal->TimeStepZone;
state.dataHeatBalFanSys->ZoneHeatIndexOccuHourBinsRepPeriod(ZoneNum, ReportPeriodIdx)[0] +=
NumOcc * state.dataGlobal->TimeStepZone;
state.dataHeatBalFanSys->ZoneHeatIndexOccupiedHourBinsRepPeriod(ZoneNum, ReportPeriodIdx)[0] +=
(NumOcc > 0) * state.dataGlobal->TimeStepZone;
DistrictHeating
(which was renamed to DistrictHeatingWater
in E+ 23.2). For example, in the last paragraph here. All *.tex files should be audited because I'm seeing additional references. Noted in this Unmet Hours post.The Input Output Reference description for SetpointManager:MixedAir only mentions using it for controlling outdoor air economizers. It should also explain that it's used to adjust temperature setpoints for any component with a control node that is upstream of the fan.
(ref helpdesk ticket 16610)
Steam:Humidifier:Gas
still mention previous "Gas" options instead of "NaturalGas". For example, output variable is labelled as "Humidifier Gas Use Rate" instead of "Humidifier NaturalGas Rate". Should likely check other output variable references to be updated from "Gas" to "NaturalGas".
In the I/O Reference, for HybridModel:Zone "Calculate Zone Internal Thermal Mass", there is no mention of where to find the output for average thermal mass. It is reported in the table report "Input Verification and Results Summary" subtable "Hybrid Model: Internal Thermal Mass". From example file HybridZoneModel.idf (which currently doesn't have an Output:Table:SummaryReports object):
Also should update the example file to generate this report. Ref helpdesk ticket 16643.
In I/O Ref, page 2426 in V24.1, Table 1.61, there is an overlapping of columns that should be fixed:
There are no at 75% numeric fields anymore
Object type description for Refrigeration:AirChiller should have "the rated operating temperature" removed.
In I/O Ref, page 698 in V24.1, Table 1.46, there is an overlapping of columns/columns that go past the margin on the left that should be fixed:
Here's a few typos in the parametric object docs:
@JasonGlazer @mjwitte @RKStrand @jmarrec @rraustad @tanaya-mankad would one of you be able to tackle all the cleanups in this issue in your current defect bundle? If not, I'll tackle it sometime soon. Thanks!
@Myoldmopar I can do these as I’ve got space in my defects works to do this. I’ll assign myself and work on this sometime soon.
A place to keep an ongoing list of documentation issues.