gridops
gridops is an open-source and customizable grid operations model for three major U.S. interconnections (Western, Eastern, and ERCOT). Production cost modeling in gridops utilizes linear DC Optimal Power Flow (DC-OPF) approximation to optimize hourly unit commitment (UC) and economic dispatch (ED) processes over a user-configurable rolling horizon.
Purpose
gridops was created to:
- Address weather and water dynamics and associated vulnerabilities in U.S. bulk power systems.
- Link with a wide range of hydrometeorological datasets and energy system/machine learning models to explore future uncertainty in grid operations.
- Analyze current and future grid stress and reliability trends under a wide range of weather conditions, generation mixes, and demand growth scenarios.
- Create simple and user-tailored representations of the U.S. interconnections to find a balance between model accuracy and run time to answer research questions of interest.
Installation
pip install gridops
Quickstart
import gridops as go
# Instantiate the model
model = go.Model(
region="west", # U.S. Western Interconnection
problem="linear", # Linear programming (economic dispatch only)
solver_name="appsi_highs", # Using open-source HiGHS solver
solver_params=None, # Optional – using default solver parameters
)
# Run for 7 days with a 24-hour rolling horizon
model.run(
config_file="example_config_file.yml", # Path to the model configuration file
n_days=7, # Running for 7 days
horizon_hours=24, # Optional – using default 24-hour horizon
)
Configuration file
gridops needs a YAML file that maps each input CSV and NPY files to their file path and each
output Parquet to its destination. Check out below for a minimal example (see
gridops/data/example_config_file.yml for a full template):
generator_parameters_file: Input/data_genparams.csv
line_parameters_file: Input/line_param.csv
# … all other input entries …
flow_file: Output/flow.parquet
mwh_file: Output/mwh.parquet
# … all other output entries …
restart_file_directory: Restart/
Supported solvers
| Solver | Interface | Notes |
|---|---|---|
| HiGHS | appsi_highs |
Open-source; installs automatically through the highspy dependency |
| Gurobi | appsi_gurobi or gurobi |
Commercial; requires a valid Gurobi license |
Users can pass any desired solver parameters via the solver_params:
model = go.Model(
solver_name="appsi_highs",
solver_params={"presolve": "on", "solver": "ipm", "time_limit": 3600},
...
)
License
BSD-2-Clause – See LICENSE.
Disclaimer
See DISCLAIMER.
Reference
If you use gridops, please cite the following article:
Akdemir, K. Z., Oikonomou, K., Kern, J. D., Voisin, N., Ssembatya, H., & Qian, J. (2024). An open-source framework for balancing computational speed and fidelity in production cost models. Environmental Research: Energy, 1(1), 015003. https://doi.org/10.1088/2753-3751/ad1751
Metadata
Release files for gridops 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gridops-1.1.0.tar.gz | 710.4 kB | With provenance | Details for gridops-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gridops-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for gridops-1.1.0-py3-none-any.whl |
Total release size: 1.4 MB
Release files / gridops-1.1.0.tar.gz
| Download URL | gridops-1.1.0.tar.gz |
|---|---|
| Size | 710.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fc277c8d76749298acea8e3633eeb5a38408f19e8e696db8d8fb4d5d21bcdf5
|
|
BLAKE2b-256 checksum How to use checksums |
be6ef95f86cce4c8cde8a36b65bde16a06419ecc83ae900364fc2d220a8957b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logRelease files / gridops-1.1.0-py3-none-any.whl
| Download URL | gridops-1.1.0-py3-none-any.whl |
|---|---|
| Size | 723.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d63f4a3c1d8d937549eb253cd4f0fac1987b68ece847a776e0367a67b28830f
|
|
BLAKE2b-256 checksum How to use checksums |
6dc8bade3e077450448385648a1049fa25c60bf09034f3caa8ab7086a37764c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logSecurity for gridops 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for gridops-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.