Model import options

Model planning

There are known differences in the topology of form and fabric between different tools and export facilities can accommodate only some of these differences. For example, in ESP-r any surface can be transparent, it need not be a child of another surface but EnergyPlus requires transparent surfaces to be children. ESP-r can calculate insolation patterns in zones of arbitrary form but EnergyPlus only supports this for convex zones.

gbXML files can be imported. However, some will need to be converted from 16 bit font encoding to ASCII text (xmlcopyeditor can do this conversion). ESP-r sets limits on the length of entity names (some long names may be truncated). Some CAD tools allow you to create facades where parent surfaces have scores of child surfaces - for ESP-r ensure <20 child surfaces. Check that thermal zones are within the complexity limits of ESP-r (you may need to use an ESP-r compiled to support larger models).

A subset of the gbXML scheme is currently parsed so the resulting ESP-r model will likely need further attribution. For example, assumptions about constructions are made based on the building type and you are given options to specify operational characteristics of zones. It will also assign ideal cotrols for zones which are conditioned. Below is the ESP-r interpretation of the standard gbXML Exercise Center test file.

gbxml import see full size

Model import options

In addition to the normal interface facilities to create and evolve models ESP-r offers the following import options:

  • DXF (v14) files as long as they follow specific conventions that allow interpretation of zones (each in a separate layer) and include only 3D entities. This option will be depreciated as gbXML matures.
  • gbXML files as long as they follow specific conventions that allow interpretation of zones (each in a separate layer) and include only 3D entities.
  • A so-called ESP-r META file (a single file tag:data representation of most of an ESP-r model) that is designed to be more easily written by external agents than the usual multi-folder model file convention of ESP-r.
  • The parsing of GBXML files includes a subset of the schema which includes surfaces and openings.

    • Model export options

    Models can be exported in the following forms:

  • DXF (v14) files with each zone in a separate layer and as 3D entities.
  • EnergyPlus IDF files (v4 v5 v6) including materials, constructions, surfaces, schedules and purchased air to approximate environmental controls.
  • Radiance (4R2) model exports with the ESP-r module e2r used to setup the viewing parameters and commissioning images./li>
  • ESP-r META file (typically used as a transport mechanism to remote users of ESP-r.

    • Entities which require additional attention

    The following entities require additional attribution or transforms to be fully functional:

  • In Radiance exports all surfaces are represented as grey-scale and manual editing is required to add textures etc. Use of IESNA data files requires the files to be located in a specific folder.
  • For EnergyPlus exports it may be necessary to plan the ESP-r model to respect the surface parent/child hierarchy of EnergyPlus. ESP-r only creates ideal environmental controls. Users would have to upgrade their IDF files.
  • DXF is best avoided as a transport form as the loss of attribution is significant.

    • Model contents reports

    In addition to information within the interface it is possible to generate a report of the contents of the model with the following options:

  • site information can be included or excluded
  • database entries used can be reported tersely or verbosely
  • geometric reports can be terse or verbose
  • schedule reports can be terse or verbose
  • control logic reports can be terse or verbose
  • flow network reports can be terse or verbose
  • plant network reports can be terse or verbose
  • CFD domain reports can be terse or verbose

    • ESP-r model contents reports are designed to highlight issues which may not be clear in the interface as well as avoiding some of the arbitrary formatting found in the model files.


    Back to top | Back to Welcome page
    ©Copyright 2017 Energy Systems Research Unit, Glasgow, Scotland. License: GPL V2. Last edited by JWH, 25 Aug 2016