openscenarioopenscenario.org/docs/oscusermeeting20151015_vires.pdf · • provide transferable xml...

15.10.201524.04.2012 - Rev. A (c) 2015 VIRES GmbH, protection notice DIN ISO 16016 Slide 1

OpenSCENARIObringing content to the road

Marius DupuisVIRES Simulationstechnologie GmbH

1st OpenSCENARIO MeetingOctober 15th, 2015

(c) 2015 VIRES Simulationstechnologie GmbHAll rights reserved

Static Content

Road SurfaceRoad Network

15.10.2015 (c) 2015 VIRES GmbH, protection notice DIN ISO 16016 Slide 2

Motivation

Fact: De-facto standardization has been realized on lower levels

Result: Road Files may be transferred between various simulation tools

+


Motivation – Current Situation

• Result: Dynamic content may not yet be transfered in a standardized wayand depends highly on the tools involved

• ADAS functionality requires extensive testing in various environments

• Feature sets of various tools are highly different

• Each tool is well suited for its specific purpose

• Migrating secenarios from one tool to another one requires high effort

• Independent 3rd parties (e.g. authorities) are not able to provide scenario

definitions in a format compatible with multiple tools

Scenario

Format A

Static Content

Tool C

User Ext. C

Scenario

Format B

Scenario

Format C

Tool B

User Ext. B

Tool A

User Ext. A


Motivation

Assumption

All tools share a considerable

fraction of common functionality

Conclusion

Description of dynamic content

may be harmonized

A B

C

Dynamic ContentStatic Content

Scenario

Objection

Same dynamic content does

not implicate identical results!


Objectives

• Provide transferable XML scenario definition for various use cases

• static content by reference

• dynamic content

• Use OpenDRIVE / OpenCRG as basic layers

• Allow for independent content provision by 3rd parties

• Provide standardized / open tool-sets for validation of scenario definitions

• Establish support services

• Establish user community

Tool A

Tool B

Tool C

Scenario

3rd Party

Specification

Static ContentImport/Export

OpenSCENARIO initiative

Support

Test and

Validation


OpenSCENARIO – Road Map

VIRES ASC(S HLRS

Daimler

Initial Team

Associated Partners

Opel

Porsche

Tool Suppliers (dSPACE, IAV, IPG etc.)

Tool Suppliers and 3rd Parties

OEMs (Audi, BMW, Volkswagen etc.)

Requirements

Results

Research (DLR, fka, FKFS etc.)

Tier1(tbd.)

Definition Phase, Stage 1

Format

Specification

Review


VIRES

Assoc. Partners (Daimler, Opel, Porsche)

Core Team


Partners and Users


Requirements

Results

Research (DLR, fka, FKFS, HLRS etc.)

Tier1(tbd.)


Format

Specification

Review

3rd parties (e.g. authorities)

ASC(S

Member B

Member C

Member A Member D

Member E

Member F

Member G

Test Tools ValidationToolsSupport/

Website



VIRES


Core Team


Partners and Users


Requirements

Results


Tier1(tbd.)


Format

Specification

Review


ASC(S

Member B

Member C

Member A Member D

Member E

Member F

Member G


Website

Who?



Maintenance Phase

VIRES


Core Team


Partners and Users


Requirements

Core Services


Tier1(tbd.)

Format

Specification

Review


ASC(S

Member B

Member C

Member A Member D

Member E

Member F

Member G

Support /

Website

Test Tools

ValidationTools

Repositories

Test Data



Mid-Term Target


OpenSCENARIO will be a key element in PEGASUS project-> we really have to deliver!


Where we are today:

Website:

OpenSCENARIO – Status

http://www.openscenario.org


Where we are today:

Downloadarea:


http://www.openscenario.org


Where we are today:

Tracking System (public and "core team"):


http://tracking.vires.com

Newsletter: [email protected]


What we have: 3rd draft specification as XMind Mind map(see also www.openscenario.org/download.html)

OpenSCENARIO – Specification


Catalogs and References



Entities (own vehicle and others):



Storyboard(by maneuver vs. by actor):



Storyboard(by maneuver):



Conditions:



Maneuver List:



Coming back to

one important question...



VIRES


Core Team


Partners and Users


Requirements

Results


Tier1(tbd.)


Format

Specification

Review


ASC(S

Member B

Member C

Member A Member D

Member E

Member F

Member G


Website

Who?



• Schema File

• Validator

• Examples

• Reference Implementations

Next Steps



That's it!

Thank you for your attention!

Questions?

openscenarioopenscenario.org/docs/oscusermeeting20151015_vires.pdf · • provide transferable xml...

Documents