-
Notifications
You must be signed in to change notification settings - Fork 32
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
[summary] converting to date index to datetime by default #113
Comments
It makes technically sense to return it as datetime64, but I am not convinced it will be easier for users in all cases. But this is not cast in stone, and if it is to be changed, it should not be changed to late. |
For me it is not that important if it is a Date object or datetime64/Pandas timestamp, but would prefer it to be the same all the way. I see that fmu-ensemble (and I assume ecl2df as it is a copy of fmu-ensemble for summaries) returns datetime64 for "raw" time_index, and the Date object if you define a time_index like "monthly", which isn't that easy to guess before I stumble opon it. |
Any change in default behaviour of this must be coordinated with fmu-ensemble. Consequences for users must be examined upfront. A less intrusive change could be to add an option |
I could live with that @berland 👍 |
#134 is merged, so API users can always get this behaviour when wanted. |
PR #207 is taking one step towards returning DatetimeIndex, by issuing a FutureWarning if an explicit |
Note: Pandas has a hard limit at 2262-04-11 when using DatetimeIndex (64-bits and nanosecond accuracy only allows representing 584 years). Eclipse simulations can go on for longer than year 2262. |
Context (and workaround): pandas-dev/pandas#7307 |
The foreseeable future in reservoir simulation is defined as 500 years. This is a showstopper for having DatetimeIndex as default in Pandas dataframes. https://equinor.slack.com/archives/C68CNC0M7/p1612947250054500 |
In the current behavior the indexes (Date) are an object ... would be much easier if they were by default as a datetime64
![image](https://user-images.githubusercontent.com/40567543/77050133-8f324200-69c9-11ea-9363-ab9776806942.png)
The text was updated successfully, but these errors were encountered: