Sandbox submissions are now OPEN. It will open for approved teams between Event submissions. We encourage entrants to use the Sandbox to verify all the runtime settings necessary to use the Evaluation Platform for upcoming Events are in place. The Submission button on this page will only be on for Events.

Please use ONLY the scenarios listed in the tables below. The Sandbox dataset library contains other scenarios from the development stage of the project that no longer work.

S0

Download the revised (12/8/2022) S0 Sandbox datasets (3.1 MB). It contains 4 network models consisting of  3-, 14-, 37- and 73-buses. Each S0 network model in this set consists one scenario with 4 JSON files for each division as follows:

1. scenario_nnn.json contains the problem input data,
2. scenario_nnn_summary.json contains information about the problem input data, including the length and number of periods as in the table below,
3. scenario_nnn_solution.json contains a feasible solution file produced by the Benchmark program for this scenario, and
4. scenario_nnn_evaluation.json, the output from the Evaluation program that calculates the objective ("z") from the solution file. This will be the score for the scenario.

These small datasets are intended to help entrants create solvers that can correctly handle Challenge 3 data formats. The solutions produced by the Benchmark are not intended to be anywhere near optimal. Their purpose is to demonstrate that feasible solutions do exist and what a valid solution file would look like.

S1

Download the S1 Sandbox datasets (55.5 MB) released December 22, 2022. It contains 4 network models consisting of  600-, 1576-, 4200- and 6049-buses. Each S1 network model in this set consists one scenario with 3 JSON files for each division as follows:

1. scenario_nnn.json contains the problem input data,
2. scenario_nnn_pop_solution.json contains a feasible solution file produced by the POP (Prior Operating Point) program for this scenario, and
3. scenario_nnn_pop_eval_summary.json, the output from the Evaluation program that calculates the objective ("z") from the solution file. This will be the score for the scenario.

E1

Download the E1 Sandbox datasets (312.5 MB) released February 14, 2023. It contains 257 scenarios comprised of 8 network models consisting of  3-, 14-, 37-, 73-, 600-, 1576-, 4200- and 6049-buses from the S0 and S1 datasets, with variations on load profiles. No industry dataset was used for Event 1.

Each E1 network model in this set consists of multiple scenarios, each with 3 files (771 total files):

1. scenario_nnn.json contains the problem input data,
2. scenario_nnn.json.pop_solution.json contains a feasible solution file produced by the POP (Prior Operating Point) program for this scenario, and
3. scenario_nnn.json.popsolution.log, the output from the Evaluation program that calculates the objective ("z") from the solution file. If positive and feasible, this will be the score for the scenario.

The solutions produced by the Prior Operating Point (POP) program are not intended to be anywhere near optimal. Their purpose is to demonstrate that feasible solutions do exist and what a valid solution file would look like. The E1 results demonstrate that positive feasible solutions are possible for every scenario (see the Best results in column E). See the Event 1 Leaderboard for more results.

S2

Download the (3/16/2023) S2 Sandbox datasets (15.5 MB). The zip file contains 2 network models consisting of 2000- and 6717-buses intended for use with Event 2. Each network model consists one scenario with 3 JSON files for each division as follows:

1. scenario_001.json contains the problem input data,
2. scenario_001.json.pop_solution.json contains a feasible solution file produced by the POP (Prior Operating Point) program for this scenario, and
3. scenario_001.json.popsolution.log, the output from the Evaluation program that calculates the objective ("z") from the solution file. This will be the score for the scenario.

E2

The E2 Sandbox datasets released May 10, 2023 are available as three downloads (one for each Division): C3E2D1 (65 MB); C3E2D2 (320 MB); and C3E2D3 (245 MB). Together they contain 175 scenarios comprised of 8 network models consisting of  73-, 617-, 1576-, 2000-, 4224-, 6049-, 6708-, and 6717-buses from the S1 and S2 datasets, with variations on load profiles. The 6708-bus network is an industry dataset and is not included in the download but is available for use in the Sandbox, although results will be limited to the objective value produced by the Evaluation program. The 6708-bus dataset makes use of the "additional_shunt" feature described on page 15 of the Data Format document.

Each E2 network model in this set consists of multiple scenarios, each with 3 files as in E1:

1. scenario_nnn.json contains the problem input data,
2. scenario_nnn.json.pop_solution.json contains a feasible solution file produced by the POP (Prior Operating Point) program for this scenario, and
3. scenario_nnn.json.popsolution.log, the output from the Evaluation program that calculates the objective ("z") from the solution file. If positive and feasible, this will be the score for the scenario.

The solutions produced by the Prior Operating Point (POP) program are not intended to be anywhere near optimal. Their purpose is to demonstrate that feasible solutions do exist and what a valid solution file would look like.

E2.1

A requirement on problem data that the penalty coefficients on certain soft constraints be strictly positive has been added to the Problem Formulation. These constraints are bus real and reactive power balance, line apparent power flow limits, multi-interval energy production and consumption limits, and reserve balance constraints on regulation down, regulation up, synchronized reserve, non-synchronized reserve, ramping reserve down, ramping reserve up, reactive power reserve down, and reactive power reserve up. This requirement is posted in the May 15, 2023 version of the Problem Formulation document, and the change is mentioned in the change log item for May 15, 2023. The data checker code in C3DataUtilities now checks for positivity of these coefficients and reports an error if they are not positive. Two public datasets, the E2 2000- and 6717-bus systems released May 10, do not meet this positivity requirement and therefore fail the current data checker. We have modified these datasets by setting the relevant coefficients equal to 1 ($/pu-h), and the modified datasets pass the data checker. Download the (5/15/2023) E2.1 Sandbox datasets (276 MB) with the updated 2000- and 6717-bus systems.