MR_EVENT
MR_EVENT defines an MR Event for a given region on a specific trading date.
Deprecation Warning
This table is in the HISTORICAL TABLES package, so is likely deprecated.
MR_EVENT defines a mandatory restriction event for a given region and trading date (04:30 to 04:00). Data within MR_EVENT includes the cut-off time for submission of MR offers for this event and a notification that the settlements figures are locked due to results from an independent expert being engaged to allocate settlement of a significant shortfall. If mandatory restrictions are defined in two regions on the same trading day, two MR events are defined.
MR_EVENT data is public, so is available to all participants.
Source
MR_EVENT updates are ad hoc.
Volume
1 Row per year
Column Schema
MR_DATE
Mandatory Restriction imposition date
Warning
Despite what the name suggests, this is a datetime, not a date.
SQL Type: DATE
Polars Type: pl.Datetime()
This column is mandatory, and a primary key.
Example: 2026/01/20 00:05:00
REGIONID
Unique RegionID
For more information, see the dedicated documentation page.
The SQL type is VARCHAR2(10).
This is actually a factor/enum, with values:
-
QLD1 -
VIC1 -
TAS1 -
NSW1 -
SA1 -
SNOWY1
This column is mandatory, and a primary key.
AUTHORISEDBY
Ignored - Tracking purpose only
SQL Type: VARCHAR2(20)
Polars Type: str
This column is not mandatory.
AUTHORISEDDATE
Required for MR_Event to take effect
Warning
Despite what the name suggests, this is a datetime, not a date.
SQL Type: DATE
Polars Type: pl.Datetime()
This column is not mandatory.
Example: 2026/01/20 00:05:00
DESCRIPTION
Description of MR
SQL Type: VARCHAR2(200)
Polars Type: str
This column is not mandatory.
LASTCHANGED
Date/Time record inserted/modified
For more information, see the dedicated documentation page.
SQL Type: DATE
Polars Type: pl.Datetime()
This column is not mandatory.
Example: 2026/01/20 00:05:00
OFFER_CUT_OFF_TIME
Cut off after when new Offers and Scaling Factor changes are disallowed
SQL Type: DATE
Polars Type: pl.Datetime()
This column is not mandatory.
Example: 2026/01/20 00:05:00
SETTLEMENT_COMPLETE
Flag:1 = MR settlement figures locked. Do not recalculate, · 0 = MR settlements to be recalculated
SQL Type: NUMBER(1,0)
Polars Type: pl.Boolean
This column is not mandatory.
New Data Timing
Ad hoc
Code Examples
Polars
Casting is enums, categoricals etc is not essential, but may speed up parsing.
Swapping int for pl.UInt16, pl.Int32 would also speed up parsing. However some of the datatypes are inferred, so they may be wrong.
This code deduplicates for you. Deduplication is normally only required across multiple months.
This code assumes that all columns are present, which may not be true for older files.
import polars as pl
import polars.selectors as cs
# e.g. "2029/03/15 00:05:00"
dt_s_fmt = "%Y/%m/%d %H:%M:%S"
csv_paths = ["SOMEFILE.CSV", "OTHERFILE.CSV"]
lf = (
pl.concat(
[
pl.scan_csv(
csv_path, # must be unzipped beforehand
skip_rows=1, # skip the header
infer_schema=False, # much faster
)
.filter(cs.by_index(0) == "D") # drop the footer
.select(~cs.by_index(range(4))) # drop metadata columns
for csv_path in csv_paths
],
how="diagonal_relaxed",
)
.with_columns(
pl.col(
"MR_DATE", "AUTHORISEDDATE", "LASTCHANGED", "OFFER_CUT_OFF_TIME"
).str.strptime(pl.Datetime, dt_s_fmt),
)
# Polars can't cast string straight to bool. Need to go via something else.
.cast({"SETTLEMENT_COMPLETE": pl.UInt8})
.cast(
{
"REGIONID": pl.Enum(["QLD1", "VIC1", "TAS1", "NSW1", "SA1", "SNOWY1"]),
"AUTHORISEDBY": str,
"DESCRIPTION": str,
"SETTLEMENT_COMPLETE": pl.Boolean,
}
)
# Deduplicate
# We want one row per ['MR_DATE', 'REGIONID']
# Tie-breaker: greatest value of ['LASTCHANGED']
.sort(["LASTCHANGED"], descending=False)
.unique(subset=["MR_DATE", "REGIONID"], keep="last")
)
Nemosis
This table is not yet available in Nemosis.
Availability
AEMO's documentation states that this table's visibility is "Public". However, it is not available in the public monthly MMSDM archive. AEMO probably call this public because it is available to all market participants over private FTP.
There is a chance that is is still public to non-participants. It may only be available for some months; or (rarely) it may be available in a non-standard location.
Deduplication and PDR Loader Configuration
The primary keys are:
The transaction type is "insert", which means that you will usually not see duplicate data. If you do, you can deduplicate based on the primary keys, without sorting first. Rows from different files with the same primary keys should have the same values.
| Report Name | Report Subtype | Version |
|---|---|---|
| MR | EVENT | 1 |
This means that the CSV files start with metadata columns:
Indexes
Links
This page as JSON (schema documented here, but may change)
Download a JSON Schema specification for this table.
Official AEMO schema documentation
Other Information
Package: HISTORICAL TABLES