Skip to content

Handle version datetime or different resolution than time_value #653

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

Open
2 tasks
brookslogan opened this issue Apr 4, 2025 · 0 comments
Open
2 tasks
Assignees

Comments

@brookslogan
Copy link
Contributor

brookslogan commented Apr 4, 2025

  • Handle version being datetime
  • Fix any erroneous calculations with time_value and version being daily-weekly or weekly-daily (lag calculations are likely assuming that they are the same time_type but they are probably only being checked for same class and typeof)
@brookslogan brookslogan self-assigned this Apr 4, 2025
@brookslogan brookslogan changed the title Allow time_value and version to have different classes&types; fix assumptions that time_types are the same Allow version to be datetime; relax / fix erroneous assumptions time_value and version are same class, type, time_type Apr 4, 2025
@brookslogan brookslogan changed the title Allow version to be datetime; relax / fix erroneous assumptions time_value and version are same class, type, time_type Allow version to be datetime; relax / fix erroneous assumptions time_value and version are same class, typeof, time_type Apr 4, 2025
@brookslogan brookslogan changed the title Allow version to be datetime; relax / fix erroneous assumptions time_value and version are same class, typeof, time_type Handle version datetime or different resolution than time_value Apr 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant