<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">Thanks Brian for sharing...</div><div dir="auto"><br></div><div dir="auto">Regards</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Ahmad</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Galaxy</div></div><div dir="auto"><br></div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:#000000"><div>-------- Original message --------</div><div>From: Brian Fountain via Equest-users <equest-users@lists.onebuilding.org> </div><div>Date: 19/10/21 11:37 pm (GMT+10:00) </div><div>To: equest-users@lists.onebuilding.org </div><div>Subject: [Equest-users] LS-F Report Totals - include Design Day values along with monthly values </div><div><br></div></div>
<div class="WordSection1">
<p class="MsoNormal">In both 2.2 and 2.3, the LS-F report which shows the annual heating and cooling from the LOADS run has an issue. There are two LS-F reports – the Design Day report and the Standard Report which shows annual LOADS results. The issue is
the totals row in the Standard Report is not the sum of the monthly results but rather also includes the Design Day report total.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">This is less of an issue in 2.2, for a couple of reasons. Firstly in 2.2 the default heating and cooling design days are a single day although more may be specified. Further in 2.2 if no design day is defined then the Design Day LS-F
report is not triggered. In 2.3 conversely, the default design days are a 7 day period. If no design day is defined in 2.3 then the sizing is done for a full year for heating plus a full year for cooling (which is why the simulation takes notably longer)
and the Design Day LS-F report reflects this two year period. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Until recently, I had not spent much time looking at LS-F. However, with Thermal Energy Demand Intensity (TEDI) being a required metric in several jurisdictions, the question of what impact individual envelope components have on TEDI comes
into play. It seems LS-F is the only place to get a measure of the annual heat loss through windows (for example). We had seen a number of .sim files where the LS-F exceeded the SS-D. I believe this issue with the total row explains that situation. The
sum of the monthly Standard Report LS-F values or the Standard Report total less the Design Day LS-F total should be used.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">It does not appear that the LS-E report which provides the same information but on a space by space basis has the same issue.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Cheers,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Brian</p>
<p class="MsoNormal"> </p>
<p style="margin-bottom:8.0pt;line-height:106%" class="MsoNormal"><b><span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#006298">Footprint<br>
<br>
</span></b><b><span style="font-size:10.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#006298">Brian Fountain<br>
</span></b><span style="font-size:9.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#3D3935">Associate<br>
<br>
</span></p>
<p class="MsoNormal"> </p>
</div>
</body></html>