Awesome
nemseer
A package for downloading and handling historical National Electricity Market (NEM) forecast data produced by the Australian Energy Market Operator (AEMO).
Installation
pip install nemseer
Many nemseer
use-cases require NEMOSIS
, which can also be installed using pip
:
pip install nemosis
Overview
nemseer
allows you to access historical AEMO pre-dispatch and Projected Assessment of System Adequacy (PASA) forecast1 data available through the MMSDM Historical Data SQLLoader. nemseer
can then compile this data into pandas DataFrames or xarray Datasets.
An overview of nemseer
functionality and potential use-cases are provided in the JOSS paper for this package.
<sub><sup>Source: Reserve services in the National Electricity Market, AEMC, 2021</sup></sub>
Whereas PASA processes are primarily used to assess resource adequacy based on technical inputs and assumptions for resources in the market (i.e. used to answer questions such as "can operational demand be met in the forecast horizon with a sufficient safety (reserve) margin?"), pre-dispatch processes incorporate the latest set of market participant offers and thus produce regional prices forecasts for energy and frequency control ancillary services (FCAS). Overviews of the various pre-dispatch and PASA processes can be found in the glossary.
nemseer
enables you to download and work with data for the following forecast types. Where available, AEMO process and table descriptions are linked:
- 5-minute pre-dispatch (
P5MIN
: Table descriptions) - Pre-dispatch (
PREDISPATCH
: Table descriptions) - Pre-dispatch Projected Assessment of System Adequacy (
PDPASA
: Tables and Descriptions) - Short Term Projected Assessment of System Adequacy (
STPASA
: Table descriptions) - Medium Term Projected Assessment of System Adequacy (
MTPASA
: Table descriptions)
Another helpful reference for PASA information is AEMO's Reliability Standard Implementation Guidelines.
ST PASA Replacement Project
Note that the methodologies for PD PASA and ST PASA are being reviewed by AEMO. In particular, the ST PASA Replacement project will combine PD PASA and ST PASA into ST PASA. For more detail, refer to the final determination of the rule change and the AEMO ST PASA Replacement Project home page.
Usage
Glossary
The glossary contains overviews of the PASA and pre-dispatch processes, and descriptions of terminology used in nemseer
.
Quick start
Check out the Quick start for guide on to use nemseer
.
Examples
Some use case examples have been included in the Examples section of the documentation.
Support
If you are having an issue with this software that has not already been raised in the issues register, please raise a new issue.
Contributing
Interested in contributing? Check out the contributing guidelines, which also includes steps to install nemseer
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.
Citation
If you use nemseer
, please cite the JOSS paper for this package
If you use code or analysis from any of the demand error and/or price convergence examples in the documentation, please also cite NEMOSIS
via this conference paper
Licenses
nemseer
was created by Abhijith Prakash. It is licensed under the terms of GNU GPL-3.0-or-later licences.
The content within the documentation for this project is licensed under a Creative Commons Attribution 4.0 International License.
Credits
nemseer
was created with cookiecutter
and the py-pkgs-cookiecutter
template.
Development of nemseer
was funded by the UNSW Digital Grid Futures Institute.
Contributor Acknowledgements
Thanks to:
- Nicholas Gorman for reviewing
nemseer
code - Krisztina Katona for reviewing and improving the glossary
- Dylan McConnell for assistance in interpreting PASA run types
- Declan Heim for suggesting improvements to
nemseer
examples
Footnotes
-
We use the term "forecast" loosely, especially given that these "forecasts" change once participants update offer information (e.g. through rebidding) or submit revised resource availabilities and energy constraints. Both of these are intended outcomes of these "ahead processes", which are run to provide system and market information to participants to inform their decision-making. However, to avoid confusion and to ensure consistency with the language used by AEMO, we use the terms "forecast" (or outputs) and "forecast types" (or ahead processes) in
nemseer
. ↩