Makes working with AEMO data more pleasant.
Ruby Versions Supported
- ruby-head (failures allowed)
- 2.6 (.0, .1, .2, .3)
- 2.5 (.0, .1, .2, .3, .4, .5)
- 2.4 (.0, .1, .2, .3, .4, .5)
- 2.3 (.0, .1, .2, .3, .4, .5, .6, .7, .8)
- 2.2 (.5, .6, .7, .8, .9, .10)
Manually from RubyGems.org
% gem install aemo
Or if you are using Bundler
# frozen_string_literal: true # Gemfile source 'https://rubygems.org' do gem 'aemo' end
Updating loss factors
- Connect to AEMO via VPN (tip: be a market participant in order to unlock this step)
- Log in to MSATS
- Navigate to Reports and Alerts » CATS » C1 - Data Replication Resynchronisation Report - Data Replication Resynchronisation Report (C1)
- Export both the CATS_DLF_CODES and CATS_TNI_CODES tables (from 1-Jan-1970 to the current date, both with 30,000 max rows)
- Wait some more...
- Navigate to Participant Outbox (you have new messages link)
- Get the file!
- Run the following:
ruby cd lib/data && ruby xml_to_json.rb
- Add tests for your new FY to spec/lib/aemo/nmi_spec.rb
rspec- note that AEMO can retroactively change factors so if there is an old failing test double check the json to make sure it's not AEMO's fault.
- Commit, push & create a pull request