-
registered a participant and set its trajectories using I use Could you advise another method to check whether the participant schedule is registered where other fleets "know" this participant so it could prevent conflict if needed. Might be my understanding is not correct either. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
are you using a custom fleet adapter, or the |
Beta Was this translation helpful? Give feedback.
-
Most of the time when a participant isn't appearing in the visualizer, it's because they are setting their itinerary using a different reference frame for time than what the visualizer is using (e.g. the participant is using system time while the schedule is visualizing simulation time). To ensure consistent time frames, I recommend always taking the value of It would be good for us to make a text-based schedule inspector that would make this occurrence more obvious, but that hasn't reached the top of our priority list yet. |
Beta Was this translation helpful? Give feedback.
Most of the time when a participant isn't appearing in the visualizer, it's because they are setting their itinerary using a different reference frame for time than what the visualizer is using (e.g. the participant is using system time while the schedule is visualizing simulation time).
To ensure consistent time frames, I recommend always taking the value of
rclcpp::Node::now
and passing it throughrmf_traffic_ros2::convert
to get the appropriatermf_traffic::Time
value to pass onto yourrmf_traffic::schedule::Participant
. After that, make sure all your ROS nodes have a consistent value for theiruse_sim_time
parameter. You can find an example of getting the current "ROS time" and conver…