ifference between revisions of "EMO:Generation Profile File Format"
(3 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
{{#hidens:}} | {{#hidens:}} | ||
− | The formatting criteria for files containing Generation Profile data to be imported into a '''''Forecast Definition''''' or a '''''Powerflow Case Definition''''' are described below. | + | The formatting criteria for files containing Generation Profile data to be imported into a '''''[[EMO:The Forecast Definition Window|Forecast Definition]]''''' or a '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition]]''''' are described below. |
The file must be in csv format and can be of any name. File format can be in one of two formats: | The file must be in csv format and can be of any name. File format can be in one of two formats: | ||
Line 58: | Line 58: | ||
:Numeric (three decimal places) or zero | :Numeric (three decimal places) or zero | ||
|} | |} | ||
+ | |||
+ | |||
+ | The following is a sample section of a Units as Columns Generation Profile file: | ||
+ | [[File:Units as Columns Gen.PNG|1000px|thumb|centre|Units as Columns Generation Profile file]] | ||
+ | |||
+ | |||
+ | === Units as Rows === | ||
+ | The file must contain two row types: | ||
+ | *two header rows | ||
+ | *one or more data rows | ||
+ | |||
+ | The header row must be the first row in the file and must contain the text formatted as presented in the following table. | ||
+ | |||
+ | {|class="wikitable" | ||
+ | ! Row | ||
+ | ! Column | ||
+ | ! Text | ||
+ | |- | ||
+ | | rowspan="2" | | ||
+ | :1 | ||
+ | | | ||
+ | :1 | ||
+ | | | ||
+ | :"Generator Names/Dates" | ||
+ | |- | ||
+ | | | ||
+ | :2 - n | ||
+ | | | ||
+ | :3 Alpha day of week (e.g. "Mon") | ||
+ | |- | ||
+ | | rowspan="2"| | ||
+ | :2 | ||
+ | | | ||
+ | :1 | ||
+ | | | ||
+ | :"Trading Period" | ||
+ | |- | ||
+ | | | ||
+ | :2 - n | ||
+ | | | ||
+ | :Numeric (1 - 50) | ||
+ | |} | ||
+ | |||
+ | |||
+ | A data row will exist for each Node and must conform to the formatting requirements as presented in the following table: | ||
+ | |||
+ | {|class="wikitable" | ||
+ | ! Column | ||
+ | ! Format | ||
+ | |- | ||
+ | | | ||
+ | :Generator Names/Dates | ||
+ | | | ||
+ | :<Unit Name> (e.g. ABY0111) | ||
+ | |- | ||
+ | | | ||
+ | :Unit Generation | ||
+ | | | ||
+ | :Numeric (three decimal paces) or zero | ||
+ | |} | ||
+ | |||
+ | |||
+ | The following is a sample section of a Units as Rows Generation Profile file: | ||
+ | [[File:Units as Rows Gen.PNG|1000px|thumb|centre|Sample section of a Units as Rows Generation Profile file]] | ||
+ | |||
+ | [[Main Page|Home]] |
Latest revision as of 10:42, 13 February 2014
The formatting criteria for files containing Generation Profile data to be imported into a Forecast Definition or a Powerflow Case Definition are described below.
The file must be in csv format and can be of any name. File format can be in one of two formats:
- Unit as Columns
- Unit as Rows
Units as Columns
The file must contain two row types:
- One header row
- One or more data rows
The header row must be the first row in the file and must contain the text formatted as presented in the following table:
Row | Column | Text |
---|---|---|
|
|
|
|
| |
|
|
A data row will exist for each Trading Period and must conform to the formatting requirements as presented in the following table:
Column | Format |
---|---|
|
|
|
|
|
|
The following is a sample section of a Units as Columns Generation Profile file:
Units as Rows
The file must contain two row types:
- two header rows
- one or more data rows
The header row must be the first row in the file and must contain the text formatted as presented in the following table.
Row | Column | Text |
---|---|---|
|
|
|
|
| |
|
|
|
|
|
A data row will exist for each Node and must conform to the formatting requirements as presented in the following table:
Column | Format |
---|---|
|
|
|
|
The following is a sample section of a Units as Rows Generation Profile file: