# Set Up the Analysis Project¶

At the top level of the ResStock repository you just downloaded, you will see two analysis project folders:

• project_national
• project_testing

## OpenStudio Measures¶

### Simulation Controls¶

Using this measure you can set the simulation timesteps per hour, the run period begin month/day and end month/day, and the calendar year (for start day of week). By default the simulations use a 10-min timestep (i.e., the number of timesteps per hour is 6), start on January 1, end on December 31, and run with a calendar year of 2007 (start day of week is Monday).

1. Simulation Timesteps Per Hour: The value entered here is the number of (zone) timesteps to use within an hour. For example a value of 6 entered here directs the program to use a zone timestep of 10 minutes and a value of 60 means a 1 minute timestep.
2. Run Period Begin Month: This numeric field should contain the starting month number (1 = January, 2 = February, etc.) for the annual run period desired.
3. Run Period Begin Day of Month: This numeric field should contain the starting day of the starting month (must be valid for month) for the annual run period desired.
4. Run Period End Month: This numeric field should contain the ending month number (1 = January, 2 = February, etc.) for the annual run period desired.
5. End Period End Day of Month: This numeric field should contain the ending day of the ending month (must be valid for month) for the annual run period desired.
6. Calendar Year:This numeric field should contain the calendar year that determines the start day of week. If you are running simulations using AMY weather files, the value entered for calendar year will not be used; it will be overridden by the actual year found in the AMY weather file.

### Build Existing Model¶

This measure creates the baseline scenario. It incrementally applies OpenStudio measures (located in the resources directory, which should be at the same level as your project directory) to create residential building models. Set the following inputs:

1. Building ID: This sets the number of simulations to run in the baseline and each upgrade case.
2. Workflow JSON: The name of the JSON file (in the resources dir) that dictates the order in which measures are to be run. If not provided, the order specified in resources/options_lookup.tsv will be used.
3. Number of Buildings Represented: The total number of buildings this sampling is meant to represent. This sets the weighting factors. For the U.S. single-family detached housing stock, this is 80 million homes.
4. Sample Weight of Simulation: The number of buildings each simulation represents. Total number of buildings / Number of simulations. This argument is optional (it is only needed for running simulations on NREL HPC), so you can leave it blank.
5. Downselect Logic: Logic that specifies the subset of the building stock to be considered in the analysis. Specify one or more parameter|option as found in the resources/options_lookup.tsv. (This uses the same syntax as the Apply Upgrade measure.) For example, if you wanted to only simulate California homes you could enter Location Region|CR11 in this field (CR refers to “Custom Region”, which is based on RECS 2009 reportable domains aggregated into groups with similar climates; see the entire custom region map). Datapoints that are excluded from the downselect logic will result in “completed invalid workflow”. Note that the Building ID input refers to the number of datapoints before downselection, not after. This means that the number of datapoints remaining after downselection would be somewhere between zero (i.e., no datapoints matched the downselect logic) and Building ID (i.e., all datapoints matched the downselect logic).
6. Measures to Ignore: INTENDED FOR ADVANCED USERS/WORKFLOW DEVELOPERS ONLY. Measures to exclude from the OpenStudio Workflow specified by listing one or more measure directories separated by ‘|’. Core ResStock measures cannot be ignored (the Build Existing Model measure will fail).

Note

Manual Sampling: To run the sampling script yourself, from the command line execute, e.g. ruby resources/run_sampling.rb -p project_national -n 10000 -o buildstock.csv, and a file buildstock.csv will be created in the resources directory.

If a custom buildstock.csv file is located in a project’s housing_characteristics directory when you run the project, it will automatically be used to generate simulations. If it’s not found, the run_sampling.rb script will be run automatically on OpenStudio-Server to create one. You’ll also want to make sure that the number of buildings in the sampling csv file matches the max value for the Building ID argument in the Build Existing Model, as that tells OpenStudio how many datapoints to run. (For each datapoint, the measure will then look up its building description from the sampling csv.)

You can use this manual sampling process to downselect which simulations you want to run. For example, you can use the command above to generate a buildstock.csv for the entire U.S. and then open up this file in Excel and delete all of the rows that you don’t want to simulate (e.g., all rows that aren’t in New York). Keep in mind that if you do this, you will need to re-enumerate the “Building” column as “1” through the number of rows.

Each “Apply Upgrade” measure defines an upgrade scenario. An upgrade scenario is a collection of options exercised with some logic and costs applied. In the simplest case, we apply the new option to all houses. The available upgrade options are in resources/options_lookup.tsv in your git repository.

For this example, we will upgrade all windows by applying the Windows|Triple, Low-E, Non-metal, Air, L-Gain option to all houses across the country. We do this by entering that in the Option 1 box on the Apply Upgrade measure. Also, we’ll give the upgrade scenario a name: “Triple-Pane Windows” and a cost of \$40/ft2 of window area by entering the number in Option 1 Cost Value and selecting “Window Area (ft^2)” for Option 1 Cost Multiplier.

Like the downselect logic, excluded datapoints (i.e., datapoints for which the upgrade does not apply) will result in “completed invalid workflow”. For a full explanation of how to set up the options and logic surrounding them, see Upgrade Scenario Configuration.

## Reporting Measures¶

In general, reporting measures process data after the simulation has finished and produced results. As a note, make sure that the Timeseries CSV Export and Utility Bill Calculations measures are placed before the Server Directory Cleanup measure.

### Simulation Output Report¶

1. Include End Use Subcategories: Leave this alone if you do not want to report annual totals for end use subcategories. Select it if you want to report them. See below for a list of available end use subcategories.

### Timeseries CSV Export¶

If you do not need the timeseries data for your simulations, you can skip this measure to save disk space. Otherwise, one csv file per datapoint will be written containing end use timeseries data for their model.

End uses are listed below.

End Use Units
total site energy [MBtu] MBtu
net site energy [MBtu] MBtu
total site electric (kWh), gas (therm), oil/propane/wood (MBtu)
net site electric (kWh)
heating electric (kWh), gas (therm), oil/propane/wood (MBtu)
cooling electric (kWh)
central system heating electric (kWh), gas (therm), oil/propane (MBtu)
central system cooling electric (kWh)
interior lighting electric (kWh)
exterior lighting electric (kWh)
exterior holiday lighting electric (kWh)
garage lighting electric (kWh)
interior equipment electric (kWh), gas (therm), propane (MBtu)
fans heating electric (kWh)
fans cooling electric (kWh)
pumps heating electric (kWh)
pumps cooling electric (kWh)
central system pumps heating electric (kWh)
central system pumps cooling electric (kWh)
water heating electric (kWh), gas (therm), oil/propane (MBtu)
pv electric (kWh)
1. Reporting Frequency: The timeseries data will be reported at hourly intervals unless otherwise specified. Available reporting frequencies are listed below.
• Timestep
• Daily
• Monthly
• Runperiod

Setting the reporting frequency to ‘Timestep’ will give you interval output equal to the zone timestep set by the Simulation Controls measure. Thus, this measure will produce 10-min interval output when you select ‘Timestep’ and leave the Simulation Controls measure at its default settings.

1. Include End Use Subcategories: Select this to include end use subcategories. The default is to not include end use subcategories. End use subcategories are listed below.

End Use Subcategory Units
refrigerator electric (kWh)
clothes washer electric (kWh)
clothes dryer electric (kWh), gas (therm), propane (MBtu)
cooking range electric (kWh), gas (therm), propane (MBtu)
dishwasher electric (kWh)
house fan electric (kWh)
range fan electric (kWh)
bath fan electric (kWh)
ceiling fan electric (kWh)
extra refrigerator electric (kWh)
freezer electric (kWh)
pool heater electric (kWh), gas (therm)
pool pump electric (kWh)
hot tub heater electric (kWh), gas (therm)
hot tub pump electric (kWh)
gas grill gas (therm)
gas lighting gas (therm)
gas fireplace gas (therm)
well pump electric (kWh)
hot water recirculation pump electric (kWh)
vehicle electric (kWh)
2. Output Variables: If you choose to report any output variables (e.g., “Zone Air Temperature” or “Site Outdoor Air Humidity Ratio”), enter a comma-separated list of output variable names. A list of available output variables can be viewed in EnergyPlus’s .rdd file.

### Utility Bill Calculations¶

This measure is currently under construction.