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.
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_timestampsendpoint 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 optionallytimestampand 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_rootswork. This implicit timestamp is currently computed on the client side.