pudl.etl.analysis_assets#

Derived / analysis assets that aren’t simple to construct.

This is really too large & generic of a category. Should we have an asset group for each set of related analyses? E.g.

  • mcoe_assets

  • service_territory_assets

  • heat_rate_assets

  • state_demand_assets

  • depreciation_assets

  • plant_parts_eia_assets

  • ferc1_eia_record_linkage_assets

Not sure what the right organization is but they’ll be defined across a bunch of different modules. Eventually I imagine these would just be the novel derived values, probably in pretty skinny tables, which get joined / aggregated with other data in the denormalized tables.

Module Contents#

Functions#

utility_analysis(→ pandas.DataFrame)

Example of how to create an analysis table that depends on an output view.

Attributes#

logger

pudl.etl.analysis_assets.logger[source]#
pudl.etl.analysis_assets.utility_analysis(utils_eia860: pandas.DataFrame) → pandas.DataFrame[source]#

Example of how to create an analysis table that depends on an output view.

This final dataframe will be written to the database (without a schema).