-
Notifications
You must be signed in to change notification settings - Fork 68
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
"OutOfBoundsDatetime: Out of bounds nanosecond timestamp" error. #433
Comments
I got the same issue: pytz.UTC.localize(pd.Timestamp.min) The workaround is to call baseline_start_date = datetime.date(2021, 1, 1)
baseline_end_date = datetime.date(2021, 12, 31)
baseline_meter_data_hourly, baseline_warnings_hourly = eemeter.get_baseline_data(
meter_data,
start=baseline_start_date,
end=baseline_end_date,
max_days=None) |
In transform.py, the starting date is computed as
If I change it into this
It works for me Should we open a pull request? |
jfenna
pushed a commit
to jfenna/eemeter-intl
that referenced
this issue
Feb 8, 2023
…g in 'filtering to a baseline data' cells that generates 'out of bounds nanosecond timestamp error as reported in issue #433 openeemeter/eemeter#433
jfenna
pushed a commit
to jfenna/eemeter-intl
that referenced
this issue
Feb 8, 2023
…g in 'filtering to a baseline data' cells that generates 'out of bounds nanosecond timestamp error as reported in issue #433 openeemeter/eemeter#433
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An error is produced when using eemeter with the most recent version of pandas.
After calling
eemeter.get_baseline_data()
, the error is:OutOfBoundsDatetime: Out of bounds nanosecond timestamp: 1677-09-21 00:12:43
.Package versions
Reverting pandas version back to 1.2.1 has fixed the issue.
The text was updated successfully, but these errors were encountered: