https://github.com/openscm/gcages

Global Climate Assessment of Global Emission Scenarios. These scenarios are typically produced by Integrated Assessment Models (IAMs).
https://github.com/openscm/gcages

Last synced: 6 months ago
JSON representation

Global Climate Assessment of Global Emission Scenarios. These scenarios are typically produced by Integrated Assessment Models (IAMs).

• Host: GitHub
• URL: https://github.com/openscm/gcages
• Owner: openscm
• License: bsd-3-clause
• Created: 2025-01-09T09:58:37.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2025-02-07T14:31:40.000Z (over 1 year ago)
• Last Synced: 2025-02-07T14:46:12.147Z (over 1 year ago)
• Language: Python
• Size: 0 Bytes
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • Changelog: changelog/README.md

Awesome Lists containing this project

README

          

# gcages

Global Climate Assessment of Global Emission Scenarios, typically (but not always) produced by Integrated Assessment Models (IAMs).

**Key info :**

[![Docs](https://readthedocs.org/projects/gcages/badge/?version=latest)](https://gcages.readthedocs.io)

[![Main branch: supported Python versions](https://img.shields.io/python/required-version-toml?tomlFilePath=https%3A%2F%2Fraw.githubusercontent.com%2Fopenscm%2Fgcages%2Fmain%2Fpyproject.toml)](https://github.com/openscm/gcages/blob/main/pyproject.toml)

[![Licence](https://img.shields.io/pypi/l/gcages?label=licence)](https://github.com/openscm/gcages/blob/main/LICENCE)

**PyPI :**

[![PyPI](https://img.shields.io/pypi/v/gcages.svg)](https://pypi.org/project/gcages/)

[![PyPI install](https://github.com/openscm/gcages/actions/workflows/install-pypi.yaml/badge.svg?branch=main)](https://github.com/openscm/gcages/actions/workflows/install-pypi.yaml)

**Tests :**

[![CI](https://github.com/openscm/gcages/actions/workflows/ci.yaml/badge.svg?branch=main)](https://github.com/openscm/gcages/actions/workflows/ci.yaml)

[![Coverage](https://codecov.io/gh/openscm/gcages/branch/main/graph/badge.svg)](https://codecov.io/gh/openscm/gcages)

**Other info :**

[![Last Commit](https://img.shields.io/github/last-commit/openscm/gcages.svg)](https://github.com/openscm/gcages/commits/main)

[![Contributors](https://img.shields.io/github/contributors/openscm/gcages.svg)](https://github.com/openscm/gcages/graphs/contributors)

## Status

- prototype: the project is just starting up and the code is all prototype

Full documentation can be found at:

[gcages.readthedocs.io](https://gcages.readthedocs.io/en/latest/).

We recommend reading the docs there because the internal documentation links

don't render correctly on GitHub's viewer.

## Installation

### As an application

If you want to use gcages as an application,

then we recommend using the 'locked' version of the package.

This version pins the version of all dependencies too,

which reduces the chance of installation issues

because of breaking updates to dependencies.

The locked version of gcages can be installed with

=== "pip"

    ```sh

    pip install 'gcages[locked]'

    ```

### As a library

If you want to use gcages as a library,

for example you want to use it

as a dependency in another package/application that you're building,

then we recommend installing the package with the commands below.

This method provides the loosest pins possible of all dependencies.

This gives you, the package/application developer,

as much freedom as possible to set the versions of different packages.

However, the tradeoff with this freedom is that you may install

incompatible versions of gcages's dependencies

(we cannot test all combinations of dependencies,

particularly ones which haven't been released yet!).

Hence, you may run into installation issues.

If you believe these are because of a problem in gcages,

please [raise an issue](https://github.com/openscm/gcages/issues).

The (non-locked) version of gcages can be installed with

=== "pip"

    ```sh

    pip install gcages

    ```

### For developers

For development, we rely on [uv](https://docs.astral.sh/uv/)

for all our dependency management.

To get started, you will need to make sure that uv is installed

([instructions here](https://docs.astral.sh/uv/getting-started/installation/)

(we found that the self-managed install was best,

particularly for upgrading uv later).

For all of our work, we use our `Makefile`.

You can read the instructions out and run the commands by hand if you wish,

but we generally discourage this because it can be error prone.

In order to create your environment, run `make virtual-environment`.

If there are any issues, the messages from the `Makefile` should guide you through.

If not, please raise an issue in the

[issue tracker](https://github.com/openscm/gcages/issues).

For the rest of our developer docs, please see [development][development].

## Original template

This project was generated from this template:

[copier core python repository](https://gitlab.com/openscm/copier-core-python-repository).

[copier](https://copier.readthedocs.io/en/stable/) is used to manage and

distribute this template.