Skip to content

fix: timestamps being returned as strings, and with wrong column header #386

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

Merged
merged 2 commits into from
Jun 11, 2025

Conversation

drake-nominal
Copy link
Contributor

@drake-nominal drake-nominal commented Jun 10, 2025

  • If user requests absolute timestamps, returns pandas timestamps rather than iso 8601 strings
  • if user under-requests tags, the error message is more intuitive
  • if user over requests tags, column names aren't removed from the dataframe, but just filled with nans
  • if there is no data for a batch of channels in a given timeslice, the channels aren't ignored from the dataframe, but just filled with nans
  • If the timestamp column was renamed, undo this renaming and keep the index consistently named timestamps

@drake-nominal drake-nominal merged commit 3a3a91b into main Jun 11, 2025
9 checks passed
@drake-nominal drake-nominal deleted the deidukas/fix-dataframe-timestamps branch June 11, 2025 01:46
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

Successfully merging this pull request may close these issues.

2 participants