-
Notifications
You must be signed in to change notification settings - Fork 39
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
Dates and documentation #41
Comments
You’re correct, it’s difficult dealing with high frequency data
…Sent from my iPhone
On 27 Jun 2023, at 11:45 AM, Moustafa Chatzouz ***@***.***> wrote:
Hi,
I think the documentation (v5) on dates is not very clear, especially with high frequency dates.
Most users, most likely have dates that look like this 01/01/2023, which corresponds to a dd/mm/yyyy format.
I think it would be more clear to show the correspondence of such conventional formatting to BEAR's dated formats.
For example. In the documentation there is no clarification how to format dates from 01/01/2023 is it 2023d0101 or 2023d101
Or should assume that 1999d208 corresponds to the 208th day of 1999 year ? Which make very time consuming and user unfriendly such way of input data, assuming that most raw data follow conventional date formatting.
I think a lot of new users will struggle on the same issue.
From the development point of view, I would recommend to have a separate functionally that convert conventional dates formats - as is standard in R and Python - to BEAR date formats. Currently, the date formatting is not the most user friendly, and I am sure many new uses like me are struggling with this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
Here is a Python script to convert dates. It worked in my case.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I think the documentation (v5) on dates is not very clear, especially with high frequency dates.
Most users, most likely have dates that look like this
01/01/2023
, which corresponds to add/mm/yyyy
format.I think it would be more clear to show the correspondence of such conventional formatting to BEAR's dated formats.
For example. In the documentation there is no clarification how to format dates from
01/01/2023
is it 2023d0101 or 2023d101Or should assume that 1999d208 corresponds to the 208th day of the year 1999, which makes it very time consuming and user unfriendly such way of input data (assuming that most raw data follow conventional date formatting)
I think a lot of new users will struggle on the same issue.
From the development point of view, I would recommend to have a separate functionally that convert conventional dates formats - as is standard in R and Python - to BEAR date formats. Currently, the date formatting is not the most user friendly, and I am sure many new uses like me are struggling with this.
Thank you and appreciate your clarifications on this
The text was updated successfully, but these errors were encountered: