Time Limit Imposed on Code2

While there may not be a specific time limit for contingency analyses in the real-world, many of the code 2 run-times from Trial Event 1 submissions were beyond what we would consider as “reasonable”. With the aim to encourage product designs that are innovative and compelling for real-world applications and to ensure that we can test your submissions against more networks and scenarios in Trial Event 2, we will impose the following time limits going forward (changes are in bold). Also note, that we will only re-solve the scenarios in Divisions 3 and 4 by request, standard procedure will be to leverage results from Divisions 1 and 2 to generate scores for Divisions 3 and 4. Please indicate whether your code is designed to operate differently in these divisions.


Division 1

Division 2

Division 3

Division 4

Code 1


10 minutes

45 minutes

Re-solve Div. 1 scenarios by request (10 minutes)

Re-solve Div. 2 scenarios by request (45 minutes)

Code 2


2 seconds / contingency

2 seconds / contingency

Re-solve by request (2 sec./cont.)

Re-solve by request

(2 sec./cont.)

This time limit only applies to the wall-clock time limit for the code to solve each scenario and produce the relevant solution file. We encourage all teams to employ a multi-node approach (up to six nodes) in order to improve their performance.

To state the new time limit for Code 2 in another way: For Trial 2, a team will receive 1 hour and 40 minutes for Code 2 to test a scenario with 3000 contingencies (3000 * 2 = 6000 seconds). The time limit is considered only against the entire execution of Code 2, not against each individual contingency, (it is okay for some contingencies to require more than 2 seconds to solve as long as the total run-time is within the limit). This wall-clock time limit is the same for a team that uses 6 nodes and for a team that elects to only use one.