Closed abhishek0208 closed 3 years ago
Working fine with the following lines in agg_results.csv
:
resultfile,indices,filename
Demand,"GLOBAL",annual_demand
ProductionByTechnology,"GLOBAL",annual_generation
@willu47 I agree that we need an alternative to storing results as .csv
files. I hadn't heard of feather and pyarrow (which seems to often be referred to parquet) so thanks for the pointers. I did a quick search of performance benchmarks between them: According to this , both pyarrow (parquet) writes out smaller files while taking longer to read files in. So maybe we go with parquet since file size is the more pressing concern?
And yes, we could aggregate hourly_generation
by commodity. In addition, could we add an entry with wildcards in the list of indexes? e.g. **P******
to select all powerplant technologies.
And yes, we could aggregate
hourly_generation
by commodity. In addition, could we add an entry with wildcards in the list of indexes? e.g.**P******
to select all powerplant technologies.
This is a good idea. I'll create a new issue.
The workflow now processes aggregated results for hourly demand and generation as
hourly_demand.csv
andhourly_generation.csv
.The above files, and related rules, require
Demand.csv
andProductionByTechnology.csv
to be included inagg_results.csv
to generateannual_demand.csv
andannual_generation.csv
.