Resolve performance issues immediately to speed up May’s development cycle.
Identify software regressions before code changes get shipped to production vehicles.
Continue to improve autonomous driving capabilities by turning anomalies seen in the field into test cases for development and validation.
Applied Intuition’s collaboration to deliver on May’s feature requests set off a ‘Simulation Flywheel’—a test-driven approach in which development becomes faster and regressions happen less frequently as the development team runs more scenarios, test cases, and continuous integration (CI) tests.
Applied Intuition’s simulator, Object Sim, allows May to test its software in virtual scenarios to ensure a vehicle drives safely and meets specific criteria for rider comfort.
A simulation-based approach replaces traditional long soak tests done on routes in the real world. The May team can create different scenarios quickly to verify safety before a software update is pushed.
May can programmatically find anomalies and other events of interest from hours of drive logs collected by its fleet of vehicles. The team can then turn these events of interest into test cases for re-simulation in Log Sim.
Applied Intuition’s CI platform, Cloud Engine, lets May identify regressions in its autonomous driving software and find root causes before the new software is deployed.
Object Sim supports faster algorithm development, allowing May to test new functionalities, such as an obstructed unprotected right-hand turn, over a database of scenarios.
May Mobility has saved hours of engineering time by catching regressions automatically in simulation before deploying software to the fleet.
By testing rider comfort and catching regressions in simulation instead of the real world, May has been able to achieve a higher-quality rider experience.
May is able to expand to new operational design domains (ODDs) faster as a result of incorporating simulations into its development cycle.
.webp)
.webp)
