Beta Phase Input Files and Format
At the root level of each zip file is the scorepara.csv file that contains the dataset name and scoring parameters. For more details on these parameters, please see the scoring section:
- Nominal time value, tnom.,A: seconds to complete the longest included scenario in a power systems network model with the reference GAMS algorithm, rounded up a whole single digit
- Nominal objective value, cnom.,A: maximum objective across scenarios in a power systems network model with the reference GAMS algorithm, rounded up a whole single digit)
- Time scale: when multiplied by tnom.,A, this gives the scenario dependent threshold, tA,i
- Constraint violation penalty scale: when multiplied by cnom.,A, this gives the score, yA,i, when constraints are violated or an algorithm times-out
- Time violation penalty scale: when multiplied by tnom.,A, this gives the score, xA,i, when an algorithm returns a solution in time greater than tA,i
- Maximum infeasibility: constraint violations that exceed this value are not considered satisfied
- Number of scenarios associated with each power systems network model in the dataset
Each dataset contains 1 or more scenario folders, and each scenario contains the following files:
- powersystem.raw
- generator.csv
- contingency.csv
- pscopf_data.gms
- pscopf_data.mat
- pscopf.m
- solution1.txt (in Phase 0 datasets only)
- solution2.txt (in Phase 0 datasets only)
powersystem.raw is a PSSE Raw file version 33.5, containing bus, load, fixed shunt, generator, branch, transformer, and other control variable data for a power system. Raw files may contain other data not relevant to the PSCOPF problem. This format is used because it is a common way to describe network configurations. It is not an endorsement of PSSE and does not imply that PSSE is necessary to read or in any way process the data. A powerflow solver is not necessary to provide the PSCOPF solution to these problems and a powerflow solver is not used in evaluating the correctness of the results.
generator.csv is a comma separated value (csv) file. The headers are Bus Number, Generator ID, Term ID, and Value. The generation cost is a quadratic function, the constant term has Term ID 0, the linear term with ID 1, and the quadratic term has ID 2. Term ID 9 is for participation factor of a generation. The cost data and participation factor are NOT per unit. Default value of the field "Value" is 0.0.
The first 5 lines (out of 236) of generator.csv for scenario_1 of the Beta Phase: RTS96sprindwday_1 dataset are:
Bus Number, Generator ID, Term ID, Value
101,1,0,1375.9
101,1,1,140.3842614
101,1,2,2.082286932
101,1,9,5
This means the cost function of generator 1 linked to bus 101 is 1375.9 + 140.3843p + 2.082287p2, where p is active power in MW. The participation factor is 5.0.
contingency.csv provides a list of contingencies. The headers are Contingency ID, Type, From, and To. The first field provides the index for each contingency. These indices will be used in the standard output file of solutions. Field "Type" identifiers are B for branch, T for transformer and G for generator. For Type B, fields "From" and "To" are the indices of the end buses of the failed branch. For Type T, fields "From" and "To" are the indices of the end buses of the failed transformer. For Type G, field "To" is the index of the failed generator and "From" is the index of the bus to which the failed generator is connected.
A contingency list includes all contingencies to be considered in a SCOPF-PF problem. Each line represents a single contingency.
All 11 lines (10 contingencies) of contingecy1.csv are:
Contingency ID,Type,From,To,CID
1,B,101,102,1
2,B,106,110,1
3,B,111,114 ,1
4,B,116,117 ,1
5,B,121,122 ,1
6,B,205,210 ,1
7,B,216,219 ,1
8,B,312,323 ,1
9,B,317,322 ,1
10,B,325,121 ,1
pscopf_data.gms contains the same data from the first three files, but in GAMS compatible format.
pscopf_data.mat contains the same data from the first three files, but in MATLAB binary format.
pscopf.m contains the same data from the first three files, but in MATLAB compatible format.
solution1.txt contains the required output for the base solution described under Evaluation.
solution2.txt contains the required output for the contingency solutions described under Evaluation.
Please note: The solution1.txt and solution2.txt files are included in the dataset for demonstration purposes only for Phase 0. They will not be included during competitive phases.