eQuest SIM File Data Extraction Using Awk

Topic: Extracting discrete data values using Gawk (GNU Awk)

Following are some (one, for now) potentially useful Gawk (using GNU Awk for Win32) scripts for extracting data from an eQuest/DOE2 output SIM file :

# Save this script to a file named BEPU.AWK in the directory # containing the simulation output files. # # BEPU.AWK extracts energy consumption totals from # the specified .SIM report using GNU Awk for Windows: # # http://gnuwin32.sourceforge.net/packages/gawk.htm # # Note that GAWK.EXE must exist in the shell path. Thus after installation # using the package installer, it is recommended that a copy of GAWK.EXE # be placed in the %WINDIR%\system32 directory. # # Usage: # # gawk -f BEPU.AWK SimFile.SIM # # ...where the program file BEPU.AWK and data file SimFile.SIM must exist. # {if ($2 ~/BEPU/) {ipr = 1}} {if (ipr == 1) {if ($1 == "TOTAL") print $1" "$2" "$3" "$4 if ($2 == "PS-H") ipr = 0}}

At left is a simple Awk script to extract the energy consumption totals in kWH and therms from the specified SIM file. Run this script from a CMD prompt in the same directory as your .SIM files; be sure to copy GAWK.EXE to %WINDIR%\System32, where %WINDIR% is usually (but not always) C:\WINDOWS. Modified from an original script posted by Joe Huang in the BLDG-SIM archives. Thanks Joe! More fun with Awk and SED to come over the next few months, as time permits or workload demands.

Note that in this example, printing is turned on (ipr = 1) by flagging the desired report, and off (ipr = 0) by flagging the report following the desired report. Examine the contents of the SIM file or see this post to determine the actual report sequence -- its not the same as shown in the drop-down box in the SIM file viewer.

More Awk examples from elsewhere...

• Quick and Dirty Data Extraction in AWK from the Linux Journal
  

SED & eQuest SIM File Reports

Topic: Extracting individual reports from SIM files using SED

See this post for another SED vs. Awk comparative editorial. Following is my own take, after fiddling around with SED for a few hours in an attempt accomplish discrete value data extraction.

Next time: Discrete value data extraction using Awk!

SED = Sledgehammer

SED seems most useful for gross editing tasks -- i.e. global search-and-replacements or chunking out reports from the SIM file. SED is essentially batch application of regular expressions.

Lacking basic programming constructs, there are fundamental functionality limitations. But for the tasks it is capable performing, SED accomplishes them exceedingly well.

Awk = Sawzall

With built-in programming language constructs, Awk seems to be more suited for 'refined' tasks like discrete value data extraction, doing arithmetic on arrays and columns, or creating custom reports.

They both seem to be the right tool, just for different tasks. Following are some potentially useful SED examples (using GNU SED for Win32):

SED /HW-BOILER/!d SimFile.SIM	Outputs from SimFile.SIM all lines with HW-BOILER
SED /PS-E/,/PS-F/!d SimFile.SIM	Outputs the PS-E report contained in SimFile.SIM
@ECHO OFF SET SIMRPT=Energy Cost Summary SET SIMBGN=BEPS SET SIMEND=BEPU SED.EXE --version >NUL IF %ERRORLEVEL% GTR 0 GOTO USAGE IF EXIST %1.SIM GOTO NEXT GOTO USAGE :NEXT SED /%SIMBGN%/,/%SIMEND%/!d %1.SIM >%TEMP%\~SED.TMP IF /I "%2" EQU "/A" GOTO APPEND SED /%SIMEND%/d %TEMP%\~SED.TMP GOTO :EOF :APPEND SED /%SIMEND%/d %TEMP%\~SED.TMP >>%0.RPT GOTO :EOF :USAGE ECHO. ECHO The %SIMBGN%.CMD script extracts the "%SIMRPT%" section from ECHO the specified .SIM report using GNU SED for Windows: ECHO. ECHO http://gnuwin32.sourceforge.net/packages/sed.htm ECHO. ECHO Note that SED.EXE must exist in the shell path. Thus after installation ECHO using the package installer, it is recommended that a copy of SED.EXE ECHO be placed in the %WINDIR%\system32 directory. ECHO. ECHO Usage: ECHO. ECHO %SIMBGN% SimFile [/A] ECHO. ECHO ...where SimFile is specified without the .SIM extension and must exist. ECHO If the optional /A parameter is supplied, the output will be appended to ECHO a file named %SIMBGN%.RPT so that a 'FOR' command may collect ECHO all %SIMBGN% reports into a single file for further processing. ECHO. ECHO Example: ECHO. ECHO FOR %%i in (*.SIM) DO %SIMBGN% "%%~ni" /A ECHO. ECHO CAUTION!!! The %SIMBGN%.RPT file must be deleted manually ECHO to be refreshed, else updates will simply be appended to it. ECHO. ECHO Released to public domain under General Public Licence (GPL) ECHO http://www.gnu.org/licenses/gpl.html ECHO Copyright 2007 by Brandon Nichols, PE ECHO.	The command script at left extracts the BEPS report from the specified .SIM file and echoes it to the screen by default. Copy the code, paste it to a blank Notepad window. Save the file as 'BEPS.CMD' (be sure to change the drop-down in the Notepad file-save dialog from '*.txt' to 'All Files') to the eQuest reports directory, or to a designated script directory in the command path. Assure that GNU SED.EXE may also be found in the command path -- see the installation tip under 'USAGE' in the script. Type 'BEPS SimFile' at the CMD prompt, where SimFile is specified WITHOUT the .SIM extension. Now for some real fun type 'BEPS' at the CMD prompt and hit return, then copy/paste the 'FOR' example displayed on the 'Usage' screen to the CMD prompt and hit return. Written to disk will be each BEPS report from all simulations in a directory into a text file named BEPS.RPT for output or further processing. To create your own report extractor, simply change the three 'SET' values at the top of the file and save it under a new name. For instance changing values of SIMRPT to Summary of Utility Rates, SIMBGN to BEPU, and SIMEND to PS-H creates a BEPU extractor.

When creating a new report extractor, examine the contents of the SIM file or see this post to determine the actual report order -- its not the same as shown in the drop-down box in the SIM file viewer.

Perhaps not immediately obvious, but a 'System Report Extractor' for a report within the SIM file 'system repeat block' will extract each instance of the report for all systems! For example, copy the script above to Notepad and change the values of SIMRPT to 'System Utility Energy Use', SIMBGN to 'SS-H', and SIMEND to 'SS-I' and save to SS-H.CMD (be sure to change the drop-down in the Notepad file-save dialog from '*.txt' to 'All Files') in same directory where the SIM files are located. Thus created is an SS-H extractor that extracts all System Utility Energy Use reports for every system from the specified SIM file!.

Type 'SS-H SimFile' (without the .SIM extension) at the command line to test the output. Note that SimFile must exist in the same directory as the script and GNU SED.EXE must be in the command search path. If the above conditions have been met and your syntax is correct, then all SS-H reports will be echoed sequentially to the screen.

Now type just 'SS-H' at the command line and hit return. Then copy/paste the 'FOR' example from the usage screen to the command line and hit return. Congratulations, you have just created the text file SS-H.RPT, containing each System Utility Energy Use report for every system from all SIM files in the current directory!

eQuest SIM File Reports

Topic: A listing of the reports in the order found in the DOE2 .SIM output file

LV-M	DOE-2.2 Units Conversion Table
LV-N	Building Coordinate Geometry
LV-A	General Project Parameters
LV-B	Summary of Spaces
LV-C	Details of Space
LV-D	Details of Exterior Surfaces
LV-E	Details of Underground Surfaces
LV-F	Details of Interior Surfaces
LV-G	Details of Schedules
LV-H	Details of Windows
LV-I	Details of Constructions
LV-J	Details of Building Shades
LS-A	Space Peak Loads Summary
LS-B	Space Peak Loads Components
LS-C	Building Peak Load Components
LS-D	Building Monthly Loads Summary
LS-E	Space Monthly Load Components
LS-F	Building Monthly Load Components
LS-K	Space Input Fuels Summary
LS-K	Building Input Fuels Summary
LS-L	Management and Solar Summary
SV-A	System Design Parameters
SS-D	Building HVAC Load Summary
SS-E	Building HVAC Load Hours
SS-M	Building HVAC Fan Elec Energy
SS-A	System Loads Summary	Begin system repeat
SS-B	System Load Summary Zones	block
SS-C	System Load Hours	|
SS-H	System Utility Energy Use	|
SS-I	Sensible/Latent Summary	|
SS-J	Peak Heating and Cooling	|
SS-K	Space Temperature Summary	This group of
SS-R	Zone Performance Summary	reports is repeated
SS-L	Fan Electric Energy Use	once for each system
SS-N	Relative Humidity Summary	|
SS-P	Heating Performance Summary	|
SS-P	Cooling Performance Summary	|
SS-G	Zone Loads Summary	|
SS-F	Zone Demand Summary	End system repeat
SS-O	Space Temperature Summary	block
PV-A	Plant Design Parameters
PS-A	Plant Energy Utilization
PS-B	Utility and Fuel Use Summary
PS-C	Equipment Loads and Energy Use
PS-D	Circulation Loop Loads
PS-E	Energy End-Use Summary for all Electric Meters
PS-E	Energy End-Use Summary for all Fuel Meters
PS-F	Energy End-Use Summary for Meters
BEPS	Building Energy Performance
BEPU	Building Utility Performance
PS-H	Loads and Energy Usage for Plant
HOURLY REPORT	Hourly Report for Energy End-Usage
EV-A	Life-Cycle Costing Parameters
ES-A	Annual Costs and Savings
ES-B	Life-Cycle Non-Energy Costs
ES-C	Life-Cycle Investment Savings
ES-D	Energy Cost Summary
ES-E	Summary of Utility Rates
ES-F	Block Charges and Ratchets

MultiEdit & Regular Expressions

Topic: Using the MultiEdit text editor and regular expressions to clean up DOE2 .inp files generated by the eQuest wizard.

MultiEdit

There are a number of adequate text editors out there -- many of them are free. My favorite text editor is not free, but IMHO MultiEdit stands a professional cut above the freeware pack. A partial list of features that makes it particularly suitable to working with DOE2 files is as follows:

• Multiple tabbed windows, allowing rapid file switching
  
• Remembered windows, from the last time the program was open
• Multiple sessions. Most useful if you wear additional hats like 'CAD Guru' or 'Systems Integrator' -- each named session recalls a group of files in exactly the same window state as when last worked upon.
  
• Split windows, permitting two different parts of the same file to be edited
  
• Line numbers and a handy 'go to line number' function
  
• Scrolling side-by-side on-screen file comparisons, highlighting the location and nature of differences between files
• An undo buffer that will take you back to the beginning of an editing session, even after a massively botched search and replacement.
• Backup files saved in a common directory on the local hard drive, off-network. This has saved many hours of rework more than once in my brief career so far with eQuest.
  
• ...more features to be listed as time permits
• And last but not least, search and replacements using 'regular expressions'

Regular Expression Examples

Regular expressions enable powerful search and replacements in a single operation that would otherwise require many operations using 'literal' search and replace strings. The syntax is necessarily cryptic for utilitarian compactness; however comprehensive free learning resources are just a google away, such as this tutorial site.
Expect a bit of a learning curve, but once you've accomplished a search and replacement in a single line that would've taken a dozen or more literal iterations, there's no going back.

Further, regular expression syntax is applicable to scripting utilities such as Perl and SED, meaning that once your approach to search and replacements has become standardized, it can be batched and run without ever opening the input files -- when I get to this point with .inp and .sim files I'll be sure to post some examples.

First and foremost, make backup files religiously when working with eQuest in general, and in particular do not fail to do so before tackling a relatively risky editing task such as this -- it's always easier (and better for your social life) to restart from the last waypoint than to rebuild a disaster.

Schedules

REMINDER: Make sure you change the type of "Regular Expression" from Perl to Unix on the "Search and Replace" Option tab.

Following are MultiEdit search and replace strings using regular expressions applicable to DOE2 schedules; be sure to uncheck the radio button entitled 'Search All Windows' (refer to screenshot below) until you're sure you know what you're doing.

• System Fan Schedules: Replace all auto-generated system fan schedules with a single fan schedule named 'EMS Fan Sch'
• Search String: (")S.* Fan Sch
• Replace String: \0EMS Fan Sch
• System Cooling Schedules: Replace all auto-generated system cooling schedules with a single cooling schedule named 'EMS Cool Sch'
• Search String: (")S.* Cool Sch
• Replace String: \0EMS Cool Sch
• System Heating Schedules: Replace all auto-generated system heating schedules with a single heating schedule named 'EMS Heat Sch'
• Search String: (")S.* Heat Sch
• Replace String: \0EMS Heat Sch
• Infiltration Schedules: Replace all auto-generated perimeter infiltration schedules with a single infiltration schedule named 'EMS P-Inf Sch'
• Search String: (")Z.* P-Inf Sch
• Replace String: \0EMS P-Inf Sch
• Infiltration Schedules: Replace all auto-generated core infiltration schedules with a single infiltration schedule named 'EMS C-Inf Sch'
• Search String: (")Z.* C-Inf Sch
• Replace String: \0EMS C-Inf Sch
• Building Occupancy Schedules: Replace all auto-generated building occupancy schedules with a single building occupancy schedule named 'EMS Occup Sch'
• Search String: (")E.* Bldg Occup Sch
• Replace String: \0EMS Occup Sch
• Building Office Equipment Schedules: Replace all auto-generated office equipment schedules with a single office equipment schedule named 'EMS OffEq Sch'
• Search String: (")E.* Bldg OffEq Sch
• Replace String: \0EMS OffEq Sch
• Building Inside Lighting Schedules: Replace all auto-generated inside lighting schedules with a single inside lighting schedule named 'EMS InsLt Sch'
• Search String: (")E.* Bldg InsLt Sch
• Replace String: \0EMS InsLt Sch
• Building Cooking Schedules: Replace all auto-generated cooking schedules with a single cooking schedule named 'EMS Cook Sch'
• Search String: (")E.* Bldg Cook Sch
• Replace String: \0EMS Cook Sch
• Exterior Lighting Schedules (same as literal): Replace the string 'Ext Lighting Sch' with the string 'EMS Ext Lighting Sch'
• Search String: "Ext Lighting Sch
• Replace String: "EMS Ext Lighting Sch
• Domestic Hot Water Schedules (same as literal): Replace the string 'DHW Eqp NRes Sch' with the string 'EMS DHW Eqp NRes Sch'
• Search String: "DHW Eqp NRes Sch
• Replace String: "EMS DHW Eqp NRes Sch

It should go without saying that the schedules named by the replacement strings need to exist in the .inp file -- see this post for an outline procedure to copy schedules from one project to another. Be aware that the search and replacements described above should be done only after swapping-out the .inp file's daily, weekly and annual schedule sections.

Envelope

Following are MultiEdit search and replace strings using regular expressions applicable to DOE2 envelope components; be sure to uncheck the radio button entitled 'Search All Windows' (refer to screenshot below) until you're sure you know what you're doing.

• Exterior Walls: Replace all auto-generated exterior wall constructions with a single construction named 'Exterior Wall Construction'
• Search String: = "E.{1,4} EWall Construction"
• Replace String: = "Exterior Wall Construction"
• Roofs: Replace all auto-generated roof constructions with a single construction named 'Exterior Roof Construction'
• Search String: = "E.{1,4} Roof Construction"
• Replace String: = "Exterior Roof Construction"
• Windows: Replace auto-generated 'Window Type #1 GT' glass types in all shells with a single glass type named 'Exterior Glass Type #1'
• Search String: = "E.{1,4} Window Type \#1 GT"
• Replace String: = "Exterior Glass Type \#1"
  
• Window Frames & Spacers: Eliminate frames and install insulated spacers on all 'Exterior Glass Type' permutations
• Search String: ("Exterior Glass Type \#.*$).*FRAME-WIDTH =.*$
• Replace String: \0$ SPACER-TYPE = INSULATED

Systems, Loops & Equipment

The following MultiEdit search and replace strings using regular expressions are applicable to DOE2 systems, loops and equipment; be sure to uncheck the radio button entitled 'Search All Windows' (refer to screenshot below) until you're sure you know what you're doing.

• Hot Water Loop: Replace assignments to the HW-LOOP keyword with 'Hot Water Loop'; note leading space to prevent matching the DHW-LOOP keyword.
  
• Search String: ( HW-LOOP *= ).*$
• Replace String: \0"Hot Water Loop"

A very handy tool for learning regular expressions is RegExBuddy, available from the author's site for a nominal fee. MultiEdit also includes some regular expression help built into the search and replace dialog box; click the left-arrows to the right of the search and replace fields when the regular expression radio button is selected:

(click on the image to see a larger version)

Next time...regular expression fun with SED and SIM files!

Note: a reasonable set of extensions for the MultiEdit 'Add Files Wizard' is as follows:
AWK SED INP TXT DOC PD2 BDL PRD SIM CSV PDH DAT CMD DAT

Process Loads:

This is the link for the process loads Btu/(People x Hr) for different kind of building

Suppress Selected eQuest Warning Dialogs

Topic: Certain eQuest warning dialogs can become a nuisance. Here's how to suppress some of them...

• The 'Browse for Replacement CAD File' dialog:

Open the project PD2 file in a text editor, find the line where the DWG file is named, and delete it. Don't delete any other lines!!!

Example:

CADFile "06129_Zoning_Plans - DWG"
FileName = "06129_Zoning_Plans.dwg"
FilePathOffset = 0
ScaleUnits = 0
ScaleValue = 1
OriginX = -17923
OriginY = -0.49998
Azimuth = 0
..

Delete the entire line beginning with 'FileName' (listed in red) containing the name of the drawing.


• The 'Check for New Utility Rates' dialog:

Manually add the following line (listed in red) to the topmost "Proj" component in the project's PD2 file:

Proj "SCL rate test"
ProgramVersion = "eQUEST 3.61.5486"
...
EnableAutoRateUpd = 0
..

The ASHRAE Appendix G Baseline

Topic: The latest edition of the ELCCA Guidelines calls for the comparison of the high-performance building alternative to a baseline building as defined by ASHRAE Standard 90.1-2004 Appendix G.


Eliminate self shading: SHADING-SURFACE = NO

eQuest Runaround Heat Recovery

Topic: Simulating runaround heat recovery in eQuest requires modifying the standard air-to-air heat recovery system

Suggest selecting system 'PSZ' for DX cooling or 'SZRH' for chilled water; other system selections may work satisfactorily. The following parametric components were utilized to obtain a combined $5,000 in savings (initially, without parasitics) on a $90,000 per year utility bill in the Pacific Northwest on a pair of 'PSZ' systems with heat recovery using 100% outside air.

$ Adjust the supply and returns statics of the main unit to
$ account for the increased pressure drop, originally:
$ SUPPLY-STATIC = 5.25
$ RETURN-STATIC = 2.60 (less delta-P, due to partial exhaust flow)
$ Example, given the above initial statics
SUPPLY-STATIC = 6.00
RETURN-STATIC = 3.00
$ Change the following keyword to YES in a parametric run; all other heat
$ recovery parameters are ignored when set to NO for the baseline case:
RECOVER-EXHAUST = NO
$ Runaround heat recovery recovers sensible energy only, no latent
ERV-RECOVER-TYPE = SENSIBLE-HX
$ Specify OA and EXH flows if only a portion of the exhaust is recovered
$ Partial recovery example
ERV-OA-FLOW = 46960
ERV-EXH-FLOW = 28590
$ Potentially the effectiveness can increase to 0.75 if a two-pass coil used
ERV-SENSIBLE-EFF = 0.53
ERV-RUN-CTRL = OA-EXHAUST-DT
ERV-RECOVER-MODE = OA-HEAT/COOL
$ FLOAT gives maximum heat recovery but recovers even unwanted heat, so
$ use the setting for temperature control
ERV-TEMP-CTRL = MIXED-AIR-RESET
$ modulation capacity control simulates variable-speed pumping
ERV-CAP-CTRL = MODULATE-HX
$ input maximum runaround pump power consumption here, it will be switched
$ on only when the ERV is activated
ERV-HX-KW = 4.5
$ use main unit's fans for heat recovery
ERV-FANS = HVAC-SUPPLY/RETURN
$ Keywords STANDARD and PREMIUM may alternately be specified here
ERV-MOTOR-CLASS = HI-EFF
$ Set the ERV statics to zero, since it is NOT a separate unit
$ in series with the main unit; i.e. pressure losses are 'unswitched'.
$ If left undefined, they will default to 1.5 inches:
ERV-OA-STATIC = 0
ERV-EXH-STATIC = 0
$ This setting eliminates condensation and frost simulation warnings
ERV-FROST-CTRL = USE-CAP-CTRL

However when the parasitic loads of the additional supply/return fan energy and runaround pump power are accounted for, eQuest demonstrates again that is difficult to break even with runaround heat recovery in this relatively mild maritime climate:

(click on the image to see a larger version)

Updating eQuest Utility Rates

Topic: How to keep utility rates current by editing the library file.

• Open the local eQLib.dat file with a text editor
  
• Find utility rate section to be updated, e.g. search for 'PSE', 'SCL' or 'Snohomish'
  
• Note the latest revision date at the beginning of the rate section
  
• Change only the rate needed, e.g. Schedule 36, Schedule 31, Schedule 20 etc.
  
• Add a 'rate changed', 'revised by' and 'date' comments for the latest revision
• BE SURE TO TEST the rate update in an actual simulation!
• If the test passes, run the 'Update eQuest' script to propagate the change
• If the test fails, run the 'Restore eQuest' script and start over
• If the test fails, DO NOT try to repair the library file as it may have been inadvertently damaged. Finding the damage is like finding the proverbial needle in a haystack, so best to limit losses and start over.
• NEVER leave the library file in a broken condition, else it may be propagated to other workstations.

Note: The above link(s) are only valid within the HEI intranet. Firefox users install the "IE Tab Plug-in", then right-click the link and select "Open in IE Tab" from the context menu.

eQuest Boiler Curve Example

Topic: Efficiency performance curves published by equipment manufacturers may not be in a format helpful for energy modeling. This example presents a manufacturers condensing boiler, and derives a set of data points to which a curve can be fit using DOE2 routines.

The following efficiency curve is published by Aerco, representing the thermal performance of KC-1000 Series condensing boilers; the color annotations have been added by the author:

(click on the image to see a larger version)

The three curves on the chart represent firing rates of 37.5%, 75% and 100% from top to bottom. Thermal efficiency can be read on the vertical axis by knowing the firing rate and return water temperature. eQuest/DOE2 however requires input data points for boiler performance curves to be in entering water temp / leaving water temp / heat input ratio (inverse of thermal efficiency) format.

According to the chart, thermal efficiency is independent of both flow and supply water temperature, so the firing rate data curves and entering water temperature points should indicate efficiency regardless of the infinite combinations of flow rates and supply temperatures possible. This produces however, essentially an infinite number of efficiency curve solutions. To solve this problem, we must temper the manufacturer's published data with a measure of sound engineering judgement.

(click on the image to see a larger version)

Realizing that a low firing rate should occur at low load conditions, a high firing rate at high load conditions, and a mid firing rate somewhere in between, let us make the careful assumption that a high firing rate will result in a 40° (100%) ΔT, a mid firing rate in a 30° (75%) ΔT , and a low firing rate in a 15° (37.5%) ΔT across the boiler.

Using these ΔT's, we can now compute a corresponding leaving water temperature for each of the data points on the chart, except for the five at the extreme right. Efficiency is poorest here as entering water temperature approaches that of leaving water temperature. So dispensing with these data points should not detract much from the resultant accuracy of the curve fit, since our control system and operational sequencing should not allow the equipment to operate in this regime anyway.

Following is the BDL code required for a binomial quadratic curve fit of the Aerco KC-1000 condensing boiler's heat input ratio in terms of entering and leaving water temperatures:

"Aerco-KC1000-HIR" = CURVE-FIT
TYPE = BI-QUADRATIC-T
INPUT-TYPE = DATA
INDEPENDENT-1 = ( 80, 80, 80, 100, 100, 100, 120,
120, 120, 140, 140, 140, 160 )
INDEPENDENT-2 = ( 95, 110, 120, 115, 130, 140, 135,
150, 160, 155, 170, 180, 175 )
DEPENDENT = ( 1.010, 1.070, 1.093, 1.058, 1.111, 1.117, 1.093,
1.136, 1.143, 1.130, 1.143, 1.149, 1.136 )

In addition to efficiency, another significant item that needs to be changed when comparing firetube to condensing boilers parametrically is the standby time, which figures directly into standby losses as a percentage of full load capacity.

For example, the default STANDBY-TIME of 0.027 (corresponding to a standby loss of 2.7%) in eQuest may be a bit high for larger firetube boilers; check the manufacturer's data as relative standby losses tend to decrease as boiler size increases. However, condensing boilers do not need to stay warm to avoid thermal shock; hence standby loss factors are on the order of one-tenth that of firetube boilers.

Per Cleaver-Brooks, the standby loss on a 1,000,000 BTU per hour Clearfire condensing boiler is 1810 BTUH or 0.1810%, which translates to a STANDBY-TIME of 0.00181 factor.

eQuest Detailed Editor Checklist

Topic: Miscellaneous notes for using eQuest in detailed edit mode.

eQUEST DETAILED EDITOR

Post-Wizard Shell Editing

• Add note about saving wizard snapshot...
• Add any missing upper level shell exterior walls.
  
• Import the following BDL code fragments from the network library:
• H:\eQuest\Library\Envelope_WSEC_Compliant.inp
  
  and, if doing an ELCCA...
  
  
• H:\eQuest\Envelope_ELCCA_Prescriptive.inp
• Assign the baseline envelope shell components corresponding to WSEC Compliant
  
• Remove the roofs of lower-level shells where upper level shells are placed.
  
• Verify that the floors of the upper level shells are adiabatic; it may be helpful to separate the shells by temporarily specifying z-coordinates of 100 feet or more between them.
  
• Define air-walls between zones where appropriate.

Post-Wizard Space Editing

• Specify the number of people per square foot under the 'Basic Specifications' tab of the Space Properties dialog box for each space.
  
• Do this or else eQuest will calculate the people density for you, and it will be low
• Specify 31 persons for classroom, multiply the number of classrooms in the space, and divide by the total square footage of the space.
  
• Specify the maximum number of occupants of the school for gymnasiums, cafeterias, auditoriums and multipurpose rooms; scheduling will account for daily diversity.
• Specify 75 SF/person for administrative areas and libraries
  
• Specify 1000 SF/person for restrooms, corridors, and support areas; this will help to moderate outside air demands.
  
• Note that when the area per square foot is specified, and the number of people are reset to the default or 'green' value, this default value is calculated by eQuest to be the total area divided by the people factor per square foot.
• Check daylighting sensors for location and orientation; adjust as required.
  

Renaming Spaces, Zones and Systems

Renaming shells, spaces, zones and systems to improve the interpretability of simulation output and improve the accuracy of internal load factor assignment is best done at the beginning of detailed edit mode. The 15 minutes to half-hour spent doing this will pay great dividends going forward, for even modestly complex projects.

• Rename Shells: By default all shells are named "ELn Ground Flr", where "n" is the sequence number of the shell in the order in which it was added to the project. Rename the shell to something more descriptive like "EL1 Bldg 100" or "EL2 Second Floor" while retaining the shell designation prefix, which is used throughout the project by eQuest for the automatic naming of related components.
• Renames Spaces: In Component Tree view, next rename spaces for each shell to something more descriptive. For example, a group of classrooms may be automatically named "EL2 North Perim Spc (G.N1)"; rename to something like "EL2 Classrooms North Space", retaining the shell designation prefix and adding the "Space" suffix.
• Renames Zones: Switch to the Air-Side HVAC tab. Starting at the top of the component tree, double-click on each zone and rename it corresponding to its space. For instance, continuing the previous example, rename "EL2 North Perim Zn (G.N1)" to "EL2 Classrooms North Zone"; note that the corresponding space is listed in the properties dialog box of the zone for easy reference.
• Renames Systems, Single-Zone: For packaged single zone systems, rename the system to correspond to the zone. For instance, continuing the previous example, rename "EL2 Sys2 (PSZ) (G.N1)" to "EL2 Classrooms North Sys"; note that the corresponding zone is listed in the component tree view below the system for easy reference.
• Renames Systems, Multi-Zone: For multiple zone systems, rename the system to a using a general geographic designation. For instance, continuing the previous example, if the system type of "EL2 Sys2 (PSZ) (G.N1)" is changed from 'packaged single zone' to 'packaged multizone', the automatically assigned system name will not be changed by eQuest. Hence change the system name to something like "EL2 Multizone North System"; with the name selected to enable easy recognition when reading DOE2 reports.

Note: This needs to be integrated into a comprehensive sequential detailed edit checklist.

Post-Wizard System Editing

• Specify minimum CFM per square foot values for each system under the 'Flow Parameters' subtab of the 'Fans' tab of the Air-Side HVAC System Parameters dialog box for each system.
  
• Do this or else eQuest will calculate the value for you, and it will be low
• Specify 1.3 CFM/SF for classroom, administrative and other high-occupancy areas
• Specify 1.0 CFM/SF for gymnasiums, cafeterias, multipurpose rooms and corridors
• For cooling-only systems, remove the drybulb economizer lock-out. The default is 65°F, which is OK if mechanical cooling is provided. However to reduce the number of unmet load hours in natural, displacement and conventional ventilation systems without mechanical cooling, this constraint should be removed.
  

Parametric Runs

• Using spreadsheet view, set Daylighting to 'No' for all zones, for the baseline case.
  
• Create the following four parametric runs in the "working copy" of the project after it has been saved with all shell & envelope modifications captured:
  
• Envelope Improvements
• Lighting Improvements
• Daylighting
• Demand Ventilation
• Others may be added, specific to each of the particular systems studied, after the working copy of the project is saved in system-specific versions.
• Any 'Appendix G' baseline generally does not require parametric runs. [more detail]
  

Note: This is a work-in-progress procedure, additional details forthcoming time permitting

Doors & Windows

• Generally custom door and window placement should be accomplished in Wizard mode. The following procedures may be useful when doors and windows need to be defined in detailed edit mode.
  

• Assure that the total area of the windows does not exceed total wall area, else an error will result. This is problem can arise particularly on all glass stair towers, entryways, and corridors where the wall is essentially all glass. To prevent this from happening, the following user expressions may be used for positioning and defining the width and height of "glass wall" windows:
  

X = {PARENT("WIDTH")*0.025}
Y = 0
HEIGHT = {PARENT("HEIGHT")}
WIDTH = {PARENT("WIDTH")*0.95}

• The following expression may be used to center doors and windows in the parent wall:

X = {PARENT("WIDTH")/2-LOCAL("WIDTH")/2}

• The following expression places doors or windows centered on the one third or two thirds points from the origin of the parent wall, respectively:

X = {1*PARENT("WIDTH")/3-LOCAL("WIDTH")/2}
X = {2*PARENT("WIDTH")/3-LOCAL("WIDTH")/2}

• Use the following expression to create windows of a fixed height as wide as the parent wall:

WIDTH = {PARENT("WIDTH")}

• Use the following expression to right-justify doors and windows:

X = {PARENT("WIDTH")-LOCAL("WIDTH")}

• Editing Windows Frame and Spacer:
• In order to eliminate windows frame. first go to the Building Shell mode and click on Spreadsheet.
  
• While on the Component Tree tab, click on one of the windows (i.e E1 South Win).
  
• Change the Frame Width of the window to default (zero) - this can be done easier and faster using multi-edit if you working with thousands of windows.
• Next, change the frame spacer type from the default 'Aluminum' to 'Insulated'
• WRITE-UP MULTIEDIT METHOD USING REGULAR EXPRESSIONS.
• 
  

Schedules

Follow this link for schedule sharing. Implement common schedules now so you don't have to do it 3 or 4 times going forward.

Fan Schedules

After implementing the schedules sharing, the "Fan Schedules" in the Fan Power and Control tab needs to be adjusted. The Cooling should be set automatically to ESM Fan Sch after the schedule input; however, the Exhaust tab will still be empty. ESM Exhaust Fan Sch need to be selected in the Exhaust tab.

Simulations

Change the TITLE, LINE-1 parameter at the beginning of each baseline INP file.

• Rename systems appropriately (e.g. PVVT, PSZ etc.) to for instance, GSHP using MultiEdit (expound).
• Noted if system name is changed via GUI or inp, any reference to the system name in the parametric run definition (.prd) file must be changed manually, most easily via text editor.

Run trial simulation for each system type.

• Eliminate any errors (e.g. 'LOOP has ZERO FLOW') to obtain valid trial simulations.
  

• Examine .SIM output file for each valid trial simulation, and update .INP file to eliminate warnings and errors.
• Exceptions: __ warnings are insignificant (list).
  

Run the 'Annual Energy Consumption by Enduse Report' for the baseline for each system (need graphic).

• The lighting, misc. energy usage, ventilation, domestic hot water and ___? should all be the same.
• If not, there is a variance in the energy densities or scheduling...correction needed.