aemo_nemweb

AEMO NEMWEB 5-minute regional reference prices (RRP), five NEM regions. Every 5-minute price of the window, from four NEMWEB places, newest first: * ``Reports/Current/Public_Prices`` - one ``PUBLIC_PRICES`` file per trading day (04:05 -> 04:00 AEST), published at ~04:05 the next morning; NEMWEB keeps ~60 days there. * ``Reports/Archive/Public_Prices`` - the same daily files bundled per month (``PUBLIC_PRICES_YYYYMM01.zip``), a rolling ~13 months. * ``Data_Archive/.../MMSDM`` - the monthly ``DISPATCHPRICE`` table of the MMS Data Model, every month since 2009, published a few weeks after the month ends; read for trading days the two above no longer hold. Its months are calendar months of SETTLEMENTDATE, so a trading day that straddles a month end reads both months. * ``Reports/Current/DispatchIS_Reports`` - one file per 5-minute dispatch run (~2 days kept), for the trading day not yet in a daily file: every file whose interval falls in the window, not only the newest. History: it used to read ONLY the newest DispatchIS file, one 5-minute price per region per run - 0.1% of the 5-minute grid - and stored AEMO's SETTLEMENTDATE as UTC, though it is AEST and marks the interval's END: every price sat 10 h 5 min late. Its daily-file lookup then keyed trading days on the AEST calendar date, so a window starting between 00:00 and 04:00 AEST never read the trading day those intervals belong to (2025-07-31 14:00-18:00 UTC was such a hole). Values are stored as published (intervention re-runs skipped); the vintage is the fetch time, as before. No auth; falls back to synthetic if NEMWEB is unreachable.