Broken out the creation of demand into its own rule and module. There was quite a bit to track with demand (different datasets, different conditions for electricity v. sectors, ect.) and this seemed like the easier option.
Changed the creation of snapshots to the build_base_network rule, as build_demand is called multiple times
Add a ReadEulp class to parse residential and commercial load data
Add input functions to determine what files to demand files need to be downloaded. One function exists for electricity only studies, one exists for sector coupling studies.
Add a prepare_multiple_demands(...) function in the Context class in build_demand to be able to parse multiple sector data from a single data set (ie. extract out res, com, ind, transport data from EFS all at once)
To do before merging:
Fix the tracking of different demands. Right now, everything gets collapsed into just electrical, heating, and cooling demand during the clustering. I should probably separate these out by sector within the carrier.
Checklist
[ ] I tested my contribution locally and it seems to work fine.
[ ] Code and workflow changes are sufficiently documented.
[ ] Changed dependencies are added to envs/environment.yaml.
[ ] Changes in configuration options are added in all of config.default.yaml.
[ ] Changes in configuration options are also documented in doc/configtables/*.csv.
Closes #283, Closes #277
Changes proposed in this Pull Request
In this PR I have:
build_base_networkrule, asbuild_demandis called multiple timesReadEulpclass to parse residential and commercial load dataprepare_multiple_demands(...)function in theContextclass inbuild_demandto be able to parse multiple sector data from a single data set (ie. extract out res, com, ind, transport data from EFS all at once)To do before merging:
electrical,heating, andcoolingdemand during the clustering. I should probably separate these out by sector within the carrier.Checklist
envs/environment.yaml.config.default.yaml.doc/configtables/*.csv.