You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: