Output Details and Examples — EnergyPlus 9.4

<< Prev | Table of Contents | Next >>


An output file ending with _perflog.csv is created whenever the PerformancePrecisionTradeoffs object is present. This log file consists of echoing the settings in the PerformancePrecisionTradeoffs object, some overall building energy results, the runtime of the simulation, oscillation outputs, and the number of warning and severe messages. The _perflog.csv file is appended to instead of replaced each time a simulation is run to facilitate evaluation of the performance objects options and their impact on the runtime and other factors so the user can determine which combination is best for their particular input file. It includes a timestamp. Since it is a CSV (comma separated value) file, it is easily opened in spreadsheet software. Please ensure that file is not open in the spreadsheet while EnergyPlus is running so that the file can be appended to. If the spreadsheet program is open with the file, it will be locked and not able to be appended. The fields in the file are shown below.

  • Program

  • Version

  • TimeStamp

  • Use Coil Direct Solution

  • Zone Radiant Exchange Algorithm

  • Override Mode

  • Number of Timesteps per Hour

  • Minimum Number of Warmup Days

  • SuppressAllBeginEnvironmentResets

  • MaxZoneTempDiff

  • Electricity ABUPS Total [J]

  • Natural Gas ABUPS Total [J]

  • Additional Fuel ABUPS Total [J]

  • District Cooling ABUPS Total [J]

  • District Heating ABUPS Total [J]

  • Water ABUPS Total [m3]

  • Values Gathered Over [hours]

  • Facility Any Zone Oscillating Temperatures Time [hours]

  • Facility Any Zone Oscillating Temperatures During Occupancy Time [hours]

  • Facility Any Zone Oscillating Temperatures in Deadband Time [hours]

  • Run Time [seconds]

  • Run Time [string]

  • Number of Warnings

  • Number of Severe

When using this file it is good to set PerformancePrecisionTradeoffs to default values the first time to establish a baseline then change one input at a time and rerunning to understand the impact of that input. The total runtime decrease and the impact on energy and the ocscillation variables should be considered prior to committing to a specific PerformancePrecisionTradeoffs scheme.