WO2021061981A1

WO2021061981A1 - Automated swarming vehicle test environment

Info

Publication number: WO2021061981A1
Application number: PCT/US2020/052488
Authority: WO
Inventors: Brian Stewart; Paul Lewis; Ben Hill; Dave HOLLINGSHEAD; Sean Gardner; John Peterson; Kasper WOICESHYN; Eric BUDD
Original assignee: Autonomous Solutions, Inc.
Priority date: 2019-09-24
Filing date: 2020-09-24
Publication date: 2021-04-01
Also published as: US20210086784A1; EP4034956A4; EP4034956A1

Abstract

An automated swarming vehicle test environment includes a vehicle automation platform (VAP), a first swarming vehicle, and a second swarming vehicle. In some embodiments, a first test plan is created by a VAP for a first swarming vehicle. The first test plan comprises: a time series of vehicle trajectory data for the first swarming vehicle, and position data for the first swarming vehicle relative to a test vehicle. The first test plan is sent from the VAP to the first swarming vehicle. In some embodiments, a second test plan is created by the VAP for a second swarming vehicle. The second test plan comprises: a time series of vehicle trajectory data for the second swarming vehicle, and position data for the second swarming vehicle relative to the test vehicle. The second test plan is sent from the VAP to the second swarming vehicle.

Description

Automated Swarming Vehicle Test Environment BACKGROUND

Autonomous vehicles are predicted to be the next iteration (or frontier) of human transportation. Currently many automobiles integrate advanced driver-assistance systems in their vehicles that allow a vehicle to be driven by a human and with some autonomy assistance. Safety, of course, is the highest priority. It is predicted that autonomous vehicles one day will be safer than human driven vehicles since autonomous vehicles can communicate with each other, react predictably, don’t get tired, don’t drive inebriated, and are not distracted. Roadways with the combination of autonomous vehicles and human conducted vehicles can be messy.

SUMMARY

An automated swarming vehicle test environment is disclosed that includes a vehicle automation platform; a first swarming vehicle; and a second swarming vehicle. The first swarming vehicle includes a first vehicle control unit in communication with the vehicle automation platform and receives a first test plan from the vehicle automation platform; a first throttle subsystem in communication with and controlled by the first vehicle control unit; a first steering subsystem in communication with and controlled by the first vehicle control unit; and a first brake subsystem in communication with and controlled by the first vehicle control unit. In some embodiments, the first vehicle control unit controls the operation of the first throttle subsystem, the first steering subsystem, and the first brake subsystem based on the first test plan. In some embodiments, the second swarming vehicle includes a second vehicle control unit in communication with the vehicle automation platform and receives a second test plan from the vehicle automation platform; a second throttle subsystem in communication with and controlled by the second vehicle control unit; a second steering subsystem in communication with and controlled by the second vehicle control unit; and a second brake subsystem in communication with and controlled by the second vehicle control unit. In some embodiments, the second vehicle control unit controls the operation of the second throttle subsystem, the second steering subsystem, and the second brake subsystem based on the second test plan.

Some embodiments include a vehicle automation platform that comprises a transceiver and a controller communicatively coupled with the transceiver. In some embodiments, the controller: creates a first test plan for a first swarming vehicle and a second test plan for a second swarming vehicle. The first test plan, for example, comprises: a time series of vehicle trajectory data for the first swarming vehicle, and position data for the first swarming vehicle relative to a test vehicle. The second test plan, for example, comprises: a time series of vehicle trajectory data for the second swarming vehicle, and position data for the second swarming vehicle relative to a test vehicle. The first test plan may be sent to the first swarming vehicle via the transceiver and the second test plan may be sent to the second swarming vehicle via the transceiver. In some embodiments, the controller receives a system test plan from a user and creates the first test plan and the second test plan based on the system test plan.

Some embodiments include a method comprising creating at a vehicle automation platform a first test plan for a first swarming vehicle, sending the first test plan from the vehicle automation platform to the first swarming vehicle; creating at the vehicle automation platform a second test plan for a second swarming vehicle; and sending the second test plan from the vehicle automation platform to the first swarming vehicle. The first test plan may include a time series of vehicle trajectory data for the first swarming vehicle, and position data for the first swarming vehicle relative to a test vehicle. The second test plan may include a time series of vehicle trajectory data for the second swarming vehicle, and position data for the second swarming vehicle relative to the test vehicle; In some embodiments, the method may also include receiving a system test plan from a user; and wherein the first test plan is created based on the system test plan, and wherein the second test plan is created based on the system test plan.

These illustrative embodiments are mentioned not to limit or define the disclosure, but to provide examples to aid understanding thereof. Additional embodiments are discussed in the Detailed Description, and further description is provided there. Advantages offered by one or more of the various embodiments may be further understood by examining this specification or by practicing one or more embodiments presented.

BRIEF DESCRIPTION OF THE FIGURES

These and other features, aspects, and advantages of the present disclosure are better understood when the following Detailed Description is read with reference to the accompanying drawings.

FIG. 1 illustrates an example automated swarming vehicle test environment according to some embodiments. FIG. 2 is a block diagram of an automated swarming vehicle test system hardware according to some embodiments.

FIG. 3 illustrates how a user test plan can be created and sent to a swarming vehicle according to some embodiments.

FIG. 4 shows a block diagram of a drive by wire automated swarming vehicle test system according to some embodiments.

FIG. 5 is a block diagram of an automated swarming vehicle test system using vehicle to vehicle communication according to some embodiments.

FIG. 6 shows an illustrative computational system for performing functionality to facilitate implementation of embodiments described herein.

DETAILED DESCRIPTION

Most road accidents occur due to human error. Car companies are making great advances to correct this by developing vehicles with advanced driver-assistance systems and autonomous vehicles. Many advanced driver-assistance systems may automate, adapt, or enhance vehicle systems for safety and better driving. These improvements reduce road fatalities by minimizing human error. Advanced driver assistance system features may include features to help avoid collisions and accidents, for example, by alerting the driver to potential problems or by taking over control of the vehicle.

Some embodiments of the invention include systems and methods for testing vehicles with advanced driver assistance systems or autonomous vehicles (e.g., test vehicles) using a swarm of autonomous vehicles following a choregraphed maneuver according to a test plan. In some embodiments, a plurality of swarming vehicles can be assigned choreographed maneuvers to test the response of a test vehicle. These choreographed maneuvers, for example, may be defined or input by test plan created or developed by user. In some embodiments, a test plan may be defined by an industry standard setting body.

As described in this disclosure, the term “autonomous vehicle” includes any vehicle that can be completely or partially operated with or without a driver. For example, an autonomous vehicle may include a vehicle with an advanced driver assistance system such as, for example, a system that can provide adaptive cruise control, collision avoidance, or pedestrian crash avoidance mitigation; incorporate satnav/trafFic warnings; alert the driver to other cars or dangers; provide lane departure warnings; provide automatic lane centering; show what is in blind spots; or connect to smartphones for navigation instructions; etc. As another example, an autonomous vehicle may include a vehicle that can be operated completely without human interaction.

FIG. 1 illustrates a swarming scenario according to some embodiments. In this example, test vehicle 105 is shown driving down a three lane freeway with four swarming vehicles: swarming vehicle 110A, swarming vehicle 110B, swarming vehicle HOC, and swarming vehicle 110D (collectively or individually swarming vehicle 110). The test vehicle 105, for example, may be an autonomous vehicle. The swarming vehicles 110, for example, can also be autonomous vehicles that are programed to perform a specific choregraphed maneuver defined within a test environment as defined by a test plan. In this embodiment, the test environment is the three lane freeway shown in FIG. 1.

The test environment may include any type of roadway environment such as, for example, a multilane highway or freeway, a city intersection, a roundabout, a road through a school zone, a road with a pedestrian walkway, road with public transportation, a parking lot, a road with a bicycle lane, etc., or any combination of these.

The swarming vehicles 110 can be programmed to perform any number of choreographed maneuvers based on a test plan. In this example, the test plan has swarm vehicle 110A driving straight along the inside lane as shown by path 115 A, the swarming vehicle HOB driving straight along the middle test lane as shown by path 115B, the swarming vehicle HOC driving in the outside lane and at some point of time swerving into the middle lane as shown by path 115C, and the swarming vehicle HOD driving in the outside lane and at some point of time swerving into the middle lane as shown by path 115D. With this test plan, for example, the test operators may strive to determine how the test vehicle 105 reacts to the choreographed maneuvers.

In some embodiments, the test plan may include an industry standard test plan and the results of the reaction by the test vehicle 105 can be used to determine whether the test vehicle meets any number of industry certifications or standards.

In some embodiments, test operators can adjust software on the test vehicle 105 based on the test vehicle’s 105 reaction. Afterwards, the test plan can be repeated as needed with the test vehicle 105. a While four swarming vehicles 110 are shown, any number of swarm vehicles may be included.

In some embodiments, the swarming vehicles 110 may include a sedan, a van, a truck, a truck with a trailer, a semi -truck, a bus, a bicycle, a motorcycle, a train, a pedestrian, etc., or any combination of these.

In some embodiments, the test vehicle 105 can be independently operated relative to the swarming vehicles 110. For example, the test vehicle 105 may be operated by the test vehicle’s operating system or control system whereas the swarming vehicles 110 may be controlled by vehicle automation platform (e.g., Mobius command and control developed by Autonomous Solutions Inc.).

In some embodiments, a test plan for a swarming vehicle 110 may include instructions to maneuver the swarming vehicle 110 around the test vehicle 105 such as, for example, based on a time series of trajectory data. In some embodiments, a test plan can be communicated to each swarming vehicle from the vehicle automation platform in real time or the test plan can be communicated prior to a test. In some embodiments, the test plan may include position, velocity, or acceleration values at each time interval with respect to the test vehicle 105 or with respect to a position within the test environment. In some embodiments, each of the heading, position, velocity, or acceleration value may include other data such as, for example, turning curvatures, trajectories, etc. At each time interval, for example, the vehicle control unit (VCU) within each swarming vehicle can determine where the swarming vehicle needs to be with respect to the test vehicle (or a fixed location within the test environment) and adjust the heading, position, velocity, or acceleration as needed to execute the test plan as accurately as possible.

In some embodiments, a test plan may be sent only to a swarming vehicle(s) and not to a test vehicle(s). In some embodiments, the test plan is sent to a swarming vehicle(s) and test vehicle(s) but the test vehicle does not ultimately follow any instructions in the test plan.

The following table is an example test plan for a swarming vehicle 110. The test plan, for example, may include one or more of the following data: time interval (e.g., on tenth of a second but any time interval can be used), test vehicle location (Vx), test vehicle location (Vy), first swarming vehicle location (Tlx), first swarming vehicle location (Tly), second swarming vehicle location relative to the test v(T2x), second swarming vehicle location (T2y), test vehicle speed (VSpeed), first swarming vehicle speed (T1 Speed), second swarming vehicle speed (T2Speed), test vehicle direction (Vheading), first swarming vehicle direction (TIHeading), second swarming vehicle direction (T2Heading), the first swarming vehicle position from the host (TlPosfmH), the first swarming vehicle angle from the host (TlASngfmH), the second swarming vehicle position from the host T2PosfmH, or the second swarming vehicle angle from the host T2AngFmH. In this example, the position of the test vehicle (Vx, Vy) is set to zero and the positions of the swarming vehicles are determined relative to the test vehicle.

The following table is another example test plan for a swarming vehicle 110. The test plan, for example, may include one or more of the following data: time interval (e g., on tenth of a second but any time interval can be used), test vehicle location (Vx), test vehicle location (Vy), first swarming vehicle location (Tlx), first swarming vehicle location (Tly), second swarming vehicle location relative to the test v(T2x), second swarming vehicle location (T2y), test vehicle speed (VSpeed), first swarming vehicle speed (T1 Speed), second swarming vehicle speed (T2 Speed), test vehicle direction (Vheading), first swarming vehicle direction (TIHeading), and second swarming vehicle direction (T2Heading). In this example, the position of the test vehicle (Vx, Vy) is set to zero and the positions of the swarming vehicles are determined relative to the test vehicle.

The above tables only shows trajectory values for two swarming vehicles. Any number of swarming vehicles may be included in a test plan. In some embodiments, each swarming vehicle 110 may include a vehicle control unit (VCU) 215 that is in communication (e.g., wireless communication) with a vehicle automation platform (VAP) 205 as shown in FIG. 2. The VCU 210 can control the swarming vehicle’s steering 215, brake 220, throttle 225, or transmission 230 systems. In some embodiments, the VCU 210 be in communication with any number of vehicle sensors 235 such as, for example, a GPS sensor, a speedometer, lidar, radar, camera, etc. In some embodiments, the VCU 210 may include all or some of the components of computational system 600. In some embodiments, the VAP 205 may include all or some of the components of computational system 600.

In some embodiments, the VAP 205 may modify a user created test plan. For example, a specific vehicle may have unique or specific acceleration rates, deceleration rats, turning radii, etc. that may be updated or modified by the VAP 205. In some embodiments, a modified test plan may include trajectory data for a single or specific swarming vehicle.

In some embodiments, the VCU 210 can create a path segment from the test plan. The path segment may describe the path (e.g., the paths 115 in FIG. 1) that each swarming vehicle 110 will follow over time. The VCU 210 may compare the position, velocity, or heading of the swarming vehicle 110 with the position, velocity, or heading specified in the test plan for past time intervals or for future time intervals. If the swarming vehicle 110 is out of position or predicted to be out of position (within predetermined tolerances or test plan provided tolerances), the VCU 210 may adjust the speed or heading of the swarming vehicle by sending commands to the steering 215, brake 220, throttle 225, or transmission 230 subsystems, etc. For example, if the swarming vehicle 110 is going to slow or is behind on its position, the VCU 210 can send a signal to the throttle 225 to apply more gas to the engine (or electricity to the motor) to speed up the swarming vehicle 110. As another example, if the swarming vehicle 110 is moving in an incorrect heading then the VCU 210 can send a command to the steering 215 to change the direction the swarming vehicle 110 is heading.

In some embodiments, a test plan can be user generated by a user and supplied to the VAP 205 as shown in FIG. 3. For example, the test plan 305 data can be input into a spreadsheet. As another example, the test plan can be created graphically within software (e.g., at the VAP 205) that shows the position of each swarming vehicle 110 over time. In some embodiments, the VAP 205 can translate the test plan 305 into data that can be recognized or executed by the VCU 210. The VAP 205 may communicate the translated test plan 310 to the VCU 210 over a wireless network 315 (e.g., WIFI network, Bluetooth network, radio network, Rajent network, 3G network, 4G network, 5G network, etc.). I

In some embodiments, the VCU 210 may send swarming vehicle sensor data to the VAP 205 such as, for example, speed, position, heading, etc. In some embodiments, the VCU 210 may

In some embodiments, the swarming vehicle 110 may include an actuation kit that can be used to drive the steering, brake, throttle, or transmission of the swarming vehicle.

In some embodiments, the swarming vehicle 110 may include drive by wire functionality which can control the brake, throttle, or transmission of the swarming vehicle as shown in FIG. 4. In some embodiments, the VCU 210 may communicate with a gateway 405 that can control or communicate commands to the steering 215, brake 220, throttle 225, or transmission 230. The gateway 405, for example, may be hosted by one or more servers in the cloud or include one or more local servers. The VCU 210 may communicate with the gateway 405 via a CAN bus interface 410. In some embodiments, the VCU 210 may be placed within swarming vehicle 110 and may be coupled with the gateway 405 of the swarming vehicle 110.

In some embodiments, the various swarming vehicles 110 may communicate trajectory data with each other. This can be done, for example, for safety and accuracy purposes. For example, each swarming vehicle may communicate with other swarming vehicles to ensure correct position is maintained or timely emergency messages are sent and received. A vehicle to vehicle communication protocol may be used as shown in FIG. 5. In some embodiments, the VCUs of the various swarming vehicles 110 may communicate with each other through a wireless network and our via a wireless network transceiver/antenna system 505. In some embodiments, the VCUs of the various swarming vehicles may communicate with each other such as, for example, trajectory data, etc. Based on trajectory data from other swarm vehicles 110, a specific swarming vehicle 110 may recognize that a collision is likely and may perform counter measures (e.g., braking, steering, speeding up, etc.) to ensure that the collision does not occur.

In some embodiments, an automated swarming vehicle test system may manage or choreograph multiple swarming vehicles in close proximity to each other at high speeds In some embodiments, an automated swarming vehicle test system may execute complex test cases with multiple vehicles with reproducible accuracy or fidelity, which may provide valuable data on the effectiveness of the test vehicle software.

In some embodiments, an automated swarming vehicle test system may convert a manned test environment to an autonomous environment, which may remove humans from risky test scenarios and may allow for more risky tests without putting the human lives at risk. Given the potential complexity of the swarming configurations, there is a higher likelihood of reduced risk to property when controlled by an automated swarming vehicle test system.

In some embodiments, an automated swarming vehicle test system may repeat a choreographed test scenario with multiple swarming vehicles the same way each time. Each test scenario, for example, may be repeated until the desired data or outcomes are achieved by the test vehicle.

In some embodiments, an automated swarming vehicle test system can reduce overall costs by eliminating recurring human costs by way of compensation, health, and varying recurring expenses.

In some embodiments, an automated swarming vehicle test system, which can the repeatedly execute test cases with a high degree of accuracy, may allow for more testing within a shorter period of time.

The computational system 600, shown in FIG. 6 can be used to perform any of the embodiments of the invention. For example, a VCU 210, gateway 405, and/or VAP 205 may include any or all the components of the computational system 600. As another example, computational system 600 can be used perform any calculation, identification and/or determination described here. Computational system 600 includes hardware elements that can be electrically coupled via a bus 605 (or may otherwise be in communication, as appropriate). The hardware elements can include one or more processors 610, including without limitation one or more general-purpose processors and/or one or more special-purpose processors (such as digital signal processing chips, graphics acceleration chips, and/or the like); one or more input devices 615, which can include without limitation a mouse, a keyboard and/or the like; and one or more output devices 620, which can include without limitation a display device, a printer and/or the like. The computational system 600 may further include (and/or be in communication with) one or more storage devices 625, which can include, without limitation, local and/or network accessible storage and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid- state storage device, such as a random access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash-updateable and/or the like. The computational system 600 might also include a communications subsystem 630, which can include without limitation a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device and/or chipset (such as a Bluetooth device, an 802.6 device, a Wi Fi device, a WiMax device, cellular communication facilities, etc.), and/or the like. The communications subsystem 630 may permit data to be exchanged with a network (such as the network described below, to name one example), and/or any other devices described herein. In many embodiments, the computational system 600 will further include a working memory 635, which can include a RAM or ROM device, as described above.

The computational system 600 also can include software elements, shown as being currently located within the working memory 635, including an operating system 640 and/or other code, such as one or more application programs 645, which may include computer programs of the invention, and/or may be designed to implement methods of the invention and/or configure systems of the invention, as described herein. For example, one or more procedures described with respect to the method(s) discussed above might be implemented as code and/or instructions executable by a computer (and/or a processor within a computer). A set of these instructions and/or codes might be stored on a computer-readable storage medium, such as the storage device(s) 625 described above.

In some cases, the storage medium might be incorporated within the computational system 600 or in communication with the computational system 600. In other embodiments, the storage medium might be separate from a computational system 600 (e.g., a removable medium, such as a compact disc, etc.), and/or provided in an installation package, such that the storage medium can be used to program a general-purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computational system 600 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computational system 600 (e g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.) then takes the form of executable code.

Unless otherwise specified, the term “substantially” means within 5% or 10% of the value referred to or within manufacturing tolerances. Unless otherwise specified, the term “about” means within 5% or 10% of the value referred to or within manufacturing tolerances.

Numerous specific details are set forth herein to provide a thorough understanding of the claimed subject matter. However, those skilled in the art will understand that the claimed subject matter may be practiced without these specific details. In other instances, methods, apparatuses or systems that would be known by one of ordinary skill have not been described in detail so as not to obscure claimed subject matter.

Some portions are presented in terms of algorithms or symbolic representations of operations on data bits or binary digital signals stored within a computing system memory, such as a computer memory. These algorithmic descriptions or representations are examples of techniques used by those of ordinary skill in the data processing arts to convey the substance of their work to others skilled in the art. An algorithm is a self-consistent sequence of operations or similar processing leading to a desired result. In this context, operations or processing involves physical manipulation of physical quantities. Typically, although not necessarily, such quantities may take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared or otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to such signals as bits, data, values, elements, symbols, characters, terms, numbers, numerals or the like. It should be understood, however, that all of these and similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, it is appreciated that throughout this specification discussions utilizing terms such as “processing,” “computing,” “calculating,” “determining,” and “identifying” or the like refer to actions or processes of a computing device, such as one or more computers or a similar electronic computing device or devices, that manipulate or transform data represented as physical electronic or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the computing platform.

The system or systems discussed herein are not limited to any particular hardware architecture or configuration. A computing device can include any suitable arrangement of components that provides a result conditioned on one or more inputs. Suitable computing devices include multipurpose microprocessor-based computer systems accessing stored software that programs or configures the computing system from a general-purpose computing apparatus to a specialized computing apparatus implementing one or more embodiments of the present subject matter. Any suitable programming, scripting, or other type of language or combinations of languages may be used to implement the teachings contained herein in software to be used in programming or configuring a computing device.

Embodiments of the methods disclosed herein may be performed in the operation of such computing devices. The order of the blocks presented in the examples above can be varied — for example, blocks can be re-ordered, combined, and/or broken into sub-blocks. Certain blocks or processes can be performed in parallel.

The use of “adapted to” or “configured to” herein is meant as open and inclusive language that does not foreclose devices adapted to or configured to perform additional tasks or steps. Additionally, the use of “based on” is meant to be open and inclusive, in that a process, step, calculation, or other action “based on” one or more recited conditions or values may, in practice, be based on additional conditions or values beyond those recited. Headings, lists, and numbering included herein are for ease of explanation only and are not meant to be limiting.

While the present subject matter has been described in detail with respect to specific embodiments thereof, it will be appreciated that those skilled in the art, upon attaining an understanding of the foregoing, may readily produce alterations to, variations of, and equivalents to such embodiments. Accordingly, it should be understood that the present disclosure has been presented for purposes of example rather than limitation, and does not preclude inclusion of such modifications, variations and/or additions to the present subject matter as would be readily apparent to one of ordinary skill in the art.

Claims

CLAIMS That which is claimed:

1. An automated swarming vehicle test environment comprising: a vehicle automation platform; a first swarming vehicle comprising: a first vehicle control unit in communication with the vehicle automation platform and that receives a first test plan from the vehicle automation platform; a first throttle subsystem in communication with and controlled by the first vehicle control unit; a first steering subsystem in communication with and controlled by the first vehicle control unit; and a first brake subsystem in communication with and controlled by the first vehicle control unit; wherein the first vehicle control unit controls the operation of the first throttle subsystem, the first steering subsystem, and the first brake subsystem based on the first test plan; a second swarming vehicle comprising: a second vehicle control unit in communication with the vehicle automation platform and that receives a second test plan from the vehicle automation platform; a second throttle subsystem in communication with and controlled by the second vehicle control unit; a second steering subsystem in communication with and controlled by the second vehicle control unit; and a second brake subsystem in communication with and controlled by the second vehicle control unit; wherein the second vehicle control unit controls the operation of the second throttle subsystem, the second steering subsystem, and the second brake subsystem based on the second test plan.

2. The automated swarming vehicle test environment according to claim 1, further comprising: a third swarming vehicle comprising: a third vehicle control unit in communication with the vehicle automation platform and that receives a third test plan from the vehicle automation platform; a third throttle subsystem in communication with and controlled by the third vehicle control unit; a third steering subsystem in communication with and controlled by the third vehicle control unit; and a third brake subsystem in communication with and controlled by the third vehicle control unit; wherein the third vehicle control unit controls the operation of the second throttle subsystem, the third steering subsystem, and the second brake subsystem based on the third test plan.

3. The automated swarming vehicle test environment according to claim 1, wherein the vehicle automation platform comprises a server that is in wireless communication with the first vehicle control unit and the second vehicle control unit.

4. The automated swarming vehicle test environment according to claim 1, wherein the first test plan comprises a time series of vehicle trajectory data.

5. The automated swarming vehicle test environment according to claim 1, further comprising a test vehicle.

6. The automated swarming vehicle test environment according to claim 5, wherein the first test plan comprises position data for the first swarming vehicle in relation the test vehicle, and wherein the second test plan comprises position data for the second swarming vehicle in relation the test vehicle.

7. The automated swarming vehicle test environment according to claim 5, wherein the first swarming vehicle comprises a first GPS sensor; and the first vehicle control unit monitors the position of the first swarming vehicle relative to the test vehicle using the first GPS sensor; and wherein the second swarming vehicle comprises a second GPS sensor; and the second vehicle control unit monitors the position of the second swarming vehicle relative to the test vehicle using the second GPS sensor.

8. The automated swarming vehicle test environment according to claim 5, wherein the first swarming vehicle includes a first GPS, wherein the first vehicle control unit monitors the position and the trajectory of the first swarming vehicle relative to the test vehicle, and wherein the first vehicle control unit stops the first swarming vehicle in the event the trajectory of the first swarming vehicle will likely cause an accident with the test vehicle.

9. The automated swarming vehicle test environment according to claim 1, wherein the vehicle automation platform receives data for a system test plan from a user and creates a first test plan and a second test plan based on the system test plan.

10. The automated swarming vehicle test environment according to claim 1, wherein the first vehicle control unit produces control signals for first throttle subsystem, the first brake subsystem, or the first steering subsystem based on the first test plan.

11. A vehicle automation platform comprising: a transceiver; and a controller communicatively coupled with the transceiver, the controller: creates a first test plan for a first swarming vehicle, the first test plan comprises: a time series of vehicle trajectory data for the first swarming vehicle, and position data for the first swarming vehicle relative to a test vehicle; sends the first test plan to the first swarming vehicle via the transceiver; creates a second test plan for a second swarming vehicle, the second test plan comprises: a time series of vehicle trajectory data for the second swarming vehicle, and position data for the second swarming vehicle relative to the test vehicle; and sends the second test plan to the second swarming vehicle via the transceiver.

12. The vehicle automation platform according to claim 11, wherein the controller receives a system test plan from a user and creates the first test plan and the second test plan based on the system test plan.

13. The vehicle automation platform according to claim 11, wherein the controller does not send the test vehicle a test plan that the test vehicle ultimately follows.

14. The vehicle automation platform according to claim 11, wherein the first test plan and the second test plan are included in a single test plan that includes the first test plan and the second test plan.

15. The vehicle automation platform according to claim 11, wherein the controller creates a third test plan for a third swarming vehicle, the third test plan comprises: a time series of vehicle trajectory data for the third swarming vehicle, and position data for the third swarming vehicle relative to the test vehicle; and wherein the controller sends the third test plan to the third swarming vehicle via the transceiver

16. A method compri sing : creating at a vehicle automation platform a first test plan for a first swarming vehicle, the first test plan comprises: a time series of vehicle trajectory data for the first swarming vehicle, and position data for the first swarming vehicle relative to a test vehicle; sending the first test plan from the vehicle automation platform to the first swarming vehicle; creating at the vehicle automation platform a second test plan for a second swarming vehicle, the second test plan comprises: a time series of vehicle trajectory data for the second swarming vehicle, and position data for the second swarming vehicle relative to the test vehicle; and sending the second test plan from the vehicle automation platform to the second swarming vehicle.

17. The method according to claim 16, further comprising receiving a system test plan from a user; and wherein the first test plan is created based on the system test plan, and wherein the second test plan is created based on the system test plan.

18. The method according to claim 16, wherein a test plan that includes instructions for the test vehicle to follow is not sent to the test vehicle.

19. The method according to claim 16, wherein the first test plan and the second test plan are included in a single test plan that includes the first test plan and the second test plan.

20. The method according to claim 16, further comprising: creating at the vehicle automation platform a third test plan for a second swarming vehicle, the third test plan comprises: a time series of vehicle trajectory data for the third swarming vehicle, and position data for the third swarming vehicle relative to the test vehicle; and sending the third test plan from the vehicle automation platform to the third swarming vehicle.