fix(ENG 2613): PJM DST transitions #701
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| df["bid_datetime_beginning_ept"], | ||
| ).dt.tz_localize(self.default_timezone) | ||
| df["Interval Start"] = ( | ||
| pd.to_datetime(df["bid_datetime_beginning_utc"], format="ISO8601") |
Collaborator
There was a problem hiding this comment.
Well sorry for my earlier suggestion to use the ept column.
WillKoehrsen
approved these changes
Oct 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Actually using the utc output from the API seems to handle DST transitions much better. EPT seems to fall down in various ways.
Correct for various DST transitions discovered in looking at historical data.