Skip to content
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

sorting issue #16

Open
dwild0 opened this issue Aug 18, 2022 · 2 comments
Open

sorting issue #16

dwild0 opened this issue Aug 18, 2022 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@dwild0
Copy link
Owner

dwild0 commented Aug 18, 2022

Sorting them by timestamps might cause ambiguity, because several specific timestamps appear more than once, while not every signal contains every kind of timestamps. More precisely, there is no timestamp, that occurs in every signal. Therefore sorting them by more sorting criteria could also become kind of difficult.

@dwild0 dwild0 added the bug Something isn't working label Aug 18, 2022
@dwild0 dwild0 self-assigned this Aug 18, 2022
@dwild0
Copy link
Owner Author

dwild0 commented Aug 18, 2022

Currently working on following functions:
Func1 : find minimum timestamp that ist not NaT
Func2: sort dataframe by all three columns

@dwild0
Copy link
Owner Author

dwild0 commented Aug 18, 2022

Fix that nonexisting timestamps are filled with NaT while converting string to datetime objects. They should be filled with time 0 values with date from existing timestamp. If that is not possible with built in to_datetime function, then a custom converting function has to be made, that converts while taking date from existing timestamps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant