Ask Your Question

Revision history [back]

Maybe it is a similar term like "thread safe" but for real-time.

Yes, I think you can use that analogy.

Essentially it implies that if whatever code you add supports deterministic execution, then the underlying ROS 2 primitives, implemented by the various ROS 2 libraries, will not "interfere" with that determinism.

So anything "real-time safe" is safe to use in a system requiring deterministic execution (ie: real-time).

Which specific grade of real-time-ness that would be (ie: soft, hard or best effort) is not made clear, but in general hard real-time suitability is what is meant.

Maybe it is a similar term like "thread safe" but for real-time.

Yes, I think you can use that analogy.

Essentially it implies that if whatever code you add supports deterministic execution, then then the underlying ROS 2 primitives, implemented by the various ROS 2 libraries, will not "interfere" with that determinism.

So anything "real-time safe" is safe to use in a system requiring deterministic execution (ie: real-time).

Which specific grade of real-time-ness that would be (ie: soft, hard or best effort) is not made clear, but in general hard real-time suitability is what is meant.