gailin-p
gailin-p
This PR demonstrates how we might use Snakemake as a workflow manager by implementing a snakemake rule for the final step in the pipeline (calculating consumed emissions). ## Why snakemake?...
Consumed results should include fuel mix. * Decide on resolution of fuel mix (high-level 930 categories? Or more specific fuels?) * Probably should refactor consumed emission rate code (`consumed.py`) into...
eGRID provides both input and output emission rates. Input emission rates can be useful in cases where fuel consumption is known in real time or near real time but emissions...
# Physics-based cleaning We use `gridemissions` to clean EIA 930 data. Currently we use 930 generation, however, this causes issues during the calculation of consumed emission rates. (see #214) A...
Currently, `impute_hourly_profiles.impute_missing_hourly_profiles` uses EIA-930 balance files, which don't have physics-based cleaning. We should use the cleanest available data instead.
Issue #86 was fixed by #91 (aggregating to BA before shaping), but this limits shaping methodologies. A dask implementation would be more scalable.
Where per-fuel type 930 data isn't available (before July 2018), should default to other hourly profile methods. This would allow the pipeline to work for older years
Some plants are not assigned a BA and are assigned an artificial BA like MS. - [ ] Why aren't these plants being assigned a BA? - [ ] What...
Fossil fuel power plants have a startup period between between a period of inactivity and the start of normal operations. During these startup periods, there are differences in plant operations...
EPA eGRID offers a range of physical aggregations: plant, state, BA, region, US. We currently offer only one physical aggregation per data type: plant-level for plant data, BA-level for power_system...