Is it worth noting in this context that in Trnsys18 we now use combined data reader + solar radiation processor types (type 15, type 99 for user-defined data ...) that have a potential of avoiding this kind of problem altogether ? (they did not exist in Trnsys16
if I remember it correctly and this kind of problem was one of the motivations for creating them back in the last century)
De : TRNSYS-users <trnsys-users-bounces@lists.onebuilding.org> de la part de David BRADLEY via TRNSYS-users <trnsys-users@lists.onebuilding.org>
Envoyé : jeudi 12 mai 2022 19:00 À : TRNSYS users mailing list at OneBuilding.org <trnsys-users@lists.onebuilding.org> Cc : David BRADLEY <d.bradley@tess-inc.com> Objet : Re: [TRNSYS-users] Basic help about Type16i Nicolas, To follow on what Jeff said, make sure that the values that are in your data file are totals for each hour (not instantaneous values measured at some point in the hour) and also make sure that your Type9 is NOT interpolating the data; Type9 does a linear interpolation while Type16 does an interpolation that is appropriate for solar radiation profiles. If Type9 is set to interpolate then a double interpolation is being done. best, David
On 05/12/2022 08:56, Nicolas Heijmans via TRNSYS-users wrote:
-- *************************** David BRADLEY Principal Thermal Energy System Specialists, LLC 3 North Pinckney Street - suite 202 Madison, WI 53703 USA P:+1.608.274.2577 d.bradley@tess-inc.com http://www.tess-inc.com http://www.trnsys.com |