Spatial Configuration#
Configuring Spatial Scope#
PyPSA-USA allows for flexible configuration of the spatial scope of your energy model, enabling you to define the geographical area and level of detail for your simulations. The spatial scope is determined by the interconnect, model_topology configuration settings.
{interconnect}is used to select which of the three asynchronous interconnection to model. You can selectwestern,eastern,texas, orusato model the entire US.
After selecting your
{interconnect}, you can specifymodel_topology: include:to filter individual states or balancing authorities to be selected in your model.
Example: Modeling California#
To create a model that includes only California, you can specify the relevant ReEDS zone IDs (p8-11) as shown below. This will limit the spatial scope to the specified regions within California. Your interconnect could be set to western or usa.
model_topology:
include:
reeds_zone: ['p8', 'p9', 'p10', 'p11']
Alternatively, you can use the code reeds_state: ‘CA’ option to achieve the same result by specifying the entire state.
A complete, maintained California configuration ships with the repository as
workflow/repo_data/config/config.california.yaml. It pairs the footprint below with CPUC
SERVM demand, the RESOLVE CAISO interface limits, and enabled imports/exports:
scenario:
interconnect: [western]
planning_horizons: [2030, 2035, 2040, 2045] # CPUC SERVM forecast years
clusters: [4] # p8, p9, p10, p11
simpl: [75]
model_topology:
transmission_network: 'reeds'
topological_boundaries: 'reeds_zone'
interface_transmission_limits: true # RESOLVE CAISO interface caps
include:
reeds_state: ['CA']
clusters is pinned to 4 because the ReEDS zonal backbone cannot be clustered below the
number of zones in the footprint, and California holds exactly four.
To run the same footprint at county resolution, switch topological_boundaries to
county and raise clusters to 58 — the number of California counties, and the number of
p06xxx nodes in the county NARIS interface table. simpl: ['county'] selects the
county-FIPS fast path in cluster_simpl, so the resource layer is built directly on county
boundaries (a numeric simpl of at least 58 also works if you want more resource zones than
transmission nodes):
scenario:
clusters: [58] # 58 California counties
simpl: ['county'] # county-FIPS fast path
model_topology:
topological_boundaries: 'county'
add_extra_components switches from the balancing-area NARIS flowgate file to the county one
(transmission_capacity_init_AC_county_NARIS2024.csv) automatically when
topological_boundaries is county — no other key needs changing. config.california.yaml
carries this same block as a commented alternative.
In addition to filtering by reeds_zone and reeds_state, you can filter by reeds_ba, trans_reg, and nerc_reg shown graphically below.
Configuring Resource Resolution#
PyPSA-USA allows you to configure the resolution at which resources are built independently
from the resolution of the final transmission network, using the simpl and clusters
wildcards in the configuration file.
{simpl}sets the number of zones the network is clustered to early in the workflow (rulecluster_resources). Demand, renewable profiles, and generators are all built at this resolution.{clusters}sets the final transmission resolution (rulecluster_network), which aggregates the{simpl}-resolution network down to the zones the optimization runs on.
For example, if you want a transmission network with 10 nodes and a resource model with 100 nodes, you would configure it as follows:
scenario:
clusters: [10m]
simpl: [100]
This setup, using an m after the clusters wildcard, results in a model with 10 transmission nodes and 100 distinct renewable resource zones, allowing for more granular modeling of renewable resource distribution while keeping the transmission network simplified: only conventional generators are aggregated to the 10 transmission zones, while renewable resources remain at the 100 simpl zones. If you use a c after the clusters wildcard, the reverse applies — conventional resources from the simpl step will not be clustered, while all other resources are. If you input an a after the clusters wildcard, no resources will be clustered beyond the simpl level.
Configuring Transmission Resolution#
Transmission Network Selection#
You can specify the transmission network you want to use by setting the model_topology: transmission_network: option. There are two available options:
‘reeds’: The ReEDS NARIS networks.
‘tamu’: The synthetic BE-TAMU nodal network.
When selecting between the ReEDS NARIS networks, you will need to also specify the model_topology: topological_boundaries:. Currently you can set county, reeds_zone, or state (note that state does not support model_topology: include: regional filtering). To use the FERC 1000 regions, you will need to use the custom network topologies described in the example below.
Transmission Network Resolution#
If you are using the TAMU/BE network, you can flexibly set an arbitrary number of clusters between the min and max number of nodes. If using a ReEDS NARIS network, you need to specify the minimum number of clusters (nodes) for your modeled interconnection. The number of nodes for each zone is detailed in the table below.
If you’re working with custom configurations, PyPSA-USA will notify you during the cluster_network stage, indicating the correct number of nodes to set in the clusters configuration.
Spatial Scope |
Reeds Zones |
TAMU |
|---|---|---|
(Min Clusters) |
(Max Clusters) |
|
Western |
35 |
4,919 |
Texas |
7 |
1,338 |
Eastern |
92 |
35,304 |
USA |
134 |
41,561 |
Example: Meshed ReEDS NARIS WECC Topology#
If you would like to mesh the three ReEDS NARIS networks you can do so by using the model_topology: aggregate: option. For instance, to create a model where California is represented at a county level resolution, but Non-CA WECC areas are represented at the FERC 1000 level, you would configure the model as follows:
scenario:
interconnect: [western]
clusters: [87]
simpl: [380] # can be set differently based on number of resource zones you'd like to keep
model_topology:
transmission_network: 'reeds'
topological_boundaries: 'county'
interface_transmission_limits: false
include:
# nothing specified here since we are modeling the entire WECC
aggregate:
trans_grp: ['NorthernGrid_South', 'NorthernGrid_West', 'NorthernGrid_East', 'WestConnect_North','WestConnect_South']
This configuration will copper plate the Non-CA regions listed under trans_grp, effectively creating a copper-plate network where resources can be clustered and shared across the region. Using these custom aggregation requires information on the region memberships which you can find in workflow/repo_data/ReEDS_Constraints/membership.csv.