Patent Application
20230202469
Embodiments of the present disclosure relate generally to operating autonomous driving vehicles. More particularly, embodiments of the disclosure relate to how to drive with caution under uncertainty for an autonomous driving vehicle (ADV).
Vehicles operating in an autonomous mode (e.g., driverless) can relieve occupants, especially the driver, from some driving-related responsibilities. When operating in an autonomous mode, the vehicle can navigate to various locations using onboard sensors, allowing the vehicle to travel with minimal human interaction or in some cases without any passengers.
Motion planning and control are critical operations in autonomous driving. However, in certain situations, the driving environment may not be clear, and the prediction of the movement of the obstacle may be uncertain. It is difficult to plan the trajectory of the ADV to avoid a collision with the obstacle.
Embodiments of the disclosure are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.
Various embodiments and aspects of the disclosures will be described with reference to details discussed below, and the accompanying drawings will illustrate the various embodiments. The following description and drawings are illustrative of the disclosure and are not to be construed as limiting the disclosure. Numerous specific details are described to provide a thorough understanding of various embodiments of the present disclosure. However, in certain instances, well-known or conventional details are not described in order to provide a concise discussion of embodiments of the present disclosures.
Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in conjunction with the embodiment can be included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification do not necessarily all refer to the same embodiment.
According to some embodiments, when the driving environment is not clear, and the prediction of the movement of the obstacle may be uncertain, it is important to adopt a caution way to drive. This disclosure provides a way to handle the uncertainty from prediction and make the driving safe. Multiple trajectories of the obstacle may be predicted with corresponding probabilities, for example, a first trajectory with a highest probability, a second trajectory with a second highest probability, etc. If the difference between the highest probability and the second highest probability is very small, below a first threshold, the ADV may drive with caution, with a speed lower than the speed limit and prepare to stop at any moment. In addition, if the difference between the highest probability and the second highest probability is not very small but small enough, above the first threshold but below a second threshold, however, the damage or consequence of the second trajectory is high, such as a collision, the ADV may also drive with caution, with the speed lower than the speed limit and prepare to stop at any moment.
According to some embodiments, an obstacle is detected based on sensor data obtained from a plurality of sensors of the ADV. Multiple trajectories of the obstacle are predicted with corresponding probabilities including a first predicted trajectory of the obstacle with a highest probability and a second predicted trajectory of the obstacle with a second highest probability. A cautionary trajectory of the ADV is planned based on at least one of a difference between the highest probability and the second highest probability or a consequence of the second trajectory. The ADV is to drive with a speed lower than a speed limit and prepare to stop in the cautionary trajectory. The ADV is controlled to drive according to the cautionary trajectory.
In one embodiment, whether a difference between the highest probability and the second highest probability is below a first predetermined threshold may be determined.
In one embodiment, it may be determined to plan the cautionary trajectory of the ADV in response to the difference between the highest probability and the second highest probability is below a first predetermined threshold.
In one embodiment, whether a difference between the highest probability and the second highest probability is above a first predetermined threshold and below a second predetermined threshold and the consequence of the second predicted trajectory includes a collision may be determined.
In one embodiment, it may be determined to plan the cautionary trajectory of the ADV in response to the difference between the highest probability and the second highest probability above a first predetermined threshold and below a second predetermined threshold and the consequence of the second predicted trajectory includes a collision.
In one embodiment, for each trajectory of the multiple trajectories of the obstacle, a consequence of a trajectory may be determined
In one embodiment, the first predicted trajectory with the highest probability and the second predicted trajectory with the second highest probability may be updated, it may be determined not to plan the cautionary trajectory of the ADV based on at least one of a difference between the updated highest probability and the updated second highest probability or a consequence of the updated second predicted trajectory.
An ADV refers to a vehicle that can be configured to in an autonomous mode in which the vehicle navigates through an environment with little or no input from a driver. Such an ADV can include a sensor system having one or more sensors that are configured to detect information about the environment in which the vehicle operates. The vehicle and its associated controller(s) use the detected information to navigate through the environment. ADV 101 can operate in a manual mode, a full autonomous mode, or a partial autonomous mode.
In one embodiment, ADV 101 includes, but is not limited to, autonomous driving system (ADS) 110, vehicle control system 111, wireless communication system 112, user interface system 113, and sensor system 115. ADV 101 may further include certain common components included in ordinary vehicles, such as, an engine, wheels, steering wheel, transmission, etc., which may be controlled by vehicle control system 111 and/or ADS 110 using a variety of communication signals and/or commands, such as, for example, acceleration signals or commands, deceleration signals or commands, steering signals or commands, braking signals or commands, etc.
Components 110-115 may be communicatively coupled to each other via an interconnect, a bus, a network, or a combination thereof. For example, components 110-115 may be communicatively coupled to each other via a controller area network (CAN) bus. A CAN bus is a vehicle bus standard designed to allow microcontrollers and devices to communicate with each other in applications without a host computer. It is a message-based protocol, designed originally for multiplex electrical wiring within automobiles, but is also used in many other contexts.
Referring now to
Sensor system 115 may further include other sensors, such as, a sonar sensor, an infrared sensor, a steering sensor, a throttle sensor, a braking sensor, and an audio sensor (e.g., microphone). An audio sensor may be configured to capture sound from the environment surrounding the ADV. A steering sensor may be configured to sense the steering angle of a steering wheel, wheels of the vehicle, or a combination thereof. A throttle sensor and a braking sensor sense the throttle position and braking position of the vehicle, respectively. In some situations, a throttle sensor and a braking sensor may be integrated as an integrated throttle/braking sensor.
In one embodiment, vehicle control system 111 includes, but is not limited to, steering unit 201, throttle unit 202 (also referred to as an acceleration unit), and braking unit 203. Steering unit 201 is to adjust the direction or heading of the vehicle. Throttle unit 202 is to control the speed of the motor or engine that in turn controls the speed and acceleration of the vehicle. Braking unit 203 is to decelerate the vehicle by providing friction to slow the wheels or tires of the vehicle. Note that the components as shown in
Referring back to
Some or all of the functions of ADV 101 may be controlled or managed by ADS 110, especially when operating in an autonomous driving mode. ADS 110 includes the necessary hardware (e.g., processor(s), memory, storage) and software (e.g., operating system, planning and routing programs) to receive information from sensor system 115, control system 111, wireless communication system 112, and/or user interface system 113, process the received information, plan a route or path from a starting point to a destination point, and then drive vehicle 101 based on the planning and control information. Alternatively, ADS 110 may be integrated with vehicle control system 111.
For example, a user as a passenger may specify a starting location and a destination of a trip, for example, via a user interface. ADS 110 obtains the trip related data. For example, ADS 110 may obtain location and route data from an MPOI server, which may be a part of servers 103-104. The location server provides location services and the MPOI server provides map services and the POIs of certain locations. Alternatively, such location and MPOI information may be cached locally in a persistent storage device of ADS 110.
While ADV 101 is moving along the route, ADS 110 may also obtain real-time traffic information from a traffic information system or server (TIS). Note that servers 103-104 may be operated by a third party entity. Alternatively, the functionalities of servers 103-104 may be integrated with ADS 110. Based on the real-time traffic information, MPOI information, and location information, as well as real-time local environment data detected or sensed by sensor system 115 (e.g., obstacles, objects, nearby vehicles), ADS 110 can plan an optimal route and drive vehicle 101, for example, via control system 111, according to the planned route to reach the specified destination safely and efficiently.
Server 103 may be a data analytics system to perform data analytics services for a variety of clients. In one embodiment, data analytics system 103 includes data collector 121 and machine learning engine 122. Data collector 121 collects driving statistics 123 from a variety of vehicles, either ADVs or regular vehicles driven by human drivers. Driving statistics 123 include information indicating the driving commands (e.g., throttle, brake, steering commands) issued and responses of the vehicles (e.g., speeds, accelerations, decelerations, directions) captured by sensors of the vehicles at different points in time. Driving statistics 123 may further include information describing the driving environments at different points in time, such as, for example, routes (including starting and destination locations), MPOIs, road conditions, weather conditions, etc.
Based on driving statistics 123, machine learning engine 122 generates or trains a set of rules, algorithms, and/or predictive models 124 for a variety of purposes. In one embodiment, algorithms 124 may include an algorithm or model to detect an obstacle based on sensor data obtained from a plurality of sensors of the ADV, an algorithm or model to predict multiple trajectories of the obstacle with corresponding probabilities including a first predicted trajectory of the obstacle with a highest probability and a second predicted trajectory of the obstacle with a second highest probability, an algorithm or model to plan a cautionary trajectory of the ADV based on at least one of a difference between the highest probability and the second highest probability or a consequence of the second trajectory, where the ADV is to drive with a speed lower than a speed limit and prepare to stop in the cautionary trajectory, and/or an algorithm or model to control the ADV to drive according to the cautionary trajectory. Algorithms 124 can then be uploaded on ADVs to be utilized during autonomous driving in real-time.
Some or all of modules 301-307 may be implemented in software, hardware, or a combination thereof. For example, these modules may be installed in persistent storage device 352, loaded into memory 351, and executed by one or more processors (not shown). Note that some or all of these modules may be communicatively coupled to or integrated with some or all modules of vehicle control system 111 of
Localization module 301 determines a current location of ADV 300 (e.g., leveraging GPS unit 212) and manages any data related to a trip or route of a user. Localization module 301 (also referred to as a map and route module) manages any data related to a trip or route of a user. A user may log in and specify a starting location and a destination of a trip, for example, via a user interface. Localization module 301 communicates with other components of ADV 300, such as map and route data 311, to obtain the trip related data. For example, localization module 301 may obtain location and route data from a location server and a map and POI (MPOI) server. A location server provides location services and an MPOI server provides map services and the POIs of certain locations, which may be cached as part of map and route data 311. While ADV 300 is moving along the route, localization module 301 may also obtain real-time traffic information from a traffic information system or server.
Based on the sensor data provided by sensor system 115 and localization information obtained by localization module 301, a perception of the surrounding environment is determined by perception module 302. The perception information may represent what an ordinary driver would perceive surrounding a vehicle in which the driver is driving. The perception can include the lane configuration, traffic light signals, a relative position of another vehicle, a pedestrian, a building, crosswalk, or other traffic related signs (e.g., stop signs, yield signs), etc., for example, in a form of an object. The lane configuration includes information describing a lane or lanes, such as, for example, a shape of the lane (e.g., straight or curvature), a width of the lane, how many lanes in a road, one-way or two-way lane, merging or splitting lanes, exiting lane, etc.
Perception module 302 may include a computer vision system or functionalities of a computer vision system to process and analyze images captured by one or more cameras in order to identify objects and/or features in the environment of the ADV. The objects can include traffic signals, road way boundaries, other vehicles, pedestrians, and/or obstacles, etc. The computer vision system may use an object recognition algorithm, video tracking, and other computer vision techniques. In some embodiments, the computer vision system can map an environment, track objects, and estimate the speed of objects, etc. Perception module 302 can also detect objects based on other sensors data provided by other sensors such as a radar and/or LIDAR.
For each of the objects, prediction module 303 predicts what the object will behave under the circumstances. The prediction is performed based on the perception data perceiving the driving environment at the point in time in view of a set of map/rout information 311 and traffic rules 312. For example, if the object is a vehicle at an opposing direction and the current driving environment includes an intersection, prediction module 303 will predict whether the vehicle will likely move straight forward or make a turn. If the perception data indicates that the intersection has no traffic light, prediction module 303 may predict that the vehicle may have to fully stop prior to enter the intersection. If the perception data indicates that the vehicle is currently at a left-turn only lane or a right-turn only lane, prediction module 303 may predict that the vehicle will more likely make a left turn or right turn respectively.
For each of the objects, decision module 304 makes a decision regarding how to handle the object. For example, for a particular object (e.g., another vehicle in a crossing route) as well as its metadata describing the object (e.g., a speed, direction, turning angle), decision module 304 decides how to encounter the object (e.g., overtake, yield, stop, pass). Decision module 304 may make such decisions according to a set of rules such as traffic rules or driving rules 312, which may be stored in persistent storage device 352.
Routing module 307 is configured to provide one or more routes or paths from a starting point to a destination point. For a given trip from a start location to a destination location, for example, received from a user, routing module 307 obtains route and map information 311 and determines all possible routes or paths from the starting location to reach the destination location. Routing module 307 may generate a reference line in a form of a topographic map for each of the routes it determines from the starting location to reach the destination location. A reference line refers to an ideal route or path without any interference from others such as other vehicles, obstacles, or traffic condition. That is, if there is no other vehicle, pedestrians, or obstacles on the road, an ADV should exactly or closely follows the reference line. The topographic maps are then provided to decision module 304 and/or planning module 305. Decision module 304 and/or planning module 305 examine all of the possible routes to select and modify one of the most optimal routes in view of other data provided by other modules such as traffic conditions from localization module 301, driving environment perceived by perception module 302, and traffic condition predicted by prediction module 303. The actual path or route for controlling the ADV may be close to or different from the reference line provided by routing module 307 dependent upon the specific driving environment at the point in time.
Based on a decision for each of the objects perceived, planning module 305 plans a path or route for the ADV, as well as driving parameters (e.g., distance, speed, and/or turning angle), using a reference line provided by routing module 307 as a basis. That is, for a given object, decision module 304 decides what to do with the object, while planning module 305 determines how to do it. For example, for a given object, decision module 304 may decide to pass the object, while planning module 305 may determine whether to pass on the left side or right side of the object. Planning and control data is generated by planning module 305 including information describing how vehicle 300 would move in a next moving cycle (e.g., next route/path segment). For example, the planning and control data may instruct vehicle 300 to move 10 meters at a speed of 30 miles per hour (mph), then change to a right lane at the speed of 25 mph.
Based on the planning and control data, control module 306 controls and drives the ADV, by sending proper commands or signals to vehicle control system 111, according to a route or path defined by the planning and control data. The planning and control data include sufficient information to drive the vehicle from a first point to a second point of a route or path using appropriate vehicle settings or driving parameters (e.g., throttle, braking, steering commands) at different points in time along the path or route.
In one embodiment, the planning phase is performed in a number of planning cycles, also referred to as driving cycles, such as, for example, in every time interval of 100 milliseconds (ms). For each of the planning cycles or driving cycles, one or more control commands will be issued based on the planning and control data. That is, for every 100 ms, planning module 305 plans a next route segment or path segment, for example, including a target position and the time required for the ADV to reach the target position. Alternatively, planning module 305 may further specify the specific speed, direction, and/or steering angle, etc. In one embodiment, planning module 305 plans a route segment or path segment for the next predetermined period of time such as 5 seconds. For each planning cycle, planning module 305 plans a target position for the current cycle (e.g., next 5 seconds) based on a target position planned in a previous cycle. Control module 306 then generates one or more control commands (e.g., throttle, brake, steering control commands) based on the planning and control data of the current cycle.
Note that decision module 304 and planning module 305 may be integrated as an integrated module. Decision module 304/planning module 305 may include a navigation system or functionalities of a navigation system to determine a driving path for the ADV. For example, the navigation system may determine a series of speeds and directional headings to affect movement of the ADV along a path that substantially avoids perceived obstacles while generally advancing the ADV along a roadway-based path leading to an ultimate destination. The destination may be set according to user inputs via user interface system 113. The navigation system may update the driving path dynamically while the ADV is in operation. The navigation system can incorporate data from a GPS system and one or more maps so as to determine the driving path for the ADV.
According to one embodiment, the obstacle such as a vehicle is identified and detected. The obstacle may be detected as a part of perception process performed by perception module 302 based on sensor data obtained from various sensors mounted on an ADV such as the sensors as shown in
According to one embodiment, trajectory module 402 may predict multiple trajectories of the obstacle including the first predicted trajectory, the second predicted trajectory, the third predicted trajectory, etc.
According to one embodiment, probability module 403 may determine the corresponding probabilities of the multiple trajectories of the obstacle including the highest probability, the second highest probability, the third highest probability, etc.
In one embodiment, prediction module 303 may output the multiple trajectories of the obstacle with corresponding probabilities to planning module 305. In one embodiment, prediction module 303 may output the top two or the top three trajectories of the obstacle with the highest probability, the second highest probability, and the third highest probability to planning module 305.
In one embodiment, difference module 501 may determine whether a difference between the highest probability and the second highest probability is below a first predetermined threshold.
In one embodiment, cautionary trajectory module 503 may determine to plan the cautionary trajectory of the ADV in response to the difference between the highest probability and the second highest probability is below a first predetermined threshold.
In one embodiment, consequence module 502 may determine, for each trajectory of the multiple trajectories of the obstacle, a consequence of a trajectory.
In one embodiment, difference module 501 may determine whether a difference between the highest probability and the second highest probability is above a first predetermined threshold and below a second predetermined threshold, and consequence module 502 may determine the consequence of the second predicted trajectory includes a collision may be determined.
In one embodiment, cautionary trajectory module 503 may determine to plan the cautionary trajectory of the ADV in response to the difference between the highest probability and the second highest probability above a first predetermined threshold and below a second predetermined threshold and the consequence of the second predicted trajectory includes a collision.
In one embodiment, cautionary trajectory module 503 may determine not to plan the cautionary trajectory of the ADV based on at least one of a difference between the updated highest probability and the updated second highest probability or a consequence of the updated second predicted trajectory.
Currently, a prediction module of an ADV only outputs a trajectory of an obstacle with the highest probability to a planning module of the ADV. However, because of the uncertainty in the prediction, the obstacle 602 may end up to follow another trajectory not with the highest probability. The ADV may not have enough time to stop in time. A collision between the ADV and the obstacle may happen. Thus, a cautionary trajectory may need to be planned to increase the safely of driving and prevent the collision.
Referring to
The prediction module of the ADV 601 may also predict the corresponding probabilities of the multiple trajectories (611a, 611b, 611c, 611d). The corresponding probabilities of the multiple trajectories (611a, 611b, 611c, 611d) may be predicted based on the history of the obstacle, the driving environment, etc.
As an example, the corresponding probabilities of the multiple trajectories (611a, 611b, 611c, 611d) may be 45%, 40%, 10%, and 5% for trajectories 611a, 611b, 611c, 611d, respective, as illustrated in Table 1 below. When a difference between the highest probability of the first trajectory 611a and the second highest probability of the second trajectory 611b is very small, below a first predetermined threshold, there may be uncertainty in the prediction of the movement of the obstacle 602.
As another example, the corresponding probabilities of the multiple trajectories (611a, 611b, 611c, 611d) may be 50%, 35%, 10%, and 5% for trajectories 611a, 611b, 611c, 611d, respective, as illustrated in Table 2 below.
As illustrated in Table 2, the difference between the highest probability of the first trajectory 611a and the second highest probability of the second trajectory 611b may be not very small, above a first predetermined threshold, but still small enough, below a second predetermined threshold. However, the consequence of the second trajectory 611b may involve a high damage, such as a collision of the obstacle 602 with the ADV 601. In this situation, a cautionary trajectory of the ADV 601 may be need to prevent the collision.
Instead of only outputting the first trajectory 611a with the highest probability, the prediction module (e.g., 303) of the ADV may output the multiple trajectories (611a, 611b, 611c, 611d) with the corresponding probabilities to the planning module (e.g., 305) of the ADV 601. In some embodiments, the prediction module (e.g., 303) of the ADV may output several selected trajectories of the multiple trajectories (611a, 611b, 611c, 611d) with the corresponding probabilities to the planning module (e.g., 305) of the ADV 601. For example, the prediction module (e.g., 303) of the ADV may select the top two, three, four or five trajectories of the multiple trajectories with the top two, three, four, or five highest probabilities to the planning module (e.g., 305) of the ADV 601.
The planning module (e.g., 305) of the ADV 601 may plan a cautionary trajectory 630 of the ADV 601 based on the difference between the highest probability and the second highest probability or a consequence of the second trajectory. In the cautionary trajectory 630, the ADV 601 is configured to drive slowly, with a speed lower than a speed limit, and prepare to apply the brake to stop at any moment.
In one embodiment, the planning module (e.g., 305) of the ADV 601 may determine whether the difference between the highest probability of the first trajectory 611a and the second highest probability of the first trajectory 611b is below a first predetermined threshold. In response to the difference between the highest probability and the second highest probability is below the first predetermined threshold, the planning module (e.g., 305) of the ADV 601 may determine to plan the cautionary trajectory 630. As an example, the first predetermined threshold may be 10%. As illustrated in Table 1, the difference between the highest probability of the first trajectory 611a and the second highest probability of the second trajectory 611b may be 5%, less than 10%, the planning module (e.g., 305) of the ADV 601 may determine to plan the cautionary trajectory 630. Please note that the first predetermined threshold may be any predetermined value, not be limited by the example.
In one embodiment, the planning module (e.g., 305) of the ADV 601 may determine whether the difference between the highest probability of the first trajectory 611a and the second highest probability of the second trajectory 611b is above the first predetermined threshold and below a second predetermined threshold, and the consequence of the second predicted trajectory includes a high damage, such as a collision. In response to determining that the difference between the highest probability of the first trajectory 611a and the second highest probability of the second trajectory 611b is above the first predetermined threshold and below a second predetermined threshold, and the consequence of the second predicted trajectory includes the high damage, such as the collision, the planning module (e.g., 305) of the ADV 601 may determine to plan the cautionary trajectory 630. As an example, the first predetermined threshold may be 10%, and the second predetermined threshold may be 20%. Please note that the first predetermined threshold and the second predetermined threshold may be any predetermined value, not be limited by the example. As illustrated in Table 2, the difference between the highest probability of the first trajectory 611a and the second highest probability of the second trajectory 611b may be 15%, above 10% but less than 20%, however, the consequence of the second predicted trajectory 611b may include the collision, the planning module (e.g., 305) of the ADV 601 may determine to plan the cautionary trajectory 630.
In one embodiment, the planning module (e.g., 305) of the ADV 601 may determine whether the consequence of at least one of the top two, three, four or five trajectories of the multiple trajectories with the top two, three, four, or five highest probabilities includes a collision, and determine to plan the cautionary trajectory 630 in response to determining that the consequence of at least one of the top two, three, four or five trajectories of the multiple trajectories with the top two, three, four, or five highest probabilities includes a collision. For example, if the consequence of the second predicted trajectory with the second highest probability, or the consequence of the third predicted trajectory with the third highest probability, or the fourth predicted trajectory with the fourth highest probability, or the fifth predicted trajectory with the fifth highest probability may include a collision, the planning module (e.g., 305) of the ADV 601 may determine to plan the cautionary trajectory 630.
The prediction module (e.g., 303) may update the multiple trajectories (611a, 611b, 611c, 611d) with the corresponding probabilities, e.g., constantly, and output the updated the updated multiple trajectories with the corresponding probabilities. As time goes by, the driving environment may become more clear, and the uncertainty may become less. For example, the probability of the first trajectory 611a may become 70%, the probability of the second trajectory 611b may become 40%, the probability of the third trajectory 611c and the probability of the fourth trajectory 611d may become 0%. Thus, the planning module (e.g., 305) of the ADV 601 may determine not to plan the cautionary trajectory 630, but resume to plan a typical trajectory.
In this way, the uncertainty from prediction may be handled with caution and the safety of the driving of the ADV may be improved.
When the driving environment of the ADV is not clear, the prediction of a movement of an obstacle may be uncertain. Prediction module 303 of the ADV may predict multiple trajectories with corresponding probabilities 706, including the first trajectory with the highest probability 708 and the second trajectory with the second highest probability 710. Planning module 305 of the ADV may determine whether to plan a cautionary trajectory of the ADV based on at least one of a difference between the highest probability and the second highest probability 712 or a consequence of the second trajectory 714.
In one embodiment, planning module 305 of the ADV may determine to plan the cautionary trajectory 630 when the difference between the highest probability and the second highest probability is below the first predetermined threshold. In one embodiment, planning module 305 of the ADV may determine to plan the cautionary trajectory 630 when the difference between the highest probability and the second highest probability 712 is above a first predetermined threshold but below a second predetermined threshold and the consequence of the second trajectory 714 includes a collision.
Control module 306 may drive the ADV according to the cautionary trajectory 630. In this way, the ADV may handle the uncertainty from prediction and drive safely to prevent the collision.
Referring to
In operation 802, the processing logic predicts multiple trajectories of the obstacle with corresponding probabilities including a first predicted trajectory of the obstacle with a highest probability and a second predicted trajectory of the obstacle with a second highest probability.
In operation 803, the processing logic plans a cautionary trajectory of the ADV based on at least one of a difference between the highest probability and the second highest probability or a consequence of the second trajectory. The ADV is to drive with a speed lower than a speed limit and prepare to stop in the cautionary trajectory.
In operation 804, the processing logic controls the ADV to drive according to the cautionary trajectory. In this way, the uncertainty from prediction may be handled with caution and the safety of the driving of the ADV may be improved.
Note that some or all of the components as shown and described above may be implemented in software, hardware, or a combination thereof. For example, such components can be implemented as software installed and stored in a persistent storage device, which can be loaded and executed in a memory by a processor (not shown) to carry out the processes or operations described throughout this application. Alternatively, such components can be implemented as executable code programmed or embedded into dedicated hardware such as an integrated circuit (e.g., an application specific IC or ASIC), a digital signal processor (DSP), or a field programmable gate array (FPGA), which can be accessed via a corresponding driver and/or operating system from an application. Furthermore, such components can be implemented as specific hardware logic in a processor or processor core as part of an instruction set accessible by a software component via one or more specific instructions.
Some portions of the preceding detailed descriptions have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as those set forth in the claims below, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
Embodiments of the disclosure also relate to an apparatus for performing the operations herein. Such a computer program is stored in a non-transitory computer readable medium. A machine-readable medium includes any mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a machine-readable (e.g., computer-readable) medium includes a machine (e.g., a computer) readable storage medium (e.g., read only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices).
The processes or methods depicted in the preceding figures may be performed by processing logic that comprises hardware (e.g. circuitry, dedicated logic, etc.), software (e.g., embodied on a non-transitory computer readable medium), or a combination of both. Although the processes or methods are described above in terms of some sequential operations, it should be appreciated that some of the operations described may be performed in a different order. Moreover, some operations may be performed in parallel rather than sequentially.
Embodiments of the present disclosure are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of embodiments of the disclosure as described herein.
In the foregoing specification, embodiments of the disclosure have been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope of the disclosure as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
