Some of the example scenarios distributed with the package include set_position invocations. For example, the "force over signal" scenario here which has
ego_vehicle.set_position(x:255.0m, y:-204.7m, z:0.0m, pitch:0.0rad, yaw:88.4rad, roll:0.0rad)
This method invocation does not seem to be recognized by scenario runner, however. Instead I get "Not Find ... Method Declaration" emitted here.
As others have noted (#1027), there does not seem to be a mechanism for controlling the spawn point in OSC2 scenario runs, but rather ego vehicle spawns in the same location every time.
- What is the right way to set the spawn location in OSC2 scenarios?
FWIW, I have tried changing ego_vehicle.set_position to ego_vehicle.position; I no longer get the error message, but I do not get the desired behavior.
Some of the example scenarios distributed with the package include
set_positioninvocations. For example, the "force over signal" scenario here which hasThis method invocation does not seem to be recognized by scenario runner, however. Instead I get "Not Find ... Method Declaration" emitted here.
As others have noted (#1027), there does not seem to be a mechanism for controlling the spawn point in OSC2 scenario runs, but rather ego vehicle spawns in the same location every time.
FWIW, I have tried changing
ego_vehicle.set_positiontoego_vehicle.position; I no longer get the error message, but I do not get the desired behavior.