Data

Tools

Indexes

Applications

Experiments

Open Sustainable Technology

Future Technology Transformation

Integrated assessment model with a realistic treatment of technology diffusion.
https://github.com/cpmodel/ftt_standalone

Category: Climate Change
Sub Category: Integrated Assessment and Climate Policy

Keywords

energy-system-model power-system-model python scenario-analysis simulation-model

Last synced: about 4 hours ago
JSON representation

Repository metadata

Future Technology Transformation models: a family of evolutionary economics models to investigate energy policy

README.md

Future Technology Transformation (FTT)

Modules

This repository contains a family of Future Technology Transformation (FTT) models. Models that are included are:

  • FTT:Power (Mercure, 2012) - updated to 2022 (generation) and 2023 (prices)
  • FTT:Heat (Knobloch et al, 2017) data up to 2020
  • FTT:Industrial heat
  • FTT:Transport (Mercure et al, 2018) - data up to 2022
  • FTT:Freight - data up to 2023
  • FTT:Hydrogen (under review)

Theoretical background

The FTT family of models are based on evolutionary economics. The uptake of new technologies typically follows an S-curve, which can be represented well with evolutionary dynamics (Mercure et al, 2012). The core equations for all of the models in the model family are coupled logistic equations of the Lotka-Volterra family, also known as the predator-prey equations. These equations are used to determine the evolution of the shares of various technologies in the models. Each model contains between ~10 to 25 technologies competing for market share.

FTT and macro-economic models

This repository contains the main version of FTT, written in Python. It comes as a package that can be imported into macro-economic models. A FORTRAN version of the model family is often used together with a macro-economic model as: E3ME-FTT. This model is managed by Cambridge Econometrics, and informs some of the inputs for the model. In specific, energy demand is an output from the coupled model.

Installation

Before you start, make sure that git is installed on your system, for instance by installing GitHub Desktop

  1. Open your terminal at a location where you want to install ftt. Type the following in your terminal to download the package from GitHub:

    git clone https://github.com/cpmodel/FTT_StandAlone.git

  2. The python package requirements are curated in the environment.yml file.
    Change directory to the repo, and then install the environment using:

    conda env create -f environment.yml

  3. On Windows, you can start the frontend with launch_frontend.bat. If Python is not yet added to your path, ensure you add this first.

Alternatively, you can download ftt by clicking the green Code button in the top right, and selecting Open with Github Desktop if you have this installed. You can import the environment in Anaconda Navigator.

Running the model

  1. You can run the frontend of the model in your browser by either double clicking open_frontend.bat or by running run_frontend.py. Select the models to run and scenarios and explore the output.
  2. Alternatively, you can run the model from the run_file.py script. Output is saved to a pickle file in the Output folder. Select the models and scenarios from the settings.ini file.
  3. Create new scenarios by adding a new folder in the Inputs folder. Data is read in first from this folder, and missing data is read from the S0 baseline folder.

How to contribute

We welcome contributions from everyone. You can report issues, fix bugs, improve the documentation, or write and propose model changes and provide updated data.

  1. New contributors can fork the repository to open pull requests with suggested code improvements
  2. Join our Discord and Open Community meetings, typically on the last Friday of the month; send an email for the invites.
  3. When you have questions, ask them on GitHub, so other people can benefit from the answers. Bugs and feature requests should be raised in GitHub Issues. Questions should be posted at the GitHub Discussions tab.
  4. Whether you open a PR or ask questions, ensure that you're using the latest version of the code. Rebase your branch before you open a PR.

Collaborations and publications

If you plan to publish work using this codebase, please let us know. Where capacity allows, we are happy to review results or confirm that analyses are consistent with the implementation.

We encourage a community-driven approach. If you need more detailed support, we welcome contributions back to the project through improvements to code, training material or data, to help strengthen the work for everyone.

References

Owner metadata

GitHub Events

Total
Last Year

Committers metadata

Last synced: 3 days ago

Total Commits: 868
Total Committers: 22
Avg Commits per committer: 39.455
Development Distribution Score (DDS): 0.388

Commits in past year: 410
Committers in past year: 10
Avg Commits per committer in past year: 41.0
Development Distribution Score (DDS) in past year: 0.315

Name Email Commits
Femke Nijsse f****e@p****t 531
Cormac Lynch 1****h 118
Rosie Hayward 1****1 36
Ian Burton i****0@e****k 32
Rosie Hayward 1****n 30
copilot-swe-agent[bot] 1****t 23
ADanneaux a****x@h****r 21
Rishi Sahastrabuddhe r****1@g****m 18
Chris Thoung ct@c****m 12
Amir Akther a****r@e****k 12
AEdwards476 a****6@e****k 12
Sanatparida01 s****0@e****k 4
Aicha Kharazi k****9@g****m 4
Pim Vercoulen pv@c****m 3
Jamie Pirie C****P 3
Carlos Paes Dos Santos Gomes u****d@e****u 2
aileenlam28 6****8 2
Carlos Eduardo Paes 5****g 1
Jamie Pirie 1****n 1
Xiaofan Feng f****3@1****m 1
dbastidas d****c@g****m 1
ghardadi g****i@g****m 1

Committer domains:

Issue and Pull Request metadata

Last synced: 3 days ago

Total issues: 97
Total pull requests: 335
Average time to close issues: 10 months
Average time to close pull requests: 19 days
Total issue authors: 14
Total pull request authors: 26
Average comments per issue: 0.91
Average comments per pull request: 1.02
Merged pull request: 228
Bot issues: 0
Bot pull requests: 0

Past year issues: 16
Past year pull requests: 57
Past year average time to close issues: about 2 months
Past year average time to close pull requests: 23 days
Past year issue authors: 2
Past year pull request authors: 9
Past year average comments per issue: 0.19
Past year average comments per pull request: 1.75
Past year merged pull request: 37
Past year bot issues: 0
Past year bot pull requests: 0

More stats: https://issues.ecosyste.ms/repositories/lookup?url=https://github.com/cpmodel/ftt_standalone

Top Issue Authors

  • Femkemilene (71)
  • cormacmlynch (9)
  • rh-camecon (3)
  • pv-camecon (3)
  • rhayward1 (2)
  • PVercoulen-CE (1)
  • QuentinLETERRIER (1)
  • ldxib2 (1)
  • ct-camecon (1)
  • gressyde (1)
  • rishids01 (1)
  • jp-camecon (1)
  • AEdwards476 (1)
  • jk694exe (1)

Top Pull Request Authors

  • Femkemilene (150)
  • cormacmlynch (35)
  • arpangolechha (30)
  • rishids01 (26)
  • ldxib2 (23)
  • varunaga13 (8)
  • rhayward1 (8)
  • Shruti-d1 (7)
  • jp-camecon (5)
  • cadupsg (4)
  • PurpleHycinth (4)
  • ct-camecon (4)
  • jk694exe (4)
  • AEdwards476 (3)
  • AmAkther (3)

Top Issue Labels

  • frontend (9)
  • hackathon (7)
  • documentation (5)
  • good first issue (5)
  • enhancement (5)
  • bug (4)
  • question (4)
  • frontend + backend (4)
  • invalid (2)

Top Pull Request Labels

  • enhancement (4)
  • documentation (4)

Score: 7.151485463904735