Recent v0.3.3 has resolved not reading in some files from AEMO correctly. This issue rather relates to some intervals being filtered out in the function which reads the json files which contain raw price setter data from AEMO xml files which filters on ENOF.
|
(df_nested_list['@DispatchedMarket'] == 'ENOF')] |
There are some intervals such as "2022-06-17T07:25:00" in which the price setter file data doesn't actually have a unit ("marginal generator") for some regions and shows "DeficitProduct" as the column: "DispatchedMarket". Would appreciate any help in understanding the price setter files and why this is the case. Below is an example of what reading the price setter data from the NEMED combined json file in the cache looks like...
Recent v0.3.3 has resolved not reading in some files from AEMO correctly. This issue rather relates to some intervals being filtered out in the function which reads the json files which contain raw price setter data from AEMO xml files which filters on ENOF.
NEMED/src/nemed/helper_functions/mod_xml_cache.py
Line 138 in 88a5f23
There are some intervals such as "2022-06-17T07:25:00" in which the price setter file data doesn't actually have a unit ("marginal generator") for some regions and shows "DeficitProduct" as the column: "DispatchedMarket". Would appreciate any help in understanding the price setter files and why this is the case. Below is an example of what reading the price setter data from the NEMED combined json file in the cache looks like...