Clarification on speed after executing AddEntityAction and TeleportAction
Describe the problem
If an AddEntityAction or a TeleportAction is applied, it is not clear which speed shall be assigned to the entity. If it is expected that a speed action is defined in addition, it might be relevant to execute the AddEntityAction/TeleportAction before executing the SpeedAction
Ask your question
If an entity will be added at a certain position. What is the expected speed? Zero, if no additional speed action is executed at the same time. Or the recent valied speed, if it was removed beforehand? The same should be explained for TeleportAction. Should the recent speed be kept or is the speed set to zero after teleportation? What happens to currently running SpeedActions (e.g. teleportation while a sinusoidal speed profile is prescribed)
This leads to further questions:
- What is the difference between AddEntityAction and TeleportAction? When is it allowed/expected to use or not use an AddEntityAction and TeleportAction
- If an entity is teleported from a position w.r.t road coordinate system to a position w.r.t to a trajectory coordinate sytem, does the meaning of longitudinal speed change?
- Are there any other actions that remain running or stopped during teleportation (e.g. speed action with transition dynamics, lateral actions, trajectory following)?