Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
General comment about the E+ component sizes table here. That sqlite output feature in E+ was originally contributed by a volunteer third party developer. The ComponentSizes table was introduced in the original design, but to my knowledge it has not been kept up to date as new components and features have been introduced to E+. As time progressed the OpenStudio team (probably before we were known as OpenStudio) recognized the value of the database output for our purposes, but we considered the ComponentSizes impractical to maintain when EnergyPlus developers (especially @JasonGlazer) were already committed to maintaining the tabular data we are all accustomed to viewing in html format. In order to leverage the existing and ongoing effort in tabular output and gain access to the entire E+ output through the database, I introduced TabularDataWithStrings which tapped into the existing code to write tables in E+. This means that anything written to html automatically shows up in sqlite. This generic approach may not be as elegant from a database design point of view, but it seems like a good tradeoff for gaining the entirety of E+ tabular output.
| | 2 | No.2 Revision |
General comment about the E+ component sizes table here. That sqlite output feature in E+ was originally contributed by a volunteer third party developer. The ComponentSizes ComponentSizes table was introduced in the original design, but to my knowledge it has not not been kept up to date as new components and features have been introduced to E+. E+.
As time progressed the OpenStudio team (probably before we were known as OpenStudio) recognized the value of the database output for our purposes, but we considered the ComponentSizes ComponentSizes impractical to maintain when EnergyPlus developers (especially @JasonGlazer) were already committed to maintaining the tabular data we are all accustomed to viewing in html format. format.
In order to leverage the existing and ongoing effort in tabular output and gain access to the entire E+ output through the database, I introduced TabularDataWithStrings TabularDataWithStrings which tapped into the existing code to write tables in E+. This means that anything written to html automatically shows up in sqlite. This generic approach may not be as elegant from a database design point of view, but it seems like a good tradeoff for gaining the entirety of E+ tabular output.
