EnergyPlus tab of the Program options dialog
You can select the version of EnergyPlus to use in your simulations. This can be useful to target a specific version you may wish to use or when a new version becomes available which might provide new functionality or address previous problems.
Tip: You should generally use the recommended DLL option as it is tightly integrated with DesignBuilder and provides progress feedback.
DesignBuilder comes with 2 internal versions of EnergyPlus:
Alternatively you can select an executable version of EnergyPlus supplied by DOE. If you are exporting IDF data for use outside DesignBuilder you should select the appropriate DOE version to avoid incompatibilities.
Note: the EnergyPlus version selected here is used for simulations within DesignBuilder but also as the target version when exporting IDF data for use outside DesignBuilder.
If you select an executable version (internal or DOE) there are four options available to control the way EnergyPlus is executed when simulating within DesignBuilder:
When using a DOE EnergyPlus executable version you must also select the folder where the selected version is installed.
When you select any option other than the default DLL option, the necessary EnergyPlus files are downloaded seamlessly prior to the first simulation following the change.
Note: If you wish to install a different DLL version of EnergyPlus to that which is recommended, you must have administrative rights on the computer.
DesignBuilder are licensed distributors of EnergyPlus. All versions of EnergyPlus supplied by DesignBuilder have been compiled by the DOE.
To run a version of EnergyPlus downloaded from the DOE website you should create a new EnergyPlus version using the Custom category and make the appropriate settings. The screenshot below shows the EnergyPlus tab on Program options in this case.
When doing this it is important to consider that the only versions officially supported by DesignBuilder are the ones in the DLL list, and of those, the only one that has been fully tested is the default DLL option. The other options provided should generally work but no guarantees are provided. You may also be able to create and use new custom EnergyPlus versions not listed under the DLL category if the IDF /ESO file input/output formats are the same as one of the options provided by DesignBuilder. In this case you should look out for possible problems with simulations not running or results not loading correctly.
This option allows you to define the format of the EnergyPlus Summary "CSV" output file. Select from:
The ESO file is the primary output from EnergyPlus used by DesignBuilder to access simulation results. ESO output files will be generated by EnergyPlus following Heating design, Cooling design and Simulation calculations. You should normally leave this option checked to ensure that results are generated.
If you choose to Save ESO simulation output then you can also select options to Prompt for filename and Auto load ESO described below.
The ESO files can be loaded later using the File > Load results file menu option, provided the model hasn't changed too much. In this case the rules are as follows:
Tell DesignBuilder whether you wish to be prompted for a filename after each simulation. If you choose not to be prompted then DesignBuilder will automatically generate output filenames based on the name of the dsb file, the calculation type, the calculation description and the date. It places the file in the EnergyPlus folder. If you choose to be prompted the file can be stored anywhere on your computer system.
Check this option to automatically load the ESO results file after simulations. If you have been warned that there will be a lot of data and the program may crash on reading results you may wish to switch this option off and reload the results later. It is often possible to read in very large ESO files after DesignBuilder has restarted following a simulation and this can be a useful for avoiding a crash due to too much data. You may also wish to switch the option off to avoid waiting for the results to read in when carrying out parametric simulations.
This option only refers to Simulation results not to Heating/Cooling Design results.
When this option is checked the EnergyPlus IDF input file associated with the simulation is stored with model and can be accessed later even after the file in the EnergyPlus folder has been overwritten. This option is off by default to help conserve memory for other operations.
Requesting Display extra warnings causes the statement:
Diagnostics,DisplayExtraWarnings;
to be included in the IDF data. This option is intended for use by experienced EnergyPlus users who understand the significance of the extra warning messages generated.
The IDF data can be formatted using the options:
Normally DesignBuilder uses human readable names in the IDF based on the names used in the model. However you can override this behaviour by changing this option. Select from:
Note: If you are using an evaluation licence then the software behaves as if the 2-Numeric setting has been selected, regardless of the selection here.
You can override the overall way that IDF names are written specifically for materials, constructions and zones by checking/unchecking this checkbox.
The locations defined by the site location (latitude and longitude) should match with that of the Hourly weather file. If you would like DesignBuilder to enforce a minimum distance then check this option.
If the above Check distance between site location and weather file option is checked then enter the maximum distance allowed between the location defined by the site latitude/longitude and the latitude/longitude set for the Hourly weather file here (in m or ft). The default setting is 200,000m i.e. 200km.
If you have compiled a special version of EnergyPlus you can use it to run simulations from within DesignBuilder by following the instructions below. Note that the custom version must be based on one of the versions supported by DesignBuilder and ideally the default version. The instructions are easiest if the version number of your custom compilation is the exactly the same as that of a version that is supported by DesignBuilder.
Test by running simulations from within DesignBuilder to ensure that your custom version is being run.