Skip to content

Dynamic Template

Goal

Proof of concept for dynamic templates, writing INSEL models and using information from an energy component library. One template will be written for each building.

Technical information

Class DynamicTemplate
Superclass WorkflowStep
Author
Maintainer
Source location simstadt-workflows-energy/src/main/java/de/hftstuttgart/simstadtworkflowsteps/template/DynamicTemplate.java
Package de.hftstuttgart.simstadtworkflowsteps.template
Project simstadt-workflows-energy

Dependencies

Parameters

Template name (templateName)

Filename ('example.hbs') or basename ('example') of Handlebars template.

The corresponding file should be in the current project or workflowstep folder.

Leave this parameter empty in order to write an example template file.

  • Type : String
  • Default : ``
  • Getter : getTemplateName()
  • Setter : setTemplateName(String)

Energy components catalog filename (energyComponentsCatalogFilename)

Filename of energy components catalog.

The corresponding file should be in the current project or workflowstep folder.

  • Type : String
  • Default : Catalog.encomp

  • Unit : [.encomp]

  • Getter : getEnergyComponentsCatalogFilename()
  • Setter : setEnergyComponentsCatalogFilename(String)

Output filename (outputFilename)

For each building, one output file will be written.

A custom filename can be specified with variables: '{{model.name}}-{{building.gmlId}}-{{template}}.insel'

Which would compile to "20140218_Gruenbuehl_LOD2_2buildings-DEBW_LOD2_1007720-test_template.insel"

  • Type : String
  • Default : {{model.name}}-{{building.gmlId}}-{{template}}
  • Getter : getOutputFilename()
  • Setter : setOutputFilename(String)

Launch INSEL (runInsel)

Run INSEL on the compiled model, for each building.

  • Type : boolean
  • Default : false
  • Getter : isRunInsel()
  • Setter : setRunInsel(boolean)

Used in