Skip to main content

NEMED

Code style: black Documentation Status

NEMED1, or NEM Emissions Data, is a python package to retrieve and process historical emissions data of the National Electricity Market (NEM), reproduced by datasets published by the Australian Energy Market Operator (AEMO).

Installation

pip install nemed

Introduction

This tool is designed to allow users to retrieve historical NEM regional emissions data, either total or marginal emissions, for any 5-minute dispatch interval or aggregations thereof. Total emissions data produced by NEMED is given as both absolute total emissions (tCO2-e) and as an emissions intensity index (tCO2-e/MWh). Marginal emissions data reflects the price setter of a particular region, yielding an emissions intensity index (tCO2-e/MWh) corresponding to a particular plant. Although data is published by AEMO via the Carbon Dioxide Equivalent Intensity Index (CDEII) Procedure this only reflects a daily summary for each region by total and (average) emissions intensity.

How does NEMED calculate emissions?

Total Emissions are computed by considering 5-minute generation dispatch data for each generator in the NEM for each respective region, along with their CO2-equivalent emissions factors per unit (generator) level. A detailed method of the process to produce results for total emissions(tCO2-e) and the corresponding emisssions intensities can be found here. The tool is able to provide these metrics on a dispatch interval basis, or aggregated to hourly, daily, monthly or yearly measures. For more advanced users, the emissions associated with each generator and hence that generator's contribution to total regional emissions can be extracted.

Marginal Emissions are computed by identifying the marginally dispatched generators from AEMO's Price Setter files, mapping emissions intensity metrics mentioned above and computing marginal emissions intensity (tCO2-e/MWh).

How accurate is NEMED?

A series of benchmark results for total emissions shows a comparison between AEMO's daily CDEII reported emissions figures and NEMED's emissions figures which have been aggregated from a 5-minute dispatch-interval resolution to a daily basis.

The example includes a region by region comparison for each metric, while an overview of the historical NEM Emissions Intensity produced using NEMED is shown here. NEM Emissions Intensity

Usage

Examples

Examples can be found in NEMED's documentation.

Possible Use Cases

Some example use cases of data produced from this tool include:

  • Analysis of historical emissions between NEM regions, generation technologies contributions to them and assessing the difference between total and marginal emissions.
  • Using emissions intensities traces (total and marginal) from NEMED in counter-factual optimisation models; studying the influence of shadow-pricing carbon or imposing carbon constraints.
  • Considering the emissions assosciated with grid-energy consumption for residential/C&I consumers, or in counterfactual studies of hypothetical EV usage or H2 electrolyser operation.

Contributing

Interested in contributing? Check out the contributing guidelines, which also includes steps to install NEMED for development.

Please note that this project is released with a Code of Conduct. By contributing to this project, you agree to abide by its terms.

License

NEMED was created by Declan Heim and Shayan Naderi. It is licensed under the terms of the BSD 3-Clause license.

Credits

This package was created using the UNSW CEEM template. It also adopts functionality from sister tools including NEMOSIS and NEMPY.

  1. Not to be confused with "Nemed", "Nimeth" of the Irish legend, who was the leader of the third group of people to settle in Ireland. ↩

Metadata

Release files for nemed 0.3.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nemed 0.3.3
File Size Uploaded Provenance Actions
nemed-0.3.3.tar.gz 161.4 kB Without provenance Details for nemed-0.3.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for nemed 0.3.3
File Interpreter ABI Platform Actions
nemed-0.3.3-py3-none-any.whl Python 3 none any Details for nemed-0.3.3-py3-none-any.whl

Total release size: 324.3 kB

Release files / nemed-0.3.3.tar.gz

Download URL nemed-0.3.3.tar.gz
Size 161.4 kB
Tags Source
SHA-256 checksum
How to use checksums
947f30b168b1c2e2738a9c72c0932bc7a54f891b629c1e1b3b50fe4cb199abfd
BLAKE2b-256 checksum
How to use checksums
fb6d54ba69bd6208ce5c77939def85785919a40d89cba53770a0fbed3c9e8230
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.2.2 CPython/3.10.11 Windows/10

Release files / nemed-0.3.3-py3-none-any.whl

Download URL nemed-0.3.3-py3-none-any.whl
Size 162.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f51687bf0c5ebaccfc2a8f3e3783e93bc87650eeb776916cf0afab3b5fe8b379
BLAKE2b-256 checksum
How to use checksums
b1da714d830951d8d4b57b0af11ecd9194f2bd346026c5842756f9e6b1552125
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.2.2 CPython/3.10.11 Windows/10

Security for nemed 0.3.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.3.3 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page