web: backend: Implement view endpoint

Replace nthreads by maxthreadid and use :static scheduling to disable
task migration. Fixes #56.

.github/workflows/test.yml

@@ -1,4 +1,4 @@
-name: Tests
+name: Build & Test
 on:
   push:
   pull_request:
@@ -6,19 +6,30 @@ on:
     - cron: '45 10 * * *'
 jobs:
   test:
+    name: Julia ${{ matrix.version }} - ${{ matrix.os }} - ${{ matrix.arch }}
     runs-on: ${{ matrix.os }}
     strategy:
       matrix:
-        julia-version: ['1.3', '1.4', '1.5', '1.6']
+        version: ['1.10', '1.12']
-        julia-arch: [x64, x86]
+        os:
-        os: [ubuntu-latest, windows-latest, macOS-latest]
+          - ubuntu-latest
-        exclude:
+        arch:
-          - os: macOS-latest
+          - x64
-            julia-arch: x86
     steps:
       - uses: actions/checkout@v2
-      - uses: julia-actions/setup-julia@latest
+      - uses: julia-actions/setup-julia@v1
         with:
-          version: ${{ matrix.julia-version }}
+          version: ${{ matrix.version }}
-      - uses: julia-actions/julia-buildpkg@latest
+          arch: ${{ matrix.arch }}
-      - uses: julia-actions/julia-runtest@latest
+      - name: Run tests
+        shell: julia --color=yes --project=test {0}
+        run: |
+          using Pkg
+          Pkg.develop(path=".")
+          Pkg.update()
+          using UnitCommitmentT
+          try
+            runtests()
+          catch
+            exit(1)
+          end

.gitignore

@@ -1,20 +1,44 @@
+*-off.md
 *.bak
 *.gz
-*.lastrun
-*.so
-*.mps
 *.ipynb
+*.lastrun
+*.mps
+*.so
+*/Manifest.toml
+.AppleDB
+.AppleDesktop
+.AppleDouble
+.DS_Store
+.DocumentRevisions-V100
+.LSOverride
+.Spotlight-V100
+.TemporaryItems
+.Trashes
+.VolumeIcon.icns
+._*
+.apdisk
+.com.apple.timemachine.donotpresent
+.fseventsd
+.idea
 .ipy*
+.vscode
+Icon
+Manifest.toml
+Network Trash Folder
+TODO.md
+Temporary Items
 benchmark/results
 benchmark/runs
 benchmark/tables
 benchmark/tmp.json
 build
+docs/_build
+docs/src/tutorials/customizing.md
+docs/src/tutorials/lmp.md
+docs/src/tutorials/market.md
+docs/src/tutorials/usage.md
 instances/**/*.json
 instances/_source
 local
 notebooks
-TODO.md
-docs/_build
-.vscode
-Manifest.toml

.zenodo.json

@@ -0,0 +1,27 @@
+{
+    "creators": [
+      {
+        "orcid": "0000-0002-5022-9802",
+        "affiliation": "Argonne National Laboratory",
+        "name": "Santos Xavier, Alinson"
+      },
+      {
+        "affiliation": "University of Florida",
+        "name": "Kazachkov, Aleksandr M."
+      },
+      {
+        "affiliation": "Technische Universität Berlin",
+        "name": "Yurdakul, Ogün"
+      },
+      {
+        "affiliation": "Purdue University",
+        "name": "He, Jun"
+      },
+      {
+        "affiliation": "Argonne National Laboratory",
+        "name": "Qiu, Feng"
+      }
+    ],
+    "title": "UnitCommitment.jl: A Julia/JuMP Optimization Package for Security-Constrained Unit Commitment",
+    "description": "<b>UnitCommitment.jl</b> (UC.jl) is an optimization package for the Security-Constrained Unit Commitment Problem (SCUC), a fundamental optimization problem in power systems used, for example, to clear the day-ahead electricity markets. The package provides benchmark instances for the problem and Julia/JuMP implementations of state-of-the-art mixed-integer programming formulations."
+  }

CHANGELOG.md

@@ -11,6 +11,37 @@ All notable changes to this project will be documented in this file.
 [semver]: https://semver.org/spec/v2.0.0.html
 [pkjjl]: https://pkgdocs.julialang.org/v1/compatibility/#compat-pre-1.0
 
+## [0.4.1] - 2025-11-05
+### Fixed
+- Fix multi-threading issues in Julia 1.12
+
+### Changed
+- The package now requires Julia 1.10 or newer
+
+## [0.4.0] - 2024-05-21
+### Added
+- Add support for two-stage stochastic problems
+- Add support for day-ahead and real-time market clearing simulation
+- Add time decomposition methods
+- Add scenario decomposition methods (progressive hedging)
+- Add support for energy storage units
+- Rewrite documentation with runnable examples
+
+## [0.3.0] - 2022-07-18
+### Added
+- Add support for multiple reserve products and zonal reserves.
+- Add flexiramp reserve products, following WanHob2016's formulation (@oyurdakul, #21).
+- Add 365 variations for each MATPOWER instance, corresponding to each day of the year.
+
+### Changed
+- To support multiple/zonal reserves, the input data format has been modified as follows:
+    - In `Generators`, replace `Provides spinning reserves?` by `Reserve eligibility`
+    - In `Parameters`, remove `Reserve shortfall penalty`
+    - Revise `Reserves` section
+- To allow new versions of UnitCommitment.jl to read old instance files, a new required field `Version` has been added to the `Parameters` section. To load v0.2 files in v0.3, please add `{"Parameters":{"Version":"0.2"}}` to the file.
+- Benchmark test cases are now downloaded on-the-fly as needed, instead of being stored in our GitHub repository. Test cases can also be directly downloaded from: https://axavier.org/UnitCommitment.jl/
+
+
 ## [0.2.2] - 2021-07-21
 ### Fixed
 - Fix small bug in validation scripts related to startup costs

LICENSE.md

@@ -1,4 +1,4 @@
-Copyright © 2020, UChicago Argonne, LLC
+Copyright © 2020-2022, UChicago Argonne, LLC
 
 All Rights Reserved
 

Makefile

@@ -2,31 +2,10 @@
 # Copyright (C) 2020, UChicago Argonne, LLC. All rights reserved.
 # Released under the modified BSD license. See COPYING.md for more details.
 
-JULIA := julia --color=yes --project=@.
+VERSION := 0.4
-VERSION := 0.2
-
-build/sysimage.so: src/utils/sysimage.jl Project.toml Manifest.toml
-	mkdir -p build
-	mkdir -p benchmark/results/test
-	cd benchmark; $(JULIA) --trace-compile=../build/precompile.jl benchmark.jl test/case14
-	$(JULIA) src/utils/sysimage.jl
-
-clean:
-	rm -rf build/*
 
 docs:
-	cd docs; make clean; make dirhtml
+	cd docs; julia --project=. -e 'include("make.jl"); make()'; cd ..
-	rsync -avP --delete-after docs/_build/dirhtml/ ../docs/$(VERSION)/
+	rsync -avP --delete-after docs/build/ ../docs/$(VERSION)/
 	
-test: build/sysimage.so
+.PHONY: docs
-	@echo Running tests...
-	$(JULIA) --sysimage build/sysimage.so -e 'using Pkg; Pkg.test("UnitCommitment")' | tee build/test.log
-
-
-format:
-	julia -e 'using JuliaFormatter; format(["src", "test", "benchmark"], verbose=true);'
-
-install-deps:
-	julia -e 'using Pkg; Pkg.add(PackageSpec(name="JuliaFormatter", version="0.14.4"))'
-
-.PHONY: docs test format install-deps

Project.toml

@@ -2,10 +2,11 @@ name = "UnitCommitment"
 uuid = "64606440-39ea-11e9-0f29-3303a1d3d877"
 authors = ["Santos Xavier, Alinson <axavier@anl.gov>"]
 repo = "https://github.com/ANL-CEEESA/UnitCommitment.jl"
-version = "0.2.2"
+version = "0.4.1"
 
 [deps]
 DataStructures = "864edb3b-99cc-5e75-8d2d-829cb0a9cfe8"
+Distributed = "8ba89e20-285c-5b6f-9357-94700520ee1b"
 Distributions = "31c24e10-a181-5473-b8eb-7969acd0382f"
 GZip = "92fee26a-97fe-5a0c-ad85-20a5f3185b63"
 JSON = "682c06a0-de6a-54ab-a142-c8b1cf79cde6"
@@ -15,23 +16,19 @@ Logging = "56ddb016-857b-54e1-b83d-db4d58db5568"
 MathOptInterface = "b8f27783-ece8-5eb3-8dc8-9495eed66fee"
 PackageCompiler = "9b87118b-4619-50d2-8e1e-99f35a4d4d9d"
 Printf = "de0858da-6303-5e67-8744-51eddeeeb8d7"
+Random = "9a3f8284-a2c9-5f02-9a11-845980a1fd5c"
 SparseArrays = "2f01184e-e22b-5df5-ae63-d93ebab69eaf"
+TimerOutputs = "a759f4b9-e2f1-59dc-863e-4aeb61b1ea8f"
+MPI = "da04e1cc-30fd-572f-bb4f-1f8673147195"
 
 [compat]
-Cbc = "0.7"
 DataStructures = "0.18"
 Distributions = "0.25"
 GZip = "0.5"
 JSON = "0.21"
-JuMP = "0.21"
+JuMP = "1"
-MathOptInterface = "0.9"
+MathOptInterface = "1"
+MPI = "0.20"
 PackageCompiler = "1"
-julia = "1"
+julia = "1.10"
-
+TimerOutputs = "0.5"
-[extras]
-Cbc = "9961bab8-2fa3-5c5a-9d89-47fab24efd76"
-Test = "8dfed614-e22c-5e08-85e1-65c5234f0b40"
-Gurobi = "2e9cd046-0924-5485-92f1-d5272153d98b"
-
-[targets]
-test = ["Cbc", "Test", "Gurobi"]

README.md

@@ -87,19 +87,18 @@ UnitCommitment.write("/tmp/output.json", solution)
 
 ## Documentation
 
-1. [Usage](https://anl-ceeesa.github.io/UnitCommitment.jl/0.2/usage/)
+See official documentation at: https://anl-ceeesa.github.io/UnitCommitment.jl/
-2. [Data Format](https://anl-ceeesa.github.io/UnitCommitment.jl/0.2/format/)
-3. [Instances](https://anl-ceeesa.github.io/UnitCommitment.jl/0.2/instances/)
-4. [JuMP Model](https://anl-ceeesa.github.io/UnitCommitment.jl/0.2/model/)
 
 ## Authors
 * **Alinson S. Xavier** (Argonne National Laboratory)
 * **Aleksandr M. Kazachkov** (University of Florida)
+* **Ogün Yurdakul** (Technische Universität Berlin)
+* **Jun He** (Purdue University)
 * **Feng Qiu** (Argonne National Laboratory)
 
 ## Acknowledgments
 
-* We would like to **Yonghong Chen** (Midcontinent Independent System Operator), **Feng Pan** (Pacific Northwest National Laboratory) for valuable feedback on early versions of this package.
+* We would like to thank **Yonghong Chen** (Midcontinent Independent System Operator), **Feng Pan** (Pacific Northwest National Laboratory) for valuable feedback on early versions of this package.
 
 * Based upon work supported by **Laboratory Directed Research and Development** (LDRD) funding from Argonne National Laboratory, provided by the Director, Office of Science, of the U.S. Department of Energy under Contract No. DE-AC02-06CH11357
 
@@ -109,15 +108,15 @@ UnitCommitment.write("/tmp/output.json", solution)
 
 If you use UnitCommitment.jl in your research (instances, models or algorithms), we kindly request that you cite the package as follows:
 
-* **Alinson S. Xavier, Aleksandr M. Kazachkov, Feng Qiu**. "UnitCommitment.jl: A Julia/JuMP Optimization Package for Security-Constrained Unit Commitment". Zenodo (2020). [DOI: 10.5281/zenodo.4269874](https://doi.org/10.5281/zenodo.4269874).
+* **Alinson S. Xavier, Aleksandr M. Kazachkov, Ogün Yurdakul, Jun He, Feng Qiu**. "UnitCommitment.jl: A Julia/JuMP Optimization Package for Security-Constrained Unit Commitment (Version 0.4)". Zenodo (2024). [DOI: 10.5281/zenodo.4269874](https://doi.org/10.5281/zenodo.4269874).
 
-If you use the instances, we additionally request that you cite the original sources, as described in the [instances page](docs/instances.md).
+If you use the instances, we additionally request that you cite the original sources, as described in the documentation.
 
 ## License
 
 ```text
 UnitCommitment.jl: A Julia/JuMP Optimization Package for Security-Constrained Unit Commitment
-Copyright © 2020-2021, UChicago Argonne, LLC. All Rights Reserved.
+Copyright © 2020-2024, UChicago Argonne, LLC. All Rights Reserved.
 
 Redistribution and use in source and binary forms, with or without modification, are permitted
 provided that the following conditions are met:

benchmark/Project.toml

@@ -1,4 +1,5 @@
 [deps]
+DocOpt = "968ba79b-81e4-546f-ab3a-2eecfa62a9db"
 Gurobi = "2e9cd046-0924-5485-92f1-d5272153d98b"
 JSON = "682c06a0-de6a-54ab-a142-c8b1cf79cde6"
 JuMP = "4076af6c-e467-56ae-b986-b466b2749572"

benchmark/benchmark.jl

@@ -1,158 +0,0 @@
-# UnitCommitment.jl: Optimization Package for Security-Constrained Unit Commitment
-# Copyright (C) 2020, UChicago Argonne, LLC. All rights reserved.
-# Released under the modified BSD license. See COPYING.md for more details.
-
-using Distributed
-using Pkg
-Pkg.activate(".")
-
-@everywhere using Pkg
-@everywhere Pkg.activate(".")
-
-@everywhere using UnitCommitment
-@everywhere using JuMP
-@everywhere using Gurobi
-@everywhere using JSON
-@everywhere using Logging
-@everywhere using Printf
-@everywhere using LinearAlgebra
-@everywhere using Random
-
-@everywhere import UnitCommitment:
-    ArrCon2000,
-    CarArr2006,
-    DamKucRajAta2016,
-    Formulation,
-    Gar1962,
-    KnuOstWat2018,
-    MorLatRam2013,
-    PanGua2016,
-    XavQiuWanThi2019
-
-@everywhere UnitCommitment._setup_logger()
-
-function main()
-    cases = [
-        "pglib-uc/ca/2014-09-01_reserves_0",
-        "pglib-uc/ca/2014-09-01_reserves_1",
-        "pglib-uc/ca/2015-03-01_reserves_0",
-        "pglib-uc/ca/2015-06-01_reserves_0",
-        "pglib-uc/ca/Scenario400_reserves_1",
-        "pglib-uc/ferc/2015-01-01_lw",
-        "pglib-uc/ferc/2015-05-01_lw",
-        "pglib-uc/ferc/2015-07-01_hw",
-        "pglib-uc/ferc/2015-10-01_lw",
-        "pglib-uc/ferc/2015-12-01_lw",
-        "pglib-uc/rts_gmlc/2020-04-03",
-        "pglib-uc/rts_gmlc/2020-09-20",
-        "pglib-uc/rts_gmlc/2020-10-27",
-        "pglib-uc/rts_gmlc/2020-11-25",
-        "pglib-uc/rts_gmlc/2020-12-23",
-        "or-lib/20_0_1_w",
-        "or-lib/20_0_5_w",
-        "or-lib/50_0_2_w",
-        "or-lib/75_0_2_w",
-        "or-lib/100_0_1_w",
-        "or-lib/100_0_4_w",
-        "or-lib/100_0_5_w",
-        "or-lib/200_0_3_w",
-        "or-lib/200_0_7_w",
-        "or-lib/200_0_9_w",
-        "tejada19/UC_24h_290g",
-        "tejada19/UC_24h_623g",
-        "tejada19/UC_24h_959g",
-        "tejada19/UC_24h_1577g",
-        "tejada19/UC_24h_1888g",
-        "tejada19/UC_168h_72g",
-        "tejada19/UC_168h_86g",
-        "tejada19/UC_168h_130g",
-        "tejada19/UC_168h_131g",
-        "tejada19/UC_168h_199g",
-    ]
-    formulations = Dict(
-        "Default" => Formulation(),
-        "ArrCon2000" => Formulation(ramping = ArrCon2000.Ramping()),
-        "CarArr2006" => Formulation(pwl_costs = CarArr2006.PwlCosts()),
-        "DamKucRajAta2016" =>
-            Formulation(ramping = DamKucRajAta2016.Ramping()),
-        "Gar1962" => Formulation(pwl_costs = Gar1962.PwlCosts()),
-        "KnuOstWat2018" =>
-            Formulation(pwl_costs = KnuOstWat2018.PwlCosts()),
-        "MorLatRam2013" => Formulation(ramping = MorLatRam2013.Ramping()),
-        "PanGua2016" => Formulation(ramping = PanGua2016.Ramping()),
-    )
-    trials = [i for i in 1:5]
-    combinations = [
-        (c, f.first, f.second, t) for c in cases for f in formulations for
-        t in trials
-    ]
-    shuffle!(combinations)
-    @sync @distributed for c in combinations
-        _run_combination(c...)
-    end
-end
-
-@everywhere function _run_combination(
-    case,
-    formulation_name,
-    formulation,
-    trial,
-)
-    name = "$formulation_name/$case"
-    dirname = "results/$name"
-    mkpath(dirname)
-    if isfile("$dirname/$trial.json")
-        @info @sprintf("%-4s %-16s %s", "skip", formulation_name, case)
-        return
-    end
-    @info @sprintf("%-4s %-16s %s", "run", formulation_name, case)
-    open("$dirname/$trial.log", "w") do file
-        redirect_stdout(file) do
-            redirect_stderr(file) do
-                return _run_sample(case, formulation, "$dirname/$trial")
-            end
-        end
-    end
-    @info @sprintf("%-4s %-16s %s", "done", formulation_name, case)
-end
-
-@everywhere function _run_sample(case, formulation, prefix)
-    total_time = @elapsed begin
-        @info "Reading: $case"
-        time_read = @elapsed begin
-            instance = UnitCommitment.read_benchmark(case)
-        end
-        @info @sprintf("Read problem in %.2f seconds", time_read)
-        BLAS.set_num_threads(4)
-        model = UnitCommitment.build_model(
-            instance = instance,
-            formulation = formulation,
-            optimizer = optimizer_with_attributes(
-                Gurobi.Optimizer,
-                "Threads" => 4,
-                "Seed" => rand(1:1000),
-            ),
-            variable_names = true,
-        )
-        @info "Optimizing..."
-        BLAS.set_num_threads(1)
-        UnitCommitment.optimize!(
-            model,
-            XavQiuWanThi2019.Method(time_limit = 3600.0, gap_limit = 1e-4),
-        )
-    end
-    @info @sprintf("Total time was %.2f seconds", total_time)
-    @info "Writing solution: $prefix.json"
-    solution = UnitCommitment.solution(model)
-    UnitCommitment.write("$prefix.json", solution)
-    @info "Verifying solution..."
-    return UnitCommitment.validate(instance, solution)
-    # @info "Exporting model..."
-    # return JuMP.write_to_file(model, model_filename)
-end
-
-if length(ARGS) > 0
-    _run_sample(ARGS[1], UnitCommitment.Formulation(), "tmp")
-else
-    main()
-end

benchmark/run.jl

@@ -0,0 +1,209 @@
+# UnitCommitment.jl: Optimization Package for Security-Constrained Unit Commitment
+# Copyright (C) 2020, UChicago Argonne, LLC. All rights reserved.
+# Released under the modified BSD license. See COPYING.md for more details.
+
+doc = """UnitCommitment.jl Benchmark Runner
+
+Usage:
+  run.jl [-s ARG]... [-m ARG]... [-c ARG]... [-f ARG]... [options]
+
+Examples:
+
+    1. Benchmark all solvers, methods and formulations:
+
+        julia run.jl
+
+    2. Benchmark formulations "default" and "ArrCon200" using Gurobi:
+
+        julia run.jl -s gurobi -f default -f ArrCon2000
+
+    3. Benchmark a few test cases, using all solvers, methods and formulations:
+
+        julia run.jl -c or-lib/20_0_1_w -c matpower/case1888rte/2017-02-01
+
+    4. Solve 4 test cases in parallel, with 2 threads available per worker:
+
+        JULIA_NUM_THREADS=2 julia --procs 4 run.jl
+
+Options:
+  -h --help             Show this screen.
+  -s --solver=ARG       Mixed-integer linear solver (e.g. gurobi)
+  -c --case=ARG         Unit commitment test case (e.g. or-lib/20_0_1_w)
+  -m --method=ARG       Solution method (e.g. default)
+  -f --formulation=ARG  Formulation (e.g. ArrCon2000)
+  --time-limit=ARG      Time limit in seconds [default: 3600]
+  --gap=ARG             Relative MIP gap tolerance [default: 0.001]
+  --trials=ARG          Number of trials [default: 5]
+"""
+
+using Distributed
+using Pkg
+Pkg.activate(".")
+@everywhere using Pkg
+@everywhere Pkg.activate(".")
+
+using DocOpt
+args = docopt(doc)
+
+@everywhere using UnitCommitment
+@everywhere UnitCommitment._setup_logger()
+
+using UnitCommitment
+using Gurobi
+using Logging
+using JuMP
+
+import UnitCommitment:
+    ArrCon2000,
+    CarArr2006,
+    DamKucRajAta2016,
+    Formulation,
+    Gar1962,
+    KnuOstWat2018,
+    MorLatRam2013,
+    PanGua2016,
+    XavQiuWanThi2019
+
+# Benchmark test cases
+# -----------------------------------------------------------------------------
+cases = [
+    "pglib-uc/ca/2014-09-01_reserves_0",
+    "pglib-uc/ca/2014-09-01_reserves_1",
+    "pglib-uc/ca/2015-03-01_reserves_0",
+    "pglib-uc/ca/2015-06-01_reserves_0",
+    "pglib-uc/ca/Scenario400_reserves_1",
+    "pglib-uc/ferc/2015-01-01_lw",
+    "pglib-uc/ferc/2015-05-01_lw",
+    "pglib-uc/ferc/2015-07-01_hw",
+    "pglib-uc/ferc/2015-10-01_lw",
+    "pglib-uc/ferc/2015-12-01_lw",
+    "pglib-uc/rts_gmlc/2020-04-03",
+    "pglib-uc/rts_gmlc/2020-09-20",
+    "pglib-uc/rts_gmlc/2020-10-27",
+    "pglib-uc/rts_gmlc/2020-11-25",
+    "pglib-uc/rts_gmlc/2020-12-23",
+    "or-lib/20_0_1_w",
+    "or-lib/20_0_5_w",
+    "or-lib/50_0_2_w",
+    "or-lib/75_0_2_w",
+    "or-lib/100_0_1_w",
+    "or-lib/100_0_4_w",
+    "or-lib/100_0_5_w",
+    "or-lib/200_0_3_w",
+    "or-lib/200_0_7_w",
+    "or-lib/200_0_9_w",
+    "tejada19/UC_24h_290g",
+    "tejada19/UC_24h_623g",
+    "tejada19/UC_24h_959g",
+    "tejada19/UC_24h_1577g",
+    "tejada19/UC_24h_1888g",
+    "tejada19/UC_168h_72g",
+    "tejada19/UC_168h_86g",
+    "tejada19/UC_168h_130g",
+    "tejada19/UC_168h_131g",
+    "tejada19/UC_168h_199g",
+    "matpower/case1888rte/2017-02-01",
+    "matpower/case1951rte/2017-02-01",
+    "matpower/case2848rte/2017-02-01",
+    "matpower/case3012wp/2017-02-01",
+    "matpower/case3375wp/2017-02-01",
+    "matpower/case6468rte/2017-02-01",
+    "matpower/case6515rte/2017-02-01",
+]
+
+# Formulations
+# -----------------------------------------------------------------------------
+formulations = Dict(
+    "default" => Formulation(),
+    "ArrCon2000" => Formulation(ramping = ArrCon2000.Ramping()),
+    "CarArr2006" => Formulation(pwl_costs = CarArr2006.PwlCosts()),
+    "DamKucRajAta2016" => Formulation(ramping = DamKucRajAta2016.Ramping()),
+    "Gar1962" => Formulation(pwl_costs = Gar1962.PwlCosts()),
+    "KnuOstWat2018" => Formulation(pwl_costs = KnuOstWat2018.PwlCosts()),
+    "MorLatRam2013" => Formulation(ramping = MorLatRam2013.Ramping()),
+    "PanGua2016" => Formulation(ramping = PanGua2016.Ramping()),
+)
+
+# Solution methods
+# -----------------------------------------------------------------------------
+const gap_limit = parse(Float64, args["--gap"])
+const time_limit = parse(Float64, args["--time-limit"])
+methods = Dict(
+    "default" => XavQiuWanThi2019.Method(
+        time_limit = time_limit,
+        gap_limit = gap_limit,
+    ),
+)
+
+# MIP solvers
+# -----------------------------------------------------------------------------
+optimizers = Dict(
+    "gurobi" => optimizer_with_attributes(
+        Gurobi.Optimizer,
+        "Threads" => Threads.nthreads(),
+    ),
+)
+
+# Parse command line arguments
+# -----------------------------------------------------------------------------
+if !isempty(args["--case"])
+    cases = args["--case"]
+end
+if !isempty(args["--formulation"])
+    formulations = filter(p -> p.first in args["--formulation"], formulations)
+end
+if !isempty(args["--method"])
+    methods = filter(p -> p.first in args["--method"], methods)
+end
+if !isempty(args["--solver"])
+    optimizers = filter(p -> p.first in args["--solver"], optimizers)
+end
+const ntrials = parse(Int, args["--trials"])
+
+# Print benchmark settings
+# -----------------------------------------------------------------------------
+function printlist(d::Dict)
+    for key in keys(d)
+        @info "  - $key"
+    end
+end
+
+function printlist(d::Vector)
+    for key in d
+        @info "  - $key"
+    end
+end
+
+@info "Computational environment:"
+@info "  - CPU: $(Sys.cpu_info()[1].model)"
+@info "  - Logical CPU cores: $(length(Sys.cpu_info()))"
+@info "  - System memory: $(round(Sys.total_memory() / 2^30, digits=2)) GiB"
+@info "  - Available workers: $(nworkers())"
+@info "  - Available threads per worker: $(Threads.nthreads())"
+
+@info "Parameters:"
+@info "  - Number of trials: $ntrials"
+@info "  - Time limit (s): $time_limit"
+@info "  - Relative MIP gap tolerance: $gap_limit"
+
+@info "Solvers:"
+printlist(optimizers)
+
+@info "Methods:"
+printlist(methods)
+
+@info "Formulations:"
+printlist(formulations)
+
+@info "Cases:"
+printlist(cases)
+
+# Run benchmarks
+# -----------------------------------------------------------------------------
+UnitCommitment._run_benchmarks(
+    cases = cases,
+    formulations = formulations,
+    methods = methods,
+    optimizers = optimizers,
+    trials = 1:ntrials,
+)

docs/Makefile

@@ -1,14 +0,0 @@
-SPHINXOPTS    ?=
-SPHINXBUILD   ?= sphinx-build
-SOURCEDIR     = .
-BUILDDIR      = _build
-
-help:
-	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
-
-.PHONY: help Makefile
-
-# Catch-all target: route all unknown targets to Sphinx using the new
-# "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
-%: Makefile
-	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)

docs/Project.toml

@@ -0,0 +1,10 @@
+[deps]
+Documenter = "e30172f5-a6a5-5a46-863b-614d45cd2de4"
+Glob = "c27321d9-0574-5035-807b-f59d2c89b15c"
+HiGHS = "87dc4568-4c63-4d18-b0c0-bb2238e4078b"
+JSON = "682c06a0-de6a-54ab-a142-c8b1cf79cde6"
+JuMP = "4076af6c-e467-56ae-b986-b466b2749572"
+Literate = "98b081ad-f1c9-55d3-8b20-4c87d4299306"
+MPI = "da04e1cc-30fd-572f-bb4f-1f8673147195"
+Revise = "295af30f-e4ad-537b-8983-00126c2a3abe"
+UnitCommitment = "64606440-39ea-11e9-0f29-3303a1d3d877"

docs/_static/custom.css

@@ -1,49 +0,0 @@
-h1.site-logo {
-    font-size: 30px !important;
-}
-
-h1.site-logo small {
-    font-size: 20px !important;
-}
-
-h1.site-logo {
-    font-size: 30px !important;
-}
-
-h1.site-logo small {
-    font-size: 20px !important;
-}
-
-tbody, thead, pre {
-    border: 1px solid rgba(0, 0, 0, 0.25);
-}
-
-table td, th {
-    padding: 8px;
-}
-
-table p {
-    margin-bottom: 0;
-}
-
-table td code {
-    white-space: nowrap;
-}
-
-table tr,
-table th {
-    border-bottom: 1px solid rgba(0, 0, 0, 0.1);
-}
-
-table tr:last-child {
-    border-bottom: 0;
-}
-
-pre {
-    box-shadow: inherit !important;
-    background-color: #fff;
-}
-
-.text-align\:center {
-    text-align: center;
-}

docs/conf.py

@@ -1,16 +0,0 @@
-project = "UnitCommitment.jl"
-copyright = "2020-2021, UChicago Argonne, LLC"
-author = ""
-release = "0.2"
-extensions = ["myst_parser"]
-templates_path = ["_templates"]
-exclude_patterns = ["_build", "Thumbs.db", ".DS_Store"]
-html_theme = "sphinx_book_theme"
-html_static_path = ["_static"]
-html_css_files = ["custom.css"]
-html_theme_options = {
-    "repository_url": "https://github.com/ANL-CEEESA/UnitCommitment.jl/",
-    "use_repository_button": True,
-    "extra_navbar": "",
-}
-html_title = f"UnitCommitment.jl<br/><small>{release}</small>"

docs/example/s1.json

@@ -0,0 +1,495 @@
+{
+    "Parameters": {
+	"Version": "0.3",
+        "Time horizon (h)": 4
+    },
+    "Generators": {
+        "g1": {
+            "Bus": "b1",
+            "Production cost curve (MW)": [
+                100,
+                110,
+                130,
+                135
+            ],
+            "Production cost curve ($)": [
+                1400,
+                1600,
+                2200,
+                2400
+            ],
+            "Startup delays (h)": [
+                1,
+                2,
+                3
+            ],
+            "Startup costs ($)": [
+                1000.0,
+                1500.0,
+                2000.0
+            ],
+            "Initial status (h)": -100,
+            "Initial power (MW)": 0
+        },
+        "g2": {
+            "Bus": "b2",
+            "Production cost curve (MW)": [
+                0,
+                47,
+                94,
+                140
+            ],
+            "Production cost curve ($)": [
+                0,
+                2256.00,
+                4733.37,
+                7395.39
+            ],
+            "Startup delays (h)": [
+                1,
+                4
+            ],
+            "Startup costs ($)": [
+                3000.0,
+                4000.0
+            ],
+            "Ramp up limit (MW)": 98.0,
+            "Ramp down limit (MW)": 98.0,
+            "Startup limit (MW)": 98.0,
+            "Shutdown limit (MW)": 98.0,
+            "Minimum uptime (h)": 4,
+            "Minimum downtime (h)": 4,
+            "Maximum daily energy (MWh)": null,
+            "Maximum daily starts": null,
+            "Initial status (h)": -8,
+            "Initial power (MW)": 0,
+            "Reserve eligibility": [
+                "r1"
+            ]
+        },
+        "g3": {
+            "Bus": "b3",
+            "Production cost curve (MW)": [
+                0,
+                33,
+                66,
+                100
+            ],
+            "Production cost curve ($)": [
+                0,
+                1113.75,
+                2369.07,
+                3891.54
+            ],
+            "Startup delays (h)": [
+                1,
+                4,
+                8
+            ],
+            "Startup costs ($)": [
+                1000.0,
+                2000.0,
+                3000.0
+            ],
+            "Ramp up limit (MW)": 70.0,
+            "Ramp down limit (MW)": 70.0,
+            "Startup limit (MW)": 70.0,
+            "Shutdown limit (MW)": 70.0,
+            "Must run?": true,
+            "Minimum uptime (h)": 1,
+            "Minimum downtime (h)": 1,
+            "Maximum daily energy (MWh)": null,
+            "Maximum daily starts": null,
+            "Initial status (h)": -6,
+            "Initial power (MW)": 0,
+            "Reserve eligibility": [
+                "r1"
+            ]
+        },
+        "g4": {
+            "Bus": "b6",
+            "Production cost curve (MW)": [
+                33,
+                66,
+                100
+            ],
+            "Production cost curve ($)": [
+                1113.75,
+                2369.07,
+                3891.54
+            ],
+            "Initial status (h)": -100,
+            "Initial power (MW)": 0,
+            "Reserve eligibility": [
+                "r1"
+            ]
+        },
+        "g5": {
+            "Bus": "b8",
+            "Production cost curve (MW)": [
+                33,
+                66,
+                100
+            ],
+            "Production cost curve ($)": [
+                1113.75,
+                2369.07,
+                3891.54
+            ],
+            "Initial status (h)": -100,
+            "Initial power (MW)": 0,
+            "Reserve eligibility": [
+                "r1"
+            ]
+        },
+        "g6": {
+            "Bus": "b8",
+            "Production cost curve (MW)": [
+                100
+            ],
+            "Production cost curve ($)": [
+                10000.00
+            ],
+            "Initial status (h)": -100,
+            "Initial power (MW)": 0,
+            "Reserve eligibility": [
+                "r1"
+            ]
+        }
+    },
+    "Buses": {
+        "b1": {
+            "Load (MW)": 0.0
+        },
+        "b2": {
+            "Load (MW)": [
+                26.01527,
+                24.46212,
+                23.29725,
+                22.90897
+            ]
+        },
+        "b3": {
+            "Load (MW)": [
+                112.93263,
+                106.19039,
+                101.1337,
+                99.44814
+            ]
+        },
+        "b4": {
+            "Load (MW)": [
+                57.30552,
+                53.88429,
+                51.31838,
+                50.46307
+            ]
+        },
+        "b5": {
+            "Load (MW)": [
+                9.11134,
+                8.56738,
+                8.15941,
+                8.02342
+            ]
+        },
+        "b6": {
+            "Load (MW)": [
+                13.42723,
+                12.62561,
+                12.02439,
+                11.82398
+            ]
+        },
+        "b7": {
+            "Load (MW)": 0.0
+        },
+        "b8": {
+            "Load (MW)": 0.0
+        },
+        "b9": {
+            "Load (MW)": [
+                35.36638,
+                33.25495,
+                31.67138,
+                31.14353
+            ]
+        },
+        "b10": {
+            "Load (MW)": [
+                10.78974,
+                10.14558,
+                9.66246,
+                9.50141
+            ]
+        },
+        "b11": {
+            "Load (MW)": [
+                4.19601,
+                3.9455,
+                3.75762,
+                3.69499
+            ]
+        },
+        "b12": {
+            "Load (MW)": [
+                7.31305,
+                6.87645,
+                6.549,
+                6.43985
+            ]
+        },
+        "b13": {
+            "Load (MW)": [
+                16.18461,
+                15.21837,
+                14.49368,
+                14.25212
+            ]
+        },
+        "b14": {
+            "Load (MW)": [
+                17.86302,
+                16.79657,
+                15.99673,
+                15.73012
+            ]
+        }
+    },
+    "Transmission lines": {
+        "l1": {
+            "Source bus": "b1",
+            "Target bus": "b2",
+            "Reactance (ohms)": 0.05917000000000001,
+            "Susceptance (S)": 29.496860773945063,
+            "Normal flow limit (MW)": 300.0,
+            "Emergency flow limit (MW)": 400.0,
+            "Flow limit penalty ($/MW)": 1000.0
+        },
+        "l2": {
+            "Source bus": "b1",
+            "Target bus": "b5",
+            "Reactance (ohms)": 0.22304000000000002,
+            "Susceptance (S)": 7.825184953346168
+        },
+        "l3": {
+            "Source bus": "b2",
+            "Target bus": "b3",
+            "Reactance (ohms)": 0.19797,
+            "Susceptance (S)": 8.816129979261149
+        },
+        "l4": {
+            "Source bus": "b2",
+            "Target bus": "b4",
+            "Reactance (ohms)": 0.17632,
+            "Susceptance (S)": 9.898645939169292
+        },
+        "l5": {
+            "Source bus": "b2",
+            "Target bus": "b5",
+            "Reactance (ohms)": 0.17388,
+            "Susceptance (S)": 10.037550333530765
+        },
+        "l6": {
+            "Source bus": "b3",
+            "Target bus": "b4",
+            "Reactance (ohms)": 0.17103,
+            "Susceptance (S)": 10.204813494675376
+        },
+        "l7": {
+            "Source bus": "b4",
+            "Target bus": "b5",
+            "Reactance (ohms)": 0.04211,
+            "Susceptance (S)": 41.44690695783257
+        },
+        "l8": {
+            "Source bus": "b4",
+            "Target bus": "b7",
+            "Reactance (ohms)": 0.20911999999999997,
+            "Susceptance (S)": 8.346065665619404
+        },
+        "l9": {
+            "Source bus": "b4",
+            "Target bus": "b9",
+            "Reactance (ohms)": 0.55618,
+            "Susceptance (S)": 3.1380654680037567
+        },
+        "l10": {
+            "Source bus": "b5",
+            "Target bus": "b6",
+            "Reactance (ohms)": 0.25201999999999997,
+            "Susceptance (S)": 6.92536009838239
+        },
+        "l11": {
+            "Source bus": "b6",
+            "Target bus": "b11",
+            "Reactance (ohms)": 0.1989,
+            "Susceptance (S)": 8.774908255376218
+        },
+        "l12": {
+            "Source bus": "b6",
+            "Target bus": "b12",
+            "Reactance (ohms)": 0.25581,
+            "Susceptance (S)": 6.8227561549365925
+        },
+        "l13": {
+            "Source bus": "b6",
+            "Target bus": "b13",
+            "Reactance (ohms)": 0.13027,
+            "Susceptance (S)": 13.397783465067395
+        },
+        "l14": {
+            "Source bus": "b7",
+            "Target bus": "b8",
+            "Reactance (ohms)": 0.17615,
+            "Susceptance (S)": 9.908198989465395
+        },
+        "l15": {
+            "Source bus": "b7",
+            "Target bus": "b9",
+            "Reactance (ohms)": 0.11001,
+            "Susceptance (S)": 15.865187273832648
+        },
+        "l16": {
+            "Source bus": "b9",
+            "Target bus": "b10",
+            "Reactance (ohms)": 0.0845,
+            "Susceptance (S)": 20.65478404727017
+        },
+        "l17": {
+            "Source bus": "b9",
+            "Target bus": "b14",
+            "Reactance (ohms)": 0.27038,
+            "Susceptance (S)": 6.4550974628091184
+        },
+        "l18": {
+            "Source bus": "b10",
+            "Target bus": "b11",
+            "Reactance (ohms)": 0.19207,
+            "Susceptance (S)": 9.08694357262628
+        },
+        "l19": {
+            "Source bus": "b12",
+            "Target bus": "b13",
+            "Reactance (ohms)": 0.19988,
+            "Susceptance (S)": 8.73188539120637
+        },
+        "l20": {
+            "Source bus": "b13",
+            "Target bus": "b14",
+            "Reactance (ohms)": 0.34802,
+            "Susceptance (S)": 5.0150257226433235
+        }
+    },
+    "Contingencies": {
+        "c1": {
+            "Affected lines": [
+                "l1"
+            ]
+        },
+        "c2": {
+            "Affected lines": [
+                "l2"
+            ]
+        },
+        "c3": {
+            "Affected lines": [
+                "l3"
+            ]
+        },
+        "c4": {
+            "Affected lines": [
+                "l4"
+            ]
+        },
+        "c5": {
+            "Affected lines": [
+                "l5"
+            ]
+        },
+        "c6": {
+            "Affected lines": [
+                "l6"
+            ]
+        },
+        "c7": {
+            "Affected lines": [
+                "l7"
+            ]
+        },
+        "c8": {
+            "Affected lines": [
+                "l8"
+            ]
+        },
+        "c9": {
+            "Affected lines": [
+                "l9"
+            ]
+        },
+        "c10": {
+            "Affected lines": [
+                "l10"
+            ]
+        },
+        "c11": {
+            "Affected lines": [
+                "l11"
+            ]
+        },
+        "c12": {
+            "Affected lines": [
+                "l12"
+            ]
+        },
+        "c13": {
+            "Affected lines": [
+                "l13"
+            ]
+        },
+        "c15": {
+            "Affected lines": [
+                "l15"
+            ]
+        },
+        "c16": {
+            "Affected lines": [
+                "l16"
+            ]
+        },
+        "c17": {
+            "Affected lines": [
+                "l17"
+            ]
+        },
+        "c18": {
+            "Affected lines": [
+                "l18"
+            ]
+        },
+        "c19": {
+            "Affected lines": [
+                "l19"
+            ]
+        },
+        "c20": {
+            "Affected lines": [
+                "l20"
+            ]
+        }
+    },
+    "Price-sensitive loads": {
+        "ps1": {
+            "Bus": "b3",
+            "Revenue ($/MW)": 100.0,
+            "Demand (MW)": 50.0
+        }
+    },
+    "Reserves": {
+        "r1": {
+            "Type": "Spinning",
+            "Amount (MW)": 100.0,
+            "Shortfall penalty ($/MW)": 1000.0
+        }
+    }
+}

docs/example/s2.json

@@ -0,0 +1,495 @@
+{
+    "Parameters": {
+	"Version": "0.3",
+        "Time horizon (h)": 4
+    },
+    "Generators": {
+        "g1": {
+            "Bus": "b1",
+            "Production cost curve (MW)": [
+                100,
+                110,
+                130,
+                135
+            ],
+            "Production cost curve ($)": [
+                1400,
+                1600,
+                2200,
+                2400
+            ],
+            "Startup delays (h)": [
+                1,
+                2,
+                3
+            ],
+            "Startup costs ($)": [
+                1000.0,
+                1500.0,
+                2000.0
+            ],
+            "Initial status (h)": -100,
+            "Initial power (MW)": 0
+        },
+        "g2": {
+            "Bus": "b2",
+            "Production cost curve (MW)": [
+                0,
+                47,
+                94,
+                140
+            ],
+            "Production cost curve ($)": [
+                0,
+                2256.00,
+                4733.37,
+                7395.39
+            ],
+            "Startup delays (h)": [
+                1,
+                4
+            ],
+            "Startup costs ($)": [
+                3000.0,
+                4000.0
+            ],
+            "Ramp up limit (MW)": 98.0,
+            "Ramp down limit (MW)": 98.0,
+            "Startup limit (MW)": 98.0,
+            "Shutdown limit (MW)": 98.0,
+            "Minimum uptime (h)": 4,
+            "Minimum downtime (h)": 4,
+            "Maximum daily energy (MWh)": null,
+            "Maximum daily starts": null,
+            "Initial status (h)": -8,
+            "Initial power (MW)": 0,
+            "Reserve eligibility": [
+                "r1"
+            ]
+        },
+        "g3": {
+            "Bus": "b3",
+            "Production cost curve (MW)": [
+                0,
+                33,
+                66,
+                100
+            ],
+            "Production cost curve ($)": [
+                0,
+                1113.75,
+                2369.07,
+                3891.54
+            ],
+            "Startup delays (h)": [
+                1,
+                4,
+                8
+            ],
+            "Startup costs ($)": [
+                1000.0,
+                2000.0,
+                3000.0
+            ],
+            "Ramp up limit (MW)": 70.0,
+            "Ramp down limit (MW)": 70.0,
+            "Startup limit (MW)": 70.0,
+            "Shutdown limit (MW)": 70.0,
+            "Must run?": true,
+            "Minimum uptime (h)": 1,
+            "Minimum downtime (h)": 1,
+            "Maximum daily energy (MWh)": null,
+            "Maximum daily starts": null,
+            "Initial status (h)": -6,
+            "Initial power (MW)": 0,
+            "Reserve eligibility": [
+                "r1"
+            ]
+        },
+        "g4": {
+            "Bus": "b6",
+            "Production cost curve (MW)": [
+                33,
+                66,
+                100
+            ],
+            "Production cost curve ($)": [
+                1113.75,
+                2369.07,
+                3891.54
+            ],
+            "Initial status (h)": -100,
+            "Initial power (MW)": 0,
+            "Reserve eligibility": [
+                "r1"
+            ]
+        },
+        "g5": {
+            "Bus": "b8",
+            "Production cost curve (MW)": [
+                33,
+                66,
+                100
+            ],
+            "Production cost curve ($)": [
+                1113.75,
+                2369.07,
+                3891.54
+            ],
+            "Initial status (h)": -100,
+            "Initial power (MW)": 0,
+            "Reserve eligibility": [
+                "r1"
+            ]
+        },
+        "g6": {
+            "Bus": "b8",
+            "Production cost curve (MW)": [
+                100
+            ],
+            "Production cost curve ($)": [
+                10000.00
+            ],
+            "Initial status (h)": -100,
+            "Initial power (MW)": 0,
+            "Reserve eligibility": [
+                "r1"
+            ]
+        }
+    },
+    "Buses": {
+        "b1": {
+            "Load (MW)": 0.0
+        },
+        "b2": {
+            "Load (MW)": [
+                26.01527,
+                24.46212,
+                23.29725,
+                22.90897
+            ]
+        },
+        "b3": {
+            "Load (MW)": [
+                112.93263,
+                106.19039,
+                101.1337,
+                99.44814
+            ]
+        },
+        "b4": {
+            "Load (MW)": [
+                57.30552,
+                53.88429,
+                51.31838,
+                50.46307
+            ]
+        },
+        "b5": {
+            "Load (MW)": [
+                9.11134,
+                8.56738,
+                8.15941,
+                8.02342
+            ]
+        },
+        "b6": {
+            "Load (MW)": [
+                13.42723,
+                12.62561,
+                12.02439,
+                11.82398
+            ]
+        },
+        "b7": {
+            "Load (MW)": 0.0
+        },
+        "b8": {
+            "Load (MW)": 0.0
+        },
+        "b9": {
+            "Load (MW)": [
+                35.36638,
+                33.25495,
+                31.67138,
+                31.14353
+            ]
+        },
+        "b10": {
+            "Load (MW)": [
+                10.78974,
+                10.14558,
+                9.66246,
+                9.50141
+            ]
+        },
+        "b11": {
+            "Load (MW)": [
+                4.19601,
+                3.9455,
+                3.75762,
+                3.69499
+            ]
+        },
+        "b12": {
+            "Load (MW)": [
+                7.31305,
+                6.87645,
+                6.549,
+                6.43985
+            ]
+        },
+        "b13": {
+            "Load (MW)": [
+                16.18461,
+                15.21837,
+                14.49368,
+                14.25212
+            ]
+        },
+        "b14": {
+            "Load (MW)": [
+                17.86302,
+                16.79657,
+                15.99673,
+                15.73012
+            ]
+        }
+    },
+    "Transmission lines": {
+        "l1": {
+            "Source bus": "b1",
+            "Target bus": "b2",
+            "Reactance (ohms)": 0.05917000000000001,
+            "Susceptance (S)": 29.496860773945063,
+            "Normal flow limit (MW)": 300.0,
+            "Emergency flow limit (MW)": 400.0,
+            "Flow limit penalty ($/MW)": 1000.0
+        },
+        "l2": {
+            "Source bus": "b1",
+            "Target bus": "b5",
+            "Reactance (ohms)": 0.22304000000000002,
+            "Susceptance (S)": 7.825184953346168
+        },
+        "l3": {
+            "Source bus": "b2",
+            "Target bus": "b3",
+            "Reactance (ohms)": 0.19797,
+            "Susceptance (S)": 8.816129979261149
+        },
+        "l4": {
+            "Source bus": "b2",
+            "Target bus": "b4",
+            "Reactance (ohms)": 0.17632,
+            "Susceptance (S)": 9.898645939169292
+        },
+        "l5": {
+            "Source bus": "b2",
+            "Target bus": "b5",
+            "Reactance (ohms)": 0.17388,
+            "Susceptance (S)": 10.037550333530765
+        },
+        "l6": {
+            "Source bus": "b3",
+            "Target bus": "b4",
+            "Reactance (ohms)": 0.17103,
+            "Susceptance (S)": 10.204813494675376
+        },
+        "l7": {
+            "Source bus": "b4",
+            "Target bus": "b5",
+            "Reactance (ohms)": 0.04211,
+            "Susceptance (S)": 41.44690695783257
+        },
+        "l8": {
+            "Source bus": "b4",
+            "Target bus": "b7",
+            "Reactance (ohms)": 0.20911999999999997,
+            "Susceptance (S)": 8.346065665619404
+        },
+        "l9": {
+            "Source bus": "b4",
+            "Target bus": "b9",
+            "Reactance (ohms)": 0.55618,
+            "Susceptance (S)": 3.1380654680037567
+        },
+        "l10": {
+            "Source bus": "b5",
+            "Target bus": "b6",
+            "Reactance (ohms)": 0.25201999999999997,
+            "Susceptance (S)": 6.92536009838239
+        },
+        "l11": {
+            "Source bus": "b6",
+            "Target bus": "b11",
+            "Reactance (ohms)": 0.1989,
+            "Susceptance (S)": 8.774908255376218
+        },
+        "l12": {
+            "Source bus": "b6",
+            "Target bus": "b12",
+            "Reactance (ohms)": 0.25581,
+            "Susceptance (S)": 6.8227561549365925
+        },
+        "l13": {
+            "Source bus": "b6",
+            "Target bus": "b13",
+            "Reactance (ohms)": 0.13027,
+            "Susceptance (S)": 13.397783465067395
+        },
+        "l14": {
+            "Source bus": "b7",
+            "Target bus": "b8",
+            "Reactance (ohms)": 0.17615,
+            "Susceptance (S)": 9.908198989465395
+        },
+        "l15": {
+            "Source bus": "b7",
+            "Target bus": "b9",
+            "Reactance (ohms)": 0.11001,
+            "Susceptance (S)": 15.865187273832648
+        },
+        "l16": {
+            "Source bus": "b9",
+            "Target bus": "b10",
+            "Reactance (ohms)": 0.0845,
+            "Susceptance (S)": 20.65478404727017
+        },
+        "l17": {
+            "Source bus": "b9",
+            "Target bus": "b14",
+            "Reactance (ohms)": 0.27038,
+            "Susceptance (S)": 6.4550974628091184
+        },
+        "l18": {
+            "Source bus": "b10",
+            "Target bus": "b11",
+            "Reactance (ohms)": 0.19207,
+            "Susceptance (S)": 9.08694357262628
+        },
+        "l19": {
+            "Source bus": "b12",
+            "Target bus": "b13",
+            "Reactance (ohms)": 0.19988,
+            "Susceptance (S)": 8.73188539120637
+        },
+        "l20": {
+            "Source bus": "b13",
+            "Target bus": "b14",
+            "Reactance (ohms)": 0.34802,
+            "Susceptance (S)": 5.0150257226433235
+        }
+    },
+    "Contingencies": {
+        "c1": {
+            "Affected lines": [
+                "l1"
+            ]
+        },
+        "c2": {
+            "Affected lines": [
+                "l2"
+            ]
+        },
+        "c3": {
+            "Affected lines": [
+                "l3"
+            ]
+        },
+        "c4": {
+            "Affected lines": [
+                "l4"
+            ]
+        },
+        "c5": {
+            "Affected lines": [
+                "l5"
+            ]
+        },
+        "c6": {
+            "Affected lines": [
+                "l6"
+            ]
+        },
+        "c7": {
+            "Affected lines": [
+                "l7"
+            ]
+        },
+        "c8": {
+            "Affected lines": [
+                "l8"
+            ]
+        },
+        "c9": {
+            "Affected lines": [
+                "l9"
+            ]
+        },
+        "c10": {
+            "Affected lines": [
+                "l10"
+            ]
+        },
+        "c11": {
+            "Affected lines": [
+                "l11"
+            ]
+        },
+        "c12": {
+            "Affected lines": [
+                "l12"
+            ]
+        },
+        "c13": {
+            "Affected lines": [
+                "l13"
+            ]
+        },
+        "c15": {
+            "Affected lines": [
+                "l15"
+            ]
+        },
+        "c16": {
+            "Affected lines": [
+                "l16"
+            ]
+        },
+        "c17": {
+            "Affected lines": [
+                "l17"
+            ]
+        },
+        "c18": {
+            "Affected lines": [
+                "l18"
+            ]
+        },
+        "c19": {
+            "Affected lines": [
+                "l19"
+            ]
+        },
+        "c20": {
+            "Affected lines": [
+                "l20"
+            ]
+        }
+    },
+    "Price-sensitive loads": {
+        "ps1": {
+            "Bus": "b3",
+            "Revenue ($/MW)": 100.0,
+            "Demand (MW)": 50.0
+        }
+    },
+    "Reserves": {
+        "r1": {
+            "Type": "Spinning",
+            "Amount (MW)": 100.0,
+            "Shortfall penalty ($/MW)": 1000.0
+        }
+    }
+}

docs/format.md

@@ -1,292 +0,0 @@
-```{sectnum}
----
-start: 2
-depth: 2
-suffix: .
----
-```
-
-
-Data Format
-===========
-
-
-Input Data Format
------------------
-
-Instances are specified by JSON files containing the following main sections:
-
-* Parameters
-* Buses
-* Generators
-* Price-sensitive loads
-* Transmission lines
-* Reserves
-* Contingencies
-
-Each section is described in detail below. For a complete example, see [case14](https://github.com/ANL-CEEESA/UnitCommitment.jl/tree/dev/instances/matpower/case14).
-
-### Parameters
-
-This section describes system-wide parameters, such as power balance penalties,  optimization parameters, such as the length of the planning horizon and the time.
-
-| Key                            | Description                                       | Default  | Time series?
-| :----------------------------- | :------------------------------------------------ | :------: | :------------:
-| `Time horizon (h)`                     | Length of the planning horizon (in hours). | Required | N
-| `Time step (min)` | Length of each time step (in minutes). Must be a divisor of 60 (e.g. 60, 30, 20, 15, etc). | `60` | N
-| `Power balance penalty ($/MW)` | Penalty for system-wide shortage or surplus in production (in $/MW). This is charged per time step. For example, if there is a shortage of 1 MW for three time steps, three times this amount will be charged. | `1000.0` | Y
-
-
-#### Example
-```json
-{
-    "Parameters": {
-        "Time horizon (h)": 4,
-        "Power balance penalty ($/MW)": 1000.0
-    }
-}
-```
-
-### Buses
-
-This section describes the characteristics of each bus in the system. 
-
-| Key                | Description                                                   | Default | Time series?
-| :----------------- | :------------------------------------------------------------ | ------- | :-------------:
-| `Load (MW)`        | Fixed load connected to the bus (in MW).                      | Required | Y
-
-
-#### Example
-```json
-{
-    "Buses": {
-        "b1": {
-            "Load (MW)": 0.0
-        },
-        "b2": {
-            "Load (MW)": [
-                26.01527,
-                24.46212,
-                23.29725,
-                22.90897
-            ]
-        }
-    }
-}
-```
-
-
-### Generators
-
-This section describes all generators in the system, including thermal units, renewable units and virtual units.
-
-| Key                       | Description                                      | Default | Time series?
-| :------------------------ | :------------------------------------------------| ------- | :-----------:
-| `Bus`                     | Identifier of the bus where this generator is located (string). | Required | N
-| `Production cost curve (MW)` and `Production cost curve ($)` | Parameters describing the piecewise-linear production costs. See below for more details. | Required | Y
-| `Startup costs ($)` and `Startup delays (h)` | Parameters describing how much it costs to start the generator after it has been shut down for a certain amount of time. If `Startup costs ($)` and `Startup delays (h)` are set to `[300.0, 400.0]` and `[1, 4]`, for example, and the generator is shut down at time `00:00` (h:min), then it costs \$300 to start up the generator at any time between `01:00` and `03:59`, and \$400 to start the generator at time `04:00` or any time after that.  The number of startup cost points is unlimited, and may be different for each generator. Startup delays must be strictly increasing and the first entry must equal `Minimum downtime (h)`. | `[0.0]` and `[1]` | N
-| `Minimum uptime (h)`      | Minimum amount of time the generator must stay operational after starting up (in hours). For example, if the generator starts up at time `00:00` (h:min) and `Minimum uptime (h)` is set to 4, then the generator can only shut down at time `04:00`. | `1` | N
-| `Minimum downtime (h)`    | Minimum amount of time the generator must stay offline after shutting down (in hours). For example, if the generator shuts down at time `00:00` (h:min) and `Minimum downtime (h)` is set to 4, then the generator can only start producing power again at time `04:00`. | `1` | N
-| `Ramp up limit (MW)`      | Maximum increase in production from one time step to the next (in MW). For example, if the generator is producing 100 MW at time step 1 and if this parameter is set to 40 MW, then the generator will produce at most 140 MW at time step 2. | `+inf` | N
-| `Ramp down limit (MW)`    | Maximum decrease in production from one time step to the next (in MW). For example, if the generator is producing 100 MW at time step 1 and this parameter is set to 40 MW, then the generator will produce at least 60 MW at time step 2. | `+inf` | N
-| `Startup limit (MW)`   | Maximum amount of power a generator can produce immediately after starting up (in MW). For example, if `Startup limit (MW)` is set to 100 MW and the unit is off at time step 1, then it may produce at most 100 MW at time step 2.| `+inf` | N
-| `Shutdown limit (MW)`     | Maximum amount of power a generator can produce immediately before shutting down (in MW). Specifically, the generator can only shut down at time step `t+1` if its production at time step `t` is below this limit.  | `+inf` | N
-| `Initial status (h)`  | If set to a positive number, indicates the amount of time (in hours) the generator has been on at the beginning of the simulation, and if set to a negative number, the amount of time the generator has been off. For example, if `Initial status (h)` is `-2`, this means that the generator was off since `-02:00` (h:min). The simulation starts at time `00:00`. If `Initial status (h)` is `3`, this means that the generator was on since `-03:00`. A value of zero is not acceptable. | Required | N
-| `Initial power (MW)`  | Amount of power the generator at time step `-1`, immediately before the planning horizon starts. | Required | N
-| `Must run?`               | If `true`, the generator should be committed, even if that is not economical (Boolean). | `false` | Y
-| `Provides spinning reserves?`    | If `true`, this generator may provide spinning reserves (Boolean). | `true` | Y
-
-#### Production costs and limits
-
-Production costs are represented as piecewise-linear curves. Figure 1 shows an example cost curve with three segments, where it costs \$1400, \$1600, \$2200 and \$2400 to generate, respectively, 100, 110, 130 and 135 MW of power. To model this generator, `Production cost curve (MW)` should be set to `[100, 110, 130, 135]`, and `Production cost curve ($)`  should be set to `[1400, 1600, 2200, 2400]`.
-Note that this curve also specifies the production limits. Specifically, the first point identifies the minimum power output when the unit is operational, while the last point identifies the maximum power output.
-
-<center>
-    <img src="../_static/cost_curve.png" style="max-width: 500px"/>
-    <div><b>Figure 1.</b> Piecewise-linear production cost curve.</div>
-    <br/>
-</center>
-
-#### Additional remarks:
-
-* For time-dependent production limits or time-dependent production costs, the usage of nested arrays is allowed. For example,  if `Production cost curve (MW)` is set to `[5.0, [10.0, 12.0, 15.0, 20.0]]`, then the unit may generate at most 10, 12, 15 and 20 MW of power during time steps 1, 2, 3 and 4, respectively. The minimum output for all time periods is fixed to at 5 MW.
-* There is no limit to the number of piecewise-linear segments, and different generators may have a different number of segments.
-* If `Production cost curve (MW)` and `Production cost curve ($)` both contain a single element, then the generator must produce exactly that amount of power when operational. To specify that the generator may produce any amount of power up to a certain limit `P`, the parameter `Production cost curve (MW)` should be set to `[0, P]`. 
-* Production cost curves must be convex.
-
-#### Example
-
-```json
-{
-    "Generators": {
-        "gen1": {
-            "Bus": "b1",
-            "Production cost curve (MW)": [100.0, 110.0, 130.0, 135.0],
-            "Production cost curve ($)": [1400.0, 1600.0, 2200.0, 2400.0],
-            "Startup costs ($)": [300.0, 400.0],
-            "Startup delays (h)": [1, 4],
-            "Ramp up limit (MW)": 232.68,
-            "Ramp down limit (MW)": 232.68,
-            "Startup limit (MW)": 232.68,
-            "Shutdown limit (MW)": 232.68,
-            "Minimum downtime (h)": 4,
-            "Minimum uptime (h)": 4,
-            "Initial status (h)": 12,
-            "Must run?": false,
-            "Provides spinning reserves?": true,
-        },
-        "gen2": {
-            "Bus": "b5",
-            "Production cost curve (MW)": [0.0, [10.0, 8.0, 0.0, 3.0]],
-            "Production cost curve ($)": [0.0, 0.0],
-            "Provides spinning reserves?": true,
-        }
-    }
-}
-```
-
-### Price-sensitive loads
-
-This section describes components in the system which may increase or reduce their energy consumption according to the energy prices. Fixed loads (as described in the `buses` section) are always served, regardless of the price, unless there is significant congestion in the system or insufficient production capacity. Price-sensitive loads, on the other hand, are only served if it is economical to do so. 
-
-| Key               | Description                                       | Default  | Time series?
-| :---------------- | :------------------------------------------------ | :------: | :------------:
-| `Bus`             | Bus where the load is located. Multiple price-sensitive loads may be placed at the same bus. | Required | N
-| `Revenue ($/MW)`  | Revenue obtained for serving each MW of power to this load. | Required | Y
-| `Demand (MW)`     | Maximum amount of power required by this load. Any amount lower than this may be served. | Required | Y
-
-
-#### Example
-```json
-{
-    "Price-sensitive loads": {
-        "p1": {
-            "Bus": "b3",
-            "Revenue ($/MW)": 23.0,
-            "Demand (MW)": 50.0
-        }
-    }
-}
-```
-
-### Transmission Lines
-
-This section describes the characteristics of transmission system, such as its topology and the susceptance of each transmission line.
-
-| Key                    | Description                                      | Default | Time series?
-| :--------------------- | :----------------------------------------------- | ------- | :------------:
-| `Source bus`           | Identifier of the bus where the transmission line originates. | Required | N
-| `Target bus`           | Identifier of the bus where the transmission line reaches. | Required | N
-| `Reactance (ohms)`     | Reactance of the transmission line (in ohms). | Required | N
-| `Susceptance (S)`      | Susceptance  of the transmission line (in siemens). | Required | N
-| `Normal flow limit (MW)` | Maximum amount of power (in MW) allowed to flow through the line when the system is in its regular, fully-operational state. | `+inf` | Y
-| `Emergency flow limit (MW)` | Maximum amount of power (in MW) allowed to flow through the line when the system is in degraded state (for example, after the failure of another transmission line). | `+inf` | Y
-| `Flow limit penalty ($/MW)` | Penalty for violating the flow limits of the transmission line (in $/MW). This is charged per time step. For example, if there is a thermal violation of 1 MW for three time steps, then three times this amount will be charged. | `5000.0` | Y
-
-#### Example
-
-```json
-{
-    "Transmission lines": {
-        "l1": {
-            "Source bus": "b1",
-            "Target bus": "b2",
-            "Reactance (ohms)": 0.05917,
-            "Susceptance (S)": 29.49686,
-            "Normal flow limit (MW)": 15000.0,
-            "Emergency flow limit (MW)": 20000.0,
-            "Flow limit penalty ($/MW)": 5000.0
-        }
-    }
-}
-```
-
-
-### Reserves
-
-This section describes the hourly amount of operating reserves required.
-
-
-| Key                   | Description                                        | Default   |  Time series?
-| :-------------------- | :------------------------------------------------- | --------- |  :----:
-| `Spinning (MW)`       | Minimum amount of system-wide spinning reserves (in MW). Only generators which are online may provide this reserve. | `0.0` | Y
-
-#### Example
-
-```json
-{
-    "Reserves": {
-        "Spinning (MW)": [
-            57.30552,
-            53.88429,
-            51.31838,
-            50.46307
-        ]
-    }
-}
-```
-
-### Contingencies
-
-This section describes credible contingency scenarios in the optimization, such as the loss of a transmission line or generator.
-
-| Key                   | Description                                      | Default
-| :-------------------- | :----------------------------------------------- | ----------
-| `Affected generators`      | List of generators affected by this contingency. May be omitted if no generators are affected. | `[]`
-| `Affected lines`      | List of transmission lines affected by this contingency. May be omitted if no lines are affected. | `[]`
-
-#### Example
-
-```json
-{
-    "Contingencies": {
-        "c1": {
-            "Affected lines": ["l1", "l2", "l3"],
-            "Affected generators": ["g1"]
-        },
-        "c2": {
-            "Affected lines": ["l4"]
-        },
-    }
-}
-```
-
-### Additional remarks
-
-#### Time series parameters
-
-Many numerical properties in the JSON file can be specified either as a single floating point number if they are time-independent, or as an array containing exactly `T` elements, if they are time-dependent, where `T` is the number of time steps in the planning horizon. For example, both formats below are valid when `T=3`:
-
-```json
-{
-    "Load (MW)": 800.0,
-    "Load (MW)": [800.0, 850.0, 730.0]
-}
-```
-
-The value `T` depends on both `Time horizon (h)` and `Time step (min)`, as the table below illustrates.
-
-Time horizon (h) | Time step (min) | T
-:---------------:|:---------------:|:----:
-24               | 60              | 24
-24               | 15              | 96
-24               | 5               | 288
-36               | 60              | 36
-36               | 15              | 144
-36               | 5               | 432
-
-Output Data Format
-------------------
-
-The output data format is also JSON-based, but it is not currently documented since we expect it to change significantly in a future version of the package.
-
-
-Current limitations
--------------------
-
-* All reserves are system-wide. Zonal reserves are not currently supported.
-* Network topology remains the same for all time periods
-* Only N-1 transmission contingencies are supported. Generator contingencies are not currently supported.
-* Time-varying minimum production amounts are not currently compatible with ramp/startup/shutdown limits.
-
-

docs/instances.md

@@ -1,343 +0,0 @@
-```{sectnum}
----
-start: 3
-depth: 2
-suffix: .
----
-```
-
-Instances
-=========
-
-UnitCommitment.jl provides a large collection of benchmark instances collected
-from the literature and converted to a [common data format](format.md). In some cases, as indicated below, the original instances have been extended, with realistic parameters, using data-driven methods. 
-If you use these instances in your research, we request that you cite UnitCommitment.jl, as well as the original sources.
-
-Raw instances files are [available at our GitHub repository](https://github.com/ANL-CEEESA/UnitCommitment.jl/tree/dev/instances). Benchmark instances can also be loaded with
-`UnitCommitment.read_benchmark(name)`, as explained in the [usage section](usage.md).
-
-
-MATPOWER
---------
-
-[MATPOWER](https://github.com/MATPOWER/matpower) is an open-source package for solving power flow problems in MATLAB and Octave. It contains a number of power flow test cases, which have been widely used in the power systems literature.
-
-Because most MATPOWER test cases were originally designed for power flow studies, they lack a number of important unit commitment parameters, such as time-varying loads, production cost curves, ramp limits, reserves and initial conditions. The test cases included in UnitCommitment.jl are extended versions of the original MATPOWER test cases, modified as following:
-
-* **Production cost** curves were generated using a data-driven approach, based on publicly available data. More specifically, machine learning models were trained to predict typical production cost curves, for each day of the year, based on a generator's maximum and minimum power output.
-
-* **Load profiles** were generated using a similar data-driven approach.
-
-* **Ramp-up, ramp-down, startup and shutdown rates** were set to a fixed proportion of the generator's maximum output.
-
-* **Minimum reserves** were set to a fixed proportion of the total demand.
-
-* **Contingencies** were set to include all N-1 transmission line contingencies that do not generate islands or isolated buses. More specifically, there is one contingency for each transmission line, as long as that transmission line is not a bridge in the network graph.
-
-For each MATPOWER test case, UC.jl provides two variations (`2017-02-01` and `2017-08-01`) corresponding respectively to a winter and to a summer test case.
-
-### MATPOWER/UW-PSTCA
-
-A variety of smaller IEEE test cases, [compiled by University of Washington](http://labs.ece.uw.edu/pstca/), corresponding mostly to small portions of the American Electric Power System in the 1960s.
-
-| Name | Buses | Generators | Lines | Contingencies | References |
-|------|-------|------------|-------|---------------|--------|
-| `matpower/case14/2017-02-01` | 14 | 5 | 20 | 19 | [MTPWR, PSTCA]
-| `matpower/case14/2017-08-01` | 14 | 5 | 20 | 19 | [MTPWR, PSTCA]
-| `matpower/case30/2017-02-01` | 30 | 6 | 41 | 38 | [MTPWR, PSTCA]
-| `matpower/case30/2017-08-01` | 30 | 6 | 41 | 38 | [MTPWR, PSTCA]
-| `matpower/case57/2017-02-01` | 57 | 7 | 80 | 79 | [MTPWR, PSTCA]
-| `matpower/case57/2017-08-01` | 57 | 7 | 80 | 79 | [MTPWR, PSTCA]
-| `matpower/case118/2017-02-01` | 118 | 54 | 186 | 177 | [MTPWR, PSTCA]
-| `matpower/case118/2017-08-01` | 118 | 54 | 186 | 177 | [MTPWR, PSTCA]
-| `matpower/case300/2017-02-01` | 300 | 69 | 411 | 320 | [MTPWR, PSTCA]
-| `matpower/case300/2017-08-01` | 300 | 69 | 411 | 320 | [MTPWR, PSTCA]
-
-
-### MATPOWER/Polish
-
-Test cases based on the Polish 400, 220 and 110 kV networks, originally provided by **Roman Korab** (Politechnika Śląska) and corrected by the MATPOWER team.
-
-| Name | Buses | Generators | Lines | Contingencies | References |
-|------|-------|------------|-------|---------------|--------|
-| `matpower/case2383wp/2017-02-01` | 2383 | 323 | 2896 | 2240 | [MTPWR]
-| `matpower/case2383wp/2017-08-01` | 2383 | 323 | 2896 | 2240 | [MTPWR]
-| `matpower/case2736sp/2017-02-01` | 2736 | 289 | 3504 | 3159 | [MTPWR]
-| `matpower/case2736sp/2017-08-01` | 2736 | 289 | 3504 | 3159 | [MTPWR]
-| `matpower/case2737sop/2017-02-01` | 2737 | 267 | 3506 | 3161 | [MTPWR]
-| `matpower/case2737sop/2017-08-01` | 2737 | 267 | 3506 | 3161 | [MTPWR]
-| `matpower/case2746wop/2017-02-01` | 2746 | 443 | 3514 | 3155 | [MTPWR]
-| `matpower/case2746wop/2017-08-01` | 2746 | 443 | 3514 | 3155 | [MTPWR]
-| `matpower/case2746wp/2017-02-01` | 2746 | 457 | 3514 | 3156 | [MTPWR]
-| `matpower/case2746wp/2017-08-01` | 2746 | 457 | 3514 | 3156 | [MTPWR]
-| `matpower/case3012wp/2017-02-01` | 3012 | 496 | 3572 | 2854 | [MTPWR]
-| `matpower/case3012wp/2017-08-01` | 3012 | 496 | 3572 | 2854 | [MTPWR]
-| `matpower/case3120sp/2017-02-01` | 3120 | 483 | 3693 | 2950 | [MTPWR]
-| `matpower/case3120sp/2017-08-01` | 3120 | 483 | 3693 | 2950 | [MTPWR]
-| `matpower/case3375wp/2017-02-01` | 3374 | 590 | 4161 | 3245 | [MTPWR]
-| `matpower/case3375wp/2017-08-01` | 3374 | 590 | 4161 | 3245 | [MTPWR]
-
-### MATPOWER/PEGASE
-
-Test cases from the [Pan European Grid Advanced Simulation and State Estimation (PEGASE) project](https://cordis.europa.eu/project/id/211407), describing part of the European high voltage transmission network.
-
-| Name | Buses | Generators | Lines | Contingencies | References |
-|------|-------|------------|-------|---------------|--------|
-| `matpower/case89pegase/2017-02-01` | 89 | 12 | 210 | 192 | [JoFlMa16, FlPaCa13, MTPWR]
-| `matpower/case89pegase/2017-08-01` | 89 | 12 | 210 | 192 | [JoFlMa16, FlPaCa13, MTPWR]
-| `matpower/case1354pegase/2017-02-01` | 1354 | 260 | 1991 | 1288 | [JoFlMa16, FlPaCa13, MTPWR]
-| `matpower/case1354pegase/2017-08-01` | 1354 | 260 | 1991 | 1288 | [JoFlMa16, FlPaCa13, MTPWR]
-| `matpower/case2869pegase/2017-02-01` | 2869 | 510 | 4582 | 3579 | [JoFlMa16, FlPaCa13, MTPWR]
-| `matpower/case2869pegase/2017-08-01` | 2869 | 510 | 4582 | 3579 | [JoFlMa16, FlPaCa13, MTPWR]
-| `matpower/case9241pegase/2017-02-01` | 9241 | 1445 | 16049 | 13932 | [JoFlMa16, FlPaCa13, MTPWR]
-| `matpower/case9241pegase/2017-08-01` | 9241 | 1445 | 16049 | 13932 | [JoFlMa16, FlPaCa13, MTPWR]
-| `matpower/case13659pegase/2017-02-01` | 13659 | 4092 | 20467 | 13932 | [JoFlMa16, FlPaCa13, MTPWR]
-| `matpower/case13659pegase/2017-08-01` | 13659 | 4092 | 20467 | 13932 | [JoFlMa16, FlPaCa13, MTPWR]
-
-### MATPOWER/RTE
-
-Test cases from the R&D Division at [Reseau de Transport d'Electricite](https://www.rte-france.com) representing the size and complexity of the French very high voltage transmission network.
-
-| Name | Buses | Generators | Lines | Contingencies | References |
-|------|-------|------------|-------|---------------|--------|
-| `matpower/case1888rte/2017-02-01` | 1888 | 296 | 2531 | 1484 | [MTPWR, JoFlMa16]
-| `matpower/case1888rte/2017-08-01` | 1888 | 296 | 2531 | 1484 | [MTPWR, JoFlMa16]
-| `matpower/case1951rte/2017-02-01` | 1951 | 390 | 2596 | 1497 | [MTPWR, JoFlMa16]
-| `matpower/case1951rte/2017-08-01` | 1951 | 390 | 2596 | 1497 | [MTPWR, JoFlMa16]
-| `matpower/case2848rte/2017-02-01` | 2848 | 544 | 3776 | 2242 | [MTPWR, JoFlMa16]
-| `matpower/case2848rte/2017-08-01` | 2848 | 544 | 3776 | 2242 | [MTPWR, JoFlMa16]
-| `matpower/case2868rte/2017-02-01` | 2868 | 596 | 3808 | 2260 | [MTPWR, JoFlMa16]
-| `matpower/case2868rte/2017-08-01` | 2868 | 596 | 3808 | 2260 | [MTPWR, JoFlMa16]
-| `matpower/case6468rte/2017-02-01` | 6468 | 1262 | 9000 | 6094 | [MTPWR, JoFlMa16]
-| `matpower/case6468rte/2017-08-01` | 6468 | 1262 | 9000 | 6094 | [MTPWR, JoFlMa16]
-| `matpower/case6470rte/2017-02-01` | 6470 | 1306 | 9005 | 6085 | [MTPWR, JoFlMa16]
-| `matpower/case6470rte/2017-08-01` | 6470 | 1306 | 9005 | 6085 | [MTPWR, JoFlMa16]
-| `matpower/case6495rte/2017-02-01` | 6495 | 1352 | 9019 | 6060 | [MTPWR, JoFlMa16]
-| `matpower/case6495rte/2017-08-01` | 6495 | 1352 | 9019 | 6060 | [MTPWR, JoFlMa16]
-| `matpower/case6515rte/2017-02-01` | 6515 | 1368 | 9037 | 6063 | [MTPWR, JoFlMa16]
-| `matpower/case6515rte/2017-08-01` | 6515 | 1368 | 9037 | 6063 | [MTPWR, JoFlMa16]
-
-
-PGLIB-UC Instances
-------------------
-
-[PGLIB-UC](https://github.com/power-grid-lib/pglib-uc) is a benchmark library curated and maintained by the [IEEE PES Task Force on Benchmarks for Validation of Emerging Power System Algorithms](https://power-grid-lib.github.io/). These test cases have been used in [KnOsWa20].
-
-### PGLIB-UC/California
-
-Test cases based on publicly available data from the California ISO. For more details, see [PGLIB-UC case file overview](https://github.com/power-grid-lib/pglib-uc).
-
-| Name | Buses | Generators | Lines | Contingencies | References |
-|------|-------|------------|-------|---------------|--------|
-| `pglib-uc/ca/2014-09-01_reserves_0` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2014-09-01_reserves_1` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2014-09-01_reserves_3` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2014-09-01_reserves_5` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2014-12-01_reserves_0` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2014-12-01_reserves_1` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2014-12-01_reserves_3` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2014-12-01_reserves_5` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2015-03-01_reserves_0` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2015-03-01_reserves_1` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2015-03-01_reserves_3` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2015-03-01_reserves_5` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2015-06-01_reserves_0` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2015-06-01_reserves_1` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2015-06-01_reserves_3` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/2015-06-01_reserves_5` | 1 | 610 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/Scenario400_reserves_0` | 1 | 611 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/Scenario400_reserves_1` | 1 | 611 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/Scenario400_reserves_3` | 1 | 611 | 0 | 0 | [KnOsWa20]
-| `pglib-uc/ca/Scenario400_reserves_5` | 1 | 611 | 0 | 0 | [KnOsWa20]
-
-
-### PGLIB-UC/FERC
-
-Test cases based on a publicly available [unit commitment test case produced by the Federal Energy Regulatory Commission](https://www.ferc.gov/industries-data/electric/power-sales-and-markets/increasing-efficiency-through-improved-software-1). For more details, see [PGLIB-UC case file overview](https://github.com/power-grid-lib/pglib-uc).
-
-| Name | Buses | Generators | Lines | Contingencies | References |
-|------|-------|------------|-------|---------------|--------|
-| `pglib-uc/ferc/2015-01-01_hw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-01-01_lw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-02-01_hw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-02-01_lw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-03-01_hw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-03-01_lw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-04-01_hw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-04-01_lw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-05-01_hw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-05-01_lw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-06-01_hw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-06-01_lw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-07-01_hw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-07-01_lw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-08-01_hw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-08-01_lw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-09-01_hw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-09-01_lw` | 1 | 979 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-10-01_hw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-10-01_lw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-11-02_hw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-11-02_lw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-12-01_hw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-| `pglib-uc/ferc/2015-12-01_lw` | 1 | 935 | 0 | 0 | [KnOsWa20, KrHiOn12]
-
-
-### PGLIB-UC/RTS-GMLC
-
-[RTS-GMLC](https://github.com/GridMod/RTS-GMLC) is an updated version of the RTS-96 test system produced by the United States Department of Energy's [Grid Modernization Laboratory Consortium](https://gmlc.doe.gov/). The PGLIB-UC/RTS-GMLC instances are modified versions of the original RTS-GMLC instances, with modified ramp-rates and without a transmission network. For more details, see [PGLIB-UC case file overview](https://github.com/power-grid-lib/pglib-uc).
-
-| Name | Buses | Generators | Lines | Contingencies | References |
-|------|-------|------------|-------|---------------|--------|
-| `pglib-uc/rts_gmlc/2020-01-27` | 1 | 154 | 0 | 0 | [BaBlEh19]
-| `pglib-uc/rts_gmlc/2020-02-09` | 1 | 154 | 0 | 0 | [BaBlEh19]
-| `pglib-uc/rts_gmlc/2020-03-05` | 1 | 154 | 0 | 0 | [BaBlEh19]
-| `pglib-uc/rts_gmlc/2020-04-03` | 1 | 154 | 0 | 0 | [BaBlEh19]
-| `pglib-uc/rts_gmlc/2020-05-05` | 1 | 154 | 0 | 0 | [BaBlEh19]
-| `pglib-uc/rts_gmlc/2020-06-09` | 1 | 154 | 0 | 0 | [BaBlEh19]
-| `pglib-uc/rts_gmlc/2020-07-06` | 1 | 154 | 0 | 0 | [BaBlEh19]
-| `pglib-uc/rts_gmlc/2020-08-12` | 1 | 154 | 0 | 0 | [BaBlEh19]
-| `pglib-uc/rts_gmlc/2020-09-20` | 1 | 154 | 0 | 0 | [BaBlEh19]
-| `pglib-uc/rts_gmlc/2020-10-27` | 1 | 154 | 0 | 0 | [BaBlEh19]
-| `pglib-uc/rts_gmlc/2020-11-25` | 1 | 154 | 0 | 0 | [BaBlEh19]
-| `pglib-uc/rts_gmlc/2020-12-23` | 1 | 154 | 0 | 0 | [BaBlEh19]
-
-
-OR-LIB/UC
----------
-
-[OR-LIB](http://people.brunel.ac.uk/~mastjjb/jeb/info.html) is a collection of test data sets for a variety of operations research problems, including unit commitment. The UC instances in OR-LIB are synthetic instances generated by a [random problem generator](http://groups.di.unipi.it/optimize/Data/UC.html) developed by the [Operations Research Group at University of Pisa](http://groups.di.unipi.it/optimize/). These test cases have been used in [FrGe06] and many other publications.
-
-| Name | Hours | Buses | Generators | Lines | Contingencies | References |
-|------|-------|-------|------------|-------|---------------|------------|
-| `or-lib/10_0_1_w` | 24 | 1 | 10 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/10_0_2_w` | 24 | 1 | 10 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/10_0_3_w` | 24 | 1 | 10 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/10_0_4_w` | 24 | 1 | 10 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/10_0_5_w` | 24 | 1 | 10 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/20_0_1_w` | 24 | 1 | 20 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/20_0_2_w` | 24 | 1 | 20 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/20_0_3_w` | 24 | 1 | 20 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/20_0_4_w` | 24 | 1 | 20 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/20_0_5_w` | 24 | 1 | 20 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/50_0_1_w` | 24 | 1 | 50 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/50_0_2_w` | 24 | 1 | 50 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/50_0_3_w` | 24 | 1 | 50 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/50_0_4_w` | 24 | 1 | 50 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/50_0_5_w` | 24 | 1 | 50 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/75_0_1_w` | 24 | 1 | 75 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/75_0_2_w` | 24 | 1 | 75 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/75_0_3_w` | 24 | 1 | 75 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/75_0_4_w` | 24 | 1 | 75 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/75_0_5_w` | 24 | 1 | 75 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/100_0_1_w` | 24 | 1 | 100 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/100_0_2_w` | 24 | 1 | 100 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/100_0_3_w` | 24 | 1 | 100 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/100_0_4_w` | 24 | 1 | 100 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/100_0_5_w` | 24 | 1 | 100 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/150_0_1_w` | 24 | 1 | 150 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/150_0_2_w` | 24 | 1 | 150 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/150_0_3_w` | 24 | 1 | 150 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/150_0_4_w` | 24 | 1 | 150 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/150_0_5_w` | 24 | 1 | 150 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_10_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_11_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_12_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_1_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_2_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_3_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_4_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_5_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_6_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_7_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_8_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-| `or-lib/200_0_9_w` | 24 | 1 | 200 | 0 | 0 | [ORLIB, FrGe06]
-
-
-Tejada19
---------
-
- Test cases used in [TeLuSa19]. These instances are similar to OR-LIB/UC, in the sense that they use the same random problem generator, but are much larger.
-
-| Name | Hours | Buses | Generators | Lines | Contingencies | References |
-|------|-------|-------|------------|-------|---------------|------------|
-| `tejada19/UC_24h_214g` | 24 | 1 | 214 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_250g` | 24 | 1 | 250 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_290g` | 24 | 1 | 290 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_480g` | 24 | 1 | 480 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_505g` | 24 | 1 | 505 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_623g` | 24 | 1 | 623 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_647g` | 24 | 1 | 647 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_836g` | 24 | 1 | 836 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_850g` | 24 | 1 | 850 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_918g` | 24 | 1 | 918 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_931g` | 24 | 1 | 931 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_940g` | 24 | 1 | 940 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_957g` | 24 | 1 | 957 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_959g` | 24 | 1 | 959 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1069g` | 24 | 1 | 1069 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1130g` | 24 | 1 | 1130 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1376g` | 24 | 1 | 1376 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1393g` | 24 | 1 | 1393 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1577g` | 24 | 1 | 1577 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1615g` | 24 | 1 | 1615 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1632g` | 24 | 1 | 1632 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1768g` | 24 | 1 | 1768 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1804g` | 24 | 1 | 1804 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1820g` | 24 | 1 | 1820 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1823g` | 24 | 1 | 1823 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_24h_1888g` | 24 | 1 | 1888 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_36g` | 168 | 1 | 36 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_38g` | 168 | 1 | 38 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_40g` | 168 | 1 | 40 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_53g` | 168 | 1 | 53 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_58g` | 168 | 1 | 58 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_59g` | 168 | 1 | 59 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_72g` | 168 | 1 | 72 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_84g` | 168 | 1 | 84 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_86g` | 168 | 1 | 86 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_88g` | 168 | 1 | 88 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_93g` | 168 | 1 | 93 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_105g` | 168 | 1 | 105 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_110g` | 168 | 1 | 110 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_125g` | 168 | 1 | 125 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_130g` | 168 | 1 | 130 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_131g` | 168 | 1 | 131 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_140g` | 168 | 1 | 140 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_165g` | 168 | 1 | 165 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_175g` | 168 | 1 | 175 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_179g` | 168 | 1 | 179 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_188g` | 168 | 1 | 188 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_192g` | 168 | 1 | 192 | 0 | 0 | [TeLuSa19]
-| `tejada19/UC_168h_199g` | 168 | 1 | 199 | 0 | 0 | [TeLuSa19]
-
-
-References
-----------
-
-* [UCJL] **Alinson S. Xavier, Aleksandr M. Kazachkov, Feng Qiu.** "UnitCommitment.jl: A Julia/JuMP Optimization Package for Security-Constrained Unit Commitment". Zenodo (2020). [DOI: 10.5281/zenodo.4269874](https://doi.org/10.5281/zenodo.4269874)
-
-* [KnOsWa20] **Bernard Knueven, James Ostrowski and Jean-Paul Watson.** "On Mixed-Integer Programming Formulations for the Unit Commitment Problem". INFORMS Journal on Computing (2020). [DOI: 10.1287/ijoc.2019.0944](https://doi.org/10.1287/ijoc.2019.0944)
-
-* [KrHiOn12] **Eric Krall, Michael Higgins and Richard P. O’Neill.** "RTO unit commitment test system." Federal Energy Regulatory Commission. Available at: <https://www.ferc.gov/industries-data/electric/power-sales-and-markets/increasing-efficiency-through-improved-software-1> (Accessed: Nov 14, 2020)
-
-* [BaBlEh19] **Clayton Barrows, Aaron Bloom, Ali Ehlen, Jussi Ikaheimo, Jennie Jorgenson, Dheepak Krishnamurthy, Jessica Lau et al.** "The IEEE Reliability Test System: A Proposed 2019 Update." IEEE Transactions on Power Systems (2019). [DOI: 10.1109/TPWRS.2019.2925557](https://doi.org/10.1109/TPWRS.2019.2925557)
-
-* [JoFlMa16] **C. Josz, S. Fliscounakis, J. Maeght, and P. Panciatici.** "AC Power Flow
-Data in MATPOWER and QCQP Format: iTesla, RTE Snapshots, and PEGASE". [ArXiv (2016)](https://arxiv.org/abs/1603.01533).
-
-* [FlPaCa13] **S. Fliscounakis, P. Panciatici, F. Capitanescu, and L. Wehenkel.**
-"Contingency ranking with respect to overloads in very large power
-systems taking into account uncertainty, preventive and corrective
-actions", Power Systems, IEEE Trans. on, (28)4:4909-4917, 2013.
-[DOI: 10.1109/TPWRS.2013.2251015](https://doi.org/10.1109/TPWRS.2013.2251015)
-
-* [MTPWR] **D. Zimmerman, C. E. Murillo-Sandnchez and R. J. Thomas.** "Matpower:  Steady-state  operations,  planning,  and  analysis  tools  forpower systems research and education", IEEE Transactions on PowerSystems, vol. 26, no. 1, pp. 12 –19, Feb. 2011. [DOI: 10.1109/TPWRS.2010.2051168](https://doi.org/10.1109/TPWRS.2010.2051168)
-
-* [PSTCA] **University of Washington, Dept. of Electrical Engineering.** "Power Systems Test Case Archive". Available at: <http://www.ee.washington.edu/research/pstca/> (Accessed: Nov 14, 2020)
-
-* [ORLIB] **J.E.Beasley.** "OR-Library: distributing test problems by electronic mail", Journal of the Operational Research Society 41(11) (1990). [DOI: 10.2307/2582903](https://doi.org/10.2307/2582903)
-
-* [FrGe06] **A. Frangioni, C. Gentile.** "Solving nonlinear single-unit commitment problems with ramping constraints" Operations Research 54(4), p. 767 - 775, 2006. [DOI: 10.1287/opre.1060.0309](https://doi.org/10.1287/opre.1060.0309)
-
-* [TeLuSa19] **D. A. Tejada-Arango, S. Lumbreras, P. Sanchez-Martin and A. Ramos.** "Which Unit-Commitment Formulation is Best? A Systematic Comparison," in IEEE Transactions on Power Systems. [DOI: 10.1109/TPWRS.2019.2962024](https://ieeexplore.ieee.org/document/8941313/).

docs/make.jl

@@ -0,0 +1,43 @@
+using Documenter
+using UnitCommitment
+using JuMP
+using Literate
+
+
+
+function make()
+    literate_sources = [
+        "src/tutorials/usage.jl",
+        "src/tutorials/customizing.jl",
+        "src/tutorials/lmp.jl",
+        "src/tutorials/market.jl",
+    ]
+    for src in literate_sources
+        Literate.markdown(
+            src,
+            dirname(src);
+            documenter = true,
+            credit = false,
+        )
+    end
+    return makedocs(
+        sitename = "UnitCommitment.jl",
+        pages = [
+            "Home" => "index.md",
+            "Tutorials" => [
+                "tutorials/usage.md",
+                "tutorials/customizing.md",
+                "tutorials/lmp.md",
+                "tutorials/market.md",
+                "tutorials/decomposition.md",
+            ],
+            "User guide" => [
+                "guides/problem.md",
+                "guides/format.md",
+                "guides/instances.md",
+            ],
+            "api.md",
+        ],
+        format = Documenter.HTML(assets = ["assets/custom.css"]),
+    )
+end

docs/model.md

@@ -1,244 +0,0 @@
-```{sectnum}
----
-start: 4
-depth: 2
-suffix: .
----
-```
-
-JuMP Model
-==========
-
-In this page, we describe the JuMP optimization model produced by the function `UnitCommitment.build_model`. A detailed understanding of this model is not necessary if you are just interested in using the package to solve some standard unit commitment cases, but it may be useful, for example, if you need to solve a slightly different problem, with additional variables and constraints. The notation in this page generally follows [KnOsWa20].
-
-Decision variables
-------------------
-
-### Generators
-
-Name | Symbol | Description | Unit
------|:--------:|-------------|:------:
-`is_on[g,t]` | $u_{g}(t)$ | True if generator `g` is on at time `t`. | Binary
-`switch_on[g,t]` | $v_{g}(t)$ | True is generator `g` switches on at time `t`. | Binary
-`switch_off[g,t]` | $w_{g}(t)$ | True if generator `g` switches off at time `t`. | Binary
-`prod_above[g,t]` |$p'_{g}(t)$ | Amount of power produced by generator `g` above its minimum power output at time `t`. For example, if the minimum power of generator `g` is 100 MW and `g` is producing 115 MW of power at time `t`, then `prod_above[g,t]` equals `15.0`. | MW
-`segprod[g,t,k]` | $p^k_g(t)$ | Amount of power from piecewise linear segment `k` produced by generator `g` at time `t`. For example, if cost curve for generator `g` is defined by the points `(100, 1400)`, `(110, 1600)`, `(130, 2200)` and `(135, 2400)`, and if the generator is producing 115 MW of power at time `t`, then `segprod[g,t,:]` equals `[10.0, 5.0, 0.0]`.| MW
-`reserve[g,t]` | $r_g(t)$ | Amount of reserves provided by generator `g` at time `t`. | MW
-`startup[g,t,s]` | $\delta^s_g(t)$ | True if generator `g` switches on at time `t` incurring start-up costs from start-up category `s`. | Binary
-
-
-### Buses
-
-Name | Symbol | Description | Unit
------|:------:|-------------|:------:
-`net_injection[b,t]` | $n_b(t)$ | Net injection at bus `b` at time `t`. | MW
-`curtail[b,t]` | $s^+_b(t)$ | Amount of load curtailed at bus `b` at time `t` | MW
-
-
-### Price-sensitive loads
-
-Name | Symbol | Description | Unit
------|:------:|-------------|:------:
-`loads[s,t]` | $d_{s}(t)$ | Amount of power served to price-sensitive load `s` at time `t`. | MW
-
-### Transmission lines
-
-Name | Symbol | Description | Unit
------|:------:|-------------|:------:
-`flow[l,t]` | $f_l(t)$ | Power flow on line `l` at time `t`. | MW
-`overflow[l,t]` | $f^+_l(t)$ | Amount of flow above the limit for line `l` at time `t`. | MW
-
-```{warning}
-
-Since transmission and N-1 security constraints are enforced in a lazy way, most of the `flow[l,t]` variables are never added to the model. Accessing `model[:flow][l,t]` without first checking that the variable exists will likely generate an error.
-```
-
-Objective function
-------------------
-
-$$
-\begin{align}
-    \text{minimize} \;\; &
-        \sum_{t \in \mathcal{T}}
-          \sum_{g \in \mathcal{G}}
-          C^\text{min}_g(t) u_g(t) \\
-    &
-        + \sum_{t \in \mathcal{T}}
-          \sum_{g \in \mathcal{G}}
-          \sum_{g \in \mathcal{K}_g}
-          C^k_g(t) p^k_g(t) \\
-    &
-        + \sum_{t \in \mathcal{T}}
-          \sum_{g \in \mathcal{G}}
-          \sum_{s \in \mathcal{S}_g}
-          C^s_{g}(t) \delta^s_g(t) \\
-    &
-        + \sum_{t \in \mathcal{T}}
-          \sum_{l \in \mathcal{L}}
-          C^\text{overflow}_{l}(t) f^+_l(t) \\
-    &
-        + \sum_{t \in \mathcal{T}}
-           \sum_{b \in \mathcal{B}}
-           C^\text{curtail}(t) s^+_b(t) \\
-    &
-        - \sum_{t \in \mathcal{T}}
-           \sum_{s \in \mathcal{PS}}
-           R_{s}(t) d_{s}(t) \\
-          
-\end{align}
-$$
-where
-- $\mathcal{B}$ is the set of buses
-- $\mathcal{G}$ is the set of generators
-- $\mathcal{L}$ is the set of transmission lines
-- $\mathcal{PS}$ is the set of price-sensitive loads
-- $\mathcal{S}_g$ is the set of start-up categories for generator $g$
-- $\mathcal{T}$ is the set of time steps
-- $C^\text{curtail}(t)$ is the curtailment penalty (in \$/MW)
-- $C^\text{min}_g(t)$ is the cost of keeping generator $g$ on and producing at minimum power during time $t$ (in \$)
-- $C^\text{overflow}_{l}(t)$ is the flow limit penalty for line $l$ at time $t$ (in \$/MW)
-- $C^k_g(t)$ is the cost for generator $g$ to produce 1 MW of power at time $t$ under piecewise linear segment $k$
-- $C^s_{g}(t)$ is the cost of starting up generator $g$ at time $t$ under start-up category $s$ (in \$)
-- $R_{s}(t)$ is the revenue obtained from serving price-sensitive load $s$ at time $t$ (in \$/MW)
-
-
-Constraints
------------
-
-TODO
-
-
-Inspecting and modifying the model
-----------------------------------
-
-### Accessing decision variables
-
-After building a model using `UnitCommitment.build_model`, it is possible to obtain a reference to the decision variables by calling `model[:varname][index]`. For example, `model[:is_on]["g1",1]` returns a direct reference to the JuMP variable indicating whether generator named "g1" is on at time 1. The script below illustrates how to build a model, solve it and display the solution without using the function `UnitCommitment.solution`.
-
-```julia
-using Cbc
-using Printf
-using JuMP
-using UnitCommitment
-
-# Load benchmark instance
-instance = UnitCommitment.read_benchmark("matpower/case118/2017-02-01")
-
-# Build JuMP model
-model = UnitCommitment.build_model(
-    instance=instance,
-    optimizer=Cbc.Optimizer,
-)
-
-# Solve the model
-UnitCommitment.optimize!(model)
-
-# Display commitment status
-for g in instance.units
-    for t in 1:instance.time
-        @printf(
-            "%-10s %5d %5.1f %5.1f %5.1f\n",
-            g.name,
-            t,
-            value(model[:is_on][g.name, t]),
-            value(model[:switch_on][g.name, t]),
-            value(model[:switch_off][g.name, t]),
-        )
-    end
-end
-```
-
-### Fixing variables, modifying objective function and adding constraints
-
-Since we now have a direct reference to the JuMP decision variables, it is possible to fix variables, change the coefficients in the objective function, or even add new constraints to the model before solving it. The script below shows how can this be accomplished. For more information on modifying an existing model, [see the JuMP documentation](https://jump.dev/JuMP.jl/stable/manual/variables/).
-
-```julia
-using Cbc
-using JuMP
-using UnitCommitment
-
-# Load benchmark instance
-instance = UnitCommitment.read_benchmark("matpower/case118/2017-02-01")
-
-# Construct JuMP model
-model = UnitCommitment.build_model(
-    instance=instance,
-    optimizer=Cbc.Optimizer,
-)
-
-# Fix a decision variable to 1.0
-JuMP.fix(
-    model[:is_on]["g1",1],
-    1.0,
-    force=true,
-)
-
-# Change the objective function
-JuMP.set_objective_coefficient(
-    model,
-    model[:switch_on]["g2",1],
-    1000.0,
-)
-
-# Create a new constraint
-@constraint(
-    model,
-    model[:is_on]["g3",1] + model[:is_on]["g4",1] <= 1,
-)
-
-# Solve the model
-UnitCommitment.optimize!(model)
-```
-
-### Adding new component to a bus
-
-The following snippet shows how to add a new grid component to a particular bus. For each time step, we create decision variables for the new grid component, add these variables to the objective function, then attach the component to a particular bus by modifying some existing model constraints. 
-
-```julia
-using Cbc
-using JuMP
-using UnitCommitment
-
-# Load instance and build base model
-instance = UnitCommitment.read_benchmark("matpower/case118/2017-02-01")
-model = UnitCommitment.build_model(
-    instance=instance,
-    optimizer=Cbc.Optimizer,
-)
-
-# Get the number of time steps in the original instance
-T = instance.time
-
-# Create decision variables for the new grid component.
-# In this example, we assume that the new component can
-# inject up to 10 MW of power at each time step, so we
-# create new continuous variables 0 ≤ x[t] ≤ 10.
-@variable(model, x[1:T], lower_bound=0.0, upper_bound=10.0)
-
-# For each time step
-for t in 1:T
-
-    # Add production costs to the objective function.
-    # In this example, we assume a cost of $5/MW.
-    set_objective_coefficient(model, x[t], 5.0)
-
-    # Attach the new component to bus b1, by modifying the
-    # constraint `eq_net_injection`.
-    set_normalized_coefficient(
-        model[:eq_net_injection]["b1", t],
-        x[t],
-        1.0,
-    )
-end
-
-# Solve the model
-UnitCommitment.optimize!(model)
-
-# Show optimal values for the x variables
-@show value.(x)
-```
-
-References
-----------
-* [KnOsWa20] **Bernard Knueven, James Ostrowski and Jean-Paul Watson.** "On Mixed-Integer Programming Formulations for the Unit Commitment Problem". INFORMS Journal on Computing (2020). [DOI: 10.1287/ijoc.2019.0944](https://doi.org/10.1287/ijoc.2019.0944)
-

docs/src/api.md

@@ -0,0 +1,63 @@
+# API Reference
+
+## Read data, build model & optimize
+
+```@docs
+UnitCommitment.read
+UnitCommitment.read_benchmark
+UnitCommitment.build_model
+UnitCommitment.optimize!
+UnitCommitment.solution
+UnitCommitment.validate
+UnitCommitment.write
+```
+
+## Locational Marginal Prices
+
+### Conventional LMPs
+
+```@docs
+UnitCommitment.compute_lmp(::JuMP.Model,::UnitCommitment.ConventionalLMP)
+```
+
+### Approximated Extended LMPs
+
+```@docs
+UnitCommitment.AELMP
+UnitCommitment.compute_lmp(::JuMP.Model,::UnitCommitment.AELMP)
+```
+
+## Modify instance
+
+```@docs
+UnitCommitment.slice
+UnitCommitment.randomize!(::UnitCommitment.UnitCommitmentInstance)
+UnitCommitment.generate_initial_conditions!
+```
+
+## Formulations
+
+```@docs
+UnitCommitment.Formulation
+UnitCommitment.ShiftFactorsFormulation
+UnitCommitment.ArrCon2000
+UnitCommitment.CarArr2006
+UnitCommitment.DamKucRajAta2016
+UnitCommitment.Gar1962
+UnitCommitment.KnuOstWat2018
+UnitCommitment.MorLatRam2013
+UnitCommitment.PanGua2016
+UnitCommitment.WanHob2016
+```
+
+## Solution Methods
+
+```@docs
+UnitCommitment.XavQiuWanThi2019.Method
+```
+
+## Randomization Methods
+
+```@docs
+UnitCommitment.XavQiuAhm2021.Randomization
+```

docs/src/assets/custom.css

@@ -0,0 +1,36 @@
+@media screen and (min-width: 1056px) {
+    #documenter .docs-main {
+      max-width: 50rem !important;
+    }
+}
+  
+
+tbody, thead, pre {
+    border: 1px solid rgba(0, 0, 0, 0.25);
+}
+
+table td, th {
+    padding: 8px;
+}
+
+table p {
+    margin-bottom: 0;
+}
+
+table td code {
+    white-space: nowrap;
+}
+
+table tr,
+table th {
+    border-bottom: 1px solid rgba(0, 0, 0, 0.1);
+}
+
+table tr:last-child {
+    border-bottom: 0;
+}
+
+code {
+    background-color: transparent;
+    color: rgb(232, 62, 140);
+}

docs/src/guides/format.md

@@ -0,0 +1,380 @@
+# JSON data format
+
+An instance of the stochastic security-constrained unit commitment (SCUC) problem is composed multiple scenarios. Each scenario should be described in an individual JSON file containing the main section belows. For deterministic instances, a single scenario file, following the same format below, may also be provided. Fields that are allowed to differ among scenarios are marked as "uncertain". Fields that are allowed to be time-dependent are marked as "time series".
+
+- [Parameters](#Parameters)
+- [Buses](#Buses)
+- [Generators](#Generators)
+- [Storage units](#Storage-units)
+- [Price-sensitive loads](#Price-sensitive-loads)
+- [Transmission lines](#Transmission-lines)
+- [Reserves](#Reserves)
+- [Contingencies](#Contingencies)
+
+Each section is described in detail below. See [case118/2017-01-01.json.gz](https://axavier.org/UnitCommitment.jl/0.4/instances/matpower/case118/2017-01-01.json.gz) for a complete example.
+
+### Parameters
+
+This section describes system-wide parameters, such as power balance penalty, and optimization parameters, such as the length of the planning horizon and the time.
+
+| Key                                        | Description                                                                                                                                                                                                                          | Default  | Time series? | Uncertain? |
+| :----------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------: | :----------: | :--------: |
+| `Version`                                  | Version of UnitCommitment.jl this file was written for. Required to ensure that the file remains readable in future versions of the package. If you are following this page to construct the file, this field should equal `0.4`.    | Required |      No      |     No     |
+| `Time horizon (min)` or `Time horizon (h)` | Length of the planning horizon (in minutes or hours). Either `Time horizon (min)` or `Time horizon (h)` is required, but not both.                                                                                                   | Required |      No      |     No     |
+| `Time step (min)`                          | Length of each time step (in minutes). Must be a divisor of 60 (e.g. 60, 30, 20, 15, etc).                                                                                                                                           |   `60`   |      No      |     No     |
+| `Power balance penalty ($/MW)`             | Penalty for system-wide shortage or surplus in production (in $/MW). This is charged per time step. For example, if there is a shortage of 1 MW for three time steps, three times this amount will be charged.                       | `1000.0` |      No      |    Yes     |
+| `Scenario name`                            | Name of the scenario.                                                                                                                                                                                                                |  `"s1"`  |      No      |    ---     |
+| `Scenario weight`                          | Weight of the scenario. The scenario weight can be any positive real number, that is, it does not have to be between zero and one. The package normalizes the weights to ensure that the probability of all scenarios sum up to one. |   1.0    |      No      |    ---     |
+
+#### Example
+
+```json
+{
+  "Parameters": {
+    "Version": "0.4",
+    "Time horizon (h)": 4,
+    "Power balance penalty ($/MW)": 1000.0,
+    "Scenario name": "s1",
+    "Scenario weight": 0.5
+  }
+}
+```
+
+### Buses
+
+This section describes the characteristics of each bus in the system.
+
+| Key         | Description                              | Default  | Time series? | Uncertain? |
+| :---------- | :--------------------------------------- | -------- | :----------: | :--------: |
+| `Load (MW)` | Fixed load connected to the bus (in MW). | Required |     Yes      |    Yes     |
+
+#### Example
+
+```json
+{
+  "Buses": {
+    "b1": {
+      "Load (MW)": 0.0
+    },
+    "b2": {
+      "Load (MW)": [26.01527, 24.46212, 23.29725, 22.90897]
+    }
+  }
+}
+```
+
+### Generators
+
+This section describes all generators in the system. Two types of units can be specified:
+
+- **Thermal units:** Units that produce power by converting heat into electrical energy, such as coal and oil power plants. These units use a more complex model, with binary decision variables, and various constraints to enforce ramp rates and minimum up/down time.
+- **Profiled units:** Simplified model for units that do not require the constraints mentioned above, only a maximum and minimum power output for each time period. Typically used for renewables and hydro.
+
+#### Thermal Units
+
+| Key                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Default           | Time series? | Uncertain? |
+| :----------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | :----------: | :--------: |
+| `Bus`                                                        | Identifier of the bus where this generator is located (string).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Required          |      No      |    Yes     |
+| `Type`                                                       | Type of the generator (string). For thermal generators, this must be `Thermal`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Required          |      No      |     No     |
+| `Production cost curve (MW)` and `Production cost curve ($)` | Parameters describing the piecewise-linear production costs. See below for more details.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Required          |     Yes      |    Yes     |
+| `Startup costs ($)` and `Startup delays (h)`                 | Parameters describing how much it costs to start the generator after it has been shut down for a certain amount of time. If `Startup costs ($)` and `Startup delays (h)` are set to `[300.0, 400.0]` and `[1, 4]`, for example, and the generator is shut down at time `00:00` (h:min), then it costs \$300 to start up the generator at any time between `01:00` and `03:59`, and \$400 to start the generator at time `04:00` or any time after that. The number of startup cost points is unlimited, and may be different for each generator. Startup delays must be strictly increasing and the first entry must equal `Minimum downtime (h)`. | `[0.0]` and `[1]` |      No      |    Yes     |
+| `Minimum uptime (h)`                                         | Minimum amount of time the generator must stay operational after starting up (in hours). For example, if the generator starts up at time `00:00` (h:min) and `Minimum uptime (h)` is set to 4, then the generator can only shut down at time `04:00`.                                                                                                                                                                                                                                                                                                                                                                                              | `1`               |      No      |    Yes     |
+| `Minimum downtime (h)`                                       | Minimum amount of time the generator must stay offline after shutting down (in hours). For example, if the generator shuts down at time `00:00` (h:min) and `Minimum downtime (h)` is set to 4, then the generator can only start producing power again at time `04:00`.                                                                                                                                                                                                                                                                                                                                                                           | `1`               |      No      |    Yes     |
+| `Ramp up limit (MW)`                                         | Maximum increase in production from one time step to the next (in MW). For example, if the generator is producing 100 MW at time step 1 and if this parameter is set to 40 MW, then the generator will produce at most 140 MW at time step 2.                                                                                                                                                                                                                                                                                                                                                                                                      | `+inf`            |      No      |    Yes     |
+| `Ramp down limit (MW)`                                       | Maximum decrease in production from one time step to the next (in MW). For example, if the generator is producing 100 MW at time step 1 and this parameter is set to 40 MW, then the generator will produce at least 60 MW at time step 2.                                                                                                                                                                                                                                                                                                                                                                                                         | `+inf`            |      No      |    Yes     |
+| `Startup limit (MW)`                                         | Maximum amount of power a generator can produce immediately after starting up (in MW). For example, if `Startup limit (MW)` is set to 100 MW and the unit is off at time step 1, then it may produce at most 100 MW at time step 2.                                                                                                                                                                                                                                                                                                                                                                                                                | `+inf`            |      No      |    Yes     |
+| `Shutdown limit (MW)`                                        | Maximum amount of power a generator can produce immediately before shutting down (in MW). Specifically, the generator can only shut down at time step `t+1` if its production at time step `t` is below this limit.                                                                                                                                                                                                                                                                                                                                                                                                                                | `+inf`            |      No      |    Yes     |
+| `Initial status (h)`                                         | If set to a positive number, indicates the amount of time (in hours) the generator has been on at the beginning of the simulation, and if set to a negative number, the amount of time the generator has been off. For example, if `Initial status (h)` is `-2`, this means that the generator was off since `-02:00` (h:min). The simulation starts at time `00:00`. If `Initial status (h)` is `3`, this means that the generator was on since `-03:00`. A value of zero is not acceptable.                                                                                                                                                      | Required          |      No      |     No     |
+| `Initial power (MW)`                                         | Amount of power the generator at time step `-1`, immediately before the planning horizon starts.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Required          |      No      |     No     |
+| `Must run?`                                                  | If `true`, the generator should be committed, even if that is not economical (Boolean).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | `false`           |     Yes      |    Yes     |
+| `Reserve eligibility`                                        | List of reserve products this generator is eligibe to provide. By default, the generator is not eligible to provide any reserves.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | `[]`              |      No      |    Yes     |
+| `Commitment status`                                          | List of commitment status over the time horizon. At time `t`, if `true`, the generator must be commited at that time period; if `false`, the generator must not be commited at that time period. If `null` at time `t`, the generator's commitment status is then decided by the model. By default, the status is a list of `null` values.                                                                                                                                                                                                                                                                                                         | `null`            |     Yes      |    Yes     |
+
+#### Profiled Units
+
+| Key                  | Description                                                                       | Default  | Time series? | Uncertain? |
+| :------------------- | :-------------------------------------------------------------------------------- | :------: | :----------: | :--------: |
+| `Bus`                | Identifier of the bus where this generator is located (string).                   | Required |      No      |    Yes     |
+| `Type`               | Type of the generator (string). For profiled generators, this must be `Profiled`. | Required |      No      |     No     |
+| `Cost ($/MW)`        | Cost incurred for serving each MW of power by this generator.                     | Required |     Yes      |    Yes     |
+| `Minimum power (MW)` | Minimum amount of power this generator may supply.                                |  `0.0`   |     Yes      |    Yes     |
+| `Maximum power (MW)` | Maximum amount of power this generator may supply.                                | Required |     Yes      |    Yes     |
+
+#### Production costs and limits
+
+Production costs are represented as piecewise-linear curves. Figure 1 shows an example cost curve with three segments, where it costs \$1400, \$1600, \$2200 and \$2400 to generate, respectively, 100, 110, 130 and 135 MW of power. To model this generator, `Production cost curve (MW)` should be set to `[100, 110, 130, 135]`, and `Production cost curve ($)` should be set to `[1400, 1600, 2200, 2400]`.
+Note that this curve also specifies the production limits. Specifically, the first point identifies the minimum power output when the unit is operational, while the last point identifies the maximum power output.
+
+```@raw html
+<center>
+    <img src="../../assets/cost_curve.png" style="max-width: 500px"/>
+    <div><b>Figure 1.</b> Piecewise-linear production cost curve.</div>
+    <br/>
+</center>
+```
+
+#### Additional remarks:
+
+- For time-dependent production limits or time-dependent production costs, the usage of nested arrays is allowed. For example, if `Production cost curve (MW)` is set to `[5.0, [10.0, 12.0, 15.0, 20.0]]`, then the unit may generate at most 10, 12, 15 and 20 MW of power during time steps 1, 2, 3 and 4, respectively. The minimum output for all time periods is fixed to at 5 MW.
+- There is no limit to the number of piecewise-linear segments, and different generators may have a different number of segments.
+- If `Production cost curve (MW)` and `Production cost curve ($)` both contain a single element, then the generator must produce exactly that amount of power when operational. To specify that the generator may produce any amount of power up to a certain limit `P`, the parameter `Production cost curve (MW)` should be set to `[0, P]`.
+- Production cost curves must be convex.
+
+#### Example
+
+```json
+{
+  "Generators": {
+    "gen1": {
+      "Bus": "b1",
+      "Type": "Thermal",
+      "Production cost curve (MW)": [100.0, 110.0, 130.0, 135.0],
+      "Production cost curve ($)": [1400.0, 1600.0, 2200.0, 2400.0],
+      "Startup costs ($)": [300.0, 400.0],
+      "Startup delays (h)": [1, 4],
+      "Ramp up limit (MW)": 232.68,
+      "Ramp down limit (MW)": 232.68,
+      "Startup limit (MW)": 232.68,
+      "Shutdown limit (MW)": 232.68,
+      "Minimum downtime (h)": 4,
+      "Minimum uptime (h)": 4,
+      "Initial status (h)": 12,
+      "Initial power (MW)": 115,
+      "Must run?": false,
+      "Reserve eligibility": ["r1"]
+    },
+    "gen2": {
+      "Bus": "b5",
+      "Type": "Thermal",
+      "Production cost curve (MW)": [0.0, [10.0, 8.0, 0.0, 3.0]],
+      "Production cost curve ($)": [0.0, 0.0],
+      "Initial status (h)": -100,
+      "Initial power (MW)": 0,
+      "Reserve eligibility": ["r1", "r2"],
+      "Commitment status": [true, false, null, true]
+    },
+    "gen3": {
+      "Bus": "b6",
+      "Type": "Profiled",
+      "Minimum power (MW)": 10.0,
+      "Maximum power (MW)": 120.0,
+      "Cost ($/MW)": 100.0
+    }
+  }
+}
+```
+
+### Storage units
+
+This section describes energy storage units in the system which charge and discharge power. The storage units consume power while charging, and generate power while discharging.
+
+| Key                                           | Description                                                                                                                                                 |        Default        | Time series? | Uncertain? |
+| :-------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------: | :----------: | :--------: |
+| `Bus`                                         | Bus where the storage unit is located. Multiple storage units may be placed at the same bus.                                                                |       Required        |      No      |    Yes     |
+| `Minimum level (MWh)`                         | Minimum of energy level this storage unit may contain.                                                                                                      |         `0.0`         |     Yes      |    Yes     |
+| `Maximum level (MWh)`                         | Maximum of energy level this storage unit may contain.                                                                                                      |       Required        |     Yes      |    Yes     |
+| `Allow simultaneous charging and discharging` | If `false`, the storage unit is not allowed to charge and discharge at the same time (Boolean).                                                             |        `true`         |     Yes      |    Yes     |
+| `Charge cost ($/MW)`                          | Cost incurred for charging each MW of power into this storage unit.                                                                                         |       Required        |     Yes      |    Yes     |
+| `Discharge cost ($/MW)`                       | Cost incurred for discharging each MW of power from this storage unit.                                                                                      |       Required        |     Yes      |    Yes     |
+| `Charge efficiency`                           | Efficiency rate to charge power into this storage unit. This value must be greater than or equal to `0.0`, and less than or equal to `1.0`.                 |         `1.0`         |     Yes      |    Yes     |
+| `Discharge efficiency`                        | Efficiency rate to discharge power from this storage unit. This value must be greater than or equal to `0.0`, and less than or equal to `1.0`.              |         `1.0`         |     Yes      |    Yes     |
+| `Loss factor`                                 | The energy dissipation rate of this storage unit. This value must be greater than or equal to `0.0`, and less than or equal to `1.0`.                       |         `0.0`         |     Yes      |    Yes     |
+| `Minimum charge rate (MW)`                    | Minimum amount of power rate this storage unit may charge.                                                                                                  |         `0.0`         |     Yes      |    Yes     |
+| `Maximum charge rate (MW)`                    | Maximum amount of power rate this storage unit may charge.                                                                                                  |       Required        |     Yes      |    Yes     |
+| `Minimum discharge rate (MW)`                 | Minimum amount of power rate this storage unit may discharge.                                                                                               |         `0.0`         |     Yes      |    Yes     |
+| `Maximum discharge rate (MW)`                 | Maximum amount of power rate this storage unit may discharge.                                                                                               |       Required        |     Yes      |    Yes     |
+| `Initial level (MWh)`                         | Amount of energy this storage unit at time step `-1`, immediately before the planning horizon starts.                                                       |         `0.0`         |      No      |    Yes     |
+| `Last period minimum level (MWh)`             | Minimum of energy level this storage unit may contain in the last time step. By default, this value is the same as the last value of `Minimum level (MWh)`. | `Minimum level (MWh)` |      No      |    Yes     |
+| `Last period maximum level (MWh)`             | Maximum of energy level this storage unit may contain in the last time step. By default, this value is the same as the last value of `Maximum level (MWh)`. | `Maximum level (MWh)` |      No      |    Yes     |
+
+#### Example
+
+```json
+{
+  "Storage units": {
+    "su1": {
+      "Bus": "b2",
+      "Maximum level (MWh)": 100.0,
+      "Charge cost ($/MW)": 2.0,
+      "Discharge cost ($/MW)": 2.5,
+      "Maximum charge rate (MW)": 10.0,
+      "Maximum discharge rate (MW)": 8.0
+    },
+    "su2": {
+      "Bus": "b2",
+      "Minimum level (MWh)": 10.0,
+      "Maximum level (MWh)": 100.0,
+      "Allow simultaneous charging and discharging": false,
+      "Charge cost ($/MW)": 3.0,
+      "Discharge cost ($/MW)": 3.5,
+      "Charge efficiency": 0.8,
+      "Discharge efficiency": 0.85,
+      "Loss factor": 0.01,
+      "Minimum charge rate (MW)": 5.0,
+      "Maximum charge rate (MW)": 10.0,
+      "Minimum discharge rate (MW)": 2.0,
+      "Maximum discharge rate (MW)": 10.0,
+      "Initial level (MWh)": 70.0,
+      "Last period minimum level (MWh)": 80.0,
+      "Last period maximum level (MWh)": 85.0
+    },
+    "su3": {
+      "Bus": "b9",
+      "Minimum level (MWh)": [10.0, 11.0, 12.0, 13.0],
+      "Maximum level (MWh)": [100.0, 110.0, 120.0, 130.0],
+      "Allow simultaneous charging and discharging": [false, false, true, true],
+      "Charge cost ($/MW)": [2.0, 2.1, 2.2, 2.3],
+      "Discharge cost ($/MW)": [1.0, 1.1, 1.2, 1.3],
+      "Charge efficiency": [0.8, 0.81, 0.82, 0.82],
+      "Discharge efficiency": [0.85, 0.86, 0.87, 0.88],
+      "Loss factor": [0.01, 0.01, 0.02, 0.02],
+      "Minimum charge rate (MW)": [5.0, 5.1, 5.2, 5.3],
+      "Maximum charge rate (MW)": [10.0, 10.1, 10.2, 10.3],
+      "Minimum discharge rate (MW)": [4.0, 4.1, 4.2, 4.3],
+      "Maximum discharge rate (MW)": [8.0, 8.1, 8.2, 8.3],
+      "Initial level (MWh)": 20.0,
+      "Last period minimum level (MWh)": 21.0,
+      "Last period maximum level (MWh)": 22.0
+    }
+  }
+}
+```
+
+### Price-sensitive loads
+
+This section describes components in the system which may increase or reduce their energy consumption according to the energy prices. Fixed loads (as described in the `buses` section) are always served, regardless of the price, unless there is significant congestion in the system or insufficient production capacity. Price-sensitive loads, on the other hand, are only served if it is economical to do so.
+
+| Key              | Description                                                                                  | Default  | Time series? | Uncertain? |
+| :--------------- | :------------------------------------------------------------------------------------------- | :------: | :----------: | :--------: |
+| `Bus`            | Bus where the load is located. Multiple price-sensitive loads may be placed at the same bus. | Required |      No      |    Yes     |
+| `Revenue ($/MW)` | Revenue obtained for serving each MW of power to this load.                                  | Required |     Yes      |    Yes     |
+| `Demand (MW)`    | Maximum amount of power required by this load. Any amount lower than this may be served.     | Required |     Yes      |    Yes     |
+
+#### Example
+
+```json
+{
+  "Price-sensitive loads": {
+    "p1": {
+      "Bus": "b3",
+      "Revenue ($/MW)": 23.0,
+      "Demand (MW)": 50.0
+    }
+  }
+}
+```
+
+### Transmission lines
+
+This section describes the characteristics of transmission system, such as its topology and the susceptance of each transmission line.
+
+| Key                         | Description                                                                                                                                                                                                                       | Default  | Time series? | Uncertain? |
+| :-------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | :----------: | :--------: |
+| `Source bus`                | Identifier of the bus where the transmission line originates.                                                                                                                                                                     | Required |      No      |    Yes     |
+| `Target bus`                | Identifier of the bus where the transmission line reaches.                                                                                                                                                                        | Required |      No      |    Yes     |
+| `Susceptance (S)`           | Susceptance of the transmission line (in siemens).                                                                                                                                                                                | Required |      No      |    Yes     |
+| `Normal flow limit (MW)`    | Maximum amount of power (in MW) allowed to flow through the line when the system is in its regular, fully-operational state.                                                                                                      | `+inf`   |     Yes      |    Yes     |
+| `Emergency flow limit (MW)` | Maximum amount of power (in MW) allowed to flow through the line when the system is in degraded state (for example, after the failure of another transmission line).                                                              | `+inf`   |      Y       |    Yes     |
+| `Flow limit penalty ($/MW)` | Penalty for violating the flow limits of the transmission line (in $/MW). This is charged per time step. For example, if there is a thermal violation of 1 MW for three time steps, then three times this amount will be charged. | `5000.0` |     Yes      |    Yes     |
+
+#### Example
+
+```json
+{
+  "Transmission lines": {
+    "l1": {
+      "Source bus": "b1",
+      "Target bus": "b2",
+      "Susceptance (S)": 29.49686,
+      "Normal flow limit (MW)": 15000.0,
+      "Emergency flow limit (MW)": 20000.0,
+      "Flow limit penalty ($/MW)": 5000.0
+    }
+  }
+}
+```
+
+### Reserves
+
+This section describes the hourly amount of reserves required.
+
+| Key                        | Description                                                                                                                                                             | Default  | Time series? | Uncertain? |
+| :------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | :----------: | :--------: |
+| `Type`                     | Type of reserve product. Must be either "spinning" or "flexiramp".                                                                                                      | Required |      No      |     No     |
+| `Amount (MW)`              | Amount of reserves required.                                                                                                                                            | Required |     Yes      |    Yes     |
+| `Shortfall penalty ($/MW)` | Penalty for shortage in meeting the reserve requirements (in $/MW). This is charged per time step. Negative value implies reserve constraints must always be satisfied. | `-1`     |     Yes      |    Yes     |
+
+#### Example 1
+
+```json
+{
+  "Reserves": {
+    "r1": {
+      "Type": "spinning",
+      "Amount (MW)": [57.30552, 53.88429, 51.31838, 50.46307],
+      "Shortfall penalty ($/MW)": 5.0
+    },
+    "r2": {
+      "Type": "flexiramp",
+      "Amount (MW)": [20.31042, 23.65273, 27.41784, 25.34057]
+    }
+  }
+}
+```
+
+### Contingencies
+
+This section describes credible contingency scenarios in the optimization, such as the loss of a transmission line or generator.
+
+| Key                   | Description                                                                                       | Default | Uncertain? |
+| :-------------------- | :------------------------------------------------------------------------------------------------ | :-----: | :--------: |
+| `Affected generators` | List of generators affected by this contingency. May be omitted if no generators are affected.    |  `[]`   |    Yes     |
+| `Affected lines`      | List of transmission lines affected by this contingency. May be omitted if no lines are affected. |  `[]`   |    Yes     |
+
+#### Example
+
+```json
+{
+  "Contingencies": {
+    "c1": {
+      "Affected lines": ["l1", "l2", "l3"],
+      "Affected generators": ["g1"]
+    },
+    "c2": {
+      "Affected lines": ["l4"]
+    }
+  }
+}
+```
+
+### Additional remarks
+
+#### Time series parameters
+
+Many numerical properties in the JSON file can be specified either as a single floating point number if they are time-independent, or as an array containing exactly `T` elements, if they are time-dependent, where `T` is the number of time steps in the planning horizon. For example, both formats below are valid when `T=3`:
+
+```json
+{
+  "Load (MW)": 800.0,
+  "Load (MW)": [800.0, 850.0, 730.0]
+}
+```
+
+The value `T` depends on both `Time horizon (h)` and `Time step (min)`, as the table below illustrates.
+
+| Time horizon (h) | Time step (min) |  T  |
+| :--------------: | :-------------: | :-: |
+|        24        |       60        | 24  |
+|        24        |       15        | 96  |
+|        24        |        5        | 288 |
+|        36        |       60        | 36  |
+|        36        |       15        | 144 |
+|        36        |        5        | 432 |
+
+## Current limitations
+
+- Network topology must remain the same for all time periods.
+- Only N-1 transmission contingencies are supported. Generator contingencies are not currently supported.
+- Time-varying minimum production amounts are not currently compatible with ramp/startup/shutdown limits.
+- Flexible ramping products can only be acquired under the `WanHob2016` formulation, which does not support spinning reserves.
+- The set of generators must be the same in all scenarios.

docs/src/guides/instances.md

@@ -0,0 +1,289 @@
+# Benchmark instances
+
+UnitCommitment.jl provides a large collection of benchmark instances collected from the literature and converted to a [common data format](../guides/format.md). In some cases, as indicated below, the original instances have been extended, with realistic parameters, using data-driven methods. If you use these instances in your research, we request that you cite UnitCommitment.jl, as well as the original sources, as listed below. Benchmark instances can be loaded with `UnitCommitment.read_benchmark(name)`, as explained in the [tutorials](../tutorials/usage.md). Instance files can also be [directly downloaded from our website](https://axavier.org/UnitCommitment.jl/0.4/instances/).
+
+!!! warning
+
+    The instances included in UC.jl are still under development and may change in the future. If you use these instances in your research, for reproducibility, you should specify what version of UC.jl they came from.
+
+## MATPOWER
+
+[MATPOWER](https://github.com/MATPOWER/matpower) is an open-source package for solving power flow problems in MATLAB and Octave. It contains a number of power flow test cases, which have been widely used in the power systems literature.
+
+Because most MATPOWER test cases were originally designed for power flow studies, they lack a number of important unit commitment parameters, such as time-varying loads, production cost curves, ramp limits, reserves and initial conditions. The test cases included in UnitCommitment.jl are extended versions of the original MATPOWER test cases, modified as following:
+
+- **Production cost** curves were generated using a data-driven approach, based on publicly available data. More specifically, machine learning models were trained to predict typical production cost curves, for each day of the year, based on a generator's maximum and minimum power output.
+
+- **Load profiles** were generated using a similar data-driven approach.
+
+- **Ramp-up, ramp-down, startup and shutdown rates** were set to a fixed proportion of the generator's maximum output.
+
+- **Minimum reserves** were set to a fixed proportion of the total demand.
+
+- **Contingencies** were set to include all N-1 transmission line contingencies that do not generate islands or isolated buses. More specifically, there is one contingency for each transmission line, as long as that transmission line is not a bridge in the network graph.
+
+For each MATPOWER test case, UC.jl provides 365 variations (`2017-01-01` to `2017-12-31`) corresponding different days of the year.
+
+### MATPOWER/UW-PSTCA
+
+A variety of smaller IEEE test cases, [compiled by University of Washington](http://labs.ece.uw.edu/pstca/), corresponding mostly to small portions of the American Electric Power System in the 1960s.
+
+| Name                          | Buses | Generators | Lines | Contingencies | References     |
+| ----------------------------- | ----- | ---------- | ----- | ------------- | -------------- |
+| `matpower/case14/2017-01-01`  | 14    | 5          | 20    | 19            | [MTPWR, PSTCA] |
+| `matpower/case30/2017-01-01`  | 30    | 6          | 41    | 38            | [MTPWR, PSTCA] |
+| `matpower/case57/2017-01-01`  | 57    | 7          | 80    | 79            | [MTPWR, PSTCA] |
+| `matpower/case118/2017-01-01` | 118   | 54         | 186   | 177           | [MTPWR, PSTCA] |
+| `matpower/case300/2017-01-01` | 300   | 69         | 411   | 320           | [MTPWR, PSTCA] |
+
+### MATPOWER/Polish
+
+Test cases based on the Polish 400, 220 and 110 kV networks, originally provided by **Roman Korab** (Politechnika Śląska) and corrected by the MATPOWER team.
+
+| Name                              | Buses | Generators | Lines | Contingencies | References |
+| --------------------------------- | ----- | ---------- | ----- | ------------- | ---------- |
+| `matpower/case2383wp/2017-01-01`  | 2383  | 323        | 2896  | 2240          | [MTPWR]    |
+| `matpower/case2736sp/2017-01-01`  | 2736  | 289        | 3504  | 3159          | [MTPWR]    |
+| `matpower/case2737sop/2017-01-01` | 2737  | 267        | 3506  | 3161          | [MTPWR]    |
+| `matpower/case2746wop/2017-01-01` | 2746  | 443        | 3514  | 3155          | [MTPWR]    |
+| `matpower/case2746wp/2017-01-01`  | 2746  | 457        | 3514  | 3156          | [MTPWR]    |
+| `matpower/case3012wp/2017-01-01`  | 3012  | 496        | 3572  | 2854          | [MTPWR]    |
+| `matpower/case3120sp/2017-01-01`  | 3120  | 483        | 3693  | 2950          | [MTPWR]    |
+| `matpower/case3375wp/2017-01-01`  | 3374  | 590        | 4161  | 3245          | [MTPWR]    |
+
+### MATPOWER/PEGASE
+
+Test cases from the [Pan European Grid Advanced Simulation and State Estimation (PEGASE) project](https://cordis.europa.eu/project/id/211407), describing part of the European high voltage transmission network.
+
+| Name                                  | Buses | Generators | Lines | Contingencies | References                  |
+| ------------------------------------- | ----- | ---------- | ----- | ------------- | --------------------------- |
+| `matpower/case89pegase/2017-01-01`    | 89    | 12         | 210   | 192           | [JoFlMa16, FlPaCa13, MTPWR] |
+| `matpower/case1354pegase/2017-01-01`  | 1354  | 260        | 1991  | 1288          | [JoFlMa16, FlPaCa13, MTPWR] |
+| `matpower/case2869pegase/2017-01-01`  | 2869  | 510        | 4582  | 3579          | [JoFlMa16, FlPaCa13, MTPWR] |
+| `matpower/case9241pegase/2017-01-01`  | 9241  | 1445       | 16049 | 13932         | [JoFlMa16, FlPaCa13, MTPWR] |
+| `matpower/case13659pegase/2017-01-01` | 13659 | 4092       | 20467 | 13932         | [JoFlMa16, FlPaCa13, MTPWR] |
+
+### MATPOWER/RTE
+
+Test cases from the R&D Division at [Reseau de Transport d'Electricite](https://www.rte-france.com) representing the size and complexity of the French very high voltage transmission network.
+
+| Name                              | Buses | Generators | Lines | Contingencies | References        |
+| --------------------------------- | ----- | ---------- | ----- | ------------- | ----------------- |
+| `matpower/case1888rte/2017-01-01` | 1888  | 296        | 2531  | 1484          | [MTPWR, JoFlMa16] |
+| `matpower/case1951rte/2017-01-01` | 1951  | 390        | 2596  | 1497          | [MTPWR, JoFlMa16] |
+| `matpower/case2848rte/2017-01-01` | 2848  | 544        | 3776  | 2242          | [MTPWR, JoFlMa16] |
+| `matpower/case2868rte/2017-01-01` | 2868  | 596        | 3808  | 2260          | [MTPWR, JoFlMa16] |
+| `matpower/case6468rte/2017-01-01` | 6468  | 1262       | 9000  | 6094          | [MTPWR, JoFlMa16] |
+| `matpower/case6470rte/2017-01-01` | 6470  | 1306       | 9005  | 6085          | [MTPWR, JoFlMa16] |
+| `matpower/case6495rte/2017-01-01` | 6495  | 1352       | 9019  | 6060          | [MTPWR, JoFlMa16] |
+| `matpower/case6515rte/2017-01-01` | 6515  | 1368       | 9037  | 6063          | [MTPWR, JoFlMa16] |
+
+## PGLIB-UC Instances
+
+[PGLIB-UC](https://github.com/power-grid-lib/pglib-uc) is a benchmark library curated and maintained by the [IEEE PES Task Force on Benchmarks for Validation of Emerging Power System Algorithms](https://power-grid-lib.github.io/). These test cases have been used in [KnOsWa20].
+
+### PGLIB-UC/California
+
+Test cases based on publicly available data from the California ISO. For more details, see [PGLIB-UC case file overview](https://github.com/power-grid-lib/pglib-uc).
+
+| Name                                 | Buses | Generators | Lines | Contingencies | References |
+| ------------------------------------ | ----- | ---------- | ----- | ------------- | ---------- |
+| `pglib-uc/ca/2014-09-01_reserves_0`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2014-09-01_reserves_1`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2014-09-01_reserves_3`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2014-09-01_reserves_5`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2014-12-01_reserves_0`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2014-12-01_reserves_1`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2014-12-01_reserves_3`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2014-12-01_reserves_5`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2015-03-01_reserves_0`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2015-03-01_reserves_1`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2015-03-01_reserves_3`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2015-03-01_reserves_5`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2015-06-01_reserves_0`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2015-06-01_reserves_1`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2015-06-01_reserves_3`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/2015-06-01_reserves_5`  | 1     | 610        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/Scenario400_reserves_0` | 1     | 611        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/Scenario400_reserves_1` | 1     | 611        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/Scenario400_reserves_3` | 1     | 611        | 0     | 0             | [KnOsWa20] |
+| `pglib-uc/ca/Scenario400_reserves_5` | 1     | 611        | 0     | 0             | [KnOsWa20] |
+
+### PGLIB-UC/FERC
+
+Test cases based on a publicly available [unit commitment test case produced by the Federal Energy Regulatory Commission](https://www.ferc.gov/industries-data/electric/power-sales-and-markets/increasing-efficiency-through-improved-software-1). For more details, see [PGLIB-UC case file overview](https://github.com/power-grid-lib/pglib-uc).
+
+| Name                          | Buses | Generators | Lines | Contingencies | References           |
+| ----------------------------- | ----- | ---------- | ----- | ------------- | -------------------- |
+| `pglib-uc/ferc/2015-01-01_hw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-01-01_lw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-02-01_hw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-02-01_lw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-03-01_hw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-03-01_lw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-04-01_hw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-04-01_lw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-05-01_hw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-05-01_lw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-06-01_hw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-06-01_lw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-07-01_hw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-07-01_lw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-08-01_hw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-08-01_lw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-09-01_hw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-09-01_lw` | 1     | 979        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-10-01_hw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-10-01_lw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-11-02_hw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-11-02_lw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-12-01_hw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+| `pglib-uc/ferc/2015-12-01_lw` | 1     | 935        | 0     | 0             | [KnOsWa20, KrHiOn12] |
+
+### PGLIB-UC/RTS-GMLC
+
+[RTS-GMLC](https://github.com/GridMod/RTS-GMLC) is an updated version of the RTS-96 test system produced by the United States Department of Energy's [Grid Modernization Laboratory Consortium](https://gmlc.doe.gov/). The PGLIB-UC/RTS-GMLC instances are modified versions of the original RTS-GMLC instances, with modified ramp-rates and without a transmission network. For more details, see [PGLIB-UC case file overview](https://github.com/power-grid-lib/pglib-uc).
+
+| Name                           | Buses | Generators | Lines | Contingencies | References |
+| ------------------------------ | ----- | ---------- | ----- | ------------- | ---------- |
+| `pglib-uc/rts_gmlc/2020-01-27` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+| `pglib-uc/rts_gmlc/2020-02-09` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+| `pglib-uc/rts_gmlc/2020-03-05` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+| `pglib-uc/rts_gmlc/2020-04-03` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+| `pglib-uc/rts_gmlc/2020-05-05` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+| `pglib-uc/rts_gmlc/2020-06-09` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+| `pglib-uc/rts_gmlc/2020-07-06` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+| `pglib-uc/rts_gmlc/2020-08-12` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+| `pglib-uc/rts_gmlc/2020-09-20` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+| `pglib-uc/rts_gmlc/2020-10-27` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+| `pglib-uc/rts_gmlc/2020-11-25` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+| `pglib-uc/rts_gmlc/2020-12-23` | 1     | 154        | 0     | 0             | [BaBlEh19] |
+
+## OR-LIB/UC
+
+[OR-LIB](http://people.brunel.ac.uk/~mastjjb/jeb/info.html) is a collection of test data sets for a variety of operations research problems, including unit commitment. The UC instances in OR-LIB are synthetic instances generated by a [random problem generator](http://groups.di.unipi.it/optimize/Data/UC.html) developed by the [Operations Research Group at University of Pisa](http://groups.di.unipi.it/optimize/). These test cases have been used in [FrGe06] and many other publications.
+
+| Name                | Hours | Buses | Generators | Lines | Contingencies | References      |
+| ------------------- | ----- | ----- | ---------- | ----- | ------------- | --------------- |
+| `or-lib/10_0_1_w`   | 24    | 1     | 10         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/10_0_2_w`   | 24    | 1     | 10         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/10_0_3_w`   | 24    | 1     | 10         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/10_0_4_w`   | 24    | 1     | 10         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/10_0_5_w`   | 24    | 1     | 10         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/20_0_1_w`   | 24    | 1     | 20         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/20_0_2_w`   | 24    | 1     | 20         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/20_0_3_w`   | 24    | 1     | 20         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/20_0_4_w`   | 24    | 1     | 20         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/20_0_5_w`   | 24    | 1     | 20         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/50_0_1_w`   | 24    | 1     | 50         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/50_0_2_w`   | 24    | 1     | 50         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/50_0_3_w`   | 24    | 1     | 50         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/50_0_4_w`   | 24    | 1     | 50         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/50_0_5_w`   | 24    | 1     | 50         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/75_0_1_w`   | 24    | 1     | 75         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/75_0_2_w`   | 24    | 1     | 75         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/75_0_3_w`   | 24    | 1     | 75         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/75_0_4_w`   | 24    | 1     | 75         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/75_0_5_w`   | 24    | 1     | 75         | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/100_0_1_w`  | 24    | 1     | 100        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/100_0_2_w`  | 24    | 1     | 100        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/100_0_3_w`  | 24    | 1     | 100        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/100_0_4_w`  | 24    | 1     | 100        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/100_0_5_w`  | 24    | 1     | 100        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/150_0_1_w`  | 24    | 1     | 150        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/150_0_2_w`  | 24    | 1     | 150        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/150_0_3_w`  | 24    | 1     | 150        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/150_0_4_w`  | 24    | 1     | 150        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/150_0_5_w`  | 24    | 1     | 150        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_10_w` | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_11_w` | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_12_w` | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_1_w`  | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_2_w`  | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_3_w`  | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_4_w`  | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_5_w`  | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_6_w`  | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_7_w`  | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_8_w`  | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+| `or-lib/200_0_9_w`  | 24    | 1     | 200        | 0     | 0             | [ORLIB, FrGe06] |
+
+## Tejada19
+
+Test cases used in [TeLuSa19]. These instances are similar to OR-LIB/UC, in the sense that they use the same random problem generator, but are much larger.
+
+| Name                    | Hours | Buses | Generators | Lines | Contingencies | References |
+| ----------------------- | ----- | ----- | ---------- | ----- | ------------- | ---------- |
+| `tejada19/UC_24h_214g`  | 24    | 1     | 214        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_250g`  | 24    | 1     | 250        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_290g`  | 24    | 1     | 290        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_480g`  | 24    | 1     | 480        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_505g`  | 24    | 1     | 505        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_623g`  | 24    | 1     | 623        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_647g`  | 24    | 1     | 647        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_836g`  | 24    | 1     | 836        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_850g`  | 24    | 1     | 850        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_918g`  | 24    | 1     | 918        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_931g`  | 24    | 1     | 931        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_940g`  | 24    | 1     | 940        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_957g`  | 24    | 1     | 957        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_959g`  | 24    | 1     | 959        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1069g` | 24    | 1     | 1069       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1130g` | 24    | 1     | 1130       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1376g` | 24    | 1     | 1376       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1393g` | 24    | 1     | 1393       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1577g` | 24    | 1     | 1577       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1615g` | 24    | 1     | 1615       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1632g` | 24    | 1     | 1632       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1768g` | 24    | 1     | 1768       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1804g` | 24    | 1     | 1804       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1820g` | 24    | 1     | 1820       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1823g` | 24    | 1     | 1823       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_24h_1888g` | 24    | 1     | 1888       | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_36g`  | 168   | 1     | 36         | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_38g`  | 168   | 1     | 38         | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_40g`  | 168   | 1     | 40         | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_53g`  | 168   | 1     | 53         | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_58g`  | 168   | 1     | 58         | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_59g`  | 168   | 1     | 59         | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_72g`  | 168   | 1     | 72         | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_84g`  | 168   | 1     | 84         | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_86g`  | 168   | 1     | 86         | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_88g`  | 168   | 1     | 88         | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_93g`  | 168   | 1     | 93         | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_105g` | 168   | 1     | 105        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_110g` | 168   | 1     | 110        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_125g` | 168   | 1     | 125        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_130g` | 168   | 1     | 130        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_131g` | 168   | 1     | 131        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_140g` | 168   | 1     | 140        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_165g` | 168   | 1     | 165        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_175g` | 168   | 1     | 175        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_179g` | 168   | 1     | 179        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_188g` | 168   | 1     | 188        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_192g` | 168   | 1     | 192        | 0     | 0             | [TeLuSa19] |
+| `tejada19/UC_168h_199g` | 168   | 1     | 199        | 0     | 0             | [TeLuSa19] |
+
+## References
+
+- [UCJL] **Alinson S. Xavier, Aleksandr M. Kazachkov, Ogün Yurdakul, Feng Qiu.** "UnitCommitment.jl: A Julia/JuMP Optimization Package for Security-Constrained Unit Commitment (Version 0.3)". Zenodo (2022). [DOI: 10.5281/zenodo.4269874](https://doi.org/10.5281/zenodo.4269874)
+
+- [KnOsWa20] **Bernard Knueven, James Ostrowski and Jean-Paul Watson.** "On Mixed-Integer Programming Formulations for the Unit Commitment Problem". INFORMS Journal on Computing (2020). [DOI: 10.1287/ijoc.2019.0944](https://doi.org/10.1287/ijoc.2019.0944)
+
+- [KrHiOn12] **Eric Krall, Michael Higgins and Richard P. O’Neill.** "RTO unit commitment test system." Federal Energy Regulatory Commission. Available at: <https://www.ferc.gov/industries-data/electric/power-sales-and-markets/increasing-efficiency-through-improved-software-1> (Accessed: Nov 14, 2020)
+
+- [BaBlEh19] **Clayton Barrows, Aaron Bloom, Ali Ehlen, Jussi Ikaheimo, Jennie Jorgenson, Dheepak Krishnamurthy, Jessica Lau et al.** "The IEEE Reliability Test System: A Proposed 2019 Update." IEEE Transactions on Power Systems (2019). [DOI: 10.1109/TPWRS.2019.2925557](https://doi.org/10.1109/TPWRS.2019.2925557)
+
+- [JoFlMa16] **C. Josz, S. Fliscounakis, J. Maeght, and P. Panciatici.** "AC Power Flow Data in MATPOWER and QCQP Format: iTesla, RTE Snapshots, and PEGASE". [ArXiv (2016)](https://arxiv.org/abs/1603.01533).
+
+- [FlPaCa13] **S. Fliscounakis, P. Panciatici, F. Capitanescu, and L. Wehenkel.** "Contingency ranking with respect to overloads in very large power systems taking into account uncertainty, preventive and corrective actions", Power Systems, IEEE Trans. on, (28)4:4909-4917, 2013. [DOI: 10.1109/TPWRS.2013.2251015](https://doi.org/10.1109/TPWRS.2013.2251015)
+
+- [MTPWR] **D. Zimmerman, C. E. Murillo-Sandnchez and R. J. Thomas.** "Matpower: Steady-state operations, planning, and analysis tools forpower systems research and education", IEEE Transactions on PowerSystems, vol. 26, no. 1, pp. 12 –19, Feb. 2011. [DOI: 10.1109/TPWRS.2010.2051168](https://doi.org/10.1109/TPWRS.2010.2051168)
+
+- [PSTCA] **University of Washington, Dept. of Electrical Engineering.** "Power Systems Test Case Archive". Available at: <http://www.ee.washington.edu/research/pstca/> (Accessed: Nov 14, 2020)
+
+- [ORLIB] **J.E.Beasley.** "OR-Library: distributing test problems by electronic mail", Journal of the Operational Research Society 41(11) (1990). [DOI: 10.2307/2582903](https://doi.org/10.2307/2582903)
+
+- [FrGe06] **A. Frangioni, C. Gentile.** "Solving nonlinear single-unit commitment problems with ramping constraints" Operations Research 54(4), p. 767 - 775, 2006. [DOI: 10.1287/opre.1060.0309](https://doi.org/10.1287/opre.1060.0309)
+
+- [TeLuSa19] **D. A. Tejada-Arango, S. Lumbreras, P. Sanchez-Martin and A. Ramos.** "Which Unit-Commitment Formulation is Best? A Systematic Comparison," in IEEE Transactions on Power Systems. [DOI: 10.1109/TPWRS.2019.2962024](https://ieeexplore.ieee.org/document/8941313/).

docs/src/guides/model.md

@@ -0,0 +1,78 @@
+JuMP Model
+==========
+
+In this page, we describe the JuMP optimization model produced by the function `build_model`. A detailed understanding of this model is not necessary if you are just interested in using the package to solve some standard unit commitment cases, but it may be useful, for example, if you need to solve a slightly different problem, with additional variables and constraints. The notation in this page generally follows [KnOsWa20].
+
+Decision variables
+------------------
+
+UC.jl models the security-constrained unit commitment problem as a two-stage stochastic program. In this approach, some of the decision variables are *first-stage decisions*, which are taken before the uncertainty is realized and must therefore be the same across all scenarios, while the remaining variables are *second-stage decisions*, which can attain a different values in each scenario. In the current version of the package, all binary variables (which model commitment decisions of thermal units) are first-stage decisions and all continuous variables are second-stage decisions.
+
+!!! note
+
+    UC.jl treats deterministic SCUC instances as a special case of the stochastic problem in which there is only one scenario, named `"s1"` by default. To access second-stage decisions, therefore, you must provide this scenario name as the value for `sn`. For example, `model[:prod_above]["s1", g, t]`. 
+
+### Generators
+
+In this section, we describe the decision variables associated with the generators, which include both thermal units (e.g., natural gas-fired power plant) and profiled units (e.g., wind turbine). 
+
+#### Thermal Units
+
+Name |  Description | Unit | Stage
+:-----|:-------------|:------: | :------:
+`is_on[g,t]` | True if generator `g` is on at time `t`. | Binary | 1
+`switch_on[g,t]` | True is generator `g` switches on at time `t`. | Binary| 1
+`switch_off[g,t]` | True if generator `g` switches off at time `t`. | Binary| 1
+`startup[g,t,s]` | True if generator `g` switches on at time `t` incurring start-up costs from start-up category `s`. | Binary| 1
+`prod_above[sn,g,t]` | Amount of power produced by generator `g` above its minimum power output at time `t` in scenario `sn`. For example, if the minimum power of generator `g` is 100 MW and `g` is producing 115 MW of power at time `t` in scenario `sn`, then `prod_above[sn,g,t]` equals `15.0`. | MW | 2
+`segprod[sn,g,t,k]` | Amount of power from piecewise linear segment `k` produced by generator `g` at time `t` in scenario `sn`. For example, if cost curve for generator `g` is defined by the points `(100, 1400)`, `(110, 1600)`, `(130, 2200)` and `(135, 2400)`, and if the generator is producing 115 MW of power at time `t` in scenario `sn`, then `segprod[sn,g,t,:]` equals `[10.0, 5.0, 0.0]`.| MW | 2
+`reserve[sn,r,g,t]` | Amount of reserve `r` provided by unit `g` at time `t` in scenario `sn`. | MW | 2
+
+!!! warning
+
+    The first-stage decision variables of the JuMP model are `is_on[g,t]`, `switch_on[g,t]`, `switch_off[g,t]`, and `startup[g,t,s]`. As such, the dictionaries corresponding to these variables do not include the scenario index in their keys. In contrast, all other variables of the created JuMP model are allowed to obtain a different value in each scenario and are thus modeled as second-stage decision variables. Accordingly, the dictionaries of all second-stage decision variables have the scenario index in their keys. This is true even if the model is created to solve the deterministic SCUC, in which case the default scenario index `s1` is included in the dictionary key.
+    
+
+#### Profiled Units
+
+Name | Description | Unit | Stage
+:-----|:-------------|:------: | :------:
+`prod_profiled[s,t]` | Amount of power produced by profiled unit `g` at time `t`. | MW | 2
+
+
+### Buses
+
+Name | Description | Unit | Stage
+:-----|:-------------|:------:| :------:
+`net_injection[sn,b,t]` | Net injection at bus `b` at time `t` in scenario `sn`. | MW | 2
+`curtail[sn,b,t]` | Amount of load curtailed at bus `b` at time `t` in scenario `sn`. | MW | 2
+
+
+### Price-sensitive loads
+
+Name |  Description | Unit | Stage
+:-----|:-------------|:------:| :------:
+`loads[sn,s,t]` | Amount of power served to price-sensitive load `s` at time `t` in scenario `sn`. | MW | 2
+
+### Transmission lines
+
+Name |  Description | Unit | Stage 
+:-----|:-------------|:------:| :------:
+`flow[sn,l,t]` |  Power flow on line `l` at time `t` in scenario `sn`. | MW | 2
+`overflow[sn,l,t]` | Amount of flow above the limit for line `l` at time `t` in scenario `sn`. | MW | 2
+
+!!! warning
+
+    Since transmission and N-1 security constraints are enforced in a lazy way, most of the `flow[l,t]` variables are never added to the model. Accessing `model[:flow][sn,l,t]` without first checking that the variable exists will likely generate an error.
+
+Objective function
+------------------
+
+TODO
+
+Constraints
+-----------
+
+TODO
+
+

docs/src/guides/problem.md

@@ -0,0 +1,618 @@
+# Problem definition
+
+The **Security-Constrained Unit Commitment Problem** (SCUC) is formulated in
+UC.jl as a two-stage stochastic mixed-integer linear optimization problem that
+aims to find the minimum-cost schedule for electricity generation while
+satisfying various physical, operational and economic constraints. In its most
+basic form, the problem is composed by:
+
+- A set of generators, which produce power, at a given cost;
+- A set of loads, which consume power;
+- A transmission network, which delivers power from generators to the loads.
+
+In addition to the basic components above, SCUC also include a wide variety of
+additional components, such as _energy storage devices_, _reserves_ and _network
+interfaces_, to name a few. On this page, we present a complete definition of
+the problem, as modeled in UC.jl. Please note that different sources in the
+literature may have significantly different definitions and assumptions.
+
+!!! note
+
+    UC.jl treats deterministic SCUC instances as a special case of the stochastic problem in which there is only one scenario, named `"s1"` by default. To access second-stage decisions, therefore, you must provide this scenario name as the value for `s`. For example, `model[:prod_above]["s1", g, t]`.
+
+!!! warning
+
+    The problem definition presented in this page is mathematically equivalent to the one solved by UC.jl. However, some constraints (ramping, piecewise-linear costs and start-up costs) have been simplified in this page for clarity. The set of constraints actually enforced by UC.jl better describes the convex hull of the problem and leads to better computational performance, but it is much more complex to describe. For further details, we refer to the package's source code and associated references.
+
+## 1. General modeling assumptions
+
+- **Time discretization:** SCUC is a multi-period problem, with decisions
+  typically covering a 24-hour or 36-hour time window. UC.jl assumes that this
+  time window is discretized into time steps of fixed length. The number of time
+  steps, as well as the duration of each time step, are configurable. In the
+  equations below, the set of time steps is denoted by $T=\{1,2,\ldots,|T|\}$.
+
+- **Decision under uncertainty:** SCUC is a two-stage stochastic problem. In the
+  first stage, we must decide the _commitment status_ of all thermal generators.
+  In the second stage, we determine the remaining decision variables, such power
+  output of all generators, the operation of energy storage devices and load
+  shedding. Stochasticity is modeled through a discrete number of scenarios
+  $s \in S$, each with given probability $p(S)$. The goal is to minimize the
+  minimum expected cost.
+
+## 2. Thermal generators
+
+A _thermal generator_ is a power generation unit that converts thermal energy,
+typically from the combustion of coal, natural gas or oil, into electrical
+energy. Scheduling thermal generators is particularly complex due to their
+operational characteristics, including minimum up and down times, ramping rates,
+and start-up and shutdown limits.
+
+### Important concepts
+
+- **Commitment, power output and startup costs:** Thermal generators can either
+  be online (on) or offline (off). When a thermal generator is on, it can
+  produce between a minimum and a maximum amount of power; when it is off, it
+  cannot produce any power. Switching a generator on incurs a startup cost,
+  which depends on how long the unit has been offline. More precisely, each
+  thermal generator $g$ has a number $K^{start}_g$ of startup categories (e.g.,
+  cold, warm and hot). Each category $k$ has a corresponding startup cost
+  $Z^{\text{start}}_{gk}$, and is available only if the unit has spent at most
+  $M^{\text{delay}}_{gk}$ time steps offline.
+
+- **Piecewise-linear production cost curve:** Besides startup costs, thermal
+  generators also incur production costs based on their power output. The
+  relationship between production cost and power output is not a linear, but a
+  convex curve, which is simplified using a piecewise-linear approximation. For
+  this purpose, each thermal generator $g$ has a number $K^{\text{cost}}_g$ of
+  piecewise-linear segments and its power output $y^{\text{prod-above}}_{gts}$
+  are broken down into
+  $\sum_{k=1}^{K^{\text{cost}}_g} y^{\text{seg-prod}}_{gtks}$, so that
+  production costs can be more easily calculated.
+
+- **Ramping, minimum up/down:** Due to physical and operational limits, such as
+  thermal inertia and mechanical stress, thermal generators cannot vary their
+  power output too dramatically from one time period to the next. Similarly,
+  thermal generators cannot switch on and off too frequently; after switching on
+  or off, units must remain at that state for a minimum specified number of time
+  steps.
+
+- **Startup and shutdown limit:** A thermal generator cannot shut off if its
+  output power level in the immediately preceding time step is very high (above
+  a specified value); the unit must first ramp down, over potentially multiple
+  time steps, and only then shut off. Similarly, the unit cannot produce a very
+  large amount of power (above a specified limit) immediately after starting up;
+  it must ramp up over potentially multiple time steps.
+
+- **Initial status:** The optimization process finds optimal commitment status
+  and power output level for all thermal generators starting at time period 1.
+  Many constraints, however, require knowledge of previous time periods (0, -1,
+  -2, ...) which are not part of the optimization model. For this reason, part
+  of the input data is the initial power output $M^{\text{init-power}}_{g}$ of
+  unit $g$ (that is, the output at time 0) and the initial status
+  $M^{\text{init-status}}_{g}$ of unit g (how many time steps has it been
+  online/offline at time time 0). If $M^{\text{init-status}}_{g}$ is positive,
+  its magnitude indicates how many time periods has the unit been online; and if
+  negative, how has it been offline.
+
+- **Must-run:** Due to various factors, including reliability considerations,
+  some units must remain operational regardless of whether it is economical for
+  them to do so. Must-run constraints are used to enforce such requirements.
+
+### Sets and constants
+
+| Symbol                          | Unit   | Description                                                                                |
+| :------------------------------ | :----- | :----------------------------------------------------------------------------------------- |
+| $K^{cost}_g$                    |        | Number of piecewise linear segments in the production cost curve.                          |
+| $K^{start}_g$                   |        | Number of startup categories (e.g. cold, warm, hot).                                       |
+| $M^{\text{delay}}_{gk}$         |        | Delay for startup category $k$.                                                            |
+| $M^{\text{init-power}}_{g}$     | MW     | Initial power output of unit $g$.                                                          |
+| $M^{\text{init-status}}_{g}$    |        | Initial status of unit $g$.                                                                |
+| $M^{\text{min-up}}_{g}$         |        | Minimum amount of time $g$ must stay on after switching on.                                |
+| $M^{\text{must-run}}_{gt}$      | Binary | One if unit $g$ must be on at time $t$.                                                    |
+| $M^{\text{pmax}}_{gt}$          | MW     | Maximum power output at time $t$.                                                          |
+| $M^{\text{pmin}}_{gt}$          | MW     | Minimum power output at time $t$.                                                          |
+| $M^{\text{ramp-down}}_{g}$      | MW     | Ramp down limit.                                                                           |
+| $M^{\text{ramp-up}}_{g}$        | MW     | Ramp up limit.                                                                             |
+| $M^{\text{seg-pmax}}_{gtks}$    | MW     | Maximum power output for piecewise-linear segment $k$ at time $t$ and scenario $s$.        |
+| $M^{\text{shutdown-limit}}_{g}$ | MW     | Maximum power unit $g$ produces immediately before shutting down                           |
+| $M^{\text{startup-limit}}_{g}$  | MW     | Maximum power unit $g$ produces immediately after starting up                              |
+| $R_g$                           |        | Set of spinning reserves that may be served by $g$.                                        |
+| $Z^{\text{pmin}}_{gt}$          | \$     | Cost to keep $g$ operational at time $t$ generating at minimum power.                      |
+| $Z^{\text{pvar}}_{gtks}$        | \$/MW  | Cost for unit $g$ to produce 1 MW of power under piecewise-linear segment $k$ at time $t$. |
+| $Z^{\text{start}}_{gk}$         | \$     | Cost to start unit $g$ at startup category $k$.                                            |
+| $G^\text{therm}$                |        | Set of thermal generators.                                                                 |
+
+### Decision variables
+
+| Symbol                        | JuMP name           | Description                                                                                   | Unit   | Stage |
+| :---------------------------- | :------------------ | :-------------------------------------------------------------------------------------------- | :----- | :---- |
+| $x^{\text{is-on}}_{gt}$       | `is_on[g,t]`        | One if generator $g$ is on at time $t$.                                                       | Binary | 1     |
+| $x^{\text{switch-on}}_{gt}$   | `switch_on[g,t]`    | One if generator $g$ switches on at time $t$.                                                 | Binary | 1     |
+| $x^{\text{switch-off}}_{gt}$  | `switch_off[g,t]`   | One if generator $g$ switches off at time $t$.                                                | Binary | 1     |
+| $x^{\text{start}}_{gtk}$      | `startup[g,t,s]`    | One if generator $g$ starts up at time $t$ under startup category $k$.                        | Binary | 1     |
+| $y^{\text{prod-above}}_{gts}$ | `prod_above[s,g,t]` | Amount of power produced by $g$ at time $t$ in scenario $s$ above the minimum power.          | MW     | 2     |
+| $y^{\text{seg-prod}}_{gtks}$  | `segprod[s,g,t,k]`  | Amount of power produced by $g$ at time $t$ in piecewise-linear segment $k$ and scenario $s$. | MW     | 2     |
+| $y^{\text{res}}_{grts}$       | `reserve[s,r,g,t]`  | Amount of spinning reserve $r$ supplied by $g$ at time $t$ in scenario $s$.                   | MW     | 2     |
+
+### Objective function terms
+
+- Production costs:
+
+```math
+\sum_{g \in G^\text{therm}} \sum_{t \in T} x^{\text{is-on}}_{gt} Z^{\text{pmin}}_{gt}
++ \sum_{s \in S} p(s) \left[
+    \sum_{g \in G^\text{therm}} \sum_{t \in T} \sum_{k=1}^{K^{cost}_g}
+    y^{\text{seg-prod}}_{gtks} Z^{\text{pvar}}_{gtks}
+\right]
+```
+
+- Start-up costs:
+
+```math
+\sum_{g \in G} \sum_{t \in T} \sum_{k=1}^{K^{start}_g} x^{\text{start}}_{gtk} Z^{\text{start}}_{gk}
+```
+
+### Constraints
+
+- Some units must remain on, even if it is not economical for them to do so:
+
+```math
+x^{\text{is-on}}_{gt} \geq M^{\text{must-run}}_{gt}
+```
+
+- After switching on, unit must remain on for some amount of time
+  (`eq_min_uptime[g,t]`):
+
+```math
+\sum_{i=max(1,t-M^{\text{min-up}}_{g}+1)}^t x^{\text{switch-on}}_{gi} \leq x^{\text{is-on}}_{gt}
+```
+
+- Same as above, but covering the initial time steps (`eq_min_uptime[g,0]`):
+
+```math
+\sum_{i=1}^{min(T,M^{\text{min-up}}_{g}-M^{\text{init-status}}_{g})} x^{\text{switch-off}}_{gi} = 0 \; \text{ if } \; M^{\text{init-status}}_{g} > 0
+```
+
+- After switching off, unit must remain offline for some amount of time
+  (`eq_min_downtime[g,t]`):
+
+```math
+\sum_{i=max(1,t-M^{\text{min-down}}_{g}+1)}^t x^{\text{switch-off}}_{gi} \leq 1 - x^{\text{is-on}}_{gt}
+```
+
+- Same as above, but covering the initial time steps (`eq_min_downtime[g,0]`):
+
+```math
+\sum_{i=1}^{min(T,M^{\text{min-down}}_{g}+M^{\text{init-status}}_{g})} x^{\text{switch-on}}_{gi} = 0 \; \text{ if } \; M^{\text{init-status}}_{g} < 0
+```
+
+- If the unit switches on, it must choose exactly one startup category
+  (`eq_startup_choose[g,t]`):
+
+```math
+x^{\text{switch-on}}_{gt} = \sum_{k=1}^{K^{start}_g} x^{\text{start}}_{gtk}
+```
+
+- If unit has not switched off in the last "delay" time periods, then startup
+  category is forbidden (`eq_startup_restrict[g,t,s]`). The last startup
+  category is always allowed. In the equation below, $L^{\text{start}}_{gtk}=1$
+  if category should be allowed based on initial status.
+
+```math
+x^{\text{start}}_{gtk} \leq L^{\text{start}}_{gtk} + \sum_{i=min\left(1,t - M^{\text{delay}}_{g,k+1} + 1\right)}^{t - M^{\text{delay}}_{kg}} x^{\text{switch-off}}_{gi}
+```
+
+- Link the binary variables together (`eq_binary_link[g,t]`):
+
+```math
+\begin{align*}
+& x^{\text{is-on}}_{gt} - x^{\text{is-on}}_{g,t-1} = x^{\text{switch-on}}_{gt} - x^{\text{switch-off}}_{gt} & \forall t > 1 \\
+\end{align*}
+```
+
+- Cannot switch on and off at the same time (`eq_switch_on_off[g,t]`):
+
+```math
+x^{\text{switch-on}}_{gt} + x^{\text{switch-off}}_{gt} \leq 1
+```
+
+- If the unit is off, it cannot produce power or provide reserves. If it is on,
+  it must to so within the specified production limits (`eq_prod_limit[s,g,t]`):
+
+```math
+y^{\text{prod-above}}_{gts} + \sum_{r \in R_g} y^{\text{res}}_{grts} \leq
+(M^{\text{pmax}}_{gt} - M^{\text{pmin}}_{gt}) x^{\text{is-on}}_{gt}
+```
+
+- Break down the "production above" variable into smaller "segment production"
+  variables, to simplify the objective function (`eq_prod_above_def[s,g,t]`):
+
+```math
+y^{\text{prod-above}}_{gts} = \sum_{k=1}^{K^{cost}_g} y^{\text{seg-prod}}_{gtks}
+```
+
+- Impose upper limit on segment production variables
+  (`eq_segprod_limit[s,g,t,k]`):
+
+```math
+0 \leq y^{\text{seg-prod}}_{gtks} \leq M^{\text{seg-pmax}}_{gtks}
+```
+
+- Unit cannot increase its production too quickly (`eq_ramp_up[s,g,t]`):
+
+```math
+y^{\text{prod-above}}_{gts} + \sum_{r \in R_g} y^{\text{res}}_{grts} \leq
+y^{\text{prod-above}}_{g,t-1,s} + M^{\text{ramp-up}}_{g}
+```
+
+- Same as above, for initial time (`eq_ramp_up[s,g,1]`):
+
+```math
+y^{\text{prod-above}}_{g,1,s} + \sum_{r \in R_g} y^{\text{res}}_{gr,1,s} \leq
+\left(M^{\text{init-power}}_{g} - M^{\text{pmin}}_{gt}\right) + M^{\text{ramp-up}}_{g}
+```
+
+- Unit cannot decrease its production too quickly (`eq_ramp_down[s,g,t]`):
+
+```math
+y^{\text{prod-above}}_{gts} \geq
+y^{\text{prod-above}}_{g,t-1,s} - M^{\text{ramp-down}}_{g}
+```
+
+- Same as above, for initial time (`eq_ramp_down[s,g,1]`):
+
+```math
+y^{\text{prod-above}}_{g,1,s} \geq
+\left(M^{\text{init-power}}_{g} - M^{\text{pmin}}_{gt}\right) - M^{\text{ramp-down}}_{g}
+```
+
+- Unit cannot produce excessive amount of power immediately after starting up
+  (`eq_startup_limit[s,g,t]`):
+
+```math
+y^{\text{prod-above}}_{gts} + \sum_{r \in R_g} y^{\text{res}}_{grts} \leq
+(M^{\text{pmax}}_{gt} - M^{\text{pmin}}_{gt}) x^{\text{is-on}}_{gt} -
+max\left\{0,M^{\text{pmax}}_{gt} - M^{\text{startup-limit}}_{g}\right\}
+x^{\text{switch-on}}_{gt}
+```
+
+- Unit cannot shutoff it it's producing too much power
+  (`eq_shutdown_limit[s,g,t]`):
+
+```math
+y^{\text{prod-above}}_{gts} \leq
+(M^{\text{pmax}}_{gt} - M^{\text{pmin}}_{gt}) x^{\text{is-on}}_{gt} -
+max\left\{0,M^{\text{pmax}}_{gt} - M^{\text{shutdown-limit}}_{g}\right\}
+x^{\text{switch-off}}_{g,t+1}
+```
+
+## 3. Profiled generators
+
+A _profiled generator_ is a simplified generator model that can be used to
+represent renewable energy resources, including wind, solar and hydro. Unlike
+thermal generators, which can be either on or off, profiled generators do not
+have status variables; the only optimization decision is on their power output
+level, which must remain between minimum and maximum time-varying amounts.
+Production cost curves for profiled generators are linear, making them again
+much simpler than thermal units.
+
+### Constants
+
+| Symbol                  | Unit  | Description                                        |
+| :---------------------- | :---- | :------------------------------------------------- |
+| $M^{\text{pmax}}_{sgt}$ | MW    | Maximum power output at time $t$ and scenario $s$. |
+| $M^{\text{pmin}}_{sgt}$ | MW    | Minimum power output at time $t$ and scenario $s$. |
+| $Z^{\text{pvar}}_{sgt}$ | \$/MW | Generation cost at time $t$ and scenario $s$.      |
+
+### Decision variables
+
+| Symbol                | JuMP name              | Unit | Description                                                   | Stage |
+| :-------------------- | :--------------------- | :--- | :------------------------------------------------------------ | :---- |
+| $y^\text{prod}_{sgt}$ | `prod_profiled[s,g,t]` | MW   | Amount of power produced by $g$ in time $t$ and scenario $s$. | 2     |
+
+### Objective function terms
+
+- Production cost:
+
+```math
+\sum_{s \in S} p(s) \left[
+  \sum_{t \in T} y^\text{prod}_{sgt} Z^{\text{pvar}}_{sgt}
+\right]
+```
+
+### Constraints
+
+- Variable bounds:
+
+```math
+M^{\text{pmin}}_{sgt} \leq y^\text{prod}_{sgt} \leq M^{\text{pmax}}_{sgt}
+```
+
+## 4. Conventional loads
+
+Loads represent the demand for electrical power by consumers and devices
+connected to the system. This section describes _conventional_ (or inelastic)
+loads, which are not sensitive to changes in electricity prices, and must always
+be served. Each bus in the transmission network has exactly one load; multiple
+loads in the same bus can be modelled by aggregating them. If there is not
+enough production or transmission capacity to serve all loads, some load can be
+curtailed, at a penalty.
+
+### Constants
+
+| Symbol                  | Unit  | Description                                                |
+| :---------------------- | :---- | :--------------------------------------------------------- |
+| $M^\text{load}_{sbt}$   | MW    | Conventional load on bus $b$ at time $s$ and scenario $s$. |
+| $Z^\text{curtail}_{st}$ | \$/MW | Load curtailment penalty at time $t$ in scenario $s$.      |
+
+### Decision variables
+
+| Symbol                   | JuMP name        | Unit | Description                                                      | Stage |
+| :----------------------- | :--------------- | :--- | :--------------------------------------------------------------- | :---- |
+| $y^\text{curtail}_{sbt}$ | `curtail[s,b,t]` | MW   | Amount of load curtailed at bus $b$ in time $t$ and scenario $s$ | 2     |
+
+### Objective function terms
+
+- Load curtailment penalty:
+
+```math
+\sum_{s \in S} p(s) \left[
+  \sum_{b \in B} \sum_{t \in T} y^\text{curtail}_{sbt} Z^\text{curtail}_{ts}
+\right]
+```
+
+### Constraints
+
+- Variable bounds:
+
+```math
+0 \leq y^\text{curtail}_{sbt} \leq M^\text{load}_{bts}
+```
+
+## 5. Price-sensitive loads
+
+_Price-sensitive loads_ refer to components in the system which may increase or
+reduce their power consumption according to energy prices. Unlike conventional
+loads, described above, price-sensitive loads are only served if it is
+economical to do so. More specifically, there are no constraints forcing these
+loads to be served; instead, there is a term in the objective function rewarding
+each MW served. Unlike conventional loads, there may be multiple price-sensitive
+loads per bus.
+
+!!! note
+
+    Some unit commitment models allow price-sensitive loads to have a piecewise-linear convex revenue curves, similar to thermal generators. This can be achieved in UC.jl by adding multiple price-sensitive loads to the bus, one for each piecewise-linear segment.
+
+### Sets and constants
+
+| Symbol                       | Unit  | Description                                                      |
+| :--------------------------- | :---- | :--------------------------------------------------------------- |
+| $M^\text{psl-demand}_{spt}$  | MW    | Demand of price-sensitive load $p$ at time $t$ and scenario $s$. |
+| $Z^\text{psl-revenue}_{spt}$ | \$/MW | Revenue from serving load $p$ at $t$ in scenario $s$.            |
+| $\text{PSL}$                 |       | Set of price-sensitive loads.                                    |
+
+### Decision variables
+
+| Symbol               | JuMP name      | Unit | Description                                       | Stage |
+| :------------------- | :------------- | :--- | :------------------------------------------------ | :---- |
+| $y^\text{psl}_{spt}$ | `loads[s,p,t]` | MW   | Amount served to $p$ in time $t$ and scenario $s$ | 2     |
+
+### Objective function terms
+
+- Revenue from serving price-sensitive loads:
+
+```math
+  - \sum_{s \in S} p(s) \left[
+    \sum_{p \in \text{PSL}} \sum_{t \in T} y^\text{psl}_{spt} Z^\text{psl-revenue}_{spt}
+  \right]
+```
+
+### Constraints
+
+- Variable bounds:
+
+```math
+0 \leq y^\text{psl}_{spt} \leq M^\text{psl-demand}_{spt}
+```
+
+## 6. Energy storage
+
+_Energy storage_ units are able to store energy during periods of low demand,
+then release energy back to the grid during periods of high demand. These
+devices include _batteries_, _pumped hydroelectric storage_, _compressed air
+energy storage_ and _flywheels_. They are becoming increasingly important in the
+modern power grid, and can help to enhance grid reliability, efficiency and
+integration of renewable energy resources.
+
+### Concepts
+
+- **Min/max energy level and charge rate:** Energy storage units can only store
+  a limited amount of energy (in MWh). To maintain the operational safety and
+  longevity of these devices, a minimum energy level may also be imposed. The
+  rate (in MW) at which these units can charge and discharge is also limited,
+  due to chemical, physical and operational considerations.
+
+- **Operational costs:** Charging and discharging energy storage units may incur
+  a cost/revenue. We assume that this cost/revenue is linear on the
+  charge/discharte rate ($/MW).
+
+- **Efficiency:** Charging an energy storage unit for one hour with an input of
+  1 MW might not result in an increase of the energy level in the device by
+  exactly 1 MWh, due to various inneficiencies in the charging process,
+  including coversion losses and heat generation. For similar reasons,
+  discharging a storage unit for one hour at 1 MW might reduce the energy level
+  by more than 1 MWh. Furthermore, even when the unit is not charging or
+  discharging, some energy level may be gradually lost over time, due to
+  unwanted chemical reactions, thermal effects of mechanical losses.
+
+- **Myopic effect:** Because the optimization process considers a fixed time
+  window, there is an inherent bias towards exploiting energy storage units to
+  their maximum within the window, completely ignoring their operation just
+  beyond this horizon. For instance, without further constraints, the
+  optimization algorithm will often ensure that all storage units are fully
+  discharged at the end of the last time step, which may not be desirable. To
+  mitigate this myopic effect, a minimum and maximum energy level may be imposed
+  at the last time step.
+
+- **Simultaneous charging and discharging:** Depending on charge and discharge
+  costs/revenue, it may make sense mathematically to simultaneously charge and
+  discharge the storage unit, thus keeping its energy level unchanged while
+  potentially collecting revenue. Additional binary variables and constraints
+  are required to prevent this incorrect model behavior.
+
+### Sets and constants
+
+| Symbol                                | Unit  | Description                                                                                           |
+| :------------------------------------ | :---- | :---------------------------------------------------------------------------------------------------- |
+| $\text{SU}$                           |       | Set of storage units                                                                                  |
+| $Z^\text{charge}_{sut}$               | \$/MW | Linear charge cost/revenue for unit $u$ at time $t$ in scenario $s$.                                  |
+| $Z^\text{discharge}_{sut}$            | \$/MW | Linear discharge cost/revenue for unit $u$ at time $t$ in scenario $s$.                               |
+| $M^\text{discharge-max}_{sut}$        | \$/MW | Maximum discharge rate for unit $u$ at time $t$ in scenario $s$.                                      |
+| $M^\text{discharge-min}_{sut}$        | \$/MW | Minimum discharge rate for unit $u$ at time $t$ in scenario $s$.                                      |
+| $M^\text{charge-max}_{sut}$           | \$/MW | Maximum charge rate for unit $u$ at time $t$ in scenario $s$.                                         |
+| $M^\text{charge-min}_{sut}$           | \$/MW | Minimum charge rate for unit $u$ at time $t$ in scenario $s$.                                         |
+| $M^\text{max-end-level}_{su}$         | MWh   | Maximum storage level of unit $u$ at the last time step in scenario $s$                               |
+| $M^\text{min-end-level}_{su}$         | MWh   | Minimum storage level of unit $u$ at the last time step in scenario $s$                               |
+| $\gamma^\text{loss}_{s,u,t}$          |       | Self-discharge factor.                                                                                |
+| $\gamma^\text{charge-eff}_{s,u,t}$    |       | Charging efficiency factor.                                                                           |
+| $\gamma^\text{discharge-eff}_{s,u,t}$ |       | Discharging efficiency factor.                                                                        |
+| $\gamma^\text{time-step}$             |       | Length of a time step, in hours. Should be 1.0 for hourly time steps, 0.5 for 30-min half steps, etc. |
+
+### Decision variables
+
+| Symbol                          | JuMP name               | Unit   | Description                                                  | Stage |
+| :------------------------------ | :---------------------- | :----- | :----------------------------------------------------------- | :---- |
+| $y^\text{level}_{sut}$          | `storage_level[s,u,t]`  | MWh    | Storage level of unit $u$ at time $t$ in scenario $s$.       | 2     |
+| $y^\text{charge}_{sut}$         | `charge_rate[s,u,t]`    | MW     | Charge rate of unit $u$ at time $t$ in scenario $s$.         | 2     |
+| $y^\text{discharge}_{sut}$      | `discharge_rate[s,u,t]` | MW     | Discharge rate of unit $u$ at time $t$ in scenario $s$.      | 2     |
+| $x^\text{is-charging}_{sut}$    | `is_charging[s,u,t]`    | Binary | True if unit $u$ is charging at time $t$ in scenario $s$.    | 2     |
+| $x^\text{is-discharging}_{sut}$ | `is_discharging[s,u,t]` | Binary | True if unit $u$ is discharging at time $t$ in scenario $s$. | 2     |
+
+### Objective function terms
+
+- Charge and discharge cost/revenue:
+
+```math
+\sum_{s \in S} p(s) \left[
+  \sum_{u \in \text{SU}} \sum_{t \in T} \left(
+    y^\text{charge}_{sut} Z^\text{charge}_{sut} +
+    y^\text{discharge}_{sut} Z^\text{discharge}_{sut}
+    \right)
+\right]
+```
+
+### Constraints
+
+- Prevent simultaneous charge and discharge
+  (`eq_simultaneous_charge_and_discharge[s,u,t]`):
+
+```math
+x^\text{is-charging}_{sut} + x^\text{is-discharging}_{sut} \leq 1
+```
+
+- Limit charge/discharge rate (`eq_min_charge_rate[s,u,t]`,
+  `eq_max_charge_rate[s,u,t]`, `eq_min_discharge_rate[s,u,t]` and
+  `eq_max_discharge_rate[s,u,t]`):
+
+```math
+\begin{align*}
+y^\text{charge}_{sut} \leq x^\text{is-charging}_{sut} M^\text{charge-max}_{sut} \\
+y^\text{charge}_{sut} \geq x^\text{is-charging}_{sut} M^\text{charge-min}_{sut} \\
+y^\text{discharge}_{sut} \leq x^\text{is-discharging}_{sut} M^\text{discharge-max}_{sut} \\
+y^\text{discharge}_{sut} \geq x^\text{is-discharging}_{sut} M^\text{discharge-min}_{sut} \\
+\end{align*}
+```
+
+- Calculate current storage level (`eq_storage_transition[s,u,t]`):
+
+```math
+y^\text{level}_{sut} =
+(1 - \gamma^\text{loss}_{s,u,t}) y^\text{level}_{su,t-1} +
+ \gamma^\text{time-step} \gamma^\text{charge-eff}_{s,u,t} y^\text{charge}_{sut} -
+\frac{\gamma^\text{time-step}}{\gamma^\text{discharge-eff}_{s,u,t}} y^\text{charge}_{sut}
+```
+
+- Enforce storage level at last time step (`eq_ending_level[s,u]`):
+
+```math
+M^\text{min-end-level}_{su} \leq y^\text{level}_{sut} \leq M^\text{max-end-level}_{su}
+```
+
+## 7. Buses and transmission lines
+
+So far, we have described generators, which produce power, loads, which consume
+power, and storage units, which store energy for later use. Another important
+element is the transmission network, which delivers the power produced by the
+generators to the loads and storage units. Mathematically, the network is
+represented as a graph $(B,L)$ where $B$ is the set of **buses** and $L$ is the
+set of **transmission lines**. Each generator, load and storage unit is located
+at a bus. The **net injection** at the bus is the sum of all power injected
+minus withdrawn at the bus. To balance production and consumption, we must
+enforce that the sum of all net injections over the entire network equal to
+zero.
+
+Besides the net balance equations, we must also enforce flow limits on the
+transmission lines. Unlike flows in other optimization problems, power flows are
+directly determined by net injections and transmission line parameters, and must
+follow physical laws. UC.jl uses the DC linearization of AC power flow
+equations. Under this linearization, the flow $f_l$ in transmission line $l$ is
+given by $\sum_{b \in B} \delta_{bl} n_b$, where $\delta_{bl}$ is a constant
+known as _injection shift factor_ (also commonly called _power transfer
+distribution factor_), computed from the line parameters, and $n_b$ is the net
+injection at bus $b$.
+
+!!! warning
+
+    To improve computational performance, power flow variables and constraints are generated on-the-fly, during `UnitCommitment.optimize!`; they are **not** added by `UnitCommitment.build_model`.
+
+### Sets and constants
+
+| Symbol                    | Unit  | Description                                                 |
+| :------------------------ | :---- | :---------------------------------------------------------- |
+| $M^\text{limit}_{slt}$    | MW    | Flow limit for line $l$ at time $t$ and scenario $s$.       |
+| $Z^\text{overflow}_{slt}$ | \$/MW | Overflow penalty for line $l$ at time $t$ and scenario $s$. |
+| $L$                       |       | Set of transmission lines.                                  |
+| $B$                       |       | Set of buses.                                               |
+
+### Decision variables
+
+| Symbol                    | JuMP name              | Unit | Description                                                           | Stage |
+| :------------------------ | :--------------------- | :--- | :-------------------------------------------------------------------- | :---- |
+| $y^\text{flow}_{slt}$     | _(added on-the-fly)_   | MW   | Flow in line $l$ at time $t$ and scenario $s$.                        | 2     |
+| $y^\text{inj}_{sbt}$      | `net_injection[s,b,t]` | MW   | Total net injection at bus $b$, time $t$ and scenario $s$.            | 2     |
+| $y^\text{overflow}_{slt}$ | `overflow[s,l,t]`      | MW   | Amount of flow above limit for line $l$ at time $t$ and scenario $s$. | 2     |
+
+### Objective function terms
+
+- Penalty for exceeding line limits:
+
+```math
+  \sum_{s \in S} p(s) \left[
+    \sum_{l \in L} \sum_{t \in T} y^\text{overflow}_{slt} Z^\text{overflow}_{slt}
+  \right]
+```
+
+### Constraints
+
+- Power produced equal power consumed (`eq_power_balance[s,t]`):
+
+```math
+\sum_{b \in B} \sum_{t \in T} y^\text{inj}_{sbt} = 0
+```
+
+- Definition of flow (_enforced on-the-fly_):
+
+```math
+y^\text{flow}_{slt} = \sum_{b \in B} \delta_{sbl} y^\text{inj}_{sbt}
+```
+
+- Flow limits (_enforced on-the-fly_):
+
+```math
+\begin{align*}
+ y^\text{flow}_{slt} & \leq M^\text{limit}_{slt} + y^\text{overflow}_{slt} \\
+-y^\text{flow}_{slt} & \leq M^\text{limit}_{slt} + y^\text{overflow}_{slt}
+\end{align*}
+```
+

docs/src/index.md

@@ -1,49 +1,43 @@
 # UnitCommitment.jl
 
-**UnitCommitment.jl** (UC.jl) is a Julia/JuMP optimization package for the Security-Constrained Unit Commitment Problem (SCUC), a fundamental optimization problem in power systems used, for example, to clear the day-ahead electricity markets. The package provides benchmark instances for the problem and Julia/JuMP implementations of state-of-the-art mixed-integer programming formulations.
+**UnitCommitment.jl** (UC.jl) is an optimization package for the Security-Constrained Unit Commitment Problem (SCUC), a fundamental optimization problem in power systems used, for example, to clear the electricity markets. Both deterministic and two-stage stochastic versions of the problem are supported. The package provides benchmark instances for the problem, a flexible and well-documented data format for the problem, as well as Julia/JuMP implementations of state-of-the-art mixed-integer programming formulations and solution methods.
 
 ## Package Components
 
-* **Data Format:** The package proposes an extensible and fully-documented JSON-based data specification format for SCUC, developed in collaboration with Independent System Operators (ISOs), which describes the most important aspects of the problem. The format supports all the most common generator characteristics (including ramping, piecewise-linear production cost curves and time-dependent startup costs), as well as operating reserves, price-sensitive loads, transmission networks and contingencies.
+- **Data Format:** The package proposes an extensible and fully-documented JSON-based data specification format for SCUC, developed in collaboration with Independent System Operators (ISOs), which describes the most important aspects of the problem. The format supports all the most common thermal generator characteristics (including ramping, piecewise-linear production cost curves and time-dependent startup costs), as well as profiled generators, reserves, price-sensitive loads, battery storage, transmission, and contingencies.
-* **Benchmark Instances:** The package provides a diverse collection of large-scale benchmark instances collected from the literature, converted into a common data format, and extended using data-driven methods to make them more challenging and realistic.
+- **Benchmark Instances:** The package provides a diverse collection of large-scale benchmark instances collected from the literature, converted into a common data format, and extended using data-driven methods to make them more challenging and realistic.
-* **Model Implementation**: The package provides a Julia/JuMP implementations of state-of-the-art formulations and solution methods for SCUC, including multiple ramping formulations ([ArrCon2000][ArrCon2000], [MorLatRam2013][MorLatRam2013], [DamKucRajAta2016][DamKucRajAta2016], [PanGua2016][PanGua2016]), multiple piecewise-linear costs formulations ([Gar1962][Gar1962], [CarArr2006][CarArr2006], [KnuOstWat2018][KnuOstWat2018]) and contingency screening methods ([XavQiuWanThi2019][XavQiuWanThi2019]). Our goal is to keep these implementations up-to-date as new methods are proposed in the literature.
+- **Model Implementation**: The package provides a Julia/JuMP implementations of state-of-the-art formulations and solution methods for the deterministic and stochastic SCUC, including multiple ramping formulations ([ArrCon2000](https://doi.org/10.1109/59.871739), [MorLatRam2013](https://doi.org/10.1109/TPWRS.2013.2251373), [DamKucRajAta2016](https://doi.org/10.1007/s10107-015-0919-9), [PanGua2016](https://doi.org/10.1287/opre.2016.1520)), piecewise-linear costs formulations ([Gar1962](https://doi.org/10.1109/AIEEPAS.1962.4501405), [CarArr2006](https://doi.org/10.1109/TPWRS.2006.876672), [KnuOstWat2018](https://doi.org/10.1109/TPWRS.2017.2783850)), contingency screening methods ([XavQiuWanThi2019](https://doi.org/10.1109/TPWRS.2019.2892620)) and decomposition methods. Our goal is to keep these implementations up-to-date as new methods are proposed in the literature.
-* **Benchmark Tools:** The package provides automated benchmark scripts to accurately evaluate the performance impact of proposed code changes.
+- **Benchmark Tools:** The package provides automated benchmark scripts to accurately evaluate the performance impact of proposed code changes.
 
-[ArrCon2000]: https://doi.org/10.1109/59.871739
+## Authors
-[CarArr2006]: https://doi.org/10.1109/TPWRS.2006.876672
-[DamKucRajAta2016]: https://doi.org/10.1007/s10107-015-0919-9
-[Gar1962]: https://doi.org/10.1109/AIEEPAS.1962.4501405
-[KnuOstWat2018]: https://doi.org/10.1109/TPWRS.2017.2783850
-[MorLatRam2013]: https://doi.org/10.1109/TPWRS.2013.2251373
-[PanGua2016]: https://doi.org/10.1287/opre.2016.1520
-[XavQiuWanThi2019]: https://doi.org/10.1109/TPWRS.2019.2892620
 
-### Authors
+- **Alinson S. Xavier** (Argonne National Laboratory)
-* **Alinson S. Xavier** (Argonne National Laboratory)
+- **Aleksandr M. Kazachkov** (University of Florida)
-* **Aleksandr M. Kazachkov** (University of Florida)
+- **Ogün Yurdakul** (Technische Universität Berlin)
-* **Feng Qiu** (Argonne National Laboratory)
+- **Jun He** (Purdue University)
+- **Feng Qiu** (Argonne National Laboratory)
 
-### Acknowledgments
+## Acknowledgments
 
-* We would like to thank **Yonghong Chen** (Midcontinent Independent System Operator), **Feng Pan** (Pacific Northwest National Laboratory) for valuable feedback on early versions of this package.
+- We would like to thank **Yonghong Chen** (Midcontinent Independent System Operator), **Feng Pan** (Pacific Northwest National Laboratory) for valuable feedback on early versions of this package.
 
-* Based upon work supported by **Laboratory Directed Research and Development** (LDRD) funding from Argonne National Laboratory, provided by the Director, Office of Science, of the U.S. Department of Energy under Contract No. DE-AC02-06CH11357
+- Based upon work supported by **Laboratory Directed Research and Development** (LDRD) funding from Argonne National Laboratory, provided by the Director, Office of Science, of the U.S. Department of Energy under Contract No. DE-AC02-06CH11357
 
-* Based upon work supported by the **U.S. Department of Energy Advanced Grid Modeling Program** under Grant DE-OE0000875.
+- Based upon work supported by the **U.S. Department of Energy Advanced Grid Modeling Program** under Grant DE-OE0000875.
 
-### Citing
+## Citing
 
 If you use UnitCommitment.jl in your research (instances, models or algorithms), we kindly request that you cite the package as follows:
 
-* **Alinson S. Xavier, Aleksandr M. Kazachkov, Feng Qiu**, "UnitCommitment.jl: A Julia/JuMP Optimization Package for Security-Constrained Unit Commitment". Zenodo (2020). [DOI: 10.5281/zenodo.4269874](https://doi.org/10.5281/zenodo.4269874).
+- **Alinson S. Xavier, Aleksandr M. Kazachkov, Ogün Yurdakul, Jun He, Feng Qiu**, "UnitCommitment.jl: A Julia/JuMP Optimization Package for Security-Constrained Unit Commitment (Version 0.4)". Zenodo (2024). [DOI: 10.5281/zenodo.4269874](https://doi.org/10.5281/zenodo.4269874).
 
-If you use the instances, we additionally request that you cite the original sources, as described in the [instances page](instances.md).
+If you use the instances, we additionally request that you cite the original sources, as described in the [instances page](guides/instances.md).
 
-### License
+## License
 
 ```text
 UnitCommitment.jl: A Julia/JuMP Optimization Package for Security-Constrained Unit Commitment
-Copyright © 2020, UChicago Argonne, LLC. All Rights Reserved.
+Copyright © 2020-2024, UChicago Argonne, LLC. All Rights Reserved.
 
 Redistribution and use in source and binary forms, with or without modification, are permitted
 provided that the following conditions are met:
@@ -67,16 +61,3 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING N
 OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 POSSIBILITY OF SUCH DAMAGE.
 ```
-
-## Site contents
-
-```{toctree}
----
-maxdepth: 2
----
-usage.md
-format.md
-instances.md
-model.md
-```
-

docs/src/tutorials/customizing.jl

@@ -0,0 +1,122 @@
+# # Model customization
+
+# In the previous tutorial, we used UnitCommitment.jl to solve benchmark and user-provided instances using a default mathematical formulation for the problem. In this tutorial, we will explore how to customize this formulation.
+
+# !!! warning
+
+#     This tutorial is not required for using UnitCommitment.jl, unless you plan to make changes to the problem formulation. In this page, we assume familiarity with the JuMP modeling language. Please see [JuMP's official documentation](https://jump.dev/JuMP.jl/stable/) for resources on getting started with JuMP. 
+
+# ## Selecting modeling components
+
+# By default, `UnitCommitment.build_model` uses a formulation that combines modeling components from different publications, and that has been carefully tested, using our own benchmark scripts, to provide good performance across a wide variety of instances. This default formulation is expected to change over time, as new methods are proposed in the literature. You can, however, construct your own formulation, based on the modeling components that you choose, as shown in the next example.
+
+# We start by importing the necessary packages and reading a benchmark instance:
+
+using HiGHS
+using JuMP
+using UnitCommitment
+
+instance = UnitCommitment.read_benchmark("matpower/case14/2017-01-01");
+
+# Next, instead of calling `UnitCommitment.build_model` with default arguments, we can provide a `UnitCommitment.Formulation` object, which describes what modeling components to use, and how should they be configured. For a complete list of modeling components available in UnitCommitment.jl, see the [API docs](../api.md).
+
+# In the example below, we switch to piecewise-linear cost modeling as defined in [KnuOstWat2018](https://doi.org/10.1109/TPWRS.2017.2783850), as well as ramping and startup costs formulation as defined in [MorLatRam2013](https://doi.org/10.1109/TPWRS.2013.2251373). In addition, we specify custom cutoffs for the shift factors formulation.
+
+model = UnitCommitment.build_model(
+    instance = instance,
+    optimizer = HiGHS.Optimizer,
+    formulation = UnitCommitment.Formulation(
+        pwl_costs = UnitCommitment.KnuOstWat2018.PwlCosts(),
+        ramping = UnitCommitment.MorLatRam2013.Ramping(),
+        startup_costs = UnitCommitment.MorLatRam2013.StartupCosts(),
+        transmission = UnitCommitment.ShiftFactorsFormulation(
+            isf_cutoff = 0.008,
+            lodf_cutoff = 0.003,
+        ),
+    ),
+);
+
+# ## Accessing decision variables
+
+# In the previous tutorial, we saw how to access the optimal solution through `UnitCommitment.solution`. While this approach works well for basic usage, it is also possible to get a direct reference to the JuMP decision variables and query their values, as the next example illustrates.
+
+# First, we load a benchmark instance and solve it, as before.
+
+instance = UnitCommitment.read_benchmark("matpower/case14/2017-01-01");
+model =
+    UnitCommitment.build_model(instance = instance, optimizer = HiGHS.Optimizer);
+UnitCommitment.optimize!(model)
+
+# At this point, it is possible to obtain a reference to the decision variables by calling `model[:varname][index]`. For example, `model[:is_on]["g1",1]` returns a direct reference to the JuMP variable indicating whether generator named "g1" is on at time 1. For a complete list of decision variables available, and how are they indexed, see the [problem definition](../guides/problem.md).
+
+@show JuMP.value(model[:is_on]["g1", 1])
+
+# To access second-stage decisions, it is necessary to specify the scenario name. UnitCommitment.jl models deterministic instances as a particular case in which there is a single scenario named "s1", so we need to use this key.
+
+@show JuMP.value(model[:prod_above]["s1", "g1", 1])
+
+# ## Modifying variables and constraints
+
+# When testing variations of the unit commitment problem, it is often necessary to modify the objective function, variables and constraints of the formulation. UnitCommitment.jl makes this process relatively easy. The first step is to construct the standard model using `UnitCommitment.build_model`:
+
+instance = UnitCommitment.read_benchmark("matpower/case14/2017-01-01");
+model =
+    UnitCommitment.build_model(instance = instance, optimizer = HiGHS.Optimizer);
+
+# Now, before calling `UnitCommitment.optimize`, we can make any desired changes to the formulation. In the previous section, we saw how to obtain a direct reference to the decision variables. It is possible to modify them by using standard JuMP methods. For example, to fix the commitment status of a particular generator, we can use `JuMP.fix`:
+
+JuMP.fix(model[:is_on]["g1", 1], 1.0, force = true)
+
+# To modify the cost coefficient of a particular variable, we can use `JuMP.set_objective_coefficient`:
+
+JuMP.set_objective_coefficient(model, model[:switch_on]["g1", 1], 1000.0)
+
+# It is also possible to make changes to the set of constraints. For example, we can add a custom constraint, using the `JuMP.@constraint` macro:
+
+@constraint(model, model[:is_on]["g3", 1] + model[:is_on]["g4", 1] <= 1,);
+
+# We can also remove an existing model constraint using `JuMP.delete`. See the [problem definition](../guides/problem.md) for a list of constraint names and indices.
+
+JuMP.delete(model, model[:eq_min_uptime]["g1", 1])
+
+# After we are done with all changes, we can call `UnitCommitment.optimize` and extract the optimal solution:
+
+UnitCommitment.optimize!(model)
+@show UnitCommitment.solution(model)
+
+# ## Modeling new grid components
+
+# In this section we demonstrate how to add a new grid component to a particular bus in the network. This is useful, for example, when developing formulations for a new type of generator, energy storage, or any other grid device. We start by reading the instance data and buliding a standard model:
+
+instance = UnitCommitment.read_benchmark("matpower/case118/2017-02-01")
+model =
+    UnitCommitment.build_model(instance = instance, optimizer = HiGHS.Optimizer);
+
+# Next, we create decision variables for the new grid component. In this example, we assume that the new component can inject up to 10 MW of power at each time step, so we create new continuous variables $0 \leq x_t \leq 10$.
+
+T = instance.time
+@variable(model, x[1:T], lower_bound = 0.0, upper_bound = 10.0);
+
+# Next, we add the production costs to the objective function. In this example, we assume a generation cost of \$5/MW:
+
+for t in 1:T
+    set_objective_coefficient(model, x[t], 5.0)
+end
+
+# We then attach the new component to bus `b1` by modifying the net injection constraint (`eq_net_injection`):
+
+for t in 1:T
+    set_normalized_coefficient(
+        model[:eq_net_injection]["s1", "b1", t],
+        x[t],
+        1.0,
+    )
+end
+
+# Next, we solve the model:
+
+UnitCommitment.optimize!(model)
+
+# We then finally extract the optimal value of the $x$ variables:
+
+@show value.(x)

docs/src/tutorials/decomposition.md

@@ -0,0 +1,105 @@
+# Decomposition methods
+
+## 1. Time decomposition for production cost modeling
+
+Solving unit commitment instances that have long time horizons (for example, year-long 8760-hour instances in production cost modeling) requires a substantial amount of computational power. To address this issue, UC.jl offers a time decomposition method, which breaks the instance down into multiple overlapping subproblems, solves them sequentially, then reassembles the solution.
+
+When solving a unit commitment instance with a dense time slot structure, computational complexity can become a significant challenge. For instance, if the instance contains hourly data for an entire year (8760 hours), solving such a model can require a substantial amount of computational power. To address this issue, UC.jl provides a time_decomposition method within the `optimize!` function. This method decomposes the problem into multiple sub-problems, solving them sequentially.
+
+The `optimize!` function takes 5 parameters: a unit commitment instance, a `TimeDecomposition` method, an optimizer, and two optional functions `after_build` and `after_optimize`. It returns a solution dictionary. The `TimeDecomposition` method itself requires four arguments: `time_window`, `time_increment`, `inner_method` (optional), and `formulation` (optional). These arguments define the time window for each sub-problem, the time increment to move to the next sub-problem, the method used to solve each sub-problem, and the formulation employed, respectively. The two functions, namely `after_build` and `after_optimize`, are invoked subsequent to the construction and optimization of each sub-model, respectively. It is imperative that the `after_build` function requires its two arguments to be consistently mapped to `model` and `instance`, while the `after_optimize` function necessitates its three arguments to be consistently mapped to `solution`, `model`, and `instance`.
+
+The code snippet below illustrates an example of solving an instance by decomposing the model into multiple 36-hour sub-problems using the `XavQiuWanThi2019` method. Each sub-problem advances 24 hours at a time. The first sub-problem covers time steps 1 to 36, the second covers time steps 25 to 60, the third covers time steps 49 to 84, and so on. The initial power levels and statuses of the second and subsequent sub-problems are set based on the results of the first 24 hours from each of their immediate prior sub-problems. In essence, this approach addresses the complexity of solving a large problem by tackling it in 24-hour intervals, while incorporating an additional 12-hour buffer to mitigate the closing window effect for each sub-problem. Furthermore, the `after_build` function imposes the restriction that `g3` and `g4` cannot be activated simultaneously during the initial time slot of each sub-problem. On the other hand, the `after_optimize` function is invoked to calculate the conventional Locational Marginal Prices (LMPs) for each sub-problem, and subsequently appends the computed values to the `lmps` vector.
+
+> **Warning**
+> Specifying `TimeDecomposition` as the value of the `inner_method` field of another `TimeDecomposition` causes errors when calling the `optimize!` function due to the different argument structures between the two `optimize!` functions.
+
+```julia
+using UnitCommitment, JuMP, Cbc, HiGHS
+
+import UnitCommitment:
+    TimeDecomposition,
+    ConventionalLMP,
+    XavQiuWanThi2019,
+    Formulation
+
+# specifying the after_build and after_optimize functions
+function after_build(model, instance)
+    @constraint(
+        model,
+        model[:is_on]["g3", 1] + model[:is_on]["g4", 1] <= 1,
+    )
+end
+
+lmps = []
+function after_optimize(solution, model, instance)
+    lmp = UnitCommitment.compute_lmp(
+        model,
+        ConventionalLMP(),
+        optimizer = HiGHS.Optimizer,
+    )
+    return push!(lmps, lmp)
+end
+
+# assume the instance is given as a 120h problem
+instance = UnitCommitment.read("instance.json")
+
+solution = UnitCommitment.optimize!(
+    instance,
+    TimeDecomposition(
+        time_window = 36,  # solve 36h problems
+        time_increment = 24,  # advance by 24h each time
+        inner_method = XavQiuWanThi2019.Method(),
+        formulation = Formulation(),
+    ),
+    optimizer = Cbc.Optimizer,
+    after_build = after_build,
+    after_optimize = after_optimize,
+)
+```
+
+## 2. Scenario decomposition with Progressive Hedging for stochstic UC
+
+By default, UC.jl uses the Extensive Form (EF) when solving stochastic instances. This approach involves constructing a single JuMP model that contains data and decision variables for all scenarios. Although EF has optimality guarantees and performs well with small test cases, it can become computationally intractable for large instances or substantial number of scenarios.
+
+Progressive Hedging (PH) is an alternative (heuristic) solution method provided by UC.jl in which the problem is decomposed into smaller scenario-based subproblems, which are then solved in parallel in separate Julia processes, potentially across multiple machines. Quadratic penalty terms are used to enforce convergence of first-stage decision variables. The method is closely related to the Alternative Direction Method of Multipliers (ADMM) and can handle larger instances, although it is not guaranteed to converge to the optimal solution. Our implementation of PH relies on Message Passing Interface (MPI) for communication. We refer to [MPI.jl Documentation](https://github.com/JuliaParallel/MPI.jl) for more details on installing MPI.
+
+The following example shows how to solve SCUC instances using progressive hedging. The script should be saved in a file, say `ph.jl`, and executed using `mpiexec -n <num-scenarios> julia ph.jl`.
+
+```julia
+using HiGHS
+using MPI
+using UnitCommitment
+using Glob
+
+# 1. Initialize MPI
+MPI.Init()
+
+# 2. Configure progressive hedging method
+ph = UnitCommitment.ProgressiveHedging()
+
+# 3. Read problem instance
+instance = UnitCommitment.read(["example/s1.json", "example/s2.json"], ph)
+
+# 4. Build JuMP model
+model = UnitCommitment.build_model(
+    instance = instance,
+    optimizer = HiGHS.Optimizer,
+)
+
+# 5. Run the decentralized optimization algorithm
+UnitCommitment.optimize!(model, ph)
+
+# 6. Fetch the solution
+solution = UnitCommitment.solution(model, ph)
+
+# 7. Close MPI
+MPI.Finalize()
+```
+
+When using PH, the model can be customized as usual, with different formulations or additional user-provided constraints. Note that `read`, in this case, takes `ph` as an argument. This allows each Julia process to read only the instance files that are relevant to it. Similarly, the `solution` function gathers the optimal solution of each processes and returns a combined dictionary.
+
+Each process solves a sub-problem with $\frac{s}{p}$ scenarios, where $s$ is the total number of scenarios and $p$ is the number of MPI processes. For instance, if we have 15 scenario files and 5 processes, then each process will solve a JuMP model that contains data for 3 scenarios. If the total number of scenarios is not divisible by the number of processes, then an error will be thrown.
+
+!!! warning
+
+    Currently, PH can handle only equiprobable scenarios. Further, `solution(model, ph)` can only handle cases where only one scenario is modeled in each process.

docs/src/tutorials/lmp.jl

@@ -0,0 +1,57 @@
+# # Locational Marginal Prices
+
+# Locational Marginal Prices (LMPs) refer to the cost of supplying electricity at specific locations of the network. LMPs are crucial for the operation of electricity markets and have many other applications, such as indicating what areas of the network may require additional generation or transmission capacity. UnitCommitment.jl implements two methods for calculating LMPS: Conventional LMPs and Approximated Extended LMPs (AELMPs). In this tutorial, we introduce each method and illustrate their usage.
+
+# ### Conventional LMPs
+
+# Conventional LMPs work by (1) solving the original SCUC problem, (2) fixing all binary variables to their optimal values, and (3) re-solving the resulting linear programming model. In this approach, the LMPs are defined as the values of the dual variables associated with the net injection constraints.
+
+# The first step to use this method is to load and optimize an instance, as explained in previous tutorials:
+
+using UnitCommitment
+using HiGHS
+
+instance = UnitCommitment.read_benchmark("matpower/case14/2017-01-01")
+model =
+    UnitCommitment.build_model(instance = instance, optimizer = HiGHS.Optimizer)
+UnitCommitment.optimize!(model)
+
+# Next, we call `UnitCommitment.compute_lmp`, as shown below. The function accepts three arguments -- a solved SCUC model, the LMP method, and a linear optimizer -- and it returns a dictionary mapping `(scenario_name, bus_name, time)` to the marginal price.
+
+lmp = UnitCommitment.compute_lmp(
+    model,
+    UnitCommitment.ConventionalLMP(),
+    optimizer = HiGHS.Optimizer,
+)
+
+# For example, the following code queries the LMP of bus `b1` in scenario `s1` at time 1:
+
+@show lmp["s1", "b1", 1]
+
+# ### Approximate Extended LMPs
+
+# Approximate Extended LMPs (AELMPs) are an alternative method to calculate locational marginal prices which attemps to minimize uplift payments. The method internally works by modifying the instance data in three ways: (1) it sets the minimum power output of each generator to zero, (2) it averages the start-up cost over the offer blocks for each generator, and (3) it relaxes all integrality constraints. To compute AELMPs, as shown in the example below, we call `compute_lmp` and provide `UnitCommitment.AELMP()` as the second argument.
+
+# This method has two configurable parameters: `allow_offline_participation` and `consider_startup_costs`. If `allow_offline_participation = true`, then offline generators are allowed to participate in the pricing. If instead `allow_offline_participation = false`, offline generators are not allowed and therefore are excluded from the system. A solved UC model is optional if offline participation is allowed, but is required if not allowed. The method forces offline participation to be allowed if the UC model supplied by the user is not solved. For the second field, If `consider_startup_costs = true`, then start-up costs are integrated and averaged over each unit production; otherwise the production costs stay the same. By default, both fields are set to `true`.
+
+# !!! warning
+
+#     This method is still under active research, and has several limitations. The implementation provided in the package is based on MISO Phase I only. It only supports fast start resources. More specifically, the minimum up/down time of all generators must be 1, the initial power of all generators must be 0, and the initial status of all generators must be negative. The method does not support time-varying start-up costs, and only currently works for deterministic instances. If offline participation is not allowed, AELMPs treats an asset to be  offline if it is never on throughout all time periods.
+
+instance = UnitCommitment.read_benchmark("test/aelmp_simple")
+
+model =
+    UnitCommitment.build_model(instance = instance, optimizer = HiGHS.Optimizer)
+
+UnitCommitment.optimize!(model)
+
+lmp = UnitCommitment.compute_lmp(
+    model,
+    UnitCommitment.AELMP(
+        allow_offline_participation = false,
+        consider_startup_costs = true,
+    ),
+    optimizer = HiGHS.Optimizer,
+)
+
+@show lmp["s1", "B1", 1]

docs/src/tutorials/market.jl

@@ -0,0 +1,183 @@
+# # Market Clearing
+
+# In North America, electricity markets are structured around two primary types of markets: the day-ahead (DA) market and the real-time (RT) market. The DA market schedules electricity generation and consumption for the next day, based on forecasts and bids from electricity suppliers and consumers. The RT market, on the other hand, operates continuously throughout the day, addressing the discrepancies between the DA schedule and actual demand, typically every five minutes. UnitCommitment.jl is able to simulate the DA and RT market clearing process. Specifically, the package provides the function `UnitCommitment.solve_market` which performs the following steps:
+
+# 1. Solve the DA market problem.
+# 2. Extract commitment status of all generators.
+# 3. Solve a sequence of RT market problems, fixing the commitment status of each generator to the corresponding optimal solution of the DA problem.
+
+# To use this function, we need to prepare an instance file corresponding to the DA market problem and multiple instance files corresponding to the RT market problems. The number of required files depends on the time granularity and window. For example, suppose that the DA problem is solved at hourly granularity and has 24 time periods, whereas the RT problems are solved at 5-minute granularity and have a single time period. Then we would need to prepare one files for the DA problem and 288 files $\left(24 \times \frac{60}{5}\right)$ for the RT market problems.
+
+# ## A small example
+
+# For simplicity, in this tutorial we illustate the usage of `UnitCommitment.solve_market` with a very small example, in which the DA problem has only two time periods. We start by creating the DA instance file:
+
+da_contents = """
+{
+    "Parameters": {
+        "Version": "0.4",
+        "Time horizon (h)": 2
+    },
+    "Buses": {
+        "b1": {
+            "Load (MW)": [200, 400]
+        }
+    },
+    "Generators": {
+        "g1": {
+            "Bus": "b1",
+            "Type": "Thermal",
+            "Production cost curve (MW)": [0, 200],
+            "Production cost curve (\$)": [0, 1000],
+            "Initial status (h)": -24,
+            "Initial power (MW)": 0
+        },
+        "g2": {
+            "Bus": "b1",
+            "Type": "Thermal",
+            "Production cost curve (MW)": [0, 300],
+            "Production cost curve (\$)": [0, 3000],
+            "Initial status (h)": -24,
+            "Initial power (MW)": 0
+        }
+    }
+}
+""";
+
+open("da.json", "w") do file
+    return write(file, da_contents)
+end;
+
+# Next, we create eight single-period RT market problems, each one with a 15-minute time granularity:
+
+for i in 1:8
+    rt_contents = """
+    {
+        "Parameters": {
+            "Version": "0.4",
+            "Time horizon (min)": 15,
+            "Time step (min)": 15
+        },
+        "Buses": {
+            "b1": {
+                "Load (MW)": [$(150 + 50 * i)]
+            }
+        },
+        "Generators": {
+            "g1": {
+                "Bus": "b1",
+                "Type": "Thermal",
+                "Production cost curve (MW)": [0, 200],
+                "Production cost curve (\$)": [0, 1000],
+                "Initial status (h)": -24,
+                "Initial power (MW)": 0
+            },
+            "g2": {
+                "Bus": "b1",
+                "Type": "Thermal",
+                "Production cost curve (MW)": [0, 300],
+                "Production cost curve (\$)": [0, 3000],
+                "Initial status (h)": -24,
+                "Initial power (MW)": 0
+            }
+        }
+    }
+    """
+    open("rt_$i.json", "w") do file
+        return write(file, rt_contents)
+    end
+end
+
+# Finally, we call `UnitCommitment.solve_market`, providing as arguments (1) the path to the DA problem; (2) a list of paths to the RT problems; (3) the mixed-integer linear optimizer.
+
+using UnitCommitment
+using HiGHS
+
+solution = UnitCommitment.solve_market(
+    "da.json",
+    [
+        "rt_1.json",
+        "rt_2.json",
+        "rt_3.json",
+        "rt_4.json",
+        "rt_5.json",
+        "rt_6.json",
+        "rt_7.json",
+        "rt_8.json",
+    ],
+    optimizer = HiGHS.Optimizer,
+)
+
+# To retrieve the day-ahead market solution, we can query `solution["DA"]`:
+
+@show solution["DA"]
+
+# To query each real-time market solution, we can query `solution["RT"][i]`. Note that LMPs are automativally calculated.
+
+@show solution["RT"][1]
+
+# ## Customizing the model and LMPs
+
+# When using the `solve_market` function it is still possible to customize the problem formulation and the LMP calculation method. In the next example, we use a custom formulation and explicitly specify the LMP method through the `settings` keyword argument:
+
+UnitCommitment.solve_market(
+    "da.json",
+    [
+        "rt_1.json",
+        "rt_2.json",
+        "rt_3.json",
+        "rt_4.json",
+        "rt_5.json",
+        "rt_6.json",
+        "rt_7.json",
+        "rt_8.json",
+    ],
+    settings = UnitCommitment.MarketSettings(
+        lmp_method = UnitCommitment.ConventionalLMP(),
+        formulation = UnitCommitment.Formulation(
+            pwl_costs = UnitCommitment.KnuOstWat2018.PwlCosts(),
+            ramping = UnitCommitment.MorLatRam2013.Ramping(),
+            startup_costs = UnitCommitment.MorLatRam2013.StartupCosts(),
+            transmission = UnitCommitment.ShiftFactorsFormulation(
+                isf_cutoff = 0.008,
+                lodf_cutoff = 0.003,
+            ),
+        ),
+    ),
+    optimizer = HiGHS.Optimizer,
+)
+
+# It is also possible to add custom variables and constraints to either the DA or RT market problems, through the usage of `after_build_da` and `after_build_rt` callback functions. Similarly, the `after_optimize_da` and `after_optimize_rt` can be used to directly analyze the JuMP models, after they have been optimized:
+
+using JuMP
+
+function after_build_da(model, instance)
+    @constraint(model, model[:is_on]["g1", 1] <= model[:is_on]["g2", 1])
+end
+
+function after_optimize_da(solution, model, instance)
+    @show value(model[:is_on]["g1", 1])
+end
+
+UnitCommitment.solve_market(
+    "da.json",
+    [
+        "rt_1.json",
+        "rt_2.json",
+        "rt_3.json",
+        "rt_4.json",
+        "rt_5.json",
+        "rt_6.json",
+        "rt_7.json",
+        "rt_8.json",
+    ],
+    after_build_da = after_build_da,
+    after_optimize_da = after_optimize_da,
+    optimizer = HiGHS.Optimizer,
+)
+
+# ## Additional considerations
+
+# - UC.jl supports two-stage stochastic DA market problems. In this case, we need one file for each DA market scenario. All RT market problems must be deterministic.
+# - UC.jl also supports multi-period RT market problems. Assume, for example, that the DA market problem is an hourly problem with 24 time periods, whereas the RT market problem uses 5-minute granularity with 4 time periods. UC.jl assumes that the first RT file covers period `0:00` to `0:20`, the second covers `0:05` to `0:25` and so on. We therefore still need 288 RT market files. To avoid going beyond the 24-hour period covered by the DA market solution, however, the last few RT market problems must have only 3, 2, and 1 time periods, covering `23:45` to `24:00`, `23:50` to `24:00` and `23:55` to `24:00`, respectively.
+# - Some MILP solvers (such as Cbc) have issues handling linear programming problems, which are required for the RT market. In this case, a separate linear programming solver can be provided to `solve_market` using the `lp_optimizer` argument. For example, `solve_market(da_file, rt_files, optimizer=Cbc.Optimizer, lp_optimizer=Clp.Optimizer)`.

docs/src/tutorials/usage.jl

@@ -0,0 +1,211 @@
+# # Getting started
+
+# ## Installing the package
+
+# UnitCommitment.jl was tested and developed with [Julia 1.10](https://julialang.org/). To install Julia, please follow the [installation guide on the official Julia website](https://julialang.org/downloads/). To install UnitCommitment.jl, run the Julia interpreter, type `]` to open the package manager, then type:
+
+# ```text
+# pkg> add UnitCommitment@0.4
+# ```
+
+# To solve the optimization models, a mixed-integer linear programming (MILP) solver is also required. Please see the [JuMP installation guide](https://jump.dev/JuMP.jl/stable/installation/) for more instructions on installing a solver. Typical open-source choices are [HiGHS](https://github.com/jump-dev/HiGHS.jl), [Cbc](https://github.com/JuliaOpt/Cbc.jl) and [GLPK](https://github.com/JuliaOpt/GLPK.jl). In the instructions below, HiGHS will be used, but any other MILP solver should also be compatible.
+
+# ## Solving a benchmark instance
+
+# We start this tutorial by illustrating how to use UnitCommitment.jl to solve one of the provided benchmark instances. The package contains a large number of deterministic benchmark instances collected from the literature and converted into a common data format, which can be used to evaluate the performance of different solution methods. See [Instances](../guides/instances.md) for more details. The first step is to import `UnitCommitment` and HiGHS.
+
+using HiGHS
+using UnitCommitment
+
+# Next, we use the function `UnitCommitment.read_benchmark` to read the instance.
+
+instance = UnitCommitment.read_benchmark("matpower/case14/2017-01-01");
+
+# Now that we have the instance loaded in memory, we build the JuMP optimization model using `UnitCommitment.build_model`:
+
+model =
+    UnitCommitment.build_model(instance = instance, optimizer = HiGHS.Optimizer);
+
+# Next, we run the optimization process, with `UnitCommitment.optimize!`:
+
+UnitCommitment.optimize!(model)
+
+# Finally, we extract the optimal solution from the model:
+
+solution = UnitCommitment.solution(model)
+
+# We can then explore the solution using Julia:
+
+@show solution["Thermal production (MW)"]["g1"]
+
+# Or export the entire solution to a JSON file:
+
+UnitCommitment.write("solution.json", solution)
+
+# ## Solving a custom deterministic instance
+
+# In the previous example, we solved a benchmark instance provided by the package. To solve a custom instance, the first step is to create an input file describing the list of elements (generators, loads and transmission lines) in the network. See [Data Format](../guides/format.md) for a complete description of the data format UC.jl expects. To keep this tutorial self-contained, we will create the input JSON file using Julia; however, this step can also be done with a simple text editor. First, we define the contents of the file:
+
+json_contents = """
+{
+    "Parameters": {
+        "Version": "0.4",
+        "Time horizon (h)": 4
+    },
+    "Buses": {
+        "b1": {
+            "Load (MW)": [100, 150, 200, 250]
+        }
+    },
+    "Generators": {
+        "g1": {
+            "Bus": "b1",
+            "Type": "Thermal",
+            "Production cost curve (MW)": [0, 200],
+            "Production cost curve (\$)": [0, 1000],
+            "Initial status (h)": -24,
+            "Initial power (MW)": 0
+        },
+        "g2": {
+            "Bus": "b1",
+            "Type": "Thermal",
+            "Production cost curve (MW)": [0, 300],
+            "Production cost curve (\$)": [0, 3000],
+            "Initial status (h)": -24,
+            "Initial power (MW)": 0
+        }
+    }
+}
+""";
+
+# Next, we write it to `example.json`.
+
+open("example.json", "w") do file
+    return write(file, json_contents)
+end;
+
+# Now that we have the input file, we can proceed as before, but using `UnitCommitment.read` instead of `UnitCommitment.read_benchmark`:
+
+instance = UnitCommitment.read("example.json");
+model =
+    UnitCommitment.build_model(instance = instance, optimizer = HiGHS.Optimizer);
+UnitCommitment.optimize!(model)
+
+# Finally, we extract and display the solution:
+
+solution = UnitCommitment.solution(model)
+
+#
+
+@show solution["Thermal production (MW)"]["g1"]
+
+#
+
+@show solution["Thermal production (MW)"]["g2"]
+
+# ## Solving a custom stochastic instance
+
+# In addition to deterministic test cases, UnitCommitment.jl can also solve two-stage stochastic instances of the problem. In this section, we demonstrate the most simple form, which builds a single (extensive form) model containing information for all scenarios. See [Decomposition](../tutorials/decomposition.md) for more advanced methods.
+
+# First, we need to create one JSON input file for each scenario. Parameters that are allowed to change across scenarios are marked as "uncertain" in the [JSON data format](../guides/format.md) page. It is also possible to specify the name and weight of each scenario, as shown below.
+
+# We start by creating `example_s1.json`, the first scenario file:
+
+json_contents_s1 = """
+{
+    "Parameters": {
+        "Version": "0.4",
+        "Time horizon (h)": 4,
+        "Scenario name": "s1",
+        "Scenario weight": 3.0
+    },
+    "Buses": {
+        "b1": {
+            "Load (MW)": [100, 150, 200, 250]
+        }
+    },
+    "Generators": {
+        "g1": {
+            "Bus": "b1",
+            "Type": "Thermal",
+            "Production cost curve (MW)": [0, 200],
+            "Production cost curve (\$)": [0, 1000],
+            "Initial status (h)": -24,
+            "Initial power (MW)": 0
+        },
+        "g2": {
+            "Bus": "b1",
+            "Type": "Thermal",
+            "Production cost curve (MW)": [0, 300],
+            "Production cost curve (\$)": [0, 3000],
+            "Initial status (h)": -24,
+            "Initial power (MW)": 0
+        }
+    }
+}
+"""
+open("example_s1.json", "w") do file
+    return write(file, json_contents_s1)
+end;
+
+# Next, we create `example_s2.json`, the second scenario file:
+
+json_contents_s2 = """
+{
+    "Parameters": {
+        "Version": "0.4",
+        "Time horizon (h)": 4,
+        "Scenario name": "s2",
+        "Scenario weight": 1.0
+    },
+    "Buses": {
+        "b1": {
+            "Load (MW)": [200, 300, 400, 500]
+        }
+    },
+    "Generators": {
+        "g1": {
+            "Bus": "b1",
+            "Type": "Thermal",
+            "Production cost curve (MW)": [0, 200],
+            "Production cost curve (\$)": [0, 1000],
+            "Initial status (h)": -24,
+            "Initial power (MW)": 0
+        },
+        "g2": {
+            "Bus": "b1",
+            "Type": "Thermal",
+            "Production cost curve (MW)": [0, 300],
+            "Production cost curve (\$)": [0, 3000],
+            "Initial status (h)": -24,
+            "Initial power (MW)": 0
+        }
+    }
+}
+""";
+open("example_s2.json", "w") do file
+    return write(file, json_contents_s2)
+end;
+
+# Now that we have our two scenario files, we can read them using `UnitCommitment.read`. Note that, instead of a single file, we now provide a list.
+
+instance = UnitCommitment.read(["example_s1.json", "example_s2.json"])
+
+# If we have a large number of scenario files, the [Glob](https://github.com/vtjnash/Glob.jl) package can also be used to avoid having to list them individually:
+
+using Glob
+instance = UnitCommitment.read(glob("example_s*.json"))
+
+# Finally, we build the model and optimize as before:
+
+model =
+    UnitCommitment.build_model(instance = instance, optimizer = HiGHS.Optimizer);
+UnitCommitment.optimize!(model)
+
+# The solution to stochastic instances follows a slightly different format, as shown below:
+
+solution = UnitCommitment.solution(model)
+
+# The solution for each scenario can be accessed through `solution[scenario_name]`. For conveniance, this includes both first- and second-stage optimal decisions:
+
+solution["s1"]

docs/src/tutorials/utils.jl

@@ -0,0 +1,74 @@
+
+# ## Generating initial conditions
+
+# When creating random unit commitment instances for benchmark purposes, it is often hard to compute, in advance, sensible initial conditions for all thermal generators. Setting initial conditions naively (for example, making all generators initially off and producing no power) can easily cause the instance to become infeasible due to excessive ramping. Initial conditions can also make it hard to modify existing instances. For example, increasing the system load without carefully modifying the initial conditions may make the problem infeasible or unrealistically challenging to solve.
+
+# To help with this issue, UC.jl provides a utility function which can generate feasible initial conditions by solving a single-period optimization problem. To illustrate its usage, we first generate a JSON file without initial conditions:
+
+json_contents = """
+{
+    "Parameters": {
+        "Version": "0.4",
+        "Time horizon (h)": 4
+    },
+    "Buses": {
+        "b1": {
+            "Load (MW)": [100, 150, 200, 250]
+        }
+    },
+    "Generators": {
+        "g1": {
+            "Bus": "b1",
+            "Type": "Thermal",
+            "Production cost curve (MW)": [0, 200],
+            "Production cost curve (\$)": [0, 1000]
+        },
+        "g2": {
+            "Bus": "b1",
+            "Type": "Thermal",
+            "Production cost curve (MW)": [0, 300],
+            "Production cost curve (\$)": [0, 3000]
+        }
+    }
+}
+""";
+open("example_initial.json", "w") do file
+    return write(file, json_contents)
+end;
+
+# Next, we read the instance and generate the initial conditions (in-place):
+
+instance = UnitCommitment.read("example_initial.json")
+UnitCommitment.generate_initial_conditions!(instance, HiGHS.Optimizer)
+
+# Finally, we optimize the resulting problem:
+
+model =
+    UnitCommitment.build_model(instance = instance, optimizer = HiGHS.Optimizer)
+UnitCommitment.optimize!(model)
+
+# !!! warning
+
+#     The function `generate_initial_conditions!` may return different initial conditions after each call, even if the same instance and the same optimizer is provided. The particular algorithm may also change in a future version of UC.jl. For these reasons, it is recommended that you generate initial conditions exactly once for each instance and store them for later use.
+
+# ## 6. Verifying solutions
+
+# When developing new formulations, it is very easy to introduce subtle errors in the model that result in incorrect solutions. To help avoiding this, UC.jl includes a utility function that verifies if a given solution is feasible, and, if not, prints all the validation errors it found. The implementation of this function is completely independent from the implementation of the optimization model, and therefore can be used to validate it.
+
+# ```jldoctest; output = false
+# using JSON
+# using UnitCommitment
+
+# # Read instance
+# instance = UnitCommitment.read("example/s1.json")
+
+# # Read solution (potentially produced by other packages)
+# solution = JSON.parsefile("example/out.json")
+
+# # Validate solution and print validation errors
+# UnitCommitment.validate(instance, solution)
+
+# # output
+
+# true
+# ```

docs/usage.md

@@ -1,149 +0,0 @@
-```{sectnum}
----
-start: 1
-depth: 2
-suffix: .
----
-```
-
-Usage
-=====
-
-Installation
-------------
-
-UnitCommitment.jl was tested and developed with [Julia 1.6](https://julialang.org/). To install Julia, please follow the [installation guide on the official Julia website](https://julialang.org/downloads/platform.html). To install UnitCommitment.jl, run the Julia interpreter, type `]` to open the package manager, then type:
-
-```text
-pkg> add UnitCommitment@0.2
-```
-
-To test that the package has been correctly installed, run:
-
-```text
-pkg> test UnitCommitment
-```
-
-If all tests pass, the package should now be ready to be used by any Julia script on the machine.
-
-To solve the optimization models, a mixed-integer linear programming (MILP) solver is also required. Please see the [JuMP installation guide](https://jump.dev/JuMP.jl/stable/installation/) for more instructions on installing a solver. Typical open-source choices are [Cbc](https://github.com/JuliaOpt/Cbc.jl) and [GLPK](https://github.com/JuliaOpt/GLPK.jl). In the instructions below, Cbc will be used, but any other MILP solver listed in JuMP installation guide should also be compatible.
-
-Typical Usage
--------------
-
-### Solving user-provided instances
-
-The first step to use UC.jl is to construct a JSON file describing your unit commitment instance. See [Data Format](format.md) for a complete description of the data format UC.jl expects. The next steps, as shown below, are to: (1) read the instance from file; (2) construct the optimization model; (3) run the optimization; and (4) extract the optimal solution.
-
-```julia
-using Cbc
-using JSON
-using UnitCommitment
-
-# 1. Read instance
-instance = UnitCommitment.read("/path/to/input.json")
-
-# 2. Construct optimization model
-model = UnitCommitment.build_model(
-    instance=instance,
-    optimizer=Cbc.Optimizer,
-)
-
-# 3. Solve model
-UnitCommitment.optimize!(model)
-
-# 4. Write solution to a file
-solution = UnitCommitment.solution(model)
-UnitCommitment.write("/path/to/output.json", solution)
-```
-
-### Solving benchmark instances
-
-UnitCommitment.jl contains a large number of benchmark instances collected from the literature and converted into a common data format. To solve one of these instances individually, instead of constructing your own, the function `read_benchmark` can be used, as shown below. See [Instances](instances.md) for the complete list of available instances.
-
-```julia
-using UnitCommitment
-instance = UnitCommitment.read_benchmark("matpower/case3375wp/2017-02-01")
-```
-
-Advanced usage
---------------
-
-### Customizing the formulation
-
-By default, `build_model` uses a formulation that combines modeling components from different publications, and that has been carefully tested, using our own benchmark scripts, to provide good performance across a wide variety of instances. This default formulation is expected to change over time, as new methods are proposed in the literature. You can, however, construct your own formulation, based on the modeling components that you choose, as shown in the next example.
-
-```julia
-using Cbc
-using UnitCommitment
-
-import UnitCommitment:
-    Formulation,
-    KnuOstWat2018,
-    MorLatRam2013,
-    ShiftFactorsFormulation
-
-instance = UnitCommitment.read_benchmark(
-    "matpower/case118/2017-02-01",
-)
-
-model = UnitCommitment.build_model(
-    instance = instance,
-    optimizer = Cbc.Optimizer,
-    formulation = Formulation(
-        pwl_costs = KnuOstWat2018.PwlCosts(),
-        ramping = MorLatRam2013.Ramping(),
-        startup_costs = MorLatRam2013.StartupCosts(),
-        transmission = ShiftFactorsFormulation(
-            isf_cutoff = 0.005,
-            lodf_cutoff = 0.001,
-        ),
-    ),
-)
-```
-
-### Generating initial conditions
-
-When creating random unit commitment instances for benchmark purposes, it is often hard to compute, in advance, sensible initial conditions for all generators. Setting initial conditions naively (for example, making all generators initially off and producing no power) can easily cause the instance to become infeasible due to excessive ramping. Initial conditions can also make it hard to modify existing instances. For example, increasing the system load without carefully modifying the initial conditions may make the problem infeasible or unrealistically challenging to solve.
-
-To help with this issue, UC.jl provides a utility function which can generate feasible initial conditions by solving a single-period optimization problem, as shown below:
-
-```julia
-using Cbc
-using UnitCommitment
-
-# Read original instance
-instance = UnitCommitment.read("instance.json")
-
-# Generate initial conditions (in-place)
-UnitCommitment.generate_initial_conditions!(instance, Cbc.Optimizer)
-
-# Construct and solve optimization model
-model = UnitCommitment.build_model(
-    instance=instance,
-    optimizer=Cbc.Optimizer,
-)
-UnitCommitment.optimize!(model)
-```
-
-```{warning}
-The function `generate_initial_conditions!` may return different initial conditions after each call, even if the same instance and the same optimizer is provided. The particular algorithm may also change in a future version of UC.jl. For these reasons, it is recommended that you generate initial conditions exactly once for each instance and store them for later use.
-```
-    
-### Verifying solutions
-
-When developing new formulations, it is very easy to introduce subtle errors in the model that result in incorrect solutions. To help with this, UC.jl includes a utility function that verifies if a given solution is feasible, and, if not, prints all the validation errors it found. The implementation of this function is completely independent from the implementation of the optimization model, and therefore can be used to validate it. The function can also be used to verify solutions produced by other optimization packages, as long as they follow the [UC.jl data format](format.md).
-
-```julia
-using JSON
-using UnitCommitment
-
-# Read instance
-instance = UnitCommitment.read("instance.json")
-
-# Read solution (potentially produced by other packages) 
-solution = JSON.parsefile("solution.json")
-
-# Validate solution and print validation errors
-UnitCommitment.validate(instance, solution)
-```

instances/README.md

@@ -1,53 +0,0 @@
-Instances
-=========
-
-UnitCommitment.jl provides a large collection of benchmark instances collected
-from the literature and converted to a common data format. If you use these instances in your research, we request that you cite UnitCommitment.jl, as well as the original sources, as listed below. [See documentation for more details](https://anl-ceeesa.github.io/UnitCommitment.jl/).
-
-References
-----------
-
-### UnitCommitment.jl
-
-* [UCJL] **Alinson S. Xavier, Feng Qiu.** "UnitCommitment.jl: A Julia/JuMP Optimization Package for Security-Constrained Unit Commitment". Zenodo (2020). [DOI: 10.5281/zenodo.4269874](https://doi.org/10.5281/zenodo.4269874)
-
-
-### MATPOWER
-
-* [MTPWR] **D. Zimmerman, C. E. Murillo-Sandnchez and R. J. Thomas.** "Matpower:  Steady-state  operations,  planning,  and  analysis  tools  forpower systems research and education", IEEE Transactions on PowerSystems, vol. 26, no. 1, pp. 12 –19, Feb. 2011. [DOI: 10.1109/TPWRS.2010.2051168](https://doi.org/10.1109/TPWRS.2010.2051168)
-
-* [PSTCA] **University of Washington, Dept. of Electrical Engineering.** "Power Systems Test Case Archive". Available at: <http://www.ee.washington.edu/research/pstca/> (Accessed: Nov 14, 2020)
-
-* [JoFlMa16] **C. Josz, S. Fliscounakis, J. Maeght, and P. Panciatici.** "AC Power Flow
-Data in MATPOWER and QCQP Format: iTesla, RTE Snapshots, and PEGASE". [ArXiv (2016)](https://arxiv.org/abs/1603.01533).
-
-* [FlPaCa13] **S. Fliscounakis, P. Panciatici, F. Capitanescu, and L. Wehenkel.**
-"Contingency ranking with respect to overloads in very large power
-systems taking into account uncertainty, preventive and corrective
-actions", Power Systems, IEEE Trans. on, (28)4:4909-4917, 2013.
-[DOI: 10.1109/TPWRS.2013.2251015](https://doi.org/10.1109/TPWRS.2013.2251015)
-
-
-### PGLIB-UC
-
-* [PGLIB] **Carleton Coffrin and Bernard Knueven.** "Power Grid Lib - Unit Commitment". Available at: <https://github.com/power-grid-lib/pglib-uc> (Accessed: Nov 14, 2020)
-
-* [KrHiOn12] **Eric Krall, Michael Higgins and Richard P. O’Neill.** "RTO unit commitment test system." Federal Energy Regulatory Commission. Available at: <https://www.ferc.gov/industries-data/electric/power-sales-and-markets/increasing-efficiency-through-improved-software-1> (Accessed: Nov 14, 2020)
-
-* [KnOsWa20] **Bernard Knueven, James Ostrowski and Jean-Paul Watson.** "On Mixed-Integer Programming Formulations for the Unit Commitment Problem". INFORMS Journal on Computing (2020). [DOI: 10.1287/ijoc.2019.0944](https://doi.org/10.1287/ijoc.2019.0944)
-
-### RTS-GMLC
-
-* https://github.com/GridMod/RTS-GMLC
-
-* [BaBlEh19] **Clayton Barrows, Aaron Bloom, Ali Ehlen, Jussi Ikaheimo, Jennie Jorgenson, Dheepak Krishnamurthy, Jessica Lau et al.** "The IEEE Reliability Test System: A Proposed 2019 Update." IEEE Transactions on Power Systems (2019). [DOI: 10.1109/TPWRS.2019.2925557](https://doi.org/10.1109/TPWRS.2019.2925557)
-
-### OR-LIB
-
-* [ORLIB] **J.E.Beasley.** "OR-Library: distributing test problems by electronic mail", Journal of the Operational Research Society 41(11) (1990). [DOI: 10.2307/2582903](https://doi.org/10.2307/2582903)
-
-* [FrGe06] **A. Frangioni, C. Gentile.** "Solving nonlinear single-unit commitment problems with ramping constraints" Operations Research 54(4), p. 767 - 775, 2006. [DOI: 10.1287/opre.1060.0309](https://doi.org/10.1287/opre.1060.0309)
-
-### Tejada19
-
-* [TeLuSa19] **D. A. Tejada-Arango, S. Lumbreras, P. Sanchez-Martin and A. Ramos.** "Which Unit-Commitment Formulation is Best? A Systematic Comparison," in IEEE Transactions on Power Systems. [DOI: 10.1109/TPWRS.2019.2962024](https://ieeexplore.ieee.org/document/8941313/).