rd2
commented
3 years ago Although linked enhancements will likely entail additions to the TBD JSON schema in the future, the enhancement can be considered completed. Closing.
Closed rd2 closed 3 years ago
rd2
commented
3 years ago Although linked enhancements will likely entail additions to the TBD JSON schema in the future, the enhancement can be considered completed. Closing.
There are essentially no placeholders in building energy simulation software applications (e.g. GUIs, engines) to keep track of connecting surface edges (i.e. major thermal bridges) and their properties - in memory or on file. Although one can infer and validate their existence through parent surface vertices (a feature of the Topolys gem), it is virtually impossible for users to attribute properties to individual edges, e.g. override an edge's default PSI-value, reset its thermal bridge type (a fenestration perimeter instead of a convex corner). The same can be said for point thermal bridges (e.g. columns). This also hinders post-simulation results processing (e.g. costing) and report generation (e.g. some energy codes require statements from modelers on how thermal bridges are handled for compliance purposes).
This enhancement enables TBD to read-in (as well as write-out for third-party apps) surface-specific point thermal bridges and custom building unit, story, space & surface-specific PSI-sets (as well as specific edge PSI type and value) from/to a JSON-formatted file. TBD now has its own JSON Schema and offers import/export example files, which have been extensively tested.
Where is a TBD output JSON file (tbd.out.json) generated? Under the files subfolder of an OpenStudio model project folder. How does one customize the thermal bridging derating calculations through a TBD import JSON file (tbd.json)? By placing the customized tbd.json under the same files subfolder. Both of these features are accessed via the Measure options/arguments.