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
Let's say I publish 2 transformations between a and b and a and c, with the same timestamp. The following warning comes up
Warning: TF_REPEATED_DATA ignoring data with a redundant timestamp for frame world at time 1654798525.529720 according to authority /icp_solver
But as the frames are different, this warning should not be there even though they have the same transformation.
A possible error is not checking frames here
The text was updated successfully, but these errors were encountered:
Each frame has one instance of the TimeCache and in that storage the history of that frame is cached in time including both the values of the transform as well as the parent. This cache is continuously aggregating and you cannot overwrite it with either a changed transform value, nor a changed parent id. If you were to publish those with the same timestamp, there would be no way to know if at that time it should resolve the parent to b or to c.
Let's say I publish 2 transformations between
a
andb
anda
andc
, with the same timestamp. The following warning comes upBut as the frames are different, this warning should not be there even though they have the same transformation.
A possible error is not checking frames here
The text was updated successfully, but these errors were encountered: