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

ASHRAE 90.1-2004 Overview

Equipment Efficiencies
Table 6.8 .1A Air Conditioners and Condensing Units (Efficiencies)
Table 6.8 .1E & F Furnaces and Boilers

Lighting Power Densities
Table 9.4 .5 Building Exteriors
Table 9.5.1 Using the Building Area Method
Table 9.6.1 Using the Space by Space Method

Appendix A

Appendix B.

(HEI intranet links above)

Heat Pump Parametrics

Topic: Calculating heat pump parametrics using DOE/ORNL's nifty online tool to justify modeling assumptions

Note that residential heat pump EER and SEER ratings are obtained from a certification test performed with the supply blower fan working against a 0.10, 0.15 or 0.20 inches of external static pressure, for 2 ton and less, 2-1/2 to 3-1/2 ton, and 4 ton and larger units respectively, per Table 2 on page 59149 of this DOE test procedure document.

One interesting thing to note is that the test tolerance is 0.05 inches of static, so a manufacturer wishing to maximize the performance rating of a given heat pump may utilize external static conditions of 0.05, 0.10 and a 0.15 respectively for the given size ranges in the test procedure.

Even more interesting (see footnotes below) is that commercial heat pumps connected to ducts aren't allowed to count supply fan energy in their EER/COP/SEER/HSPF calculations, according to ANSI/ARI/ASHRAE ISO Standard 13256-1:1998.

Thus for most low-cfm heat pump applications, the impact of the test-condition supply fan energy can be conservatively ignored. That is, not subtracted-out from the relevant performance equation in order to calculate a new EER, SEER, COP or HSPF.

Which is not to say that supply fan energy should be ignored, only that it needs to be modeled separately at actual design conditions. Supply fans for commercial heat pumps usually run continuously, and can easily be modeled as such in eQuest -- just be sure to select 'Indoor Fan Mode' as 'Continuous' on the 'Flow Parameters' panel of the system 'Fans' tab.

(click on the image to see a larger version)

If challenged to subtract-out supply fan energy by LEED or energy rebate reviewers, refer to ANSI/ARI/ASHRAE ISO Standard 13256-1:1998 Water-Source Heat Pumps - Testing and Rating for Performance - Part 1: Water-to-Air and Brine-to-Air Heat Pump. Minor excerpts reprinted below.

Footnotes courtesy of Xiaobing Liu:

1. The fan power included in the EER/COP calculation may not be the same as the fan actual demand when the heat pump runs. For water-source heat pumps, ANSI/ARI/ASHRAE ISO Standard 13256-1:1998 (Water-source heat pumps - testing and rating for performance - Part 1: Water-to-air and brine-to-air heat pump) states following requirements for fan power input in COP/EER calculations

4.1.2 Power input of fans for heat pumps without duct connection

In the case of heat pumps which are not designed for duct connection and which are equipped with an integral fan, all power consumed by the fans shall be included in the effective power input to the heat pump.

4.1.3 Power input of fans for heat pumps with duct connection

4.1.3.2 If a fan is an integral part of a heat pump, only the portion of the fan power required to overcome the internal resistance shall be included in the effective power input to the heat pump. The fraction which is to be excluded from the total power consumed by the fan shall be calculated using the following formula: φfa = q x Δp / η

where

φfa is the fan power adjustment, in watts;

η = 0.3 × 103 by convention;

Δp is the measured external static pressure difference, in pascals;

q is the nominal airflow rate, in litres per second.

This value shall be subtracted from the heating capacity and added to the cooling capacity.

2. The reason for this is that, in a particular heat pump installation, depending on the air flow and external static pressure of the duct work, the fan power is different, which is unknown when the heat pump is tested in the lab. So, to isolate from the unknown effect of the external duct work, only the portion of the fan power required to overcome the internal resistance shall be included in the effective power input to the heat pump if the heat pump is designed for duct connection. Therefore, the fan power in the real operating condition should be specified in the simulation to more accurately predict the fan energy consumption.

PFEC Standard Submittal Package

Topic: Standard documents and backup eQuest reports for a PFEC Submittal package.

• Cover Letter (Word)
• PFEC Form (Excel)
• Monthly Energy Consumption by Enduse (eQuest Report)
• Monthly Utility Bills -- All Rates (eQuest Report)
• eQuest Energy Model View (screencapture via MSPaint)

Example Document (HEI intranet link)

eQuest Multiuse Facilities

Topic: Requirements and assumptions for modeling multiuse facilities for LEED certification.

See ASHRAE 90.1-2004 Table 5-5.4, Building Envelope Requirements for Climate Zone 4 for baseline thermal performance parameters.

The Washington State Energy Analysis Parameters spreadsheet documents energy end usage assumptions for LEED and WSEC modeling.

FUNCTIONAL AREA	WSEC	ASHRAE	DESIGN
Residential	0.8	1.0
Corridor	0.8	0.5
Lobby	1.2	1.3
Retail	1.5	1.5
Club House/ Fitness	1.0	0.9
Covered Parking	0.2	0.3
Exterior	0.5	0.5