Currently, a different timestamp is provided to the waitForTransform and transformPose functions which may cause issues if they are different. The system should use the msg timestamp, however, because of an issue with the bayesian tracker, the msg timestamp is set to 0.0 causing the waitForTransform to timeout (causing a 3 second delay in starting). To solve this, I have instead set it to use the current timestamp.
Currently, a different timestamp is provided to the waitForTransform and transformPose functions which may cause issues if they are different. The system should use the msg timestamp, however, because of an issue with the bayesian tracker, the msg timestamp is set to 0.0 causing the waitForTransform to timeout (causing a 3 second delay in starting). To solve this, I have instead set it to use the current timestamp.