Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link electric OpEx to income statement table #2723

Merged
merged 2 commits into from
Jul 13, 2023

Conversation

zaneselvans
Copy link
Member

PR Overview

  • Adds a calculation linking the electric operating expenses back to the income statement table.
  • Adds metadata for a DBF-only factoids that appears in the income statement table.

PR Checklist

  • Merge the most recent version of the branch you are merging into (probably dev).
  • All CI checks are passing. Run tests locally to debug failures
  • Make sure you've included good docstrings.
  • For major data coverage & analysis changes, run data validation tests
  • Include unit tests for new functions and classes.
  • Defensive data quality/sanity checks in analyses & data processing functions.
  • Update the release notes and reference reference the PR and related issues.
  • Do your own explanatory review of the PR to help the reviewer understand what's going on and identify issues preemptively.

src/pudl/transform/ferc1.py Show resolved Hide resolved
Comment on lines 1679 to 1681
# This is already an in-table calculated field so we need to handle
# it differently.
# "utility_operating_expenses": [
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't sure what to make of these commented out calculations, which seem related to but different from the ones I've added, and didn't understand the comment above them.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm this is an ella question idk

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we're aiming for the same goal here, and you just caught a few sub-fields I had missed, so I defer to your calculation. Is there a reason that sales_expense which is also listed as an operation expense isn't included as a component?

The issue of having one calculation for the electric dimension and one calculation for the non-electric dimensions still remains (and is what the original comment above this section is trying to point out, if unclearly).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Following our conversation, scratch the second point - this calculation is correct and mine points to the wrong factoid, fixing the calculation part of this issue.

@zaneselvans zaneselvans added ferc1 Anything having to do with FERC Form 1 data-repair Interpolating or extrapolating data that we don't actually have. metadata Anything having to do with the content, formatting, or storage of metadata. Mostly datapackages. xbrl Related to the FERC XBRL transition labels Jul 12, 2023
Copy link
Member

@cmgosnell cmgosnell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me!!

Comment on lines +1729 to +1754
"amortization_and_depletion_of_utility_plant": [
{
"calc_component_to_replace": {},
"calc_component_new": {
"name": "amortization_limited_term_electric_plant",
"weight": 1.0,
"source_tables": [
"depreciation_amortization_summary_ferc1"
],
"utility_type": "electric",
"subdimension": "electric",
},
},
{
"calc_component_to_replace": {},
"calc_component_new": {
"name": "amortization_other_electric_plant",
"weight": 1.0,
"source_tables": [
"depreciation_amortization_summary_ferc1"
],
"utility_type": "electric",
"subdimension": "electric",
},
},
],
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These calculations link line 8 of the income statement form to the last two data columns in the depreciation amortization summary table.

These factoids appear in the original data table and the original metadata for this table, but they appear to be missing from the exploded metadeta and exploded data, which seems weird to me. This table is part of the income statement hierarchy that we're working with.

I copied the use of utility type and subdimension here, but I don't understand what subdimension means.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@e-belfer does this new calculation seem reasonable?

@cmgosnell do you know why some of these facts might show up in the original data/metadata but not make it through to the exploded versions?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this seems reasonable - here the "subdimension" refers to the plant_function column which is initially total in the raw data but we've replaced with electric, while utility_type still refers to electric as well.

@zaneselvans zaneselvans merged commit 820cb77 into xbrl-calculation-tree Jul 13, 2023
7 of 8 checks passed
@zaneselvans zaneselvans deleted the income-opex-calculations branch July 13, 2023 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data-repair Interpolating or extrapolating data that we don't actually have. ferc1 Anything having to do with FERC Form 1 metadata Anything having to do with the content, formatting, or storage of metadata. Mostly datapackages. xbrl Related to the FERC XBRL transition
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

3 participants