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
Following on from this conversation on zulip, I think it would be great to have methods to access both time (since start, in whichever unit, see #59).
The proposition is to:
Encode start_time as a metadata field (needs to have Add metadata #19 implemented in some form)
start_time can be either a numeric/ difftime in which case it's the time since 0 that tracking should begin (enything before should be NA) or a datetime timestamp.
Have methods for converting between difftime (not the class, just time since start) and timestamp.
Ensure that further methods do not encounter issues with timestamps - such as calculate_ functions
The text was updated successfully, but these errors were encountered:
Following on from this conversation on zulip, I think it would be great to have methods to access both time (since start, in whichever unit, see #59).
The proposition is to:
start_time
as a metadata field (needs to have Add metadata #19 implemented in some form)start_time
can be either anumeric
/difftime
in which case it's the time since 0 that tracking should begin (enything before should beNA
) or adatetime
timestamp.difftime
(not the class, just time since start) andtimestamp
.calculate_
functionsThe text was updated successfully, but these errors were encountered: