Time Series Hourly Table

The Time Series Hourly table contains values for variables that may be changed on an hourly basis, such as wind profiles.

NOTE: Multiple Time Series Hourly tables may be checked in-study. When multiple tables are selected, Aurora will merge them together at the beginning of a run. A few things to note:

1. The ID, Date, and Hour combination should be unique for the group of tables as a whole. This requirement is most easily met by making sure the ID field is unique in each table. For example, multiple tables in-study should not have a row with ID=‘Test’, Date=1/1/2018 and Hour=1.

2. While Primary Keys must be unique within a given table, multiple tables may use the same Primary Keys.

For more information on how to specify a time series for a variable, see Entering a Time Series.

References to data series in the Data column of the Time Series Hourly table may have one of the following formats:

HR_ID or HR_ID|Data

where ID is the name of the data series in the ID column and Data is the "Data " column.

Multiple data columns, with user-specified (or custom) column names, can be added and referenced using the following format:

HR_ID|CustomDataColumn

where CustomDataColumn is the name of the custom data column being referenced in the Time Series Hourly table.

NOTE: Multiple custom data columns can be added to a Time Series Hourly table, however a column called "Data" must exist in the table even when multiple data columns have been added. Invalid data column names include: Year, Hour, Month, and Day.

Applying Data to Multiple Years

A single year of data in the Time Series Hourly table can be re-used over multiple years when the referencing cell has the following format:

HR_ID|CustomDataColumn|OriginalYear

where OriginalYear refers to the year of the hourly data series to be re-used in subsequent years of the study period.

The ability to re-use hourly data from one year over subsequent years of the study period has the potential benefit of reducing the size of the Time Series Hourly table and facilitating data management.

For another method of how to use hourly data across multiple years, see Using Hourly Data via CDS.

Day of Week

To automatically align a particular year of data to the days of week in another year, add |DOW to the end of the time series hourly reference that includes a year and Aurora will do extra work to match up the days of week in the simulation year with the original year, e.g. hr_WindShape|ERCOTWest|2018|DOW. It does this using the following method:

For a given simulation date, Aurora finds the current day of week for it, and for the corresponding date in the reference year.
If the day of week is the same for both, then that reference date is used.
Otherwise, Aurora adds some number of days (less than seven) to the reference date to get to a date that has the same day of week as the simulation date. If that date is still in the reference year, it is used.
Otherwise, in the case where the simulation date is at the end of December and the found reference date is in January of the next year, Aurora subtracts 364 days from the reference date and uses that day.

For example, suppose that the reference year is 2018 and the current simulation date is 7/5/2022, a Tuesday. The date chosen from the reference year would be 7/10/2018, a corresponding Tuesday. If using the same years, and the simulation date was 12/30/2022, a Friday, then the date chosen from the reference year would be 1/5/2018, the nearest corresponding Friday.

COLUMNS INCLUDE

Time Series Hourly Table