Overview

This section covers the fundamentals of event file, including:

• Event Creation
• Event File Fields
• Property Definitions
• Sample Configurations
• Batch File Execution

Creating an Event File

Event files allow you to simulate system changes and can be created manually or generated from historical load data.

Common Use Cases

• Simulating unit outages.
• Adding link constraints (e.g., VisLuz or MinVis).
• Modifying the generation capacity of a specific unit.

---

Step-by-Step Procedure

• Event File
• Event Set

1

Create a New Event File

1. Navigate to the Events folder in your directory.
2. Create a copy of an existing event file to use as a template.
3. Rename the copied file to reflect your new scenario.
4. Open the new file in your preferred text or spreadsheet editor.

2

Edit Event Fields

Modify the fields based on the specific parameters of your desired event. Refer to the data dictionary below to ensure accurate inputs.

---

Event File Fields

General Fields

Every event configuration requires the following foundational fields:

• EID: An arbitrary Event ID assigned by the user.
• Type: The object type associated with the event (e.g., Region, Link, Site, SUnit, DUnit, Sites, Storage).
• StartTime / EndTime: The exact start and end times defining the event's duration.
• Property: The specific object property you wish to modify (see the Property Definitions section below).
• Capacity: The numerical value applied to the selected property.

DUID (Object ID) Mapping

The DUID field requires a specific Object ID. The required value depends entirely on the Type you selected above:

Selected Type	Required DUID Value
Link	MINVIS1 or VISLUZ1
SUnit / DUnit	The specific Unit ID from the database.
Site	The specific Site ID from the database.
Sites	BATTERY, BIO, CCGT, COAL, DIESEL, DISPDEM, GEO, HYDRO, MR ALL, OCGT, PUMP, or ROR.
Region	CLUZ, CVIS, or CMIN.
Storage	The specific Storage ID from the database.

---

Property Definitions by Object Type

Depending on the Type of object you are modifying, you can adjust specific properties in the Property field. Select an object type below to view its available properties:

• Pool
• Region
• Sites
• SUnit / DUnit / Site
• Link

Pool

• %SRMC: Percentage multiplier for Short Run Marginal Cost (SRMC).
• %BidPrc: Percentage multiplier for the price of all bids.
• MaxPrc: Maximum (ceiling) price.
• MinPrc: Minimum (floor) price.
• VOCE: Value of carbon emissions.
• Weather: HOTDAY, WARMDAY, NORMAL, COOLDAY, or COLDDAY.
• DemScale: Multiplier for demand.

Configuration Examples

Here are practical examples of how to configure the CSV fields for common event scenarios:

• Unit Outages
• Modify Capacity
• Link Constraints

Unit Outages

To simulate an outage for specific generator units (SUnit), set the %MwCap (MW Capacity Percentage) to 0. This effectively reduces their capacity to zero during the specified timeframe.

*EID	Type	DUID	StartTime	EndTime	Property	Capacity
05TPC_G0	SUnit	05TPC_G0	11/25/2025 2:50:00 AM	11/25/2025 5:25:00 AM	%MwCap	0
13DCPP_U	SUnit	13DCPP_U	11/27/2025 4:55:00 AM	11/28/2025 12:05:00 AM	%MwCap	0
01MARVEL	SUnit	01MARVEL	11/27/2025 12:25:00 PM	11/28/2025 12:05:00 AM	%MwCap	0
03QPPL_G	SUnit	03QPPL_G	11/29/2025 8:40:00 AM	11/29/2025 9:00:00 AM	%MwCap	0
01ANDA_G	SUnit	01ANDA_G	11/29/2025 11:00:00 PM	11/30/2025 12:05:00 AM	%MwCap	0
01APEC_G	SUnit	01APEC_G	11/30/2025 9:15:00 AM	11/30/2025 9:25:00 AM	%MwCap	0

Running Events via Batch File

When executing your simulation through a batch file, the command-line flag you use depends on whether you are applying a single event file or a grouped event set.

• Single Event File (-e) Use the -e flag followed by the exact filename of your individual event.

  Single Event Example

  iPool.exe -o BASECAL -s BACK01 -e Ev_HISTORICAL.csv

• Event Set File (-eset) Use the -eset flag followed by the filename of your Event Set CSV. This will instruct the system to run all files listed within that set.

  Single Event Example

  iPool.exe -o BASECAL -s BACK01 -eset EventSet.csv