pudl.analysis.plant_parts_eia#

Aggregate plant parts to make an EIA master plant-part table.

Practically speaking, a plant is a collection of generator(s). There are many attributes of generators (i.e. prime mover, primary fuel source, technology type). We can use these generator attributes to group generator records into larger aggregate records which we call “plant-parts”. A plant part is a record which corresponds to a particular collection of generators that all share an identical attribute. E.g. all of the generators with unit_id=2, or all of the generators with coal as their primary fuel source.

The EIA data about power plants (from EIA 923 and 860) is reported in tables with records that correspond to mostly generators and plants. Other datasets (cough cough FERC1) are less well organized and include plants, generators and other plant-parts all in the same table without any clear labels. The master plant-part table is an attempt to create records corresponding to many different plant-parts in order to connect specific slices of EIA plants to other datasets.

Because generators are often owned by multiple utilities, another dimention of the master unit list involves generating two records for each owner: one of the portion of the plant part they own and one for the plant part as a whole. The portion records are labeled in the ownership column as “owned” and the total records are labeled as “total”.

This module refers to “true granularies”. Many plant parts we cobble together here in the master plant-part list refer to the same collection of infrastructure as other plant-part list records. For example, if we have a “plant_prime_mover” plant part record and a “plant_unit” plant part record which were both cobbled together from the same two generators. We want to be able to reduce the plant-part list to only unique collections of generators, so we label the first unique granularity as a true granularity and label the subsequent records as false granularities with the true_gran column. In order to choose which plant-part to keep in these instances, we assigned a PLANT_PARTS_ORDERED and label whichever plant-part comes first as the unique granularity.

Recipe Book for the plant-part list

PLANT_PARTS is the main recipe book for how each of the plant-parts need to be compiled. These plant-parts represent ways to group generators based on widely reported values in EIA. All of these are logical ways to group collections of generators - in most cases - but some groupings of generators are more prevelant or relevant than others for certain types of plants.

The canonical example here is the plant_unit. A unit is a collection of generators that operate together - most notably the combined-cycle natural gas plants. Combined-cycle units generally consist of a number of gas turbines which feed excess steam to a number of steam turbines.

>>> df_gens = pd.DataFrame({
...     'plant_id_eia': [1, 1, 1],
...     'generator_id': ['a', 'b', 'c'],
...     'unit_id_pudl': [1, 1, 1],
...     'prime_mover_code': ['CT', 'CT', 'CA'],
...     'capacity_mw': [50, 50, 100],
... })
>>> df_gens
    plant_id_eia    generator_id    unit_id_pudl    prime_mover_code    capacity_mw
0              1               a               1                  CT             50
1              1               b               1                  CT             50
2              1               c               1                  CA            100

A good example of a plant-part that isn’t really logical also comes from a combined-cycle unit. Grouping this example plant by the prime_mover_code would generate two records that would basically never show up in FERC1. This stems from the inseparability of the generators.

>>> df_plant_prime_mover = pd.DataFrame({
...     'plant_id_eia': [1, 1],
...     'plant_part': ['plant_prime_mover', 'plant_prime_mover'],
...     'prime_mover_code': ['CT', 'CA'],
...     'capacity_mw': [100, 100],
... })
>>> df_plant_prime_mover
    plant_id_eia         plant_part    prime_mover_code    capacity_mw
0              1  plant_prime_mover                  CT            100
1              1  plant_prime_mover                  CA            100

In this case the unit is more relevant:

>>> df_plant_unit = pd.DataFrame({
...     'plant_id_eia': [1],
...     'plant_part': ['plant_unit'],
...     'unit_id_pudl': [1],
...     'capacity_mw': [200],
... })
>>> df_plant_unit
    plant_id_eia    plant_part    unit_id_pudl    capacity_mw
0              1    plant_unit               1            200

But if this same plant had both this combined-cycle unit and two more generators that were self contained “GT” or gas combustion turbine, a frequent way to group these generators is differnt for the combined-cycle unit and the gas-turbine.

>>> df_gens = pd.DataFrame({
...     'plant_id_eia': [1, 1, 1, 1, 1],
...     'generator_id': ['a', 'b', 'c', 'd', 'e'],
...     'unit_id_pudl': [1, 1, 1, 2, 3],
...     'prime_mover_code': ['CT', 'CT', 'CA', 'GT', 'GT'],
...     'capacity_mw': [50, 50, 100, 75, 75],
... })
>>> df_gens
    plant_id_eia    generator_id    unit_id_pudl    prime_mover_code    capacity_mw
0              1               a               1                  CT             50
1              1               b               1                  CT             50
2              1               c               1                  CA            100
3              1               d               2                  GT             75
4              1               e               3                  GT             75
>>> df_plant_part = pd.DataFrame({
...     'plant_id_eia': [1, 1],
...     'plant_part': ['plant_unit', 'plant_prime_mover'],
...     'unit_id_pudl': [1, pd.NA],
...     'prime_mover_code': [pd.NA, 'GT',],
...     'capacity_mw': [200, 150],
... })
>>> df_plant_part
    plant_id_eia           plant_part    unit_id_pudl    prime_mover_code    capacity_mw
0              1           plant_unit               1                <NA>            200
1              1    plant_prime_mover            <NA>                  GT            150

In this case last, the plant_unit record would have a null plant_prime_mover because the unit contains more than one prime_mover_code. Same goes for the unit_id_pudl of the plant_prime_mover. This is handled in the :class:AddConsistentAttributes.

Overview of flow for generating the master unit list:

The two main classes which enable the generation of the plant-part table are:

  • MakeMegaGenTbl: All of the plant parts are compiled from generators. So this class generates a big dataframe of generators with any ID and data columns we’ll need. This is also where we add records regarding utility ownership slices. The table includes two records for every generator-owner: one for the “total” generator (assuming the owner owns 100% of the generator) and one for the report ownership fraction of that generator with all of the data columns scaled to the ownership fraction.

  • MakePlantParts: This class uses the generator dataframe as well as the information stored in PLANT_PARTS to know how to aggregate each of the plant parts. Then we have plant part dataframes with the columns which identify the plant part and all of the data columns aggregated to the level of the plant part. With that compiled plant part dataframe we also add in qualifier columns with AddConsistentAttributes. A qualifer column is a column which contain data that is not endemic to the plant part record (it is not one of the identifying columns or aggregated data columns) but the data is still useful data that is attributable to each of the plant part records. For more detail on what a qualifier column is, see AddConsistentAttributes.execute().

Generating the plant-parts list

There are two ways to generate the plant-parts table: one directly using the pudl.output.pudltabl.PudlTabl object and the other using the classes from this module. Either option needs a pudl.output.pudltabl.PudlTabl object.

Create the pudl.output.pudltabl.PudlTabl object:

import pudl
pudl_engine = sa.create_engine(pudl.workspace.setup.get_defaults()['pudl_db'])
pudl_out = pudl.output.pudltabl.PudlTabl(pudl_engine,freq='AS')

Then make the table via pudl_out:

plant_parts_eia = pudl_out.plant_parts_eia()

OR make the table via objects in this module:

gens_mega = MakeMegaGenTbl().execute(mcoe, own_eia860)
parts_compiler = MakePlantParts(pudl_out)
plant_parts_eia = parts_compiler.execute(gens_mega=gens_mega)

Module Contents#

Classes#

MakeMegaGenTbl

Compiler for a MEGA generator table with ownership integrated.

MakePlantParts

Compile the plant parts for the master unit list.

PlantPart

Plant-part table maker.

TrueGranLabeler

Label the plant-part table records with their true granularity.

AddAttribute

Base class for adding attributes to plant-part tables.

AddConsistentAttributes

Adder of attributes records to a plant-part table.

AddPriorityAttribute

Add Attributes based on a priority sorting from PRIORITY_ATTRIBUTES.

AddMaxMinAttribute

Add Attributes based on the maximum or minimum value of a sorted attribute.

Functions#

validate_run_aggregations(plant_parts_eia, gens_mega)

Run a test of the aggregated columns.

_test_prep_merge(part_name, plant_parts_eia, gens_mega)

Run the test groupby and merge with the aggregations.

make_id_cols_list()

Get a list of the id columns (primary keys) for all of the plant parts.

make_parts_to_ids_dict()

Make dict w/ plant-part names (keys) to the main id column (values).

add_record_id(part_df, id_cols[, plant_part_col, year])

Add a record id to a compiled part df.

match_to_single_plant_part(→ pandas.DataFrame)

Match data with a variety of granularities to a single plant-part.

Attributes#

logger

width

max_columns

PLANT_PARTS

this dictionary contains a key for each of the 'plant parts' that should

PLANT_PARTS_ORDERED

PLANT_PARTS_LITERAL

IDX_TO_ADD

list of additional columns to add to the id_cols in PLANT_PARTS.

IDX_OWN_TO_ADD

list of additional columns beyond the IDX_TO_ADD to add to the

SUM_COLS

list of columns to sum when aggregating a table.

WTAVG_DICT

a dictionary of columns (keys) to perform weighted averages on and

CONSISTENT_ATTRIBUTE_COLS

a list of column names to add as attributes when they are consistent into

PRIORITY_ATTRIBUTES_DICT

MAX_MIN_ATTRIBUTES_DICT

FIRST_COLS

pudl.analysis.plant_parts_eia.logger[source]#
pudl.analysis.plant_parts_eia.width = 1000[source]#
pudl.analysis.plant_parts_eia.max_columns = 1000[source]#
pudl.analysis.plant_parts_eia.PLANT_PARTS :dict[str, dict[str, list]][source]#

this dictionary contains a key for each of the ‘plant parts’ that should end up in the plant parts list. The top-level value for each key is another dictionary, which contains keys:

  • id_cols (the primary key type id columns for this plant part). The plant_id_eia column must come first.

Type:

dict

pudl.analysis.plant_parts_eia.PLANT_PARTS_ORDERED :list[str] = ['plant', 'plant_unit', 'plant_prime_mover', 'plant_technology', 'plant_prime_fuel',...[source]#
pudl.analysis.plant_parts_eia.PLANT_PARTS_LITERAL[source]#
pudl.analysis.plant_parts_eia.IDX_TO_ADD :list[str] = ['report_date', 'operational_status_pudl'][source]#

list of additional columns to add to the id_cols in PLANT_PARTS. The id_cols are the base columns that we need to aggregate on, but we also need to add the report date to keep the records time sensitive and the operational_status_pudl to separate the operating plant-parts from the non-operating plant-parts.

Type:

list

pudl.analysis.plant_parts_eia.IDX_OWN_TO_ADD :list[str] = ['utility_id_eia', 'ownership'][source]#

list of additional columns beyond the IDX_TO_ADD to add to the id_cols in PLANT_PARTS when we are dealing with plant-part records that have been broken out into “owned” and “total” records for each of their owners.

Type:

list

pudl.analysis.plant_parts_eia.SUM_COLS :list[str] = ['total_fuel_cost', 'net_generation_mwh', 'capacity_mw', 'capacity_eoy_mw', 'total_mmbtu'][source]#

list of columns to sum when aggregating a table.

Type:

list

pudl.analysis.plant_parts_eia.WTAVG_DICT[source]#

a dictionary of columns (keys) to perform weighted averages on and the weight column (values)

Type:

dict

pudl.analysis.plant_parts_eia.CONSISTENT_ATTRIBUTE_COLS = ['fuel_type_code_pudl', 'planned_retirement_date', 'retirement_date', 'generator_id',...[source]#

a list of column names to add as attributes when they are consistent into the aggregated plant-part records. All the plant part ID columns must be in consistent attributes.

Type:

list

pudl.analysis.plant_parts_eia.PRIORITY_ATTRIBUTES_DICT[source]#
pudl.analysis.plant_parts_eia.MAX_MIN_ATTRIBUTES_DICT[source]#
pudl.analysis.plant_parts_eia.FIRST_COLS = ['plant_id_eia', 'report_date', 'plant_part', 'generator_id', 'unit_id_pudl',...[source]#
class pudl.analysis.plant_parts_eia.MakeMegaGenTbl[source]#

Compiler for a MEGA generator table with ownership integrated.

Examples

Input Tables

Here is an example of one plant with three generators. We will use capacity_mw as the data column.

>>> mcoe = pd.DataFrame({
...     'plant_id_eia': [1, 1, 1],
...     'report_date': ['2020-01-01', '2020-01-01','2020-01-01'],
...     'generator_id': ['a', 'b', 'c'],
...     'utility_id_eia': [111, 111, 111],
...     'unit_id_pudl': [1, 1, 1],
...     'prime_mover_code': ['CT', 'CT', 'CA'],
...     'technology_description': [
...         'Natural Gas Fired Combined Cycle', 'Natural Gas Fired Combined Cycle', 'Natural Gas Fired Combined Cycle'
...     ],
...     'operational_status': ['existing', 'existing','existing'],
...     'retirement_date': [pd.NA, pd.NA, pd.NA],
...     'capacity_mw': [50, 50, 100],
... }).astype({
...     'retirement_date': "datetime64[ns]",
...     'report_date': "datetime64[ns]",
... })
>>> mcoe
    plant_id_eia    report_date     generator_id   utility_id_eia   unit_id_pudl    prime_mover_code              technology_description   operational_status  retirement_date      capacity_mw
0              1     2020-01-01                a              111              1                  CT    Natural Gas Fired Combined Cycle             existing               NaT              50
1              1     2020-01-01                b              111              1                  CT    Natural Gas Fired Combined Cycle             existing               NaT              50
2              1     2020-01-01                c              111              1                  CA    Natural Gas Fired Combined Cycle             existing               NaT             100

The ownership table from EIA 860 includes one record for every owner of each generator. In this example generator c has two owners.

>>> df_own_eia860 = pd.DataFrame({
...     'plant_id_eia': [1, 1, 1, 1],
...     'report_date': ['2020-01-01', '2020-01-01','2020-01-01', '2020-01-01'],
...     'generator_id': ['a', 'b', 'c', 'c'],
...     'utility_id_eia': [111, 111, 111, 111],
...     'owner_utility_id_eia': [111, 111, 111, 888],
...     'fraction_owned': [1, 1, .75, .25]
... }).astype({'report_date': "datetime64[ns]"})
>>> df_own_eia860
    plant_id_eia    report_date   generator_id      utility_id_eia  owner_utility_id_eia  fraction_owned
0              1     2020-01-01              a                 111                   111            1.00
1              1     2020-01-01              b                 111                   111            1.00
2              1     2020-01-01              c                 111                   111            0.75
3              1     2020-01-01              c                 111                   888            0.25

Output Mega Generators Table

MakeMegaGenTbl().execute(mcoe, df_own_eia860, slice_cols=['capacity_mw']) produces the output table gens_mega which includes two main sections: the generators with a “total” ownership stake for each of their owners and the generators with an “owned” ownership stake for each of their owners. For the generators that are owned 100% by one utility, the records are identical except the ownership column. For the generators that have more than one owner, there are two “total” records with 100% of the capacity of that generator - one for each owner - and two “owned” records with the capacity scaled to the ownership stake of each of the owner utilites - represented by fraction_owned.

execute(mcoe: pandas.DataFrame, own_eia860: pandas.DataFrame, slice_cols: list[str] = SUM_COLS, validate_own_merge: str = '1:m') pandas.DataFrame[source]#

Make the mega generators table with ownership integrated.

Parameters:
  • mcoe – generator-based mcoe table from pudl.output.PudlTabl.mcoe()

  • own_eia860 – ownership table from pudl.output.PudlTabl.own_eia860()

  • scale_cols – list of columns to slice by ownership fraction in MakeMegaGenTbl.scale_by_ownership(). Default is SUM_COLS

  • validate_own_merge – how the merge between mcoe and own_eia860 is to be validated via pd.merge. If there should be one record for each plant/generator/date in mcoe then the default 1:m should be used.

Returns:

a table of all of the generators with identifying columns and data columns, sliced by ownership which makes “total” and “owned” records for each generator owner. The “owned” records have the generator’s data scaled to the ownership percentage (e.g. if a 200 MW generator has a 75% stake owner and a 25% stake owner, this will result in two “owned” records with 150 MW and 50 MW). The “total” records correspond to the full plant for every owner (e.g. using the same 2-owner 200 MW generator as above, each owner will have a records with 200 MW).

get_gens_mega_table(mcoe)[source]#

Compile the main generators table that will be used as base of PPL.

Get a table of all of the generators there ever were and all of the data PUDL has to offer about those generators. This generator table will be used to compile all of the “plant-parts”, so we need to ensure that any of the id columns from the other plant-parts are in this generator table as well as all of the data columns that we are going to aggregate to the various plant-parts.

Returns:

pandas.DataFrame

label_operating_gens(gen_df: pandas.DataFrame) pandas.DataFrame[source]#

Label the operating generators.

We want to distinguish between “operating” generators (those that report as “existing” and those that retire mid-year) and everything else so that we can group the operating generators into their own plant-parts separate from retired or proposed generators. We do this by creating a new label column called “operational_status_pudl”.

This method also adds a column called “capacity_eoy_mw”, which is the end of year capacity of the generators. We assume that if a generator isn’t “existing”, its EOY capacity should be zero.

Parameters:

gen_df (pandas.DataFrame) – annual table of all generators from EIA.

Returns

pandas.DataFrame: annual table of all generators from EIA that operated within each reporting year.

Todo

This function results in warning: PerformanceWarning: DataFrame is highly fragmented… I expect this is because of the number of columns that are being assigned here via .loc[:, col_to_assign].

scale_by_ownership(gens_mega, own_eia860, scale_cols=SUM_COLS, validate='1:m')[source]#

Generate proportional data by ownership %s.

Why do we have to do this at all? Sometimes generators are owned by many different utility owners that own slices of that generator. EIA reports which portion of each generator is owned by which utility relatively clearly in their ownership table. On the other hand, in FERC1, sometimes a partial owner reports the full plant-part, sometimes they report only their ownership portion of the plant-part. And of course it is not labeld in FERC1. Because of this, we need to compile all of the possible ownership slices of the EIA generators.

In order to accumulate every possible version of how a generator could be reported, this method generates two records for each generator’s reported owners: one of the portion of the plant part they own and one for the plant-part as a whole. The portion records are labeled in the ownership column as “owned” and the total records are labeled as “total”.

In this function we merge in the ownership table so that generators with multiple owners then have one record per owner with the ownership fraction (in column fraction_owned). Because the ownership table only contains records for generators that have multiple owners, we assume that all other generators are owned 100% by their operator. Then we generate the “total” records by duplicating the “owned” records but assigning the fraction_owned to be 1 (i.e. 100%).

class pudl.analysis.plant_parts_eia.MakePlantParts(pudl_out)[source]#

Compile the plant parts for the master unit list.

This object generates a master list of different “plant-parts”, which are various collections of generators - i.e. units, fuel-types, whole plants, etc. - as well as various ownership arrangements. Each plant-part is included in the master plant-part table associated with each of the plant-part’s owner twice - once with the data scaled to the fraction of each owners’ ownership and another for a total plant-part for each owner.

This master plant parts table is generated by first creating a complete generators table - with all of the data columns we will be aggregating to different plant-part’s and sliced and scaled by ownership. Then we use the complete generator table to aggregate by each of the plant-part categories. Next we add a label for each plant-part record which indicates whether or not the record is a unique grouping of generator records.

The coordinating function here is execute().

execute(gens_mega)[source]#

Aggregate and slice data points by each plant part.

Returns:

The complete plant parts list

Return type:

pandas.DataFrame

add_additonal_cols(plant_parts_eia)[source]#

Add additonal data and id columns.

This method adds a set of either calculated columns or PUDL ID columns.

Returns:

master unit list table with these additional columns:

  • utility_id_pudl +

  • plant_id_pudl +

  • capacity_factor +

  • ownership_dupe (boolean): indicator of whether the “owned” record has a corresponding “total” duplicate.

Return type:

pandas.DataFrame

_clean_plant_parts(plant_parts_eia)[source]#
validate_ownership_for_owned_records(plant_parts_eia)[source]#

Test ownership - fraction owned for owned records.

This test can be run at the end of or with the result of MakePlantParts.execute(). It tests a few aspects of the the fraction_owned column and raises assertions if the tests fail.

class pudl.analysis.plant_parts_eia.PlantPart(part_name: PLANT_PARTS_LITERAL)[source]#

Plant-part table maker.

The coordinating method here is execute().

Examples

Below are some examples of how the main processing step in this class operates: PlantPart.ag_part_by_own_slice(). If we have a plant with four generators that looks like this:

>>> gens_mega = pd.DataFrame({
...     'plant_id_eia': [1, 1, 1, 1],
...     'report_date': ['2020-01-01', '2020-01-01', '2020-01-01', '2020-01-01',],
...     'utility_id_eia': [111, 111, 111, 111],
...     'generator_id': ['a', 'b', 'c', 'd'],
...     'prime_mover_code': ['ST', 'GT', 'CT', 'CA'],
...     'energy_source_code_1': ['BIT', 'NG', 'NG', 'NG'],
...     'ownership': ['total', 'total', 'total', 'total',],
...     'operational_status_pudl': ['operating', 'operating', 'operating', 'operating'],
...     'capacity_mw': [400, 50, 125, 75],
... }).astype({
...     'report_date': 'datetime64[ns]',
... })
>>> gens_mega
    plant_id_eia   report_date      utility_id_eia  generator_id    prime_mover_code        energy_source_code_1    ownership       operational_status_pudl         capacity_mw
0              1    2020-01-01                 111             a                  ST                         BIT        total                     operating                 400
1              1    2020-01-01                 111             b                  GT                          NG        total                     operating                  50
2              1    2020-01-01                 111             c                  CT                          NG        total                     operating                 125
3              1    2020-01-01                 111             d                  CA                          NG        total                     operating                  75

This gens_mega table can then be aggregated by plant, plant_prime_fuel, plant_prime_mover, or plant_gen.

execute(gens_mega: pandas.DataFrame, sum_cols: list[str] = SUM_COLS, wtavg_dict: dict = WTAVG_DICT) pandas.DataFrame[source]#

Get a table of data aggregated by a specific plant-part.

This method will take gens_mega and aggregate the generator records to the level of the plant-part. This is mostly done via ag_part_by_own_slice(). Then several additional columns are added and the records are labeled as true or false granularities.

Returns:

a table with records that have been aggregated to a plant-part.

ag_part_by_own_slice(gens_mega, sum_cols=SUM_COLS, wtavg_dict=WTAVG_DICT) pandas.DataFrame[source]#

Aggregate the plant part by seperating ownership types.

There are total records and owned records in this master unit list. Those records need to be aggregated differently to scale. The “total” ownership slice is now grouped and aggregated as a single version of the full plant and then the utilities are merged back. The “owned” ownership slice is grouped and aggregated with the utility_id_eia, so the portions of generators created by scale_by_ownership will be appropriately aggregated to each plant part level.

Returns:

dataframe aggregated to the level of the part_name

Return type:

pandas.DataFrame

ag_fraction_owned(part_ag: pandas.DataFrame)[source]#

Calculate the fraction owned for a plant-part df.

This method takes a dataframe of records that are aggregated to the level of a plant-part (with certain id_cols) and appends a fraction_owned column, which indicates the % ownership that a particular utility owner has for each aggreated plant-part record.

For partial owner records (ownership == “owned”), fraction_owned is calcuated based on the portion of the capacity and the total capacity of the plant. For total owner records (ownership == “total”), the fraction_owned is always 1.

This method is meant to be run after ag_part_by_own_slice().

Parameters:

part_ag

add_new_plant_name(part_df, gens_mega)[source]#

Add plants names into the compiled plant part df.

Parameters:
  • part_df (pandas.DataFrame) – dataframe containing records associated with one plant part (ex: all plant’s or plant_prime_mover’s).

  • gens_mega (pandas.DataFrame) – a table of all of the generators with identifying columns and data columns, sliced by ownership which makes “total” and “owned” records for each generator owner.

add_record_count_per_plant(part_df: pandas.DataFrame) pandas.DataFrame[source]#

Add a record count for each set of plant part records in each plant.

Parameters:

part_df – dataframe containing records associated with one plant part (ex: all plant’s or plant_prime_mover’s).

Returns:

augmented version of part_df with a new column named record_count

class pudl.analysis.plant_parts_eia.TrueGranLabeler[source]#

Label the plant-part table records with their true granularity.

The coordinating function here is :meth``execute``.

execute(ppl)[source]#

Merge the true granularity labels onto the plant part df.

This method will add the columns true_gran, appro_part_label, and appro_record_id_eia to the plant parts list which denote whether each plant-part is a true or false granularity.

First the plant part list records are matched to generators. Then the matched records are sorted by PLANT_PARTS_ORDERED and the highest granularity record for each generator is marked as the true granularity. The appropriate true granular part label and record id is then merged on to get the plant part table with true granularity labels.

Parameters:

ppl – (pd.DataFrame) The plant parts list

class pudl.analysis.plant_parts_eia.AddAttribute(attribute_col: str, part_name: str, assign_col_dict: dict[str, str] | None = None)[source]#

Base class for adding attributes to plant-part tables.

assign_col(gens_mega)[source]#

Add a new column to gens_mega.

class pudl.analysis.plant_parts_eia.AddConsistentAttributes(attribute_col: str, part_name: str, assign_col_dict: dict[str, str] | None = None)[source]#

Bases: AddAttribute

Adder of attributes records to a plant-part table.

execute(part_df, gens_mega)[source]#

Get qualifier records.

For an individual dataframe of one plant part (e.g. only “plant_prime_mover” plant part records), we typically have identifying columns and aggregated data columns. The identifying columns for a given plant part are only those columns which are required to uniquely specify a record of that type of plant part. For example, to uniquely specify a plant_unit record, we need both plant_id_eia, unit_id_pudl, report_date and nothing else. In other words, the identifying columns for a given plant part would make up a natural composite primary key for a table composed entirely of that type of plant part. Every plant part is cobbled together from generator records, so each record in each part_df can be thought of as a collection of generators.

Identifier and qualifier columns are the same columns; whether a column is an identifier or a qualifier is a function of the plant part you’re considering. All the other columns which could be identifiers in the context of other plant parrts (but aren’t for this plant part) are qualifiers.

This method takes a part_df and goes and checks whether or not the data we are trying to grab from the record_name column is consistent across every component genertor from each record.

Parameters:
  • part_df (pandas.DataFrame) – dataframe containing records associated with one plant part.

  • gens_mega (pandas.DataFrame) – a table of all of the generators with identifying columns and data columns, sliced by ownership which makes “total” and “owned” records for each generator owner.

get_consistent_qualifiers(record_df)[source]#

Get fully consistent qualifier records.

When data is a qualifer column is identical for every record in a plant part, we associate this data point with the record. If the data points for the related generator records are not identical, then nothing is associated with the record.

Parameters:
  • record_df (pandas.DataFrame) – the dataframe with the record

  • base_cols (list) – list of identifying columns.

  • record_name (string) – name of qualitative record

class pudl.analysis.plant_parts_eia.AddPriorityAttribute(attribute_col: str, part_name: str, assign_col_dict: dict[str, str] | None = None)[source]#

Bases: AddAttribute

Add Attributes based on a priority sorting from PRIORITY_ATTRIBUTES.

This object associates one attribute from the generators that make up a plant-part based on a sorted list within PRIORITY_ATTRIBUTES. For example, for “operational_status” we will grab the highest level of operational status that is associated with each records’ component generators. The order of operational status is defined within the method as: ‘existing’, ‘proposed’, then ‘retired’. For example if a plant_unit is composed of two generators, and one of them is “existing” and another is “retired” the entire plant_unit will be considered “existing”.

execute(part_df, gens_mega)[source]#

Add the attribute to the plant-part df based on priority.

Parameters:
  • part_df (pandas.DataFrame) – dataframe containing records associated with one plant part.

  • gens_mega (pandas.DataFrame) – a table of all of the generators with identifying columns and data columns, sliced by ownership which makes “total” and “owned” records for each generator owner.

class pudl.analysis.plant_parts_eia.AddMaxMinAttribute(attribute_col: str, part_name: str, assign_col_dict: dict[str, str] | None = None)[source]#

Bases: AddAttribute

Add Attributes based on the maximum or minimum value of a sorted attribute.

This object adds an attribute based on the maximum or minimum of another attribute within a group of plant parts uniquely identified by their base ID columns.

execute(part_df, gens_mega, att_dtype: str, keep: Literal[first, last] = 'first')[source]#

Add the attribute to the plant part df based on sorting of another attribute.

Parameters:
  • part_df (pandas.DataFrame) – dataframe containing records associated with one plant part.

  • gens_mega (pandas.DataFrame) – a table of all of the generators with identifying columns and data columns, sliced by ownership which makes “total” and “owned” records for each generator owner.

  • att_dtype (string) – Pandas data type of the new attribute

  • keep (string) – Whether to keep the first or last record in a sorted grouping of attributes. Passing in “first” indicates the new attribute is a maximum attribute. See pandas.drop_duplicates().

pudl.analysis.plant_parts_eia.validate_run_aggregations(plant_parts_eia, gens_mega)[source]#

Run a test of the aggregated columns.

This test will used the plant_parts_eia, re-run groubys and check similarity.

pudl.analysis.plant_parts_eia._test_prep_merge(part_name, plant_parts_eia, gens_mega)[source]#

Run the test groupby and merge with the aggregations.

pudl.analysis.plant_parts_eia.make_id_cols_list()[source]#

Get a list of the id columns (primary keys) for all of the plant parts.

Returns:

a list of the ID columns for all of the plant-parts, including report_date

Return type:

list

pudl.analysis.plant_parts_eia.make_parts_to_ids_dict()[source]#

Make dict w/ plant-part names (keys) to the main id column (values).

All plant-parts have 1 or 2 ID columns in PLANT_PARTS plant_id_eia and a secondary column (with the exception of the “plant” plant-part). The plant_id_eia column is always first, so we’re going to grab the last column.

Returns:

plant-part names (keys) cooresponding to the main ID column (value).

Return type:

dictionary

pudl.analysis.plant_parts_eia.add_record_id(part_df, id_cols, plant_part_col='plant_part', year=True)[source]#

Add a record id to a compiled part df.

We need a standardized way to refer to these compiled records that contains enough information in the id itself that in theory we could deconstruct the id and determine which plant id and plant part id columns are associated with this record.

pudl.analysis.plant_parts_eia.match_to_single_plant_part(multi_gran_df: pandas.DataFrame, ppl: pandas.DataFrame, part_name: PLANT_PARTS_LITERAL = 'plant_gen', cols_to_keep: list[str] = []) pandas.DataFrame[source]#

Match data with a variety of granularities to a single plant-part.

This method merges an input dataframe (multi_gran_df) containing data that has a heterogeneous set of plant-part granularities with a subset of the EIA plant-part list that has a single granularity. Currently this is only tested where the single granularity is generators. In general this will be a one-to-many merge in which values from single records in the input data end up associated with several records from the plant part list. First, we select a subset of the full EIA plant-part list corresponding to the plant part specified by the part_name argument. In theory this could be the plant, generator, fuel type, etc. Currently only generators are supported. Then, we iterate over all the possible plant parts, selecting the subset of records in multi_gran_df that have that granularity, and merge the homogeneous subset of the plant part list that we selected above onto that subset of the input data. Each iteration uses a different set of columns to merge on – the columns which define the primary key for the plant part being merged. Each iteration creates a separate dataframe, corresponding to a particular plant part, and at the end they are all concatenated together and returned.

Parameters:
  • multi_gran_df – a data table where all records have been linked to EIA plant-part list but they may be heterogeneous in its plant-part granularities (i.e. some records could be of ‘plant’ plant-part type while others are ‘plant_gen’ or ‘plant_prime_mover’). All of the plant-part list columns need to be present in this table.

  • ppl – the EIA plant-part list.

  • part_name – name of the single plant part to match to. Must be a key in PLANT_PARTS dictionary.

  • cols_to_keep – columns from the original data multi_gran_df that you want to show up in the output. These should not be columns that show up in the ppl.

Returns:

A dataframe in which records correspond to part_name (in the current implementation: the records all correspond to EIA generators!). This is an intermediate table that cannot be used directly for analysis because the data columns from the original dataset are duplicated and still need to be scaled up/down.