-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
core_eia860m__changelog_generators contains NULL valid_until_date values #3614
Comments
Just checked and all of the max dates do indeed have null because of this line |
I think that shift/fillna(max_date) combo assumes that all the timeseries are contiguous and end at the most recent reporting date. I think some of them end earlier or have reporting gaps, so the |
we use
If we want to keep this definition then the |
That makes sense to me! |
Describe the bug
core_eia860m__changelog_generators
contains 950+ NULL values in thevalid_until_date
column. I don't think they should exist because this column is derived fromreport_date
and none of those are NULL. Most of the NULLs (700+) are from the last report_date in the series (currently 2023-12-01), but ~200 others exist throughout the time span of the data. Maybe it has to do with the last date in each generator's series?Bug Severity
This table is encoded as a changelog between two dates --
valid_until_date
specifies one of the boundaries. It is hard to interpret the data without that boundary.To Reproduce
Software Environment?
in
pudl.sqlite
version v2024.2.6The text was updated successfully, but these errors were encountered: