ltbams 0.9.9__py3-none-any.whl → 1.0.2a1__py3-none-any.whl

docs/source/getting_started/formats/pypower.rst

@@ -0,0 +1,223 @@
+.. _input-pypower:
+
+PYPOWER
+--------
+
+AMS includes `PYPOWER cases <https://github.com/CURENT/ams/tree/develop/ams/cases/pypower>`_
+in version 2 for scheduling modeling and analysis. PYPOWER cases follow the same format as MATPOWER.
+
+The PYPOWER case is defined as a Python dictionary that includes ``bus``, ``gen``, ``branch``,
+``areas``, and ``gencost``.
+Defines the PYPOWER case file format.
+
+A PYPOWER case file is a Python file or MAT-file that defines or returns a dict named ``ppc``, referred to
+as a "PYPOWER case dict". The keys of this dict are ``bus``, ``gen``, ``branch``, ``areas``, and
+``gencost``.
+With the exception of C{baseMVA}, a scalar, each data variable is an array, where a row corresponds
+to a single bus, branch, gen, etc. The format of the data is similar to the PTI format described in
+`PTI Load Flow Data Format <http://www.ee.washington.edu/research/pstca/formats/pti.txt>`_.
+
+
+Example Case9
+~~~~~~~~~~~~~~~~~~
+
+.. code:: python
+
+    ppc = {"version": '2'}
+
+    ##-----  Power Flow Data  -----##
+    ## system MVA base
+    ppc["baseMVA"] = 100.0
+
+    ## bus data
+    # bus_i type Pd Qd Gs Bs area Vm Va baseKV zone Vmax Vmin
+    ppc["bus"] = array([
+        [1, 3, 0,    0, 0, 0, 1, 1, 0, 345, 1, 1.1, 0.9],
+        [2, 2, 0,    0, 0, 0, 1, 1, 0, 345, 1, 1.1, 0.9],
+        [3, 2, 0,    0, 0, 0, 1, 1, 0, 345, 1, 1.1, 0.9],
+        [4, 1, 0,    0, 0, 0, 1, 1, 0, 345, 1, 1.1, 0.9],
+        [5, 1, 90,  30, 0, 0, 1, 1, 0, 345, 1, 1.1, 0.9],
+        [6, 1, 0,    0, 0, 0, 1, 1, 0, 345, 1, 1.1, 0.9],
+        [7, 1, 100, 35, 0, 0, 1, 1, 0, 345, 1, 1.1, 0.9],
+        [8, 1, 0,    0, 0, 0, 1, 1, 0, 345, 1, 1.1, 0.9],
+        [9, 1, 125, 50, 0, 0, 1, 1, 0, 345, 1, 1.1, 0.9]
+    ])
+
+    ## generator data
+    # bus, Pg, Qg, Qmax, Qmin, Vg, mBase, status, Pmax, Pmin, Pc1, Pc2,
+    # Qc1min, Qc1max, Qc2min, Qc2max, ramp_agc, ramp_10, ramp_30, ramp_q, apf
+    ppc["gen"] = array([
+        [1, 0,   0, 300, -300, 1, 100, 1, 250, 10, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
+        [2, 163, 0, 300, -300, 1, 100, 1, 300, 10, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
+        [3, 85,  0, 300, -300, 1, 100, 1, 270, 10, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
+    ])
+
+    ## branch data
+    # fbus, tbus, r, x, b, rateA, rateB, rateC, ratio, angle, status, angmin, angmax
+    ppc["branch"] = array([
+        [1, 4, 0,      0.0576, 0,     250, 250, 250, 0, 0, 1, -360, 360],
+        [4, 5, 0.017,  0.092,  0.158, 250, 250, 250, 0, 0, 1, -360, 360],
+        [5, 6, 0.039,  0.17,   0.358, 150, 150, 150, 0, 0, 1, -360, 360],
+        [3, 6, 0,      0.0586, 0,     300, 300, 300, 0, 0, 1, -360, 360],
+        [6, 7, 0.0119, 0.1008, 0.209, 150, 150, 150, 0, 0, 1, -360, 360],
+        [7, 8, 0.0085, 0.072,  0.149, 250, 250, 250, 0, 0, 1, -360, 360],
+        [8, 2, 0,      0.0625, 0,     250, 250, 250, 0, 0, 1, -360, 360],
+        [8, 9, 0.032,  0.161,  0.306, 250, 250, 250, 0, 0, 1, -360, 360],
+        [9, 4, 0.01,   0.085,  0.176, 250, 250, 250, 0, 0, 1, -360, 360]
+    ])
+
+    ##-----  OPF Data  -----##
+    ## area data
+    # area refbus
+    ppc["areas"] = array([
+        [1, 5]
+    ])
+
+    ## generator cost data
+    # 1 startup shutdown n x1 y1 ... xn yn
+    # 2 startup shutdown n c(n-1) ... c0
+    ppc["gencost"] = array([
+        [2, 1500, 0, 3, 0.11,   5,   150],
+        [2, 2000, 0, 3, 0.085,  1.2, 600],
+        [2, 3000, 0, 3, 0.1225, 1,   335]
+    ])
+
+
+Version Information
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+There are two versions of the PYPOWER case file format. The current
+version of PYPOWER uses version 2 of the PYPOWER case format
+internally and includes a ``version`` field with a value of ``2`` to make
+the version explicit. Earlier versions of PYPOWER used the version 1
+case format, which defined the data matrices as individual variables,
+as opposed to keys of a dict. Case files in version 1 format with
+OPF data also included an (unused) ``areas`` variable. While the version 1
+format has now been deprecated, it is still handled automatically by
+``loadcase`` and ``savecase`` which are able to load and save case files in both
+version 1 and version 2 formats.
+
+See also doc for `idx_bus`, `idx_brch`, `idx_gen`, `idx_area` and `idx_cost`
+regarding constants which can be used as named column indices for the data
+matrices. Also described in the first three are additional results columns
+that are added to the bus, branch, and gen matrices by the power flow and OPF
+solvers.
+
+The case dict also allows for additional fields to be included.
+The OPF is designed to recognize fields named ``A``, ``l``, ``u``, ``H``, ``Cw``,
+``N``, ``fparm``, ``z0``, ``zl``, and ``zu`` as parameters used to directly extend
+the OPF formulation (see doc for `opf` for details). Other user-defined fields may
+also be included and will be automatically loaded by the ``loadcase`` function
+and, given an appropriate 'savecase' callback function (see doc for
+`add_userfcn`), saved by the ``savecase`` function.
+
+
+Bus
+~~~~~~~~~
+
+#.  bus number (positive integer)
+#.  bus type
+    - PQ bus = 1
+    - PV bus = 2
+    - reference bus = 3
+    - isolated bus = 4
+#.  ``Pd``, real power demand (MW)
+#.  ``Qd``, reactive power demand (MVAr)
+#.  ``Gs``, shunt conductance (MW demanded at V = 1.0 p.u.)
+#.  ``Bs``, shunt susceptance (MVAr injected at V = 1.0 p.u.)
+#.  area number (positive integer)
+#.  ``Vm``, voltage magnitude (p.u.)
+#.  ``Va``, voltage angle (degrees)
+#.  ``baseKV``, base voltage (kV)
+#.  ``zone``, loss zone (positive integer)
+#.  ``maxVm``, maximum voltage magnitude (p.u.)
+#.  ``minVm``, minimum voltage magnitude (p.u.)
+
+Generator
+~~~~~~~~~~~~~~~~~~
+
+#.  bus number
+#.  ``Pg``, real power output (MW)
+#.  ``Qg``, reactive power output (MVAr)
+#.  ``Qmax``, maximum reactive power output (MVAr)
+#.  ``Qmin``, minimum reactive power output (MVAr)
+#.  ``Vg``, voltage magnitude setpoint (p.u.)
+#.  ``mBase``, total MVA base of this machine, defaults to baseMVA
+#.  status
+    - ``>  0`` - machine in service
+    - ``<= 0`` - machine out of service
+#.  ``Pmax``, maximum real power output (MW)
+#.  ``Pmin``, minimum real power output (MW)
+#.  ``Pc1``, lower real power output of PQ capability curve (MW)
+#.  ``Pc2``, upper real power output of PQ capability curve (MW)
+#.  ``Qc1min``, minimum reactive power output at Pc1 (MVAr)
+#.  ``Qc1max``, maximum reactive power output at Pc1 (MVAr)
+#.  ``Qc2min``, minimum reactive power output at Pc2 (MVAr)
+#.  ``Qc2max``, maximum reactive power output at Pc2 (MVAr)
+#.  ramp rate for load following/AGC (MW/min)
+#.  ramp rate for 10-minute reserves (MW)
+#.  ramp rate for 30-minute reserves (MW)
+#.  ramp rate for reactive power (2-sec timescale) (MVAr/min)
+#.  APF, area participation factor
+
+
+Branch
+~~~~~~~~~
+
+#.  ``f``, from bus number
+#.  ``t``, to bus number
+#.  ``r``, resistance (p.u.)
+#.  ``x``, reactance (p.u.)
+#.  ``b``, total line charging susceptance (p.u.)
+#.  ``rateA``, MVA rating A (long-term rating)
+#.  ``rateB``, MVA rating B (short-term rating)
+#.  ``rateC``, MVA rating C (emergency rating)
+#.  ``ratio``, transformer off nominal turns ratio (``= 0`` for lines)
+#.  ``angle``, transformer phase shift angle (degrees), positive -> delay
+
+    -  (Gf, shunt conductance at from bus p.u.)
+    -  (Bf, shunt susceptance at from bus p.u.)
+    -  (Gt, shunt conductance at to bus p.u.)
+    -  (Bt, shunt susceptance at to bus p.u.)
+#.  initial branch status, 1 - in service, 0 - out of service
+#.  minimum angle difference, angle(Vf) - angle(Vt) (degrees)
+#.  maximum angle difference, angle(Vf) - angle(Vt) (degrees)
+
+
+Generator Cost
+~~~~~~~~~~~~~~~~~~
+
+.. note::
+
+   If ``gen`` has ``ng`` rows, then the first ``ng`` rows of ``gencost`` contain
+   the cost for active power produced by the corresponding generators.
+   If ``gencost`` has :math:`2 \times ng` rows then rows :math:`ng + 1` to :math:`2 \times ng`
+   contain the reactive power costs in the same format.
+
+#.  ``model``, 1 - piecewise linear, 2 - polynomial
+#.  ``startup``, startup cost in US dollars
+#.  ``shutdown``, shutdown cost in US dollars
+#.  ``N``, number of cost coefficients to follow for polynomial cost function,
+    or number of data points for piecewise linear.
+    The following parameters define the total cost function ``f(p)``,
+    where units of ``f`` and ``p`` are $/hr and MW (or MVAr), respectively.
+
+    -  For MODEL = 1: ``p0, f0, p1, f1, ..., pn, fn``
+       where ``p0 < p1 < ... < pn`` and the cost ``f(p)`` is defined by
+       the coordinates ``(p0,f0), (p1,f1), ..., (pn,fn)`` of the
+       end/break-points of the piecewise linear cost function.
+    -  For MODEL = 2: ``cn, ..., c1, c0``
+       ``n + 1`` coefficients of an ``n``-th order polynomial cost function,
+       starting with the highest order, where cost is
+       :math:`f(p) = c_n \times p^n + \ldots + c_1 \times p + c_0`.
+
+
+Area (deprecated)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. note::
+
+   This data is not used by PYPOWER and is no longer necessary for version 2 case files with OPF data.
+
+#.  ``i``, area number
+#.  ``price_ref_bus``, reference bus for that area

docs/source/getting_started/formats/xlsx.rst

@@ -0,0 +1,23 @@
+.. _input-xlsx:
+
+AMS xlsx
+----------
+
+The AMS xlsx format allows one to use Excel for convenient viewing and
+editing. If you do not use Excel, there are alternatives such as the free and
+open-source `LibreOffice <https://www.libreoffice.org>`_.
+
+Format definition
+.................
+
+The AMS xlsx format contains multiple workbooks (also known as "sheets") shown
+as tabs at the bottom. The name of a workbook is a *model* name, and each
+workbook contains the parameters of all *devices* that are *instances* of the
+model.
+
+.. image:: xlsx.png
+   :width: 700
+   :alt: Example of an AMS xlsx file
+
+Benefiting from a consistent format style, data manipulation is similar to that in 
+`ANDES xlsx <http://andes.rtfd.io/en/latest/getting_started/formats/xlsx.html>`_.

docs/source/getting_started/index.rst

@@ -0,0 +1,76 @@
+
+.. raw:: html
+
+   <embed>
+   <h1 style="letter-spacing: 0.4em; font-size: 2.5em !important;
+   margin-bottom: 0; padding-bottom: 0"> AMS </h1>
+
+   <p style="color: #00746F; font-variant: small-caps; font-weight: bold;
+   margin-bottom: 2em">
+   Python Library for Flexible Scheduling Modeling and Co-Simulation with Dynamics</p>
+   </embed>
+
+.. _getting-started:
+
+===============
+Getting started
+===============
+
+.. toctree::
+    :maxdepth: 3
+    :hidden:
+
+    overview
+    install
+    formats/index
+    testcase
+    verification
+    copyright
+
+Quick install
+=============
+
+.. panels::
+    :card: + install-card
+    :column: col-lg-6 col-md-6 col-sm-12 col-xs-12 p-3
+
+    Working with conda?
+    ^^^^^^^^^^^^^^^^^^^
+    AMS will available on conda-forge and can be installed with
+    Anaconda, Miniconda, and Mambaforge:
+
+    ++++++++++++++++++++++
+
+    .. code-block:: bash
+
+        conda install -c conda-forge ltbams
+
+    ---
+
+    Prefer pip?
+    ^^^^^^^^^^^
+
+    AMS will be installed via pip from `PyPI <https://pypi.org/project/ltbams>`__.
+
+    ++++
+
+    .. code-block:: bash
+
+        pip install ltbams
+
+    ---
+    :column: col-12 p-3
+
+    New to Python?
+    ^^^^^^^^^^^^^^
+    Set up a Mambaforge environment following :ref:`Setup Mambaforge`. We
+    recommend Mambaforge on Windows and Apple Silicon for new users.
+
+    ---
+    :column: col-12 p-3
+
+    Are you a developer?
+    ^^^^^^^^^^^^^^^^^^^^
+
+    Installing from source? Looking to develop models? Check the
+    guide in :ref:`Develop Install`.

docs/source/getting_started/install.rst

@@ -0,0 +1,234 @@
+.. _install:
+
+************
+Installation
+************
+
+New to Python
+=============
+
+.. _Setup Mambaforge:
+
+Setting Up Mambaforge
+---------------------
+If you are new to Python and want to get started quickly, you can use
+Mambaforge, which is a conda-like package manager configured with conda-forge.
+
+Step 1:
+
+Downloaded the latest Mambaforge for your platform from
+https://github.com/conda-forge/miniforge#mambaforge.
+Most users will use ``x86_64(amd64)`` for Intel and AMD processors.
+Mac users with Apple Silicon should use ``arm64(Apple Silicon)``
+for best performance.
+
+Next, complete the Mambaforge installation on your system.
+
+.. note::
+
+    Mambaforge is a drop-in replacement for conda. If you have an existing
+    conda installation, you can replace all following ``mamba`` commands
+    with ``conda`` and achieve the same functionality.
+
+    If you are using Anaconda or Miniconda on Windows, you should open
+    ``Anaconda Prompt`` instead of ``Miniforge Prompt``.
+
+Step 2:
+
+Open Terminal (on Linux or maxOS) or `Miniforge Prompt` (on Windows, **not cmd!!**).
+Make sure you are in a conda environment - you should see ``(base)`` prepended to the
+command-line prompt, such as ``(base) C:\Users\username>``.
+
+Create an environment for AMS (recommended)
+
+.. code:: bash
+
+     mamba create --name ams python=3.8
+
+Activate the new environment with
+
+.. code:: bash
+
+     mamba activate ams
+
+.. note::
+
+    You will need to activate the ``ams`` environment every time
+    in a new Miniforge Prompt or shell.
+
+If these steps complete without error, you now have a working Python environment.
+See the commands at the top to :ref:`getting-started` AMS.
+
+.. _Install_extras:
+
+Extra support package
+=====================
+
+Some AMS features require extra support packages, which are not installed by
+default. For example, to build the documentation, one will need to install
+development packages. Other packages will be required for interoperability.
+
+The extra support packages are specified in groups. The following group names
+are supported, with descriptions given below:
+
+- ``dev``: packages to support development such as testing and documentation
+
+.. note::
+
+    TODO: Extra support packages are not supported by conda/mamba installation. One
+    needs to install AMS with ``pip``.
+
+To install packages in the ``dev`` when installing AMS, do:
+
+.. code:: bash
+
+    pip install ltbams[dev]
+
+To install all extra packages, do:
+
+.. code:: bash
+
+    pip install ltbams[all]
+
+One can also inspect the ``requirements-extra.txt`` to identify the packages
+for manual installation.
+
+.. _Develop Install:
+
+Develop Install
+===============
+
+The development mode installation is for users who want to modify
+the code and, for example, develop new models or routines.
+The benefit of development mode installation is that
+changes to source code will be reflected immediately without re-installation.
+
+Step 1: Get AMS source code
+
+As a developer, you are strongly encouraged to clone the source code using ``git``
+from either your fork or the original repository. Clone the repository with
+
+.. code:: bash
+
+    git clone https://github.com/CURENT/ams
+
+.. note::
+
+    Replace the URL with yours to use your fork. With ``git``, you can later easily
+    update the source code and perform version control.
+
+Alternatively, you can download the AMS source code from
+https://github.com/CURENT/ams and extract all files to the path of your
+choice. Although works, this method is discouraged because tracking changes and
+pushing back code edits will require significant manual efforts.
+
+.. _`Step 2`:
+
+Step 2: Install dependencies
+
+In the Mambaforge environment, use ``cd`` to change directory to the AMS root folder.
+The folder should contain the ``setup.py`` file.
+
+Install dependencies with
+
+.. code:: bash
+
+    mamba install --file requirements.txt
+    mamba install --file requirements-extra.txt
+
+Alternatively, you can install them with ``pip``:
+
+.. code:: bash
+
+    pip install -r requirements.txt
+    pip install -r requirements-extra.txt
+
+Step 3: Install AMS in the development mode using
+
+.. code:: bash
+
+      python3 -m pip install -e .
+
+Note the dot at the end. Pip will take care of the rest.
+
+.. note::
+
+    The AMS version number shown in ``pip list``
+    will stuck at the version that was intalled, unless
+    AMS is develop-installed again.
+    It will not update automatically with ``git pull``.
+
+    To check the latest version number, check the preamble
+    by running the ``ams`` command or chek the output of
+    ``python -c "import ams; print(ams.__version__)"``
+
+.. note::
+
+    AMS updates may infrequently introduce new package
+    requirements. If you see an ``ImportError`` after updating
+    AMS, you can manually install the missing dependencies
+    or redo `Step 2`_.
+
+.. note::
+
+    To install extra support packages, one can append ``[NAME_OF_EXTRA]`` to
+    ``pip install -e .``. For example, ``pip install -e .[doc]`` will
+    install packages to support documentation when installing AMS in the
+    development, editable mode.
+
+Updating AMS
+==============
+
+.. warning::
+
+    If AMS has been installed in the development mode using source code, you
+    will need to use ``git`` or the manual approach to update the source code.
+    In this case, Do not proceed with the following steps, as they will install
+    a separate site-package installation on top of the development one.
+
+Regular AMS updates will be pushed to both ``conda-forge`` and Python package index.
+It is recommended to use the latest version for bug fixes and new features.
+We also recommended you to check the :ref:`ReleaseNotes` before updating to stay informed
+of changes that might break your downstream code.
+
+Depending you how you installed AMS, you will use one of the following ways to upgrade.
+
+If you installed it from mamba or conda, run
+
+.. code:: bash
+
+    conda install -c conda-forge --yes ltbams
+
+If you install it from PyPI (namely, through ``pip``), run
+
+.. code:: bash
+
+    python3 -m pip install --yes ltbams
+
+
+Uninstall Multiple Copies
+=========================
+
+A common mistake new users make is to have multiple copies of AMS installed in
+the same environment. This can happen when one previously installed AMS in the
+development mode but later ran ``conda install`` or ``python3 -m pip install``
+to install the latest version. As a result, only the most recently installed
+version will be accessible.
+
+In this case, we recommend that you uninstall all version and reinstall only one
+copy using your preferred mode. Uninstalling all copies can be done by calling
+``conda remove ams`` and ``python3 -m pip uninstall ams``. The prompted path
+will indicate the copy to be removed. One may need to run the two commands for a
+couple of time until the package managers indicate that the ``ams`` package
+can no longer be found.
+
+Troubleshooting
+===============
+
+If you get an error message on Windows, reading ::
+
+    ImportError: DLL load failed: The specified module could not be found.
+
+It is a path issue of your Python. In fact, Python on Windows is so broken that
+many people are resorting to WSL2 just for Python. Fixes can be convoluted, but
+the easiest one is to install AMS in a Conda/Mambaforge environment.

docs/source/getting_started/overview.rst

@@ -0,0 +1,26 @@
+.. _package-overview:
+
+================
+Package Overview
+================
+
+AMS is an open-source packages for flexible scheduling modeling and co-simulation with
+the in-house dynanic simulation engine `ANDES <https://github.com/curent/andes>`_.
+
+AMS is currently under active development. To get involved,
+
+* Report issues in the
+  `GitHub issues page <https://github.com/CURENT/ams/issues>`_
+* Learn version control with
+  `the command-line git <https://git-scm.com/docs/gittutorial>`_ or
+  `GitHub Desktop <https://help.github.com/en/desktop/getting-started-with-github-desktop>`_
+
+This work was supported in part by the Engineering Research Center Program of
+the National Science Foundation and the Department of Energy under NSF Award
+Number EEC-1041877 and the CURENT_ Industry Partnership Program. AMS is made
+open source as part of the CURENT Large Scale Testbed project.
+
+AMS is developed and actively maintained by `Jinning Wang <https://jinningwang.github.io/>`_.
+See the GitHub repository for a full list of contributors.
+
+.. _CURENT: https://curent.utk.edu

docs/source/getting_started/testcase.rst

@@ -0,0 +1,45 @@
+.. _testcase:
+
+************
+Test cases
+************
+
+AMS ships with with test cases in the ``ams/cases`` folder.
+The cases can be found in the `online repository`_.
+
+.. _`online repository`: https://github.com/CURENT/ams/tree/master/ams/cases
+
+Summary
+=======
+
+Below is a summary of the folders and the corresponding test cases. Some folders
+contain a README file with notes. When viewing the case folder on GitHub, one
+can conveniently read the README file below the file listing.
+
+- ``5bus``: a small PJM 5-bus test case for power flow study [PJM5]_.
+- ``ieee14`` and ``ieee39``: the IEEE 14-bus and 39-bus test cases [IEEE]_.
+- ``ieee123``: the IEEE 123-bus test case [TSG]_.
+- ``matpower``: a subset of test cases from [MATPOWER]_.
+- ``npcc`` and ``wecc``: NPCC 140-bus and WECC 179-bus test cases [SciData]_.
+
+How to contribute
+=================
+
+We welcome the contribution of test cases! You can make a pull request to
+contribute new test cases. Please follow the structure in the ``cases`` folder
+and provide an example Jupyter notebook (see ``examples/demonstration``) to
+showcase the results of your system.
+
+.. [PJM5] F. Li and R. Bo, "Small test systems for power system economic
+        studies," IEEE PES General Meeting, 2010, pp. 1-4, doi:
+        10.1109/PES.2010.5589973.
+.. [IEEE] University of Washington, "Power Systems Test Case Archive", [Online]. Available:
+        https://labs.ece.uw.edu/pstca/
+.. [TSG] X. Wang, F. Li, Q. Zhang, Q. Shi and J. Wang, "Profit-Oriented BESS Siting
+        and Sizing in Deregulated Distribution Systems," in IEEE Transactions on Smart
+        Grid, vol. 14, no. 2, pp. 1528-1540, March 2023, doi: 10.1109/TSG.2022.3150768.
+.. [MATPOWER] R. D. Zimmerman, "MATPOWER", [Online]. Available:
+        https://matpower.org/
+.. [SciData] Q. Zhang and F. Li, “A Dataset for Electricity Market Studies on Western
+        and Northeastern Power Grids in the United States,” Scientific Data, vol. 10,
+        no. 1, p. 646, Sep. 2023, doi: 10.1038/s41597-023-02448-w.

docs/source/getting_started/verification.rst

@@ -0,0 +1,13 @@
+.. _verification:
+
+============
+Verification
+============
+
+This section presents the verification of AMS by comparing the DCOPF results
+with other tools.
+
+.. toctree::
+   :maxdepth: 2
+
+   ../_examples/verification/ams_dcopf_verification.ipynb