Scenario Declaration (Syntax)
Describe the feature
Scenario Declaration - Use
In order to define a scenario, the scenario must be declared.
- This shall require the keyword: 'scenario'.
- This shall require a name or scenario-identifier for identifying the scenario.
Any scenario where executive behavior is required.
- There shall be a keyword for a executing a block of scenario behavior.
- Recommended keyword “do”.
- To request execution of behavior: action or scenario invocations are used by requesting actors to “do” a defined behavior.
- Behavior can / should be organized / constructed inside of temporal-operators to achieve the best results which allow for easily allow for serialization and parallelization (allowing for behavior to start and end at the same time).
ORIGINAL SYNTAX
<scenario-declaration> ::= 'scenario' <actor-name>'.'<scenario-name>[':' <base-scenario-type>(<condition>)] [':' #
<scenario-member>+] #
'do' ['only'] <do-member> #
<scenario-member> ::= <field-declaration>
| <constraint-declaration>
| <event-declaration> #
| <scenario-modifier-invocation> #
| <set-declaration> #
Describe the solution you would like
UPDATE / REDUCED
<scenario-declaration> ::= 'scenario' [<actor-name>'.‘]<scenario-name>':'
<scenario-member>+
'do' ['only'] <do-member>
<scenario-member> ::= <field-declaration>
| <constraint-declaration>
| <event-declaration>
| <method-declaration> #
| <cover-declaration> #
<do-member> ::= <temporal-operator>
| <scenario-invocation>
<temporal-operator> ::= <serial-invocation>
| <parallel-invocation>
| <one-of-invocation>
| <mix-invocation>
ALTERNATIVE – REDUCED FURTHER
<scenario-declaration> ::= 'scenario' [<actor-name>'.‘]<scenario-name>':'
<scenario-member>+]
'do' <do-member>
<scenario-member> ::= <field-declaration>
| <constraint-declaration>
| <event-declaration>
<do-member> ::= <temporal-operator>
| <scenario-invocation>
<temporal-operator> ::= <serial-invocation>
| <parallel-invocation>
| <one-of-invocation>
| <mix-invocation>
ALTERNATIVE#2
(See below) (and see link)
https://code.asam.net/simulation/standard/openscenario-2.0/-/issues/90
https://code.asam.net/simulation/standard/openscenario-2.0/-/issues/90
VOTE RECORDS
Question: Adopt “scenario-declariation” syntax?
Vote Results:
UPDATE-REDUCED-
ALTERNATIVE_REDUCED_FURTHER-
ALTERNATIV#2-
Abstain-
Not-Cast-
Decided on:
ALTERNATIVE#2
<scenario-declaration> ::= 'scenario' [<actor-name>'.‘]<scenario-name>':'
<scenario-member>+]
'do' <do-member>
<scenario-member> ::= <field-declaration>
| <constraint-declaration>
| <event-declaration>
<do-member> ::= <temporal-operator>
| <scenario-invocation>
Describe alternatives you have considered
Describe the backwards compatibility
Additional context
https://code.asam.net/simulation/standard/openscenario-2.0/-/issues/90