Grid, pipelines and other infrastructure - GCAM

From IAMC-Documentation
Jump to navigation Jump to search
Alert-warning.png Note: The documentation of GCAM is 'under review' and is not yet 'published'!

Model Documentation - GCAM

Corresponding documentation
Previous versions
No previous version available
Model information
Model link
Institution Pacific Northwest National Laboratory, Joint Global Change Research Institute (PNNL, JGCRI), USA, https://www.pnnl.gov/projects/jgcri.
Solution concept General equilibrium (closed economy)GCAM solves all energy, water, and land markets simultaneously
Solution method Recursive dynamic solution method
Anticipation GCAM is a dynamic recursive model, meaning that decision-makers do not know the future when making a decision today. After it solves each period, the model then uses the resulting state of the world, including the consequences of decisions made in that period - such as resource depletion, capital stock retirements and installations, and changes to the landscape - and then moves to the next time step and performs the same exercise. For long-lived investments, decision-makers may account for future profit streams, but those estimates would be based on current prices. For some parts of the model, economic agents use prior experience to form expectations based on multi-period experiences.

Gas Pipeline, Delivered Gas, and Wholesale Gas

The gas pipeline sector explicitly represents the energy consumed by compressors for transmission and distribution of natural gas. Delivered gas and wholesale gas are differentiated in their consumers and therefore cost mark-ups; delivered gas refers to gas used by the buildings and transportation sectors, whereas wholesale gas is used by industrial and energy sector consumers. The historical input-output coefficient of the gas pipeline sector in any region is estimated as the sum of reported pipeline energy consumption, delivered gas, and wholesale gas, divided by the sum of delivered gas and wholesale gas. See the gas pipeline section in the documentation.