This repository provides source code for MUSICC, a project run by the Connected Places Catapult on behalf of the Department for Transport.

[[TOC]]

As highly automated vehicles (HAVs) are deployed on public roads, regulators need to make sure that these systems are safe. This challenge requires coordination between regulators and system developers – with common (or at least aligned) approaches to validation desirable.

One of the big challenges is achieving enough coverage of real-world situations to know that Automated Driving Systems (ADS) are acceptably safe. ADS developers have indicated that testing by driving vehicles on public roads is not enough, due to:

• The large number of miles needed to cover all situations which could be encountered.
• A lack of control of the test parameters.

The solution is likely to involve more than one technology but will almost certainly include an element of simulation. MUSICC has created a system to store and share scenarios: an ADS will be expected to demonstrate its performance in these before release to market. As far as we know, MUSICC is the first project of its type to build a proof of concept system specifically designed for regulatory use.

The project is led by a regulator (Department for Transport) and an impartial, neutral mediator (Connected Places Catapult). It is influenced by a highly credible industrial advisory group, including representatives of several major OEMs, tool providers, ADS developers, research and innovation organisations, CAV testbeds and insurers.

A working prototype has been built and interested stakeholders are invited to sign up and try out the system. We are particularly interested in feedback on how test scenarios might be used in a future regulatory regime, which can be provided either by email or on GitLab.

Our aim is to create a central scenario repository for regulatory use (as prototyped at CPC). However, many organisations would like a tool to store and manage their own test scenarios without having to make those scenarios publicly available. We've made this possible by enabling users to install their own instance of MUSICC, using Docker and/or the code in this repository. From our point-of-view, the benefits are:

• If MUSICC is used operationally, we get better feedback on how it needs to evolve, and better evidence that it is a useful, practical tool.
• Other organisations can contribute to the codebase.
• It encourages the industry to adopt MUSICC's scenario format.
• Regulators other than the DfT have the opportunity to try out MUSICC in a test environment.

User installations of MUSICC can synchronise the regulatory scenario set from the master instance with the click of a button.

We have released this code under the AGPL, but would like to assure anyone who wishes to integrate their tools with MUSICC that a well-defined API exists for this, and there should not be any risk to their existing IP.

1. Pull the latest MUSICC Docker image and Postgres 12 from Docker Hub

docker pull connectedplacescatapult/musicc:latest
docker pull postgres:12

2. Create a network for the database and MUSICC and run the containers

docker network create musicc_net
docker run -d --name=db --network=musicc_net -e POSTGRES_PASSWORD=postgres postgres:12
docker run -d -p 80:80 --name=web --network=musicc_net connectedplacescatapult/musicc:latest

3. Navigate to localhost

The default admin account details are

• username: admin
• password: admin

To access the admin panel navigate to localhost/admin

To synchronise the regulatory scenarios, and SDL revisions, from the master instance managed by CPC, first register your private system:

• Log on to the master instance
• Go to 'profile' (top-right), 'My Registered Systems', and generate a registration token
• On your local instance, go to the 'system' tab (along the bottom)
• Click on 'Register System' and copy the token in
• Choose a prefix. This will be applied to the "friendly" ID for all scenarios created in this instance. Note scenarios from the CPC-managed "master" instance of MUSICC all have an "M" prefix (e.g. M1234)

To synchronise the scenarios and SDL:

• On the master instance, under 'My Registered Systems', click 'Generate synchronisation token' for your new private instance
• On your private installation, in the 'system' tab, click 'Synchronise system' and copy this token into the box

• User guide (PDF) - this is the best place to start
• Guide to MUSICC's scenario format (PDF), aka the SDL (scenario description language)
• Developer setup and building from source
• Docker configuration
• Guide on how to contribute to the project
• Roadmap for future development
• Doxygen for code

• ASAM OpenSCENARIO
• ASAM OpenDRIVE
• ASAM OpenLABEL
• Es Mini, an OpenSCENARIO visualisation/simulation tool