Simulation issueshttps://code.asam.net/groups/simulation/-/issues2022-04-11T13:44:41Zhttps://code.asam.net/simulation/openscenario/2.x/-/issues/93Will OpenSCENARIO 2.0 support "Logically Abstract Scenarios"?2022-04-11T13:44:41ZRichard HeidtmanWill OpenSCENARIO 2.0 support "Logically Abstract Scenarios"?Will OpenSCENARIO 2.0 support "Logically Abstract Scenarios"?
... given this will eventually be logical and concrete for testing.
Definition:
"A scenario that mixes aspects of abstract scenarios and logical scenarios." (Accept IEEE a...Will OpenSCENARIO 2.0 support "Logically Abstract Scenarios"?
... given this will eventually be logical and concrete for testing.
Definition:
"A scenario that mixes aspects of abstract scenarios and logical scenarios." (Accept IEEE and ASAM definitions of Abstract and Logical Scenarios.)
A scenario that:
1) has every intention of being understood and tested by a machine
2) uses an object oriented "structure for abstraction" 3) follows "rules of abstraction" 4) follows an intent to meet rules of concretion. Intentionally does not define all dimensions of test, so they can later be optimized. Missing from a Logically Abstract Scenario are both: a Parameter Space Full Factorial and method of selection.
<!--- Provide a general summary of the issue in the Title above -->
Please see the purposed use case.
Use Case:
As a scenario developer, I realize that there are aspects of the real world that are always expanding and changing (i.e. roads, maps, signs, road markings, types of objects and vehicles) and there are aspects of the world that don't seem to change as often like human behavior and weather. (As weather has existed for all human history and since the advent of cars on the roads and pedestrian behavior, we are doing the same sorts of things.) I want to create scenarios that are robust, long lasting and logical to human behaviors and parameters but are abstract to the aspects of the real world that are always changing. This is a partially logical scenario for position, speed and distance but abstract for specific map, location on map and for object representations. Some define this as a Logically Abstract Scenario. This allows for my robust scenario to always select from the latest library of aspects of real world. Weather can be tuned for individual test cases given a project ODD.
In our definition of a Logically Abstract Scenario, you must define an Abstract Road Network / Nexus that can logically be used to map onto a true RoadNetwork (OpenDrive file).
In our definition of a Logically Abstract Scenario, there is always a constraint for every parameter. Some of these constraint are under defined: keep(thisParameter == ""). This allows the user to later define: keep(thisParameter == [5..100]kph) ... keep(thisParmeter == 100).
This makes transitioning easy and possible: Abstract --> Logically Abstract --> Logical --> Concrete
This makes transitioning from "Logically Abstract" --> "Logical" as simple as assigning values to the constraints.
Process:
Abstract (has no reference at all to a road network or lanes, has broken references that will require more work to map later) -->
Logically Abstract (has constraints to satisfy a road network, lanes can be referenced abstractly, route can be referenced abstractly, I can create and anchor a starting distance from the beginning of a route or start of a RoadSegment / laneSection ) -->
Logical ( values can easily just be assigned to exiting constraints (i.e. a list of RoadNetworks, list of direct lane and list of route assignment to constraints ) note: likely will need a dictionary for this -->
Concrete (pick RoadNetwork, pick lane assignments, pick route) (Done.)
Please see my use case:
http://www.plantuml.com/plantuml/uml/VLN1RYCt3BtxAuYzR084WoxQq-QoYqqE0P9DiMct5r_a6TgZHaDDHOqTz-jBKbOcJXC36KyaKUJZ8_dc2sUNyZI4XVspe9WHaj_q-JDyQdvjVci-_G9V6HnmY-IIZz3X5aCSCLt03IHqmV-Ba7kNvGSJWjE7HsmpGrphfbd1BgRGmPBCjbY5dTipuDFegFEq0Nb1splQwEBCDzX0YgxZ2nZSAB_iDoGltPETz2Xciipx4IrKNFrjKPTadhRO-pOWdzlgNN26gu3g8dtCm8W3v5YGgBbOPYG8_X6XdmP76c65lTlwcCpv3ftwRq0esJdATZt99ZxpndFUAQucpXSGegGP7EUQUuWRtxeWjoM2XPhZi5cCBha1CyfoDHrON75EhhMOkJ_5_MlY9KPbMv3_qNi6-NCQ97iNmhu2cek_beJ7o3xxI1SWaR0pN9tdxAX5GrKHcVMI58zV-rQBg4ctJcz39DtGssPNYYTmnuICbCs86tY80qA7Qq_QPOfF8TugC8FujGPRqiC1PKr6pkEEpVkmFx0-fv9ZvO4neA9DSJ3AWiiebi6laajx9NBcrFXSKc6qWRzAuQ6rIa6U24iwdZg_zTta0fYprZ4oRFmMIHbEqRAzlxfg5elFLoMzYXzsFlSpY_9e-OVOOU3BnUTlVOoCGD5ANgYfGDuxljMHbZg_T_uZkkuxPidgiO4RueokWqdC7DbPfRbKBi5tV9eOpYf6yIpC7RavVoUKsJstH7277Tp4dsLU9ViGmEG8F3LIroCyCozsrrH2Rz_Awlp0t3mcq4PISq-vjB_d9QcZhlGHouMsDtHgFdZI4tDTvydKK7CEkCxM323ODcBUcLqTjDSqDKB0dunmXzbrBhkNrL09XVlr4QkEt-ZgkIVEaXLOiw1ggAYgfV3zTXzn7B0Eyfl4I1tDK99NeNsoaUIC8ukoctYQZ-EkFEdfmmT5Sqqy9IoqIy9f_-BE65nRLQz3RfDVbUL11pxoBB2Un4SHKeJUobRJcKEVZlSgXfjfBmxdhIENQ-dZKiIuFbMSosUZEnlI2xXJgPFfXjiY8ZeCzZtGMDTF8oQF0vA5onBCWCrAKHebcypgc168RP6YhGiJGjj7toAVFtzEMR-DaEDfc7KY1TuPdxzOlzAMAcicUsaQJ1irdseoAyefcmS_JA6e_U_o5Ze7Vibg8S9uiDQrV6UglaLAcET-vX82NTl_dwfuuCXgOJJVZqXNFsv-NjVlZ3nx81JUM7LTo24EJkSO_vb4hOC2YSaE5AiWtwBwcrE9QTQk8iWMlwg-GNiZw_UTTCzvitdeumvscdqonA6ox8y3sK1KRvSBpd5SV47gfY7y1m00
## Describe your Question or Problem
Will OpenSCENARIO 2.0 support "Logically Abstract Scenarios"?
... given this will eventually be logical and concrete for testing.
Problem: I need to have this methodology recognized to ensure enough sharing of this type of scenario is possible within industry. I see a problem / gap of transitioning directly from "Abstract Scenario" to "Logical Scenario"; it feels like a lot of effort is necessary to make this transition. I would like there to be more ease in making a scenarios logical and then concrete. This definition is also necessary for tool vendors that want to build a tool to develop, transition or aid scenario progression.
## Describe your research
Working currently with multiple tool vendors on these topics. Have seen the expectations of vendors. OpenScenario 1.0 has these constraints, in concrete scenarios. Vendors are looking for faster ways to make this transition from 1.0 to 2.0 easier.
## Proposal 1
Implement Logically Abstract Scenario Use Case in Work Flow folder:
using the contents of : LogicallyAbstractScenarioUseCase_2021_Aug_07-fixed.zip
[LogicallyAbstractScenarioUseCase_2021_Aug_07-fixed.zip](/uploads/3d1f4e254b3674fcf50f08a3100fad2d/LogicallyAbstractScenarioUseCase_2021_Aug_07-fixed.zip)
Updated UML:
'http://www.plantuml.com/plantuml/uml/dLPDR-Cs4xxxLmnyMHlmwdtJzkIzR93a420VHTBTNdePIsEB3KMg7CgE--ixGrgcrzraWGAHP9BpySmp7yndZXZYqDb9-Z5nFX84isdZ4YwgdwjVgel_moK30jVaC1WF3Mt9-fx20cuX45hpDq5iCSgB0W7gmptLaS6lTJD9mSu7sy0VBibcARl3FGEzzkWQupOW7wXRT1jTp4n55GIF3I-WmrxUR3PEFhedE-55n6GPzpqbLtxrftfL7sffIwsfBV5SLs-3oxWIgCQx3n6Og8FeCn8HLyb83gnv8MY73frwM56BM-D3ChuZLFiL22KxT36f1zca8szSuWv-DN1SWFKIfaMEO-pMRqoDLhN5WxegVZX9z1YmeqYoN0q75bSS0zR9PspVuVwSUFKniYt8VsiDW_oXEea6hTsFW4horn9mxzb4uzq2n1Cr2LTZEAAhIL4LH28jJXIFMPjQawX1rwZQu9rk96sLoyc3G7qW9XUJ45Vmx3k2XjR6QPKfFeLufy0InCk3Ct7qV40v1YFdViV9UhS_i5v2YNxaWScIeWs-IvHPZ2IIrgm2XhqIMJXDV0fnYT4AVi-9Xpfb2kBWA8TZN6EsfXdGGZ9M8nF3ncp9ASF1fsWVhw-hoMHvdSCRySFEnBQmA8-cl_CDMVuqMLwrtZE1yodbcPeHo5l7TzhIakUtpfyyDWyK9QgN2Zx2hUD8sC30L0XM6JW8mV_ar-l0C1jXYd4bxzJIl7hBdGeUoyBYOOSs_clkMM70MaWZ2OmxHuI5cwGxerViUajBjN0dE_C3WwLTKgrxfrh6nTm9XjLQamkAHQDk4qILxupJasH_RAmq5i47iBIEgIf006v4l4bokZKoCBAcHQmiV662UuhOOCJJjEWiXSVrgRZYcOxhOqrCrV7qtsLV12gOFVX8o-97MxB1qAZ35O5nyDYJUxwwURXykds4dwgBQlxfZUfZtz6n_GkDXKD9VH8KfdGylwP6vaWzotsGHwxQEAlbCqidXahCKmLrutW8b1Cb98NzYMfliHv7PaDS1xFAoyCG-S1bEalGqzftuyoQGglfriWai1HS2Qbwt--PBomfIqR7zRS6rz87a-Mj00XHckOBfp9v9uymoqCYUc-LY8F6VUh-1TphHQXp0-xoUD8MIpUDOhfvxGs5Zbn2eVGAs3A0Sjab8hHp7OXW7d1Rj0D1tNfJ4yzp-CXiDWhaFRYbnHNQJ7HNUtMJFL-LSYc2XrX-B7YShcdwXg7J4PrVoi0F3PInzzyjF9jkiFd2-bM-aixk6oqiUYNTcZD9nI4JrqVIptER4wSMwa2nj21dX8HrcvDNRfFicHemfzbUmAur8fmF-RiP1oj77qsaZayc9aBmEws0V0bIaqk1v-FKmZmrhfzklzwC5xOyUt1K4xDUa1AzOukgJ7yD0jHgs3xa0wKCeyITB1PAVIXNGBxRZh69IWh-U-mNA-EHcZ5YfpujxsIZzRlnNxC4suxbODINASxIVJJ24WySVJ_vJAuPEliF
[LogicallyAbstractScenarioUseCasePlant_UML.uml](/uploads/5c4313f19d46cd10514ca786c566aa9c/LogicallyAbstractScenarioUseCasePlant_UML.uml)
![LogicallyAbstractScenarioUseCasePlant_UML](/uploads/7318619d1bcbbc649146d6f757cd9d18/LogicallyAbstractScenarioUseCasePlant_UML.png)
![Abstraction](/uploads/c92f11598021c35d39ab23a1a4a1ea5f/Abstraction.png)
![ParmaterValueAbstractions](/uploads/843d2aa1697430b8929114a83ef33137/ParmaterValueAbstractions.png)
## Ask your question
Can the Usage and Pragmatics group consider this use case?>2.1Richard HeidtmanRichard Heidtman2021-03-01https://code.asam.net/simulation/openscenario/2.x/-/issues/303Referring the end of a road and a position that is offroad2023-07-20T09:32:20ZRichard HeidtmanReferring the end of a road and a position that is offroad<!--- Provide a general summary of the issue in the Title above -->
## Describe the feature
<!--- Is your feature request related to a problem? --->
<!--- A clear and concise description of what the problem is. --->
<!--- Example: I am...<!--- Provide a general summary of the issue in the Title above -->
## Describe the feature
<!--- Is your feature request related to a problem? --->
<!--- A clear and concise description of what the problem is. --->
<!--- Example: I am always frustrated when [...]. --->
In Domain Model for Road / Abstract Road Network / Nexus I would like a way to: express a position that is EndOfRoad and express a position that is OffRoad. Will this be possible?
What is EndOfRoad: There is/are no more road(s) to traverse.
What is OffRoad: The object is no longer on the road but is on an OpenArea.
What is OffDrivablRoad: The object is no longer on the road but is on a sidewalk (type), SideWalkJunction, ParkingSpot, Junction, ?
## Describe the solution you would like
<!--- A clear and concise description of what you want to happen. --->
## OPTION 1 - this may not be right
![image](/uploads/1709d1cbe5b0a87498927f694524a6a2/image.png)
## OPTION 2 - this may not be right
```
roads = [R_A.end(), R_B.start(), R_C.end(), R_D.start()]
until: v1.sPosition == R_A.end() ??? Is R_A.end() => sPosition?
```
## Describe alternatives you have considered
<!--- A clear and concise description of any alternative solutions or features you have considered. --->
## Describe the backwards compatibility
<!--- How does the feature impact the backwards compatibility of the current major version of OpenSCENARIO? --->
<!--- If the suggested feature would be implemented would there be an issue with the previous versions of OpenSCENARIO? What part of OpenSCENARIO would break or improve by this feature? --->
## Additional context
<!--- Add any other context or screenshots about the feature request here. --->
## LINKED TO:
https://code.asam.net/simulation/standard/openscenario-2.0/-/issues/242
<!--- If you already know which Project Group or Working Group is relevant for this issue, add it here (with the command /label)-->
<!--- Group labels you can use are: ~DomainModel ~Usage&Pragmatics ~Language -->
<!--- Subgroup labels can be found here https://code.asam.net/simulation/standard/openscenario-2.0/-/labels -->>2.1Richard HeidtmanRichard Heidtman2021-08-09https://code.asam.net/simulation/openscenario/2.x/-/issues/364Need position term "alongside" (like ahead_of and behind) in Domain Model2021-12-09T18:00:55ZRichard HeidtmanNeed position term "alongside" (like ahead_of and behind) in Domain ModelNeed position term "alongside" (like ahead_of and behind) in Domain Model
See Related Issue "Park" - https://code.asam.net/simulation/standard/openscenario-2.0/-/issues/363
Semantic meaning - neither behind nor ahead_of (exactly matche...Need position term "alongside" (like ahead_of and behind) in Domain Model
See Related Issue "Park" - https://code.asam.net/simulation/standard/openscenario-2.0/-/issues/363
Semantic meaning - neither behind nor ahead_of (exactly matched for the s-position)
### Use Case1 - Park Alongside vehicle2
### Use Case2 - Drive Alongside vehicle2>2.1Richard HeidtmanRichard Heidtman2021-08-31https://code.asam.net/simulation/openscenario/2.x/-/issues/363Need "Turn" Action in Domain Model2021-12-09T18:00:26ZRichard HeidtmanNeed "Turn" Action in Domain ModelNeed "Turn" Action in Domain Model
```
Turn() with:
direction(left)
through(junction: j1)
along(route: r1)
within(duration: 5 sec)
at(at: start)
until( @event1)
Turn() with:
direction(left)
t...Need "Turn" Action in Domain Model
```
Turn() with:
direction(left)
through(junction: j1)
along(route: r1)
within(duration: 5 sec)
at(at: start)
until( @event1)
Turn() with:
direction(left)
through(junction: j1)
from(ls_1.lane: 1)
to(ls_4.lane: 1)
within(duration: 5 sec)
at(at: start)
until( @event1)
```
Rich's funny syntax:
```
Turn( [Direction] THROUGH [Junction] USE [Path] WITHIN [Duration] ) at:start until: @event #NOT_YET_SUPPORTED
Turn( [Direction] THROUGH [Junction] FROM [Lane] TO [Lane] USE [Path] WITHIN [Duration] ) at:start until: @event #NOT_YET_SUPPORTED
```>2.1Richard HeidtmanRichard Heidtman2021-08-31https://code.asam.net/simulation/openscenario/2.x/-/issues/359Use of Semi-colon ";" (Syntax) Example from DM: vehicle1.drive() with: speed(...2021-10-29T09:56:34ZRichard HeidtmanUse of Semi-colon ";" (Syntax) Example from DM: vehicle1.drive() with: speed(30kph); acceleration(5kphps)Use of Semi-colon ";"
Example from DM:
saw this mentioned here: https://code.asam.net/simulation/standard/openscenario-2.0/-/blob/DM/Modifiers-for-Actions/Domain_Model/Modifiers/Modifiers_for_actions.adoc
```
vehicle1.drive() with: sp...Use of Semi-colon ";"
Example from DM:
saw this mentioned here: https://code.asam.net/simulation/standard/openscenario-2.0/-/blob/DM/Modifiers-for-Actions/Domain_Model/Modifiers/Modifiers_for_actions.adoc
```
vehicle1.drive() with: speed(30kph); acceleration(5kphps)
```
### Proposal 1
```
probably needs to go with "with"...
[';']
```>2.1Pierre MAI (PMSF IT Consulting)Pierre MAI (PMSF IT Consulting)2021-08-31https://code.asam.net/simulation/openscenario/2.x/-/issues/358Need "Reverse" Action opposite to Drive in the opposite direction. Need it ex...2021-12-09T18:00:40ZRichard HeidtmanNeed "Reverse" Action opposite to Drive in the opposite direction. Need it explicitly.Need "Reverse" Action opposite to Drive in the opposite direction. Need it explicitly.
### Example 1
```
v1.Reverse() with:
speed(speed: 5 kph)
at(at: start)
until(@event1)
```Need "Reverse" Action opposite to Drive in the opposite direction. Need it explicitly.
### Example 1
```
v1.Reverse() with:
speed(speed: 5 kph)
at(at: start)
until(@event1)
```>2.12021-08-31https://code.asam.net/simulation/openscenario/2.x/-/issues/205Expressions needed for "Stochastics Constraints from OSC1.1"2021-12-09T18:06:03ZRichard HeidtmanExpressions needed for "Stochastics Constraints from OSC1.1"<!--- Provide a general summary of the issue in the Title above -->
Expressions needed for "Stochastics Constraints from OSC1.1"
Need expressions for describing:
```
1) ProbabilityDistributionSet with a probability given value and weigh...<!--- Provide a general summary of the issue in the Title above -->
Expressions needed for "Stochastics Constraints from OSC1.1"
Need expressions for describing:
```
1) ProbabilityDistributionSet with a probability given value and weight (or weighted probability).
2) NormalDistribution with a given: expected mean value, variance (stdev), min and max.
3) UniformDistribution with a given: min and max.
4) PoissonDistribution with a given: expected value, min and max.
5) Histogram with a given: binName, weight (or weighted probability) and min and max.
```
## Describe the feature
<!--- Is your feature request related to a problem? --->
<!--- A clear and concise description of what the problem is. --->
<!--- Example: I am always frustrated when [...]. --->
## Describe the solution you would like
<!--- A clear and concise description of what you want to happen. --->
```
keep( parameterName == probability with:
prob(value, weight)
prob(value, weight)
prob(value, weight)
prob(value, weight))
keep( parameterName == normal with:
expected_value(mean)
variance(stdev)
range(min,max))
keep( parameterName == uniform with: range(min, max) )
keep( parameterName == poisson with:
expected_value(value)
range(min, max))
keep( parameterName == histogram with:
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max)))
```
## Syntax Proposal 1
```
Add to <keyword> : 'probability', 'normal', 'uniform', 'poisson', 'histogram', 'prob', 'expected_value', 'variance', 'bin'
Add the following syntax:
<probability-expression> ::= 'prob''('<value>',' <weight>')'
<expected-value-expression> ::= 'expected_value''('<mean>')'
<variance-expression> ::= 'variance''('<stdev>')'
<bin-expression> ::= 'bin''('<bin-identifier>, <weight>, <range>')'
<weight> :: = <number> #
<mean> ::= <number> #
<stdev> ::= <number> #
<with-declaration-for-stochastics> ::= 'with'':'
<with-member-for-stochastics>+
<with-member-for-stochastics> ::= <probability-expression> | <expected-value-expression>
| <variance-expression> | <bin-expression>
Respect This from Types Group:
<constraint-expression>::= (<bool-expression> [<bool-implication>]) | <stochastic-expression>
<bool-implication>::= '=>' <bool-expression>
<stochastic-expression> :: = <probability-constraint> | <normal-distribution-constraint> | <uniform-distribution-constraint>
| <poisson-distribution-constraint> | <histogram-constraint>
<probability-constraint> ::= <parameter-name> '==' 'probability' <with-declaration-for-stochastics>
#NOTE: Use <probability-expression> as <with-member-for-stochastics>
<normal-distribution-constraint> ::= <parameter-name> '==' 'normal' <with-declaration-for-stochastics>
#NOTE: Use <expected-value-expression>, <variance-expression>, <range> as <with-member-for-stochastics>
<uniform-distribution-constraint> ::= <parameter-name> '==' 'uniform' <with-declaration-for-stochastics>
#NOTE: Use <range> as <with-member-for-stochastics>
<poisson-distribution-constraint> ::= <parameter-name> '==' 'poisson' <with-declaration-for-stochastics>
#NOTE: Use <expected-value-expression>, <range> as <with-member-for-stochastics>
<histogram-constraint> ::= <parameter-name> '==' 'histogram' <with-declaration-for-stochastics>
#NOTE: Use <bin-expression> as <with-member-for-stochastics>
Create these as examples:
(<parameter-name> '==' <value>) | (<parameter-name> '>=' <value>) | (<parameter-name> '<=' <value>)
| (<parameter-name> '>' <value>) | (<parameter-name> '<' <value>)
| (<parameter-name> 'Undefined') | (<parameter-name> 'Abstract') | (<parameter-name> '==' 'None')
Create Examples for Stochastic Constraints, as above with numbers:
keep( parameterName == probability with:
prob(value, weight)
prob(value, weight)
prob(value, weight)
prob(value, weight))
keep( parameterName == normal with:
expected_value(mean)
variance(stdev)
range(min,max))
keep( parameterName == uniform with: range(min, max) )
keep( parameterName == poisson with:
expected_value(value)
range(min, max))
keep( parameterName == histogram with:
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max))
bin(binName, weight, range(min, max)))
```
### Vote: Accept Proposal 1
```
Vote:
Yes-3-(Rich Heidtman, Rolf Magnus, Tjark Koopmann)
No-0
Abstain-0
No-Vote-0
```
NOTE: Should be revisited in 2.1 for possible corrections.
## Describe alternatives you have considered
<!--- A clear and concise description of any alternative solutions or features you have considered. --->
## Describe the backwards compatibility
<!--- How does the feature impact the backwards compatibility of the current major version of OpenSCENARIO? --->
<!--- If the suggested feature would be implemented would there be an issue with the previous versions of OpenSCENARIO? What part of OpenSCENARIO would break or improve by this feature? --->
This is desired for compatibility with OpenSCENARIO v1.1.
https://releases.asam.net/OpenSCENARIO/1.1.0/modelDocumentation/content/XsdTreeView.html
```
This may require use of sample() to define numberOfTestRuns and weither or not use a randomSeed.
Note: randomSeed is optional in OpenSCENARIO 1.1.0 and this should be integer (there is an error with this currently being double).
```
![image](/uploads/7099d66aa618a7f75acd8ed9893ce567/image.png)
![image](/uploads/da40ee66c97c27a098ac5270dd083f07/image.png)
## Additional context
<!--- Add any other context or screenshots about the feature request here. --->
<!--- If you already know which Project Group or Working Group is relevant for this issue, add it here (with the command /label)-->
<!--- Group labels you can use are: ~DomainModel ~Usage&Pragmatics ~Language -->
<!--- Subgroup labels can be found here https://code.asam.net/simulation/standard/openscenario-2.0/-/labels -->>2.1Richard HeidtmanRichard Heidtman2021-08-31https://code.asam.net/simulation/openscenario/2.x/-/issues/765Handling structural complexity migrating from OSC1.x to OSC2.02023-12-07T12:28:26ZNajumun HIDHAYATHULLA (MathWorks)Handling structural complexity migrating from OSC1.x to OSC2.0OSC 1.x is hierarchically nested and complex when compared to OSC 2.0 serial and Parallel phases.
**We need to address the gap in migration from OSC1.x to 2.0 for structural complexity.**
**OSC1.x Equivalent**
![OSC1](/uploads/8b43193...OSC 1.x is hierarchically nested and complex when compared to OSC 2.0 serial and Parallel phases.
**We need to address the gap in migration from OSC1.x to 2.0 for structural complexity.**
**OSC1.x Equivalent**
![OSC1](/uploads/8b43193e601eb4d987adfa4072add77a/OSC1.JPG)
**OSC2.0**
![2.0](/uploads/175f5ff3170c5ee25922405a0aebf359/2.0.jpg)>2.1Mirko BULAJA (AVL-AST d.o.o.)Mirko BULAJA (AVL-AST d.o.o.)2023-03-09https://code.asam.net/simulation/openscenario/2.x/-/issues/764TimeToCollision2024-03-21T13:21:15ZNajumun HIDHAYATHULLA (MathWorks)TimeToCollisionThe definition for _**TimeToCollision**_ is different across OSC1.x and OSC2.0. We need to ensure same meaning is conveyed for TimeToCollision.
OSC1.x - Time to collision is calculated as the distance divided by the relative speed.
OS...The definition for _**TimeToCollision**_ is different across OSC1.x and OSC2.0. We need to ensure same meaning is conveyed for TimeToCollision.
OSC1.x - Time to collision is calculated as the distance divided by the relative speed.
OSC2.0 - Time that is left until a possible collision between a traffic_participant and a reference physical_object takes place.
(_Here assumption is both the actors move with their current velocities_)
**Possible solution:**
Either ensure it is defined the same across the standards or update the migration guideline with the possible approach.>2.12023-03-09https://code.asam.net/simulation/openscenario/2.x/-/issues/763Support for 'continuous' property in OSC2.0 Actions2023-12-07T12:24:35ZNajumun HIDHAYATHULLA (MathWorks)Support for 'continuous' property in OSC2.0 ActionsFor RelativeTargetSpeed Action, LongitudinalDistance Action and LateralDistance Action, we have a continuous property in OSC1.x. There is no equivalent for the same in OSC2.0 DM.
Following workarounds has been considered for OSC2.0. Pl...For RelativeTargetSpeed Action, LongitudinalDistance Action and LateralDistance Action, we have a continuous property in OSC1.x. There is no equivalent for the same in OSC2.0 DM.
Following workarounds has been considered for OSC2.0. Please confirm if this is the right approach. If not, it is recommended to include it in the OSC2.0 DM.
**RelativeTargetSpeed action**
![spd_cont](/uploads/8147ebdcad3072ff1407ddce02b281ae/spd_cont.jpg)
**LongitudinalDistance action**
![lon_cont](/uploads/7eb0ba9b77fa222da37881610113765e/lon_cont.png)>2.1Rolf MAGNUS (Akkodis)Rolf MAGNUS (Akkodis)2023-03-09https://code.asam.net/simulation/openscenario/2.x/-/issues/761No equivalent to MiscObject Category in OSC 2.0 DM2023-12-07T12:28:06ZNajumun HIDHAYATHULLA (MathWorks)No equivalent to MiscObject Category in OSC 2.0 DMThere is no way to represent static objects like tree, building etc. in OSC 2.0. We use MiscObject category in [OSC1.x](https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/MiscObj...There is no way to represent static objects like tree, building etc. in OSC 2.0. We use MiscObject category in [OSC1.x](https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/MiscObjectCategory.html)>2.1Florian BOCK (CARIAD SE)Florian BOCK (CARIAD SE)2023-03-09https://code.asam.net/simulation/openscenario/2.x/-/issues/757OverrideGearAction update (from OverrideControllerValueAction)2023-12-07T12:27:31ZMirko BULAJA (AVL-AST d.o.o.)OverrideGearAction update (from OverrideControllerValueAction)Manual and automatic gear support in the `OverrideGearAction`.
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/OverrideGearAction.htmlManual and automatic gear support in the `OverrideGearAction`.
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/OverrideGearAction.html>2.1Nicolas OCHOA LLERAS (DENSO Automotive)Nicolas OCHOA LLERAS (DENSO Automotive)2023-03-16https://code.asam.net/simulation/openscenario/2.x/-/issues/756DirectionalDimension support in 1.2 conditions2023-12-15T09:27:43ZMirko BULAJA (AVL-AST d.o.o.)DirectionalDimension support in 1.2 conditions`DirectionalDimension` enumeration and usage in `AccelerationCondition`, `RelativeSpeedCondition` and `SpeedCondition`.
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/Direct...`DirectionalDimension` enumeration and usage in `AccelerationCondition`, `RelativeSpeedCondition` and `SpeedCondition`.
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/DirectionalDimension.html>2.1Mirko BULAJA (AVL-AST d.o.o.)Mirko BULAJA (AVL-AST d.o.o.)2023-03-16https://code.asam.net/simulation/openscenario/2.x/-/issues/752Dome image is not covered in migration guide2023-12-07T12:51:26ZAndreas RAUSCHERT (BMW Group)andreas.rb.rauschert@bmw.deDome image is not covered in migration guideWas introduced in OSC 1.2
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/DomeImage.htmlWas introduced in OSC 1.2
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/DomeImage.html>2.12023-03-16https://code.asam.net/simulation/openscenario/2.x/-/issues/750Animation action is missing in the migration guide2023-12-07T12:27:17ZAndreas RAUSCHERT (BMW Group)andreas.rb.rauschert@bmw.deAnimation action is missing in the migration guideWas introduced with OSC 1.2
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/AnimationAction.htmlWas introduced with OSC 1.2
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/AnimationAction.html>2.1Evan LOWE (Hexagon)Evan LOWE (Hexagon)2023-03-23https://code.asam.net/simulation/openscenario/2.x/-/issues/748Relative clearance condition is missingin the migration guide2023-12-07T12:26:47ZAndreas RAUSCHERT (BMW Group)andreas.rb.rauschert@bmw.deRelative clearance condition is missingin the migration guideWas introduced with OSC 1.2
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/RelativeClearanceCondition.htmlWas introduced with OSC 1.2
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/RelativeClearanceCondition.html>2.1Rolf MAGNUS (Akkodis)Rolf MAGNUS (Akkodis)2023-03-23https://code.asam.net/simulation/openscenario/2.x/-/issues/747Speed profile action is missing in the migration guide2023-12-07T12:29:20ZAndreas RAUSCHERT (BMW Group)andreas.rb.rauschert@bmw.deSpeed profile action is missing in the migration guideWas introduced newly in OSC 1.2.
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/SpeedProfileAction.htmlWas introduced newly in OSC 1.2.
https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/SpeedProfileAction.html>2.1Zuqiu MAO (51WORLD)Zuqiu MAO (51WORLD)2023-03-23https://code.asam.net/simulation/openscenario/2.x/-/issues/746Non-movement controllers are missing in the migration guide2023-12-07T12:37:14ZAndreas RAUSCHERT (BMW Group)andreas.rb.rauschert@bmw.deNon-movement controllers are missing in the migration guideNew Animation & Light controllers from 1.2New Animation & Light controllers from 1.2>2.12023-03-30https://code.asam.net/simulation/openscenario/2.x/-/issues/745Metadata conversion is missing in the migration guide2023-12-07T12:37:20ZAndreas RAUSCHERT (BMW Group)andreas.rb.rauschert@bmw.deMetadata conversion is missing in the migration guideAt the moment the metadata of the scenario file header is addressed in the migration guide here:
https://simulation.pages.asam.net/openscenario/openscenario-antora-gen/ASAM_OpenSCENARIO_Migration/latest/mg_storyboard.html#_file_headers
...At the moment the metadata of the scenario file header is addressed in the migration guide here:
https://simulation.pages.asam.net/openscenario/openscenario-antora-gen/ASAM_OpenSCENARIO_Migration/latest/mg_storyboard.html#_file_headers
It is stated that 'Metadata can be added as fields to the top-level scenario.'
Needs clarification, what fields are (example?) and if this is a sufficient solution>2.12023-03-30https://code.asam.net/simulation/openscenario/2.x/-/issues/744Parameter constraints are missing in the migration guide2023-12-07T12:40:30ZAndreas RAUSCHERT (BMW Group)andreas.rb.rauschert@bmw.deParameter constraints are missing in the migration guideThe migration guide currently only mentions how parameter declarations can be converted: https://www.asam.net/static_downloads/public/asam-openscenario/2.0.0/migration/mg_parameters.html
But the additional `ValueConstraint` for paramete...The migration guide currently only mentions how parameter declarations can be converted: https://www.asam.net/static_downloads/public/asam-openscenario/2.0.0/migration/mg_parameters.html
But the additional `ValueConstraint` for parameters is not mentioned in the migration guide: https://www.asam.net/static_downloads/ASAM_OpenSCENARIO_V1.2.0_Model_Documentation/modelDocumentation/content/ValueConstraintGroup.html>2.12023-03-30