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
For a variety of reasons, it would be useful to take root ids and find the most recent timestamp at which they are or were valid. This would be the later-in-time complement of the root_timestamps endpoint that returns the earliest timepoints for a given root id. Experience suggests that the values this returns are not valid timestamps for the ids in question either, and we need to manually add a small time increment to use these timestamps.
The proposed function would take root_ids, a list/array of root ids and optionally timestamp and return an equal length list of the latest timestamps at or before the timestamp specified, at which each of the respective root ids would be valid in the ChunkedGraph. If a timestamp is not provided, it would default to the current timestamp in the same way functions like get_roots work. This implicit timestamp is currently computed on the client side.
The text was updated successfully, but these errors were encountered:
The current endpoint is just called root_timestamps with no indication of early or late timestamps, and the CAVEclient function follows this nomenclature. For clarity when reading the API or using CAVEclient, this feature could be implemented as new parameters on the same endpoint, with one defaulting to latest=False (with False being the existing behavior and True being the behavior described above) and the second being to timestamp=None (with None not being used for latest=False and a timestamp being necessary only in the latest=True case)
For a variety of reasons, it would be useful to take root ids and find the most recent timestamp at which they are or were valid. This would be the later-in-time complement of the
root_timestamps
endpoint that returns the earliest timepoints for a given root id. Experience suggests that the values this returns are not valid timestamps for the ids in question either, and we need to manually add a small time increment to use these timestamps.The proposed function would take
root_ids
, a list/array of root ids and optionallytimestamp
and return an equal length list of the latest timestamps at or before the timestamp specified, at which each of the respective root ids would be valid in the ChunkedGraph. If a timestamp is not provided, it would default to the current timestamp in the same way functions likeget_roots
work. This implicit timestamp is currently computed on the client side.The text was updated successfully, but these errors were encountered: