catalyst-cooperative/pudl

PUDL Development Setup Before starting on any of these tasks, you'll want to set up your development environment. Fork the PUDL repository and follow the steps to set up the PUDL development environment Activate the pudl-dev environment: pixi install Grab the latest raw data for any relevant tables - in this case, RUS 7 or 12. To do so, run pudl_datastore --dataset rus7 (and/or rus12) Generate the existing RUS assets: follow the instructions to open Dagster, and in the left-hand menu find the "raw_rus12" asset group. Click "Materialize all", and repeat for the core and out assets. Repeat for RUS 7 if needed. Alternately, instead of materializing the data yourself grab the latest successful nightly build data and validate that. At the end of these steps, you should have successfully materialized all existing assets in PUDL and will be ready to begin validation. For each table, identify all calculations using the corresponding PDF form from the correct data source page and the

NoteIf you're interested in taking on this issue, you can absolutely just take on validating one or two tables from the list below - this is an issue we'd like to chip away at, so don't let the number of tables prevent you from taking this on! Overview What is the problem we're solving? For very simple items, this can be encapsulated in the success criteria. In #5039 we validated totals records for a number of records. This Some validations are blocked by the need to update the existing DBT test. For instance, the "totals" field from the electric_plant_in_service utility_plant_group in the core_rus12__yearly_utility_plant_changes table is composed of multiple totals field from other utility plant groups. To successfully sum this, we need to be able to specify that the sub-components are identified by more than one column's values - we can do this by updating the macro to take tuples and combinations of columns, rather than single values. Success Criteria How will we know that we're do