Open cmgosnell opened 6 days ago
When running just on the direct_support_1
and with the field type updated for the plant IDs:
[1523 1548 1576 1589 1596 1727 1728 1795 1796 1827 1864 1865 1879 1892 1895 1909 1920 1922 1934 1943 1946 1977 2028 2046 2059 2069 2088 2101 2102 2105 2108 2109 2110 2111 2112 2116 2125 2126 2133 2143 2224 2236 2315 2316 2317 2408 2448]
Adding these IDs to the harvesting process seems to have fixed the issue, and pudl_check_fks
is now passing on #3699.
There are new sets of plant_id's and generator id's in the
core_eia860__scd_generators_energy_storage
table which are all about whether a storage generator supports another generator. Goal of this issue is to add these new id's into special FK relationships. It is possible that we will need to harvest these new ID's in order to actually have all of the ID's in the harvested generators table. Another possible barrier is that there definitely nulls in these columns. Is it okay to have nulls in a column with a foreign key relationship to a table that doesn't have any nulls?These are the columns at question:
Running
pudl_check_fks
without the new alembic schema produces the following errors:Which have the following values: