Nodes (nodes)

A model can specify any number of nodes. These nodes are linked together by transmission technologies. By consuming a carrier in one node and outputting it in another, linked node, transmission technologies allow resources to be drawn from the system at a different node from where they are brought into it.

The nodes section specifies each node:

nodes:
  region1:
    latitude: 40
    longitude: -2
    available_area: 100
    node_flow_out_max:
      data: [1000, 2000]
      index: [electricity, gas]
      dims: carriers
    techs:
      unmet_demand_power:
      demand_power:
      ccgt:
        flow_cap_max: 30000

For technologies to be installable at a node, they must be listed under techs for that node. As seen in the example above, each allowed tech must be listed, and can optionally specify node-specific parameters. If given, node-specific parameters supersede any parameters given at the technology level.

Nodes can optionally specify geographic coordinates (latitude and longitude) which are used in visualisation or to compute distances along transmission links. Nodes can also have any arbitrary parameter assigned which will be available in the optimisation problem, indexed over the nodes dimension. They can also have parameters that use the indexed parameter syntax to define node+other dimension data. In the above example, node_flow_out_max at region1 could be used to create your own math constraint that limits the total outflow of the carriers electricity and gas at that node.

Understanding node-level parameters

techs is the only required parameter in a node. This can be an empty dictionary (techs: {}), which you may use if your node is just a junction for transmission technologies (which you do not define in the techs of a node - rather, you define them as separate technologies that connect from one node to another node).

See also

See the techs page for the different formats in which you can define parameters, which holds for node-level parameters too.

(De)activating nodes

In an override you may want to remove a node entirely from the model. The easiest way to do this is to set active: false. The resulting input dataset won't feature that node in any way. You can even do this to deactivate technologies at a node. Conversely, setting active: true in an override will lead to the node reappearing.

Note

When deactivating nodes, any transmission technologies that link to that node will also be deactivated.