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

Lane ID parameters need to be of type integer #49

Closed
arauschert opened this issue Sep 29, 2021 · 1 comment · Fixed by #61
Closed

Lane ID parameters need to be of type integer #49

arauschert opened this issue Sep 29, 2021 · 1 comment · Fixed by #61
Labels
bug Something isn't working

Comments

@arauschert
Copy link
Collaborator

in the parameter declaraions for some scenarios lane IDs are defined. In their usage they need to be strings, but this doesn't work for constraints (e.g. 3 < LaneId < 5). Therefore the parameters should be defined as integer, so they can be used for checking constraints and within expressions. They would need to be implicitly converted to a string when they are used as string attribute for a laneID

@arauschert arauschert added the bug Something isn't working label Sep 29, 2021
@frazar
Copy link

frazar commented Nov 8, 2023

Isn't the lane ID defined as a String in the specification?
image

Another option to achieve validation of the constraint could be to have a series of Constraint Groups. For example, for allowing only lane IDs between -3 and -5:

    <ParameterDeclaration name="Ego_InitPosition_LaneId" parameterType="string" value="-4">
      <ConstraintGroup>
        <ValueConstraint rule="equalTo" value="-5" />"
      </ConstraintGroup>
      <ConstraintGroup>
        <ValueConstraint rule="equalTo" value="-4" />"
      </ConstraintGroup>
      <ConstraintGroup>
        <ValueConstraint rule="equalTo" value="-3" />"
      </ConstraintGroup>
    </ParameterDeclaration>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants