Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ALKS Controller activation too late #48

Closed
arauschert opened this issue Sep 24, 2021 · 1 comment · Fixed by #50
Closed

ALKS Controller activation too late #48

arauschert opened this issue Sep 24, 2021 · 1 comment · Fixed by #50
Labels
enhancement New feature or request

Comments

@arauschert
Copy link
Collaborator

For the activation of the ALKS controller the condition is SimulationTime=10000 sec. This raised some questions, since the scenario doesn't last that long.
The idea is that this value has to be changed to e.g. 1 sec., if an external controller is connected to the environment simulation.
Maybe there are more intuitive ways to model this without having to use further OpenSCENARIO 1 features. (e.g. an additional parameter "external_ego_control" with type="boolean" and default value="false" and an additional ParameterValueCondition with parameter="external_ego_control" rule="equalsTo" value="true" would also work, but not used yet in the scenarios).

@arauschert arauschert added the enhancement New feature or request label Sep 24, 2021
@arauschert
Copy link
Collaborator Author

A further idea is to create a parameter "ALKS_activation_time" with the initial value "10000". This makes things more transparent without having to use additional OpenSCENARIO features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant