search

ftgTUGraz / Chat2Scenario

[IEEE IV 2024] Official implementation of paper "Chat2Scenario: Scenario Extraction From Dataset Through Utilization of Large Language Model"
13 stars 0 forks source link

Adapting OpenScenario to VTD #59

Open rechuin opened 5 months ago

rechuin commented 5 months ago

Hi Developers,

I would update several changes to adapt VTD configuration

  1. VTD only support Openscenario 1.0. but your generated file based on the 1.2 library. Therefore, some modification should be done, or provide a option to user to choose which simulation software they are using in your source code

  2. I use this description to generate the scenario "The ego vehicle maintains its lane and velocity. Initially, Target Vehicle 1 is driving in the left adjacent lane. It then accelerates and changes lanes to the right, eventually driving in front of the ego vehicle."

  3. the generated file and fixed file can be found in the attachment testScenario.zip

  4. some syntax need to change: TimeReference None/ /TimeReference to TimeReference        Timing domainAbsoluteRelative="absolute" scale="1" offset="0"/ /TimeReference

  5. remove the TrajectoryRef tag

  6. For the Scenario not to stop at the first frame. StopTrigger need to change below: Condition name="stop_simulation" delay="0.0" conditionEdge="none" SimulationTimeCondition value="11.68" rule="greaterOrEqual"/ to Condition name="stop_simulation" delay="0.0" conditionEdge="rising" SimulationTimeCondition value="11.68" rule="greaterThan"/

  7. For the cars to get on the trajectory, change for each trajectory. StartTrigger need to change below: Condition name="start" delay="0.0" conditionEdge="none" SimulationTimeCondition value="0.0" rule="greaterOrEqual"/ to Condition name="start" delay="0.0" conditionEdge="rising" SimulationTimeCondition value="0.0" rule="greaterThan"/

  8. you also can find the vehicle name definitions are different in scenarioObject section. I would suggest this name should be customized by user.

Thanks for your effort in this project

ZhengyuWang123 commented 4 months ago

Hi,

Thanks very much for using Chat2Scenario. Please see my answers of your questions in below:

- Question #1 - #3: We already add a new feature in Chat2Scenario, where the ASAM OpenSCENARIO version 1.0 1.1 and 1.2 can be freely selected by the users. This new feature will be released soon.

- Question #4: Short answer: This syntax is not necessary to be changed. Explanation: Both syntaxes mean that the sccenario starts at t=0s in the simulator. More details are available in the ASAM homepage https://releases.asam.net/OpenSCENARIO/1.0.0/Model-Documentation/content/TimeReference.html

- Question #5: If you choose the ASAM OpenSCENARIO 1.0.0, the parameter TrajectoryRef tag will be not existed in the xosc file.

- Question #6 - #7: Short answer: 1) In ASAM OpenSCENARIO 1.0, the rule = "greaterThan" is automtically configured by Chat2Scenario. For version 1.1 and 1.2, the rule = "greaterOrEqual" is utilized. 2) conditionEdge = "none" should not be changed.

Explanation:
If we use conditionEdge = "rising", this condition in the start triggers can never be fulfilled. First step time is 0.0. Since rule for the Act start trigger is greaterThan, the act is not started yet. Next step time is greater than 0.0 and the act is started. At this point the event trigger condition are evaluated for the first time. And since there are no previous value to compare with, there are no "rising" edge detected. Please see more details in https://github.com/esmini/esmini/issues/461

Question #8: As the requirements of users are quite diverse, currently we are not capable to satisfy all of them. This feature could be added in the future.

Have any further questions, please do not hesitate to reach us out.

Best regards, Chat2Scenario Team