Investigate lack of monthly year-to-date data in out_eia923__monthly_generation_fuel_by_generator table #3634
Labels
data-validation
Issues related to checking whether data meets our quality expectations.
eia923
Anything having to do with EIA Form 923
time
what even is time. fixing and changing the way in which PUDL data deals with time
In #3625 it seemed odd that there was no 2023 data showing up in the
out_eia923__monthly_generation_fuel_by_generator
table, even with 11 months of 2023incremental_ytd
records from the EIA-923:This seems a little bit fishy. We use
pudl.output.eia923.drop_ytd_for_annual_tables()
to avoid "annual" aggregations of data where we don't have a whole year of data, but here it seems like we're also somehow excluding monthly year to date records, which I don't think is intentional? Anddrop_ytd_for_annual_tables()
does not get called whenfreq=="MS"
Investigate why this truncation is happening, and evaluate whether that's the expected / desired behavior.
Possible explanation
The
out_eia923__monthly_generation_fuel_by_generator
table depends on the fuel & generation allocation process, which depends on the boiler generator association table, and that table is only available from the annual EIA-860, not the monthly EIA-860M data, so the fact that we don't have the allocated generation & fuel table for periods in which there's only EIA-860M data right now makes sense.If we wanted to hack it to give us some estimate of the most recent allocated data we could just forward fill the BGA table up to the most recent year, and it would be mostly right since these associations don't really change unless there's a major overhaul to a plant, but we're not doing that now.
The text was updated successfully, but these errors were encountered: