Patent Grant
11836968
This invention relates generally to the machine learning field, and more specifically, to new and useful systems and methods for configuring and using a multi-stage object classification and condition pipeline.
Traditionally, infrastructure maintenance and reliability assessments are performed by human operators. These human operators are tasked with the responsibility of visually inspecting and assessing infrastructure components. This process can be time-consuming, labor-intensive, and requires a high level of specialized knowledge and training in the specific field of the infrastructure components being assessed. Furthermore, this process fails to scale effectively in instances where hundreds or thousands of infrastructure components require assessment.
Therefore, there is a need in the art for using machine learning to accelerate the process of infrastructure maintenance and reliability assessments. The embodiments of the present application provide technical solutions that address, at least, the needs described above, as well as the deficiencies of the start of the art.
In one embodiment, a computer-program product embodied in a non-transitory machine-readable storage medium storing computer instructions that, when executed by one or more processors, perform operations including detecting, via a localization machine learning model, a target object within a scene based on downsampled image data of the scene; identifying, via the one or more processors, a likely position of the target object within original image data of the scene based on object position data computed by the localization machine learning model; extracting, from the original image data of the scene, a target sub-image containing the target object based on the likely position of the target object; classifying, via an object classification machine learning model, the target object to a probable object class of a plurality of distinct object classes based on a target image resolution of the target sub-image, wherein the plurality of distinct object classes includes an out-of-scope object class and one or more in-scope object classes; routing, via the one or more processors, the target image resolution of the target sub-image to a target object-condition machine learning classification model of a plurality of distinct object-condition machine learning classification models based on a mapping between the plurality of distinct object classes and the plurality of distinct object-condition machine learning classification models; classifying, via the target object-condition machine learning classification model, the target object to a probable object-condition class of a plurality of distinct object-condition classes; and displaying, via a graphical user interface, a representation of the target object in association with the probable object-condition class based on the classifying of the target object via the target object-condition machine learning classification model.
In one embodiment, the computer-program product further includes generating the localization machine learning model, wherein generating the localization machine learning model includes implementing an object detection machine learning model; adapting a multi-criteria loss function of the object detection machine learning model to a target multi-criteria loss function based on eliminating one or more loss function components of the multi-criteria loss function; and transforming the object detection machine learning model to the localization machine learning model based on implementing the target multi-criteria loss function during a training of the object detection machine learning model.
In one embodiment, the multi-criteria loss function of the object detection machine learning model includes an object classification error component; and the target multi-criteria loss function excludes the object classification error component.
In one embodiment, the object position data computed by the localization machine learning model defines an approximate spatial area of the target object in the downsampled image data of the scene; identifying the likely position of the target object within the original image data of the scene includes correlating, via the one or more processors, the approximate spatial area of the target object to a distinct spatial area in the original image data of the scene; and the target sub-image extracted from the original image data of the scene includes the distinct spatial area.
In one embodiment, the scene further includes a second object distinct from the target object; the computer-program product further includes computer instructions for performing operations including identifying, via the one or more processors, a likely position of the second object within the original image data of the scene based on the object position data computed by the localization machine learning model; and extracting, from the original image data of the scene, a second sub-image containing the second object based on the likely position of the second object.
In one embodiment, the computer-program product further includes classifying, via the object classification machine learning model, the second object to a probable object class of the plurality of distinct object classes based on a target image resolution of the second sub-image, wherein: the object classification machine learning model classifies the second object to the out-of-scope object class and the target object to one of the one or more in-scope object classes; the out-of-scope object class indicates that the second sub-image is immaterial to a target classification objective of the plurality of distinct object-condition machine learning classification models; and the one of the one or more in-scope object classes indicates that the target sub-image is germane to the target classification objective of the plurality of distinct object-condition machine learning classification models.
In one embodiment, the computer-program product further includes bypassing an object-condition classification of the second sub-image when the object classification machine learning model classifies the second object to the out-of-scope object class.
In one embodiment, the computer-program further includes classifying, via the object classification machine learning model, the second object to a probable object class of the plurality of distinct object classes based on a target image resolution of the second sub-image, wherein: the one or more in-scope object classes include a first in-scope object class and a second in-scope object class; the object classification machine learning model classifies the target object to the first in-scope object class; the object classification machine learning model classifies the second object to the second in-scope object class; and wherein the routing further includes: routing the target image resolution of the target sub-image to a distinct object-condition machine learning classification model of the plurality of distinct object-condition machine learning classification models that corresponds to the first in-scope object class; and routing the target image resolution of the second sub-image to a distinct object-condition machine learning classification model of the plurality of distinct object-condition machine learning classification models that corresponds to the second in-scope object class.
In one embodiment, the mapping between the plurality of distinct object classes and the plurality of distinct object-condition machine learning classification models defines a plurality of distinct routing nexuses; each distinct routing nexus of the plurality of distinct routing nexuses associates a distinct one of the plurality of distinct object classes to a distinct one of the plurality of distinct object-condition machine learning classification models; and the routing of the target image resolution of the target sub-image is further based on identifying a target routing nexus that corresponds to the probable object class of the target object.
In one embodiment, the probable object class indicates a probable object type of the target object; and the probable object-condition class indicates a probable operating state of the target object.
In one embodiment, the computer-program further includes implementing a multi-stage object classification and condition pipeline, wherein: a first stage of the multi-stage object classification and condition pipeline includes the detecting, by the localization machine learning model, of the target object within the scene; a second stage of the multi-stage object classification and condition pipeline includes the classifying, by the object classification machine learning model, of the target object to the probable object class; and a third stage of the multi-stage object classification and condition pipeline includes the classifying, by the target object-condition machine learning classification model, of the target object to the probable object-condition class.
In one embodiment, the original image data of the scene has a first image resolution; and the downsampled image data of the scene has a second image resolution lower than the first image resolution.
In one embodiment, the downsampled image data of the scene satisfies a target image resolution parameter of the localization machine learning model.
In one embodiment, a computer-implemented method includes detecting, via a localization machine learning model, a target object within a scene based on downsampled image data of the scene; identifying, via the one or more processors, a likely position of the target object within original image data of the scene based on object position data computed by the localization machine learning model; extracting, from the original image data of the scene, a target sub-image containing the target object based on the likely position of the target object; classifying, via an object classification machine learning model, the target object to a probable object class of a plurality of distinct object classes based on a target image resolution of the target sub-image, wherein the plurality of distinct object classes includes an out-of-scope object class and one or more in-scope object classes; routing, via the one or more processors, the target image resolution of the target sub-image to a target object-condition machine learning classification model of a plurality of distinct object-condition machine learning classification models based on a mapping between the plurality of distinct object classes and the plurality of distinct object-condition machine learning classification models; classifying, via the target object-condition machine learning classification model, the target object to a probable object-condition class of a plurality of distinct object-condition classes; and displaying, via a graphical user interface, a representation of the target object in association with the probable object-condition class based on the classifying of the target object via the target object-condition machine learning classification model.
In one embodiment, the computer-implemented further includes generating the localization machine learning model, wherein generating the localization machine learning model includes: implementing an object detection machine learning model; adapting a multi-criteria loss function of the object detection machine learning model to a target multi-criteria loss function based on eliminating one or more loss function components of the multi-criteria loss function; and transforming the object detection machine learning model to the localization machine learning model based on implementing the target multi-criteria loss function during a training of the object detection machine learning model.
In one embodiment, the multi-criteria loss function of the object detection machine learning model includes an object classification error component; and the target multi-criteria loss function excludes the object classification error component.
In one embodiment, the object position data computed by the localization machine learning model defines an approximate spatial area of the target object in the downsampled image data of the scene; identifying the likely position of the target object within the original image data of the scene includes: correlating, via the one or more processors, the approximate spatial area of the target object to a distinct spatial area in the original image data of the scene; and the target sub-image extracted from the original image data of the scene includes the distinct spatial area.
In one embodiment, the scene further includes a second object distinct from the target object; the computer-program product further includes computer instructions for performing operations including: identifying, via the one or more processors, a likely position of the second object within the original image data of the scene based on the object position data computed by the localization machine learning model; and extracting, from the original image data of the scene, a second sub-image containing the second object based on the likely position of the second object.
In one embodiment, the computer-implemented further includes classifying, via the object classification machine learning model, the second object to a probable object class of the plurality of distinct object classes based on a target image resolution of the second sub-image, wherein: the object classification machine learning model classifies the second object to the out-of-scope object class and the target object to one of the one or more in-scope object classes; the out-of-scope object class indicates that the second sub-image is immaterial to a target classification objective of the plurality of distinct object-condition machine learning classification models; and the one of the one or more in-scope object classes indicates that the target sub-image is germane to the target classification objective of the plurality of distinct object-condition machine learning classification models.
In one embodiment, the computer-implemented further includes bypassing an object-condition classification of the second sub-image when the object classification machine learning model classifies the second object to the out-of-scope object class.
In one embodiment, the computer-implemented further includes classifying, via the object classification machine learning model, the second object to a probable object class of the plurality of distinct object classes based on a target image resolution of the second sub-image, wherein: the one or more in-scope object classes include a first in-scope object class and a second in-scope object class; the object classification machine learning model classifies the target object to the first in-scope object class; the object classification machine learning model classifies the second object to the second in-scope object class; and wherein the routing further includes: routing the target image resolution of the target sub-image to a distinct object-condition machine learning classification model of the plurality of distinct object-condition machine learning classification models that corresponds to the first in-scope object class; and routing the target image resolution of the second sub-image to a distinct object-condition machine learning classification model of the plurality of distinct object-condition machine learning classification models that corresponds to the second in-scope object class.
In one embodiment, the mapping between the plurality of distinct object classes and the plurality of distinct object-condition machine learning classification models defines a plurality of distinct routing nexuses; each distinct routing nexus of the plurality of distinct routing nexuses associates a distinct one of the plurality of distinct object classes to a distinct one of the plurality of distinct object-condition machine learning classification models; and the routing of the target image resolution of the target sub-image is further based on identifying a target routing nexus that corresponds to the probable object class of the target object.
In one embodiment, the probable object class indicates a probable object type of the target object; and the probable object-condition class indicates a probable operating state of the target object.
In one embodiment, the computer-implemented method further includes implementing a multi-stage object classification and condition pipeline, wherein: a first stage of the multi-stage object classification and condition pipeline includes the detecting, by the localization machine learning model, of the target object within the scene; a second stage of the multi-stage object classification and condition pipeline includes the classifying, by the object classification machine learning model, of the target object to the probable object class; and a third stage of the multi-stage object classification and condition pipeline includes the classifying, by the target object-condition machine learning classification model, of the target object to the probable object-condition class.
In one embodiment, the original image data of the scene has a first image resolution; and the downsampled image data of the scene has a second image resolution lower than the first image resolution.
In one embodiment, the downsampled image data of the scene satisfies a target image resolution parameter of the localization machine learning model.
In one embodiment, a computer-implemented system includes one or more processors; a memory; a computer-readable medium operably coupled to the one or more processors, the computer-readable medium having computer-readable instructions stored thereon that, when executed by the one or more processors, cause a computing device to perform operations comprising: detecting, via a localization machine learning model, a target object within a scene based on downsampled image data of the scene; identifying, via the one or more processors, a likely position of the target object within original image data of the scene based on object position data computed by the localization machine learning model; extracting, from the original image data of the scene, a target sub-image containing the target object based on the likely position of the target object; classifying, via an object classification machine learning model, the target object to a probable object class of a plurality of distinct object classes based on a target image resolution of the target sub-image, wherein the plurality of distinct object classes includes an out-of-scope object class and one or more in-scope object classes; routing, via the one or more processors, the target image resolution of the target sub-image to a target object-condition machine learning classification model of a plurality of distinct object-condition machine learning classification models based on a mapping between the plurality of distinct object classes and the plurality of distinct object-condition machine learning classification models; classifying, via the target object-condition machine learning classification model, the target object to a probable object-condition class of a plurality of distinct object-condition classes; and displaying, via a graphical user interface, a representation of the target object in association with the probable object-condition class based on the classifying of the target object via the target object-condition machine learning classification model.
In one embodiment, the computer-implemented system further includes generating the localization machine learning model, wherein generating the localization machine learning model includes: implementing an object detection machine learning model; adapting a multi-criteria loss function of the object detection machine learning model to a target multi-criteria loss function based on eliminating one or more loss function components of the multi-criteria loss function; and transforming the object detection machine learning model to the localization machine learning model based on implementing the target multi-criteria loss function during a training of the object detection machine learning model.
In one embodiment, the multi-criteria loss function of the object detection machine learning model includes an object classification error component; and the target multi-criteria loss function excludes the object classification error component.
In one embodiment, the object position data computed by the localization machine learning model defines an approximate spatial area of the target object in the downsampled image data of the scene; identifying the likely position of the target object within the original image data of the scene includes: correlating, via the one or more processors, the approximate spatial area of the target object to a distinct spatial area in the original image data of the scene; and the target sub-image extracted from the original image data of the scene includes the distinct spatial area.
The following description of the preferred embodiments of the inventions are not intended to limit the inventions to these preferred embodiments, but rather to enable any person skilled in the art to make and use these inventions.
In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of embodiments of the technology. However, it will be apparent that various embodiments may be practiced without these specific details. The figures and description are not intended to be restrictive.
The ensuing description provides example embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the example embodiments will provide those skilled in the art with an enabling description for implementing an example embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the technology as set forth in the appended claims.
Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but could have additional operations not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
Systems depicted in some of the figures may be provided in various configurations. In some embodiments, the systems may be configured as a distributed system where one or more components of the system are distributed across one or more networks in a cloud computing system.
Data transmission network 100 may also include computing environment 114. Computing environment 114 may be a specialized computer or other machine that processes the data received within the data transmission network 100. Data transmission network 100 also includes one or more network devices 102. Network devices 102 may include client devices that attempt to communicate with computing environment 114. For example, network devices 102 may send data to the computing environment 114 to be processed, may send signals to the computing environment 114 to control different aspects of the computing environment or the data it is processing, among other reasons. Network devices 102 may interact with the computing environment 114 through a number of ways, such as, for example, over one or more networks 108. As shown in
In other embodiments, network devices may provide a large amount of data, either all at once or streaming over a period of time (e.g., using event stream processing (ESP), described further with respect to
Data transmission network 100 may also include one or more network-attached data stores 110. Network-attached data stores 110 are used to store data to be processed by the computing environment 114 as well as any intermediate or final data generated by the computing system in non-volatile memory. However, in certain embodiments, the configuration of the computing environment 114 allows its operations to be performed such that intermediate and final data results can be stored solely in volatile memory (e.g., RAM), without a requirement that intermediate or final data results be stored to non-volatile types of memory (e.g., disk). This can be useful in certain situations, such as when the computing environment 114 receives ad hoc queries from a user and when responses, which are generated by processing large amounts of data, need to be generated on-the-fly. In this non-limiting situation, the computing environment 114 may be configured to retain the processed information within memory so that responses can be generated for the user at different levels of detail as well as allow a user to interactively query against this information.
Network-attached data stores may store a variety of different types of data organized in a variety of different ways and from a variety of different sources. For example, network-attached data storage may include storage other than primary storage located within computing environment 114 that is directly accessible by processors located therein. Network-attached data storage may include secondary, tertiary or auxiliary storage, such as large hard drives, servers, virtual memory, among other types. Storage devices may include portable or non-portable storage devices, optical storage devices, and various other mediums capable of storing, containing data. A machine-readable storage medium or computer-readable storage medium may include a non-transitory medium in which data can be stored and that does not include carrier waves and/or transitory electronic signals. Examples of a non-transitory medium may include, for example, a magnetic disk or tape, optical storage media such as compact disk or digital versatile disk, flash memory, memory or memory devices. A computer-program product may include code and/or machine-executable instructions that may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, among others. Furthermore, the data stores may hold a variety of different types of data. For example, network-attached data stores no may hold unstructured (e.g., raw) data, such as manufacturing data (e.g., a database containing records identifying products being manufactured with parameter data for each product, such as colors and models) or product sales databases (e.g., a database containing individual data records identifying details of individual product sales).
The unstructured data may be presented to the computing environment 114 in different forms such as a flat file or a conglomerate of data records, and may have data values and accompanying time stamps. The computing environment 114 may be used to analyze the unstructured data in a variety of ways to determine the best way to structure (e.g., hierarchically) that data, such that the structured data is tailored to a type of further analysis that a user wishes to perform on the data. For example, after being processed, the unstructured time stamped data may be aggregated by time (e.g., into daily time period units) to generate time series data and/or structured hierarchically according to one or more dimensions (e.g., parameters, attributes, and/or variables). For example, data may be stored in a hierarchical data structure, such as a ROLAP OR MOLAP database, or may be stored in another tabular form, such as in a flat-hierarchy form.
Data transmission network 100 may also include one or more server farms 106. Computing environment 114 may route select communications or data to the one or more sever farms 106 or one or more servers within the server farms. Server farms 106 can be configured to provide information in a predetermined manner. For example, server farms 106 may access data to transmit in response to a communication. Server farms 106 may be separately housed from each other device within data transmission network 100, such as computing environment 114, and/or may be part of a device or system.
Server farms 106 may host a variety of different types of data processing as part of data transmission network 100. Server farms 106 may receive a variety of different data from network devices, from computing environment 114, from cloud network 116, or from other sources. The data may have been obtained or collected from one or more sensors, as inputs from a control database, or may have been received as inputs from an external system or device. Server farms 106 may assist in processing the data by turning raw data into processed data based on one or more rules implemented by the server farms. For example, sensor data may be analyzed to determine changes in an environment over time or in real-time.
Data transmission network 100 may also include one or more cloud networks 116. Cloud network 116 may include a cloud infrastructure system that provides cloud services. In certain embodiments, services provided by the cloud network 116 may include a host of services that are made available to users of the cloud infrastructure system on demand. Cloud network 116 is shown in
While each device, server and system in
Each communication within data transmission network 100 (e.g., between client devices, between servers 106 and computing environment 114 or between a server and a device) may occur over one or more networks 108. Networks 108 may include one or more of a variety of different types of networks, including a wireless network, a wired network, or a combination of a wired and wireless network. Examples of suitable networks include the Internet, a personal area network, a local area network (LAN), a wide area network (WAN), or a wireless local area network (WLAN). A wireless network may include a wireless interface or combination of wireless interfaces. As an example, a network in the one or more networks 108 may include a short-range communication channel, such as a BLUETOOTH® communication channel or a BLUETOOTH® Low Energy communication channel. A wired network may include a wired interface. The wired and/or wireless networks may be implemented using routers, access points, bridges, gateways, or the like, to connect devices in the network 114, as will be further described with respect to
Some aspects may utilize the Internet of Things (IoT), where things (e.g., machines, devices, phones, sensors) can be connected to networks and the data from these things can be collected and processed within the things and/or external to the things. For example, the IoT can include sensors in many different devices, and high value analytics can be applied to identify hidden relationships and drive increased efficiencies. This can apply to both big data analytics and real-time (e.g., ESP) analytics. This will be described further below with respect to
As noted, computing environment 114 may include a communications grid 120 and a transmission network database system 118. Communications grid 120 may be a grid-based computing system for processing large amounts of data. The transmission network database system 118 may be for managing, storing, and retrieving large amounts of data that are distributed to and stored in the one or more network-attached data stores 110 or other data stores that reside at different locations within the transmission network database system 118. The compute nodes in the grid-based computing system 120 and the transmission network database system 118 may share the same processor hardware, such as processors that are located within computing environment 114.
As shown in
Although network devices 204-209 are shown in
As noted, one type of system that may include various sensors that collect data to be processed and/or transmitted to a computing environment according to certain embodiments includes an oil drilling system. For example, the one or more drilling operation sensors may include surface sensors that measure a hook load, a fluid rate, a temperature and a density in and out of the wellbore, a standpipe pressure, a surface torque, a rotation speed of a drill pipe, a rate of penetration, a mechanical specific energy, etc. and downhole sensors that measure a rotation speed of a bit, fluid densities, downhole torque, downhole vibration (axial, tangential, lateral), a weight applied at a drill bit, an annular pressure, a differential pressure, an azimuth, an inclination, a dog leg severity, a measured depth, a vertical depth, a downhole temperature, etc. Besides the raw data collected directly by the sensors, other data may include parameters either developed by the sensors or assigned to the system by a client or other controlling device. For example, one or more drilling operation control parameters may control settings such as a mud motor speed to flow ratio, a bit diameter, a predicted formation top, seismic data, weather data, etc. Other data may be generated using physical models such as an earth model, a weather model, a seismic model, a bottom hole assembly model, a well plan model, an annular friction model, etc. In addition to sensor and control settings, predicted outputs, of for example, the rate of penetration, mechanical specific energy, hook load, flow in fluid rate, flow out fluid rate, pump pressure, surface torque, rotation speed of the drill pipe, annular pressure, annular friction pressure, annular temperature, equivalent circulating density, etc. may also be stored in the data warehouse.
In another example, another type of system that may include various sensors that collect data to be processed and/or transmitted to a computing environment according to certain embodiments includes a home automation or similar automated network in a different environment, such as an office space, school, public space, sports venue, or a variety of other locations. Network devices in such an automated network may include network devices that allow a user to access, control, and/or configure various home appliances located within the user's home (e.g., a television, radio, light, fan, humidifier, sensor, microwave, iron, and/or the like), or outside of the user's home (e.g., exterior motion sensors, exterior lighting, garage door openers, sprinkler systems, or the like). For example, network device 102 may include a home automation switch that may be coupled with a home appliance. In another embodiment, a network device can allow a user to access, control, and/or configure devices, such as office-related devices (e.g., copy machine, printer, or fax machine), audio and/or video related devices (e.g., a receiver, a speaker, a projector, a DVD player, or a television), media-playback devices (e.g., a compact disc player, a CD player, or the like), computing devices (e.g., a home computer, a laptop computer, a tablet, a personal digital assistant (PDA), a computing device, or a wearable device), lighting devices (e.g., a lamp or recessed lighting), devices associated with a security system, devices associated with an alarm system, devices that can be operated in an automobile (e.g., radio devices, navigation devices), and/or the like. Data may be collected from such various sensors in raw form, or data may be processed by the sensors to create parameters or other data either developed by the sensors based on the raw data or assigned to the system by a client or other controlling device.
In another example, another type of system that may include various sensors that collect data to be processed and/or transmitted to a computing environment according to certain embodiments includes a power or energy grid. A variety of different network devices may be included in an energy grid, such as various devices within one or more power plants, energy farms (e.g., wind farm, solar farm, among others) energy storage facilities, factories, homes and businesses of consumers, among others. One or more of such devices may include one or more sensors that detect energy gain or loss, electrical input or output or loss, and a variety of other efficiencies. These sensors may collect data to inform users of how the energy grid, and individual devices within the grid, may be functioning and how they may be made more efficient.
Network device sensors may also perform processing on data it collects before transmitting the data to the computing environment 114, or before deciding whether to transmit data to the computing environment 114. For example, network devices may determine whether data collected meets certain rules, for example by comparing data or values calculated from the data and comparing that data to one or more thresholds. The network device may use this data and/or comparisons to determine if the data should be transmitted to the computing environment 214 for further use or processing.
Computing environment 214 may include machines 220 and 240. Although computing environment 214 is shown in
Computing environment 214 can communicate with various devices via one or more routers 225 or other inter-network or intra-network connection components. For example, computing environment 214 may communicate with devices 230 via one or more routers 225. Computing environment 214 may collect, analyze and/or store data from or pertaining to communications, client device operations, client rules, and/or user-associated actions stored at one or more data stores 235. Such data may influence communication routing to the devices within computing environment 214, how data is stored or processed within computing environment 214, among other actions.
Notably, various other devices can further be used to influence communication routing and/or processing between devices within computing environment 214 and with devices outside of computing environment 214. For example, as shown in
In addition to computing environment 214 collecting data (e.g., as received from network devices, such as sensors, and client devices or other sources) to be processed as part of a big data analytics project, it may also receive data in real time as part of a streaming analytics environment. As noted, data may be collected using a variety of sources as communicated via different kinds of networks or locally. Such data may be received on a real-time streaming basis. For example, network devices may receive data periodically from network device sensors as the sensors continuously sense, monitor and track changes in their environments. Devices within computing environment 214 may also perform pre-analysis on data it receives to determine if the data received should be processed as part of an ongoing project. The data received and collected by computing environment 214, no matter what the source or method or timing of receipt, may be processed over a period of time for a client to determine results data based on the client's needs and rules.
The model can include layers 301-307. The layers are arranged in a stack. Each layer in the stack serves the layer one level higher than it (except for the application layer, which is the highest layer), and is served by the layer one level below it (except for the physical layer, which is the lowest layer). The physical layer is the lowest layer because it receives and transmits raw bites of data, and is the farthest layer from the user in a communications system. On the other hand, the application layer is the highest layer because it interacts directly with a software application.
As noted, the model includes a physical layer 301. Physical layer 301 represents physical communication, and can define parameters of that physical communication. For example, such physical communication may come in the form of electrical, optical, or electromagnetic signals. Physical layer 301 also defines protocols that may control communications within a data transmission network.
Link layer 302 defines links and mechanisms used to transmit (i.e., move) data across a network. The link layer 302 manages node-to-node communications, such as within a grid computing environment. Link layer 302 can detect and correct errors (e.g., transmission errors in the physical layer 301). Link layer 302 can also include a media access control (MAC) layer and logical link control (LLC) layer.
Network layer 303 defines the protocol for routing within a network. In other words, the network layer coordinates transferring data across nodes in a same network (e.g., such as a grid computing environment). Network layer 303 can also define the processes used to structure local addressing within the network.
Transport layer 304 can manage the transmission of data and the quality of the transmission and/or receipt of that data. Transport layer 304 can provide a protocol for transferring data, such as, for example, a Transmission Control Protocol (TCP). Transport layer 304 can assemble and disassemble data frames for transmission. The transport layer can also detect transmission errors occurring in the layers below it.
Session layer 305 can establish, maintain, and manage communication connections between devices on a network. In other words, the session layer controls the dialogues or nature of communications between network devices on the network. The session layer may also establish checkpointing, adjournment, termination, and restart procedures.
Presentation layer 306 can provide translation for communications between the application and network layers. In other words, this layer may encrypt, decrypt and/or format data based on data types and/or encodings known to be accepted by an application or network layer.
Application layer 307 interacts directly with software applications and end users, and manages communications between them. Application layer 307 can identify destinations, local resource states or availability and/or communication content or formatting using the applications.
Intra-network connection components 321 and 322 are shown to operate in lower levels, such as physical layer 301 and link layer 302, respectively. For example, a hub can operate in the physical layer, a switch can operate in the link layer, and a router can operate in the network layer. Inter-network connection components 323 and 328 are shown to operate on higher levels, such as layers 303-307. For example, routers can operate in the network layer and network devices can operate in the transport, session, presentation, and application layers.
As noted, a computing environment 314 can interact with and/or operate on, in various embodiments, one, more, all or any of the various layers. For example, computing environment 314 can interact with a hub (e.g., via the link layer) so as to adjust which devices the hub communicates with. The physical layer may be served by the link layer, so it may implement such data from the link layer. For example, the computing environment 314 may control which devices it will receive data from. For example, if the computing environment 314 knows that a certain network device has turned off, broken, or otherwise become unavailable or unreliable, the computing environment 314 may instruct the hub to prevent any data from being transmitted to the computing environment 314 from that network device. Such a process may be beneficial to avoid receiving data that is inaccurate or that has been influenced by an uncontrolled environment. As another example, computing environment 314 can communicate with a bridge, switch, router or gateway and influence which device within the system (e.g., system 200) the component selects as a destination. In some embodiments, computing environment 314 can interact with various layers by exchanging communications with equipment operating on a particular layer by routing or modifying existing communications. In another embodiment, such as in a grid computing environment, a node may determine how data within the environment should be routed (e.g., which node should receive certain data) based on certain parameters or information provided by other layers within the model.
As noted, the computing environment 314 may be a part of a communications grid environment, the communications of which may be implemented as shown in the protocol of
Communications grid computing system (or just “communications grid”) 400 also includes one or more worker nodes. Shown in
A control node may connect with an external device with which the control node may communicate (e.g., a grid user, such as a server or computer, may connect to a controller of the grid). For example, a server or computer may connect to control nodes and may transmit a project or job to the node. The project may include a data set. The data set may be of any size. Once the control node receives such a project including a large data set, the control node may distribute the data set or projects related to the data set to be performed by worker nodes. Alternatively, for a project including a large data set, the data set may be received or stored by a machine other than a control node (e.g., a HADOOP® standard-compliant data node employing the HADOOP® Distributed File System, or HDFS).
Control nodes may maintain knowledge of the status of the nodes in the grid (i.e., grid status information), accept work requests from clients, subdivide the work across worker nodes, and coordinate the worker nodes, among other responsibilities. Worker nodes may accept work requests from a control node and provide the control node with results of the work performed by the worker node. A grid may be started from a single node (e.g., a machine, computer, server, etc.). This first node may be assigned or may start as the primary control node that will control any additional nodes that enter the grid.
When a project is submitted for execution (e.g., by a client or a controller of the grid) it may be assigned to a set of nodes. After the nodes are assigned to a project, a data structure (i.e., a communicator) may be created. The communicator may be used by the project for information to be shared between the project codes running on each node. A communication handle may be created on each node. A handle, for example, is a reference to the communicator that is valid within a single process on a single node, and the handle may be used when requesting communications between nodes.
A control node, such as control node 402, may be designated as the primary control node. A server, computer or other external device may connect to the primary control node. Once the control node receives a project, the primary control node may distribute portions of the project to its worker nodes for execution. For example, when a project is initiated on communications grid 400, primary control node 402 controls the work to be performed for the project in order to complete the project as requested or instructed. The primary control node may distribute work to the worker nodes based on various factors, such as which subsets or portions of projects may be completed most efficiently and in the correct amount of time. For example, a worker node may perform analysis on a portion of data that is already local (e.g., stored on) the worker node. The primary control node also coordinates and processes the results of the work performed by each worker node after each worker node executes and completes its job. For example, the primary control node may receive a result from one or more worker nodes, and the control node may organize (e.g., collect and assemble) the results received and compile them to produce a complete result for the project received from the end user.
Any remaining control nodes, such as control nodes 404 and 406, may be assigned as backup control nodes for the project. In an embodiment, backup control nodes may not control any portion of the project. Instead, backup control nodes may serve as a backup for the primary control node and take over as primary control node if the primary control node were to fail. If a communications grid were to include only a single control node, and the control node were to fail (e.g., the control node is shut off or breaks) then the communications grid as a whole may fail and any project or job being run on the communications grid may fail and may not complete. While the project may be run again, such a failure may cause a delay (severe delay in some cases, such as overnight delay) in completion of the project. Therefore, a grid with multiple control nodes, including a backup control node, may be beneficial.
To add another node or machine to the grid, the primary control node may open a pair of listening sockets, for example. A socket may be used to accept work requests from clients, and the second socket may be used to accept connections from other grid nodes. The primary control node may be provided with a list of other nodes (e.g., other machines, computers, servers) that will participate in the grid, and the role that each node will fill in the grid. Upon startup of the primary control node (e.g., the first node on the grid), the primary control node may use a network protocol to start the server process on every other node in the grid. Command line parameters, for example, may inform each node of one or more pieces of information, such as: the role that the node will have in the grid, the host name of the primary control node, the port number on which the primary control node is accepting connections from peer nodes, among others. The information may also be provided in a configuration file, transmitted over a secure shell tunnel, recovered from a configuration server, among others. While the other machines in the grid may not initially know about the configuration of the grid, that information may also be sent to each other node by the primary control node. Updates of the grid information may also be subsequently sent to those nodes.
For any control node other than the primary control node added to the grid, the control node may open three sockets. The first socket may accept work requests from clients, the second socket may accept connections from other grid members, and the third socket may connect (e.g., permanently) to the primary control node. When a control node (e.g., primary control node) receives a connection from another control node, it first checks to see if the peer node is in the list of configured nodes in the grid. If it is not on the list, the control node may clear the connection. If it is on the list, it may then attempt to authenticate the connection. If authentication is successful, the authenticating node may transmit information to its peer, such as the port number on which a node is listening for connections, the host name of the node, information about how to authenticate the node, among other information. When a node, such as the new control node, receives information about another active node, it will check to see if it already has a connection to that other node. If it does not have a connection to that node, it may then establish a connection to that control node.
Any worker node added to the grid may establish a connection to the primary control node and any other control nodes on the grid. After establishing the connection, it may authenticate itself to the grid (e.g., any control nodes, including both primary and backup, or a server or user controlling the grid). After successful authentication, the worker node may accept configuration information from the control node.
When a node joins a communications grid (e.g., when the node is powered on or connected to an existing node on the grid or both), the node is assigned (e.g., by an operating system of the grid) a universally unique identifier (UUID). This unique identifier may help other nodes and external entities (devices, users, etc.) to identify the node and distinguish it from other nodes. When a node is connected to the grid, the node may share its unique identifier with the other nodes in the grid. Since each node may share its unique identifier, each node may know the unique identifier of every other node on the grid. Unique identifiers may also designate a hierarchy of each of the nodes (e.g., backup control nodes) within the grid. For example, the unique identifiers of each of the backup control nodes may be stored in a list of backup control nodes to indicate an order in which the backup control nodes will take over for a failed primary control node to become a new primary control node. However, a hierarchy of nodes may also be determined using methods other than using the unique identifiers of the nodes. For example, the hierarchy may be predetermined, or may be assigned based on other predetermined factors.
The grid may add new machines at any time (e.g., initiated from any control node). Upon adding a new node to the grid, the control node may first add the new node to its table of grid nodes. The control node may also then notify every other control node about the new node. The nodes receiving the notification may acknowledge that they have updated their configuration information.
Primary control node 402 may, for example, transmit one or more communications to backup control nodes 404 and 406 (and, for example, to other control or worker nodes within the communications grid). Such communications may be sent periodically, at fixed time intervals, between known fixed stages of the project's execution, among other protocols. The communications transmitted by primary control node 402 may be of varied types and may include a variety of types of information. For example, primary control node 402 may transmit snapshots (e.g., status information) of the communications grid so that backup control node 404 always has a recent snapshot of the communications grid. The snapshot or grid status may include, for example, the structure of the grid (including, for example, the worker nodes in the grid, unique identifiers of the nodes, or their relationships with the primary control node) and the status of a project (including, for example, the status of each worker node's portion of the project). The snapshot may also include analysis or results received from worker nodes in the communications grid. The backup control nodes may receive and store the backup data received from the primary control node. The backup control nodes may transmit a request for such a snapshot (or other information) from the primary control node, or the primary control node may send such information periodically to the backup control nodes.
As noted, the backup data may allow the backup control node to take over as primary control node if the primary control node fails without requiring the grid to start the project over from scratch. If the primary control node fails, the backup control node that will take over as primary control node may retrieve the most recent version of the snapshot received from the primary control node and use the snapshot to continue the project from the stage of the project indicated by the backup data. This may prevent failure of the project as a whole.
A backup control node may use various methods to determine that the primary control node has failed. In one example of such a method, the primary control node may transmit (e.g., periodically) a communication to the backup control node that indicates that the primary control node is working and has not failed, such as a heartbeat communication. The backup control node may determine that the primary control node has failed if the backup control node has not received a heartbeat communication for a certain predetermined period of time. Alternatively, a backup control node may also receive a communication from the primary control node itself (before it failed) or from a worker node that the primary control node has failed, for example because the primary control node has failed to communicate with the worker node.
Different methods may be performed to determine which backup control node of a set of backup control nodes (e.g., backup control nodes 404 and 406) will take over for failed primary control node 402 and become the new primary control node. For example, the new primary control node may be chosen based on a ranking or “hierarchy” of backup control nodes based on their unique identifiers. In an alternative embodiment, a backup control node may be assigned to be the new primary control node by another device in the communications grid or from an external device (e.g., a system infrastructure or an end user, such as a server or computer, controlling the communications grid). In another alternative embodiment, the backup control node that takes over as the new primary control node may be designated based on bandwidth or other statistics about the communications grid.
A worker node within the communications grid may also fail. If a worker node fails, work being performed by the failed worker node may be redistributed amongst the operational worker nodes. In an alternative embodiment, the primary control node may transmit a communication to each of the operable worker nodes still on the communications grid that each of the worker nodes should purposefully fail also. After each of the worker nodes fail, they may each retrieve their most recent saved checkpoint of their status and re-start the project from that checkpoint to minimize lost progress on the project being executed.
The process may also include receiving a failure communication corresponding to a node in the communications grid in operation 506. For example, a node may receive a failure communication including an indication that the primary control node has failed, prompting a backup control node to take over for the primary control node. In an alternative embodiment, a node may receive a failure that a worker node has failed, prompting a control node to reassign the work being performed by the worker node. The process may also include reassigning a node or a portion of the project being executed by the failed node, as described in operation 508. For example, a control node may designate the backup control node as a new primary control node based on the failure communication upon receiving the failure communication. If the failed node is a worker node, a control node may identify a project status of the failed worker node using the snapshot of the communications grid, where the project status of the failed worker node includes a status of a portion of the project being executed by the failed worker node at the failure time.
The process may also include receiving updated grid status information based on the reassignment, as described in operation 510, and transmitting a set of instructions based on the updated grid status information to one or more nodes in the communications grid, as described in operation 512. The updated grid status information may include an updated project status of the primary control node or an updated project status of the worker node. The updated information may be transmitted to the other nodes in the grid to update their stale stored information.
Similar to in
Each node also includes a data store 624. Data stores 624, similar to network-attached data stores 110 in
Each node also includes a user-defined function (UDF) 626. The UDF provides a mechanism for the DBMS 628 to transfer data to or receive data from the database stored in the data stores 624 that are managed by the DBMS. For example, UDF 626 can be invoked by the DBMS to provide data to the GESC for processing. The UDF 626 may establish a socket connection (not shown) with the GESC to transfer the data. Alternatively, the UDF 626 can transfer data to the GESC by writing data to shared memory accessible by both the UDF and the GESC.
The GESC 620 at the nodes 602 and 620 may be connected via a network, such as network 108 shown in
DBMS 628 may control the creation, maintenance, and use of database or data structure (not shown) within a nodes 602 or 610. The database may organize data stored in data stores 624. The DBMS 628 at control node 602 may accept requests for data and transfer the appropriate data for the request. With such a process, collections of data may be distributed across multiple physical locations. In this example, each node 602 and 610 stores a portion of the total data managed by the management system in its associated data store 624.
Furthermore, the DBMS may be responsible for protecting against data loss using replication techniques. Replication includes providing a backup copy of data stored on one node on one or more other nodes. Therefore, if one node fails, the data from the failed node can be recovered from a replicated copy residing at another node. However, as described herein with respect to
To initiate the project, the control node may determine if the query requests use of the grid-based computing environment to execute the project. If the determination is no, then the control node initiates execution of the project in a solo environment (e.g., at the control node), as described in operation 710. If the determination is yes, the control node may initiate execution of the project in the grid-based computing environment, as described in operation 706. In such a situation, the request may include a requested configuration of the grid. For example, the request may include a number of control nodes and a number of worker nodes to be used in the grid when executing the project. After the project has been completed, the control node may transmit results of the analysis yielded by the grid, as described in operation 708. Whether the project is executed in a solo or grid-based environment, the control node provides the results of the project, as described in operation 712.
As noted with respect to
The ESPE may receive streaming data over a period of time related to certain events, such as events or other data sensed by one or more network devices. The ESPE may perform operations associated with processing data created by the one or more devices. For example, the ESPE may receive data from the one or more network devices 204-209 shown in
The engine container is the top-level container in a model that manages the resources of the one or more projects 802. In an illustrative embodiment, for example, there may be only one ESPE 800 for each instance of the ESP application, and ESPE Boo may have a unique engine name. Additionally, the one or more projects 802 may each have unique project names, and each query may have a unique continuous query name and begin with a uniquely named source window of the one or more source windows 806. ESPE 800 may or may not be persistent.
Continuous query modeling involves defining directed graphs of windows for event stream manipulation and transformation. A window in the context of event stream manipulation and transformation is a processing node in an event stream processing model. A window in a continuous query can perform aggregations, computations, pattern-matching, and other operations on data flowing through the window. A continuous query may be described as a directed graph of source, relational, pattern matching, and procedural windows. The one or more source windows 806 and the one or more derived windows 808 represent continuously executing queries that generate updates to a query result set as new event blocks stream through ESPE 800. A directed graph, for example, is a set of nodes connected by edges, where the edges have a direction associated with them.
An event object may be described as a packet of data accessible as a collection of fields, with at least one of the fields defined as a key or unique identifier (ID). The event object may be created using a variety of formats including binary, alphanumeric, XML, etc. Each event object may include one or more fields designated as a primary identifier (ID) for the event so ESPE 800 can support operation codes (opcodes) for events including insert, update, upsert, and delete. Upsert opcodes update the event if the key field already exists; otherwise, the event is inserted. For illustration, an event object may be a packed binary representation of a set of field values and include both metadata and field data associated with an event. The metadata may include an opcode indicating if the event represents an insert, update, delete, or upsert, a set of flags indicating if the event is a normal, partial-update, or a retention generated event from retention policy management, and a set of microsecond timestamps that can be used for latency measurements.
An event block object may be described as a grouping or package of event objects. An event stream may be described as a flow of event block objects. A continuous query of the one or more continuous queries 804 transforms a source event stream made up of streaming event block objects published into ESPE 800 into one or more output event streams using the one or more source windows 806 and the one or more derived windows 808. A continuous query can also be thought of as data flow modeling.
The one or more source windows 806 are at the top of the directed graph and have no windows feeding into them. Event streams are published into the one or more source windows 806, and from there, the event streams may be directed to the next set of connected windows as defined by the directed graph. The one or more derived windows 808 are all instantiated windows that are not source windows and that have other windows streaming events into them. The one or more derived windows 808 may perform computations or transformations on the incoming event streams. The one or more derived windows 808 transform event streams based on the window type (that is operators such as join, filter, compute, aggregate, copy, pattern match, procedural, union, etc.) and window settings. As event streams are published into ESPE 800, they are continuously queried, and the resulting sets of derived windows in these queries are continuously updated.
Within the application, a user may interact with one or more user interface windows presented to the user in a display under control of the ESPE independently or through a browser application in an order selectable by the user. For example, a user may execute an ESP application, which causes presentation of a first user interface window, which may include a plurality of menus and selectors such as drop down menus, buttons, text boxes, hyperlinks, etc. associated with the ESP application as understood by a person of skill in the art. As further understood by a person of skill in the art, various operations may be performed in parallel, for example, using a plurality of threads.
At operation 900, an ESP application may define and start an ESPE, thereby instantiating an ESPE at a device, such as machine 220 and/or 240. In an operation 902, the engine container is created. For illustration, ESPE 800 may be instantiated using a function call that specifies the engine container as a manager for the model.
In an operation 904, the one or more continuous queries 804 are instantiated by ESPE 800 as a model. The one or more continuous queries 804 may be instantiated with a dedicated thread pool or pools that generate updates as new events stream through ESPE 800. For illustration, the one or more continuous queries 804 may be created to model business processing logic within ESPE 800, to predict events within ESPE 800, to model a physical system within ESPE 800, to predict the physical system state within ESPE 800, etc. For example, as noted, ESPE 800 may be used to support sensor data monitoring and management (e.g., sensing may include force, torque, load, strain, position, temperature, air pressure, fluid flow, chemical properties, resistance, electromagnetic fields, radiation, irradiance, proximity, acoustics, moisture, distance, speed, vibrations, acceleration, electrical potential, or electrical current, etc.).
ESPE 800 may analyze and process events in motion or “event streams.” Instead of storing data and running queries against the stored data, ESPE 800 may store queries and stream data through them to allow continuous analysis of data as it is received. The one or more source windows 806 and the one or more derived windows 808 may be created based on the relational, pattern matching, and procedural algorithms that transform the input event streams into the output event streams to model, simulate, score, test, predict, etc. based on the continuous query model defined and application to the streamed data.
In an operation 906, a publish/subscribe (pub/sub) capability is initialized for ESPE 800. In an illustrative embodiment, a pub/sub capability is initialized for each project of the one or more projects 802. To initialize and enable pub/sub capability for ESPE 800, a port number may be provided. Pub/sub clients can use a host name of an ESP device running the ESPE and the port number to establish pub/sub connections to ESPE 800.
Publish-subscribe is a message-oriented interaction paradigm based on indirect addressing. Processed data recipients specify their interest in receiving information from ESPE 800 by subscribing to specific classes of events, while information sources publish events to ESPE 800 without directly addressing the receiving parties. ESPE 800 coordinates the interactions and processes the data. In some cases, the data source receives confirmation that the published information has been received by a data recipient.
A publish/subscribe API may be described as a library that enables an event publisher, such as publishing device 1022, to publish event streams into ESPE 800 or an event subscriber, such as event subscribing device A 1024a, event subscribing device B 1024b, and event subscribing device C 1024c, to subscribe to event streams from ESPE 800. For illustration, one or more publish/subscribe APIs may be defined. Using the publish/subscribe API, an event publishing application may publish event streams into a running event stream processor project source window of ESPE 800, and the event subscription application may subscribe to an event stream processor project source window of ESPE 800.
The publish/subscribe API provides cross-platform connectivity and endianness compatibility between ESP application and other networked applications, such as event publishing applications instantiated at publishing device 1022, and event subscription applications instantiated at one or more of event subscribing device A 1024a, event subscribing device B 1024b, and event subscribing device C 1024c.
Referring back to
ESP subsystem 800 may include a publishing client 1002, ESPE 800, a subscribing client A 1004, a subscribing client B 1006, and a subscribing client C 1008. Publishing client 1002 may be started by an event publishing application executing at publishing device 1022 using the publish/subscribe API. Subscribing client A 1004 may be started by an event subscription application A, executing at event subscribing device A 1024a using the publish/subscribe API. Subscribing client B 1006 may be started by an event subscription application B executing at event subscribing device B 1024b using the publish/subscribe API. Subscribing client C 1008 may be started by an event subscription application C executing at event subscribing device C 1024c using the publish/subscribe API.
An event block object containing one or more event objects is injected into a source window of the one or more source windows 806 from an instance of an event publishing application on event publishing device 1022. The event block object may be generated, for example, by the event publishing application and may be received by publishing client 1002. A unique ID may be maintained as the event block object is passed between the one or more source windows 806 and/or the one or more derived windows 808 of ESPE 800, and to subscribing client A 1004, subscribing client B 1006, and subscribing client C 1008 and to event subscription device A 1024a, event subscription device B 1024b, and event subscription device C 1024c. Publishing client 1002 may further generate and include a unique embedded transaction ID in the event block object as the event block object is processed by a continuous query, as well as the unique ID that publishing device 1022 assigned to the event block object.
In an operation 912, the event block object is processed through the one or more continuous queries 804. In an operation 914, the processed event block object is output to one or more computing devices of the event subscribing devices 1024a-c. For example, subscribing client A 1004, subscribing client B 1006, and subscribing client C 1008 may send the received event block object to event subscription device A 1024a, event subscription device B 1024b, and event subscription device C 1024c, respectively.
ESPE 800 maintains the event block containership aspect of the received event blocks from when the event block is published into a source window and works its way through the directed graph defined by the one or more continuous queries 804 with the various event translations before being output to subscribers. Subscribers can correlate a group of subscribed events back to a group of published events by comparing the unique ID of the event block object that a publisher, such as publishing device 1022, attached to the event block object with the event block ID received by the subscriber.
In an operation 916, a determination is made concerning whether or not processing is stopped. If processing is not stopped, processing continues in operation 910 to continue receiving the one or more event streams containing event block objects from the, for example, one or more network devices. If processing is stopped, processing continues in an operation 918. In operation 918, the started projects are stopped. In operation 920, the ESPE is shutdown.
As noted, in some embodiments, big data is processed for an analytics project after the data is received and stored. In other embodiments, distributed applications process continuously flowing data in real-time from distributed sources by applying queries to the data before distributing the data to geographically distributed recipients. As noted, an event stream processing engine (ESPE) may continuously apply the queries to the data as it is received and determines which entities receive the processed data. This allows for large amounts of data being received and/or collected in a variety of environments to be processed and distributed in real time. For example, as shown with respect to
Aspects of the current disclosure provide technical solutions to technical problems, such as computing problems that arise when an ESP device fails which results in a complete service interruption and potentially significant data loss. The data loss can be catastrophic when the streamed data is supporting mission critical operations such as those in support of an ongoing manufacturing or drilling operation. An embodiment of an ESP system achieves a rapid and seamless failover of ESPE running at the plurality of ESP devices without service interruption or data loss, thus significantly improving the reliability of an operational system that relies on the live or real-time processing of the data streams. The event publishing systems, the event subscribing systems, and each ESPE not executing at a failed ESP device are not aware of or effected by the failed ESP device. The ESP system may include thousands of event publishing systems and event subscribing systems. The ESP system keeps the failover logic and awareness within the boundaries of out-messaging network connector and out-messaging network device.
In one example embodiment, a system is provided to support a failover when event stream processing (ESP) event blocks. The system includes, but is not limited to, an out-messaging network device and a computing device. The computing device includes, but is not limited to, a processor and a computer-readable medium operably coupled to the processor. The processor is configured to execute an ESP engine (ESPE). The computer-readable medium has instructions stored thereon that, when executed by the processor, cause the computing device to support the failover. An event block object is received from the ESPE that includes a unique identifier. A first status of the computing device as active or standby is determined. When the first status is active, a second status of the computing device as newly active or not newly active is determined. Newly active is determined when the computing device is switched from a standby status to an active status. When the second status is newly active, a last published event block object identifier that uniquely identifies a last published event block object is determined. A next event block object is selected from a non-transitory computer-readable medium accessible by the computing device. The next event block object has an event block object identifier that is greater than the determined last published event block object identifier. The selected next event block object is published to an out-messaging network device. When the second status of the computing device is not newly active, the received event block object is published to the out-messaging network device. When the first status of the computing device is standby, the received event block object is stored in the non-transitory computer-readable medium.
Different machine-learning models may be used interchangeably to perform a task. Examples of tasks that can be performed at least partially using machine-learning models include various types of scoring; bioinformatics; cheminformatics; software engineering; fraud detection; customer segmentation; generating online recommendations; adaptive websites; determining customer lifetime value; search engines; placing advertisements in real time or near real time; classifying DNA sequences; affective computing; performing natural language processing and understanding; object recognition and computer vision; robotic locomotion; playing games; optimization and metaheuristics; detecting network intrusions; medical diagnosis and monitoring; or predicting when an asset, such as a machine, will need maintenance.
Any number and combination of tools can be used to create machine-learning models. Examples of tools for creating and managing machine-learning models can include SAS® Enterprise Miner, SAS® Rapid Predictive Modeler, and SAS® Model Manager, SAS Cloud Analytic Services (CAS)®, SAS Viya® of all which are by SAS Institute Inc. of Cary, North Carolina.
Machine-learning models can be constructed through an at least partially automated (e.g., with little or no human involvement) process called training. During training, input data can be iteratively supplied to a machine-learning model to enable the machine-learning model to identify patterns related to the input data or to identify relationships between the input data and output data. With training, the machine-learning model can be transformed from an untrained state to a trained state. Input data can be split into one or more training sets and one or more validation sets, and the training process may be repeated multiple times. The splitting may follow a k-fold cross-validation rule, a leave-one-out-rule, a leave-p-out rule, or a holdout rule. An overview of training and using a machine-learning model is described below with respect to the flow chart of
In block 1102, training data is received. In some examples, the training data is received from a remote database or a local database, constructed from various subsets of data, or input by a user. The training data can be used in its raw form for training a machine-learning model or pre-processed into another form, which can then be used for training the machine-learning model. For example, the raw form of the training data can be smoothed, truncated, aggregated, clustered, or otherwise manipulated into another form, which can then be used for training the machine-learning model.
In block 1104, a machine-learning model is trained using the training data. The machine-learning model can be trained in a supervised, unsupervised, or semi-supervised manner. In supervised training, each input in the training data is correlated to a desired output. This desired output may be a scalar, a vector, or a different type of data structure such as text or an image. This may enable the machine-learning model to learn a mapping between the inputs and desired outputs. In unsupervised training, the training data includes inputs, but not desired outputs, so that the machine-learning model has to find structure in the inputs on its own. In semi-supervised training, only some of the inputs in the training data are correlated to desired outputs.
In block 1106, the machine-learning model is evaluated. For example, an evaluation dataset can be obtained, for example, via user input or from a database. The evaluation dataset can include inputs correlated to desired outputs. The inputs can be provided to the machine-learning model and the outputs from the machine-learning model can be compared to the desired outputs. If the outputs from the machine-learning model closely correspond with the desired outputs, the machine-learning model may have a high degree of accuracy. For example, if 90% or more of the outputs from the machine-learning model are the same as the desired outputs in the evaluation dataset, the machine-learning model may have a high degree of accuracy. Otherwise, the machine-learning model may have a low degree of accuracy. The 90% number is an example only. A realistic and desirable accuracy percentage is dependent on the problem and the data.
In some examples, if, at 1108, the machine-learning model has an inadequate degree of accuracy for a particular task, the process can return to block 1104, where the machine-learning model can be further trained using additional training data or otherwise modified to improve accuracy. However, if, at 1108. the machine-learning model has an adequate degree of accuracy for the particular task, the process can continue to block 1110.
In block 1110, new data is received. In some examples, the new data is received from a remote database or a local database, constructed from various subsets of data, or input by a user. The new data may be unknown to the machine-learning model. For example, the machine-learning model may not have previously processed or analyzed the new data.
In block 1112, the trained machine-learning model is used to analyze the new data and provide a result. For example, the new data can be provided as input to the trained machine-learning model. The trained machine-learning model can analyze the new data and provide a result that includes a classification of the new data into a particular class, a clustering of the new data into a particular group, a prediction based on the new data, or any combination of these.
In block 1114, the result is post-processed. For example, the result can be added to, multiplied with, or otherwise combined with other data as part of a job. As another example, the result can be transformed from a first format, such as a time series format, into another format, such as a count series format. Any number and combination of operations can be performed on the result during post-processing.
A more specific example of a machine-learning model is the neural network 1200 shown in
The neurons 1208 and connections 1255 thereamong may have numeric weights, which can be tuned during training of the neural network 1200. For example, training data can be provided to at least the inputs 1222 to the input layer 1202 of the neural network 1200, and the neural network 1200 can use the training data to tune one or more numeric weights of the neural network 1200. In some examples, the neural network 1200 can be trained using backpropagation. Backpropagation can include determining a gradient of a particular numeric weight based on a difference between an actual output of the neural network 1200 at the outputs 1277 and a desired output of the neural network 1200. Based on the gradient, one or more numeric weights of the neural network 1200 can be updated to reduce the difference therebetween, thereby increasing the accuracy of the neural network 1200. This process can be repeated multiple times to train the neural network 1200. For example, this process can be repeated hundreds or thousands of times to train the neural network 1200.
In some examples, the neural network 1200 is a feed-forward neural network. In a feed-forward neural network, the connections 1255 are instantiated and/or weighted so that every neuron 1208 only propagates an output value to a subsequent layer of the neural network 1200. For example, data may only move one direction (forward) from one neuron 1208 to the next neuron 1208 in a feed-forward neural network. Such a “forward” direction may be defined as proceeding from the input layer 1202 through the one or more hidden layers 1204, and toward the output layer 1206.
In other examples, the neural network 1200 may be a recurrent neural network. A recurrent neural network can include one or more feedback loops among the connections 1255, thereby allowing data to propagate in both forward and backward through the neural network 1200. Such a “backward” direction may be defined as proceeding in the opposite direction of forward, such as from the output layer 1206 through the one or more hidden layers 1204, and toward the input layer 1202. This can allow for information to persist within the recurrent neural network. For example, a recurrent neural network can determine an output based at least partially on information that the recurrent neural network has seen before, giving the recurrent neural network the ability to use previous input to inform the output.
In some examples, the neural network 1200 operates by receiving a vector of numbers from one layer; transforming the vector of numbers into a new vector of numbers using a matrix of numeric weights, a nonlinearity, or both; and providing the new vector of numbers to a subsequent layer (“subsequent” in the sense of moving “forward”) of the neural network 1200. Each subsequent layer of the neural network 1200 can repeat this process until the neural network 1200 outputs a final result at the outputs 1277 of the output layer 1206. For example, the neural network 1200 can receive a vector of numbers at the inputs 1222 of the input layer 1202. The neural network 1200 can multiply the vector of numbers by a matrix of numeric weights to determine a weighted vector. The matrix of numeric weights can be tuned during the training of the neural network 1200. The neural network 1200 can transform the weighted vector using a nonlinearity, such as a sigmoid tangent or the hyperbolic tangent. In some examples, the nonlinearity can include a rectified linear unit, which can be expressed using the equation y=max(x, 0) where y is the output and x is an input value from the weighted vector. The transformed output can be supplied to a subsequent layer (e.g., a hidden layer 1204) of the neural network 1200. The subsequent layer of the neural network 1200 can receive the transformed output, multiply the transformed output by a matrix of numeric weights and a nonlinearity, and provide the result to yet another layer of the neural network 1200 (e.g., another, subsequent, hidden layer 1204). This process continues until the neural network 1200 outputs a final result at the outputs 1277 of the output layer 1206.
As also depicted in
The neuromorphic device 1250 may incorporate a storage interface 1299 by which neural network configuration data 1293 that is descriptive of various parameters and hyper parameters of the neural network 1200 may be stored and/or retrieved. More specifically, the neural network configuration data 1293 may include such parameters as weighting and/or biasing values derived through the training of the neural network 1200, as has been described. Alternatively, or additionally, the neural network configuration data 1293 may include such hyperparameters as the manner in which the neurons 1208 are to be interconnected (e.g., feed-forward or recurrent), the trigger function to be implemented within the neurons 1208, the quantity of layers and/or the overall quantity of the neurons 1208. The neural network configuration data 1293 may provide such information for more than one neuromorphic device 1250 where multiple ones have been interconnected to support larger neural networks.
Other examples of the present disclosure may include any number and combination of machine-learning models having any number and combination of characteristics. The machine-learning model(s) can be trained in a supervised, semi-supervised, or unsupervised manner, or any combination of these. The machine-learning model(s) can be implemented using a single computing device or multiple computing devices, such as the communications grid computing system 400 discussed above.
Implementing some examples of the present disclosure at least in part by using machine-learning models can reduce the total number of processing iterations, time, memory, electrical power, or any combination of these consumed by a computing device when analyzing data. For example, a neural network may more readily identify patterns in data than other approaches. This may enable the neural network to analyze the data using fewer processing cycles and less memory than other approaches, while obtaining a similar or greater level of accuracy.
Some machine-learning approaches may be more efficiently and speedily executed and processed with machine-learning specific processors (e.g., not a generic CPU). Such processors may also provide an energy savings when compared to generic CPUs. For example, some of these processors can include a graphical processing unit (GPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), an artificial intelligence (AI) accelerator, a neural computing core, a neural computing engine, a neural processing unit, a purpose-built chip architecture for deep learning, and/or some other machine-learning specific processor that implements a machine learning approach or one or more neural networks using semiconductor (e.g., silicon (Si), gallium arsenide (GaAs)) devices. These processors may also be employed in heterogeneous computing architectures with a number of and/or a variety of different types of cores, engines, nodes, and/or layers to achieve various energy efficiencies, processing speed improvements, data communication speed improvements, and/or data efficiency targets and improvements throughout various parts of the system when compared to a homogeneous computing architecture that employs CPUs for general purpose computing.
It may be that at least a subset of the containers 1336 are each allocated a similar combination and amounts of resources so that each is of a similar configuration with a similar range of capabilities, and therefore, are interchangeable. This may be done in embodiments in which it is desired to have at least such a subset of the containers 1336 already instantiated prior to the receipt of requests to perform analyses, and thus, prior to the specific resource requirements of each of those analyses being known.
Alternatively, or additionally, it may be that at least a subset of the containers 1336 are not instantiated until after the processing system 1300 receives requests to perform analyses where each request may include indications of the resources required for one of those analyses. Such information concerning resource requirements may then be used to guide the selection of resources and/or the amount of each resource allocated to each such container 1336. As a result, it may be that one or more of the containers 1336 are caused to have somewhat specialized configurations such that there may be differing types of containers to support the performance of different analyses and/or different portions of analyses.
It may be that the entirety of the logic of a requested analysis is implemented within a single executable routine 1334. In such embodiments, it may be that the entirety of that analysis is performed within a single container 1336 as that single executable routine 1334 is executed therein. However, it may be that such a single executable routine 1334, when executed, is at least intended to cause the instantiation of multiple instances of itself that are intended to be executed at least partially in parallel. This may result in the execution of multiple instances of such an executable routine 1334 within a single container 1336 and/or across multiple containers 1336.
Alternatively, or additionally, it may be that the logic of a requested analysis is implemented with multiple differing executable routines 1334. In such embodiments, it may be that at least a subset of such differing executable routines 1334 are executed within a single container 1336. However, it may be that the execution of at least a subset of such differing executable routines 1334 is distributed across multiple containers 1336.
Where an executable routine 1334 of an analysis is under development, and/or is under scrutiny to confirm its functionality, it may be that the container 1336 within which that executable routine 1334 is to be executed is additionally configured assist in limiting and/or monitoring aspects of the functionality of that executable routine 1334. More specifically, the execution environment provided by such a container 1336 may be configured to enforce limitations on accesses that are allowed to be made to memory and/or I/O addresses to control what storage locations and/or I/O devices may be accessible to that executable routine 1334. Such limitations may be derived based on comments within the programming code of the executable routine 1334 and/or other information that describes what functionality the executable routine 1334 is expected to have, including what memory and/or I/O accesses are expected to be made when the executable routine 1334 is executed. Then, when the executable routine 1334 is executed within such a container 1336, the accesses that are attempted to be made by the executable routine 1334 may be monitored to identify any behavior that deviates from what is expected.
Where the possibility exists that different executable routines 1334 may be written in different programming languages, it may be that different subsets of containers 1336 are configured to support different programming languages. In such embodiments, it may be that each executable routine 1334 is analyzed to identify what programming language it is written in, and then what container 1336 is assigned to support the execution of that executable routine 1334 may be at least partially based on the identified programming language. Where the possibility exists that a single requested analysis may be based on the execution of multiple executable routines 1334 that may each be written in a different programming language, it may be that at least a subset of the containers 1336 are configured to support the performance of various data structure and/or data format conversion operations to enable a data object output by one executable routine 1334 written in one programming language to be accepted as an input to another executable routine 1334 written in another programming language.
As depicted, at least a subset of the containers 1336 may be instantiated within one or more VMs 1331 that may be instantiated within one or more node devices 1330. Thus, in some embodiments, it may be that the processing, storage and/or other resources of at least one node device 1330 may be partially allocated through the instantiation of one or more VMs 1331, and then in turn, may be further allocated within at least one VM 1331 through the instantiation of one or more containers 1336.
In some embodiments, it may be that such a nested allocation of resources may be carried out to effect an allocation of resources based on two differing criteria. By way of example, it may be that the instantiation of VMs 1331 is used to allocate the resources of a node device 1330 to multiple users or groups of users in accordance with any of a variety of service agreements by which amounts of processing, storage and/or other resources are paid for each such user or group of users. Then, within each VM 1331 or set of VMs 1331 that is allocated to a particular user or group of users, containers 1336 may be allocated to distribute the resources allocated to each VM 1331 among various analyses that are requested to be performed by that particular user or group of users.
As depicted, where the processing system 1300 includes more than one node device 1330, the processing system 1300 may also include at least one control device 1350 within which one or more control routines 1354 may be executed to control various aspects of the use of the node device(s) 1330 to perform requested analyses. By way of example, it may be that at least one control routine 1354 implements logic to control the allocation of the processing, storage and/or other resources of each node device 1300 to each VM 1331 and/or container 1336 that is instantiated therein. Thus, it may be the control device(s) 1350 that effects a nested allocation of resources, such as the aforedescribed example allocation of resources based on two differing criteria.
As also depicted, the processing system 1300 may also include one or more distinct requesting devices 1370 from which requests to perform analyses may be received by the control device(s) 1350. Thus, and by way of example, it may be that at least one control routine 1354 implements logic to monitor for the receipt of requests from authorized users and/or groups of users for various analyses to be performed using the processing, storage and/or other resources of the node device(s) 1330 of the processing system 1300. The control device(s) 1350 may receive indications of the availability of resources, the status of the performances of analyses that are already underway, and/or still other status information from the node device(s) 1330 in response to polling, at a recurring interval of time, and/or in response to the occurrence of various preselected events. More specifically, the control device(s) 1350 may receive indications of status for each container 1336, each VM 1331 and/or each node device 1330. At least one control routine 1354 may implement logic that may use such information to select container(s) 1336, VM(s) 1331 and/or node device(s) 1330 that are to be used in the execution of the executable routine(s) 1334 associated with each requested analysis.
As further depicted, in some embodiments, the one or more control routines 1354 may be executed within one or more containers 1356 and/or within one or more VMs 1351 that may be instantiated within the one or more control devices 1350. It may be that multiple instances of one or more varieties of control routine 1354 may be executed within separate containers 1356, within separate VMs 1351 and/or within separate control devices 1350 to better enable parallelized control over parallel performances of requested analyses, to provide improved redundancy against failures for such control functions, and/or to separate differing ones of the control routines 1354 that perform different functions. By way of example, it may be that multiple instances of a first variety of control routine 1354 that communicate with the requesting device(s) 1370 are executed in a first set of containers 1356 instantiated within a first VM 1351, while multiple instances of a second variety of control routine 1354 that control the allocation of resources of the node device(s) 1330 are executed in a second set of containers 1356 instantiated within a second VM 1351. It may be that the control of the allocation of resources for performing requested analyses may include deriving an order of performance of portions of each requested analysis based on such factors as data dependencies thereamong, as well as allocating the use of containers 1336 in a manner that effectuates such a derived order of performance.
Where multiple instances of control routine 1354 are used to control the allocation of resources for performing requested analyses, such as the assignment of individual ones of the containers 1336 to be used in executing executable routines 1334 of each of multiple requested analyses, it may be that each requested analysis is assigned to be controlled by just one of the instances of control routine 1354. This may be done as part of treating each requested analysis as one or more “ACID transactions” that each have the four properties of atomicity, consistency, isolation and durability such that a single instance of control routine 1354 is given full control over the entirety of each such transaction to better ensure that either all of each such transaction is either entirely performed or is entirely not performed. As will be familiar to those skilled in the art, allowing partial performances to occur may cause cache incoherencies and/or data corruption issues.
As additionally depicted, the control device(s) 1350 may communicate with the requesting device(s) 1370 and with the node device(s) 1330 through portions of a network 1399 extending thereamong. Again, such a network as the depicted network 1399 may be based on any of a variety of wired and/or wireless technologies, and may employ any of a variety of protocols by which commands, status, data and/or still other varieties of information may be exchanged. It may be that one or more instances of a control routine 1354 cause the instantiation and maintenance of a web portal or other variety of portal that is based on any of a variety of communication protocols, etc. (e.g., a restful API). Through such a portal, requests for the performance of various analyses may be received from requesting device(s) 1370, and/or the results of such requested analyses may be provided thereto. Alternatively, or additionally, it may be that one or more instances of a control routine 1354 cause the instantiation of and maintenance of a message passing interface and/or message queues. Through such an interface and/or queues, individual containers 1336 may each be assigned to execute at least one executable routine 1334 associated with a requested analysis to cause the performance of at least a portion of that analysis.
Although not specifically depicted, it may be that at least one control routine 1354 may include logic to implement a form of management of the containers 1336 based on the Kubernetes container management platform promulgated by Could Native Computing Foundation of San Francisco, CA, USA. In such embodiments, containers 1336 in which executable routines 1334 of requested analyses may be instantiated within “pods” (not specifically shown) in which other containers may also be instantiated for the execution of other supporting routines. Such supporting routines may cooperate with control routine(s) 1354 to implement a communications protocol with the control device(s) 1350 via the network 1399 (e.g., a message passing interface, one or more message queues, etc.). Alternatively, or additionally, such supporting routines may serve to provide access to one or more storage repositories (not specifically shown) in which at least data objects may be stored for use in performing the requested analyses.
Method for Configuring and Using a Multi-Stage Object Classification and Condition Pipeline
As described in more detail herein, a system or service implementing the method 1400 may use the multi-stage object classification and condition pipeline 1501 to predict a probable object class and/or a probable object-condition class for target objects detected within a subject scene. The multi-stage object classification and condition pipeline 1501, in one or more embodiments, may include a first stage 1532 that includes using a machine learning-based object localization model 1508, a second stage 1534 that includes using a machine learning-based object classification model 1524, and a third stage 1536 that includes using at least one object-condition machine learning classification model 1528.
Generating the Machine Learning-Based Object Localization Model
In one or more embodiments, the system or service implementing the method 1400 may function to generate the machine learning-based object localization model 1508 using any suitable machine learning model training and testing platform.
As described in more detail herein, in one or more embodiments, the machine learning-based object localization model 1508, when trained, may function to identify (e.g., detect and locate) electrical components within a downsampled digital image of an electrical grid that correspond to one or more target electrical component object classes. For instance, in the non-limiting example of
In one or more embodiments, generating the machine learning-based object localization model 1508 may include obtaining an object detection machine learning model (e.g., YOLO, YOLOv2, YOLOv3, YOLOv4, YOLOv5, FAST R-CNN, or any suitable object detection machine learning model). For instance, in a non-limiting example, the system or service implementing the method 1400 may function to obtain a YOLOv2 object detection machine learning model that may have used the multi-criteria loss function 2010 during a model training. The multi-criteria loss function 2010, in some embodiments, may include a bounding box coordinate regression error component 2012, a bounding box score prediction error component 2014, and an object classification error component 2016.
It shall be recognized that the bounding box coordinate regression error component 2012 may be used to evaluate a proficiency of a target machine learning model (e.g., YOLOv2 object detection machine learning model) in predicting bounding boxes of objects present within a subject image during a training of the target machine learning model. Specifically, the bounding box coordinate regression error component 2012 may use sum-squared error (SSE) to measure a difference between predicted bounding box coordinates and ground-truth bounding box coordinates. It shall be recognized that λcoord relates to a hyperparameter that controls a contribution of a localization loss associated with the bounding box coordinate regression error component 2012 with respect to the bounding box score prediction error component 2014 and the object classification error component 2016, S relates to a number of grid cells along each image direction, B relates to a number of bounding boxes predicted by each grid cell, Lijobj is an indicator function that is equal to one (1) when the j-th bounding box in the i-th grid cell is responsible for the object and is equal to zero (0) otherwise, ,
,
,
relate to predicted coordinates and predicted dimensions (e.g., predicted x, predicted y, predicted width, and predicted height) of a subject bounding box, and
,
,
,
relate to ground-truth coordinates and dimensions (e.g., ground-truth x, ground-truth y, ground-truth width, and ground-truth height) of the subject bounding box.
It shall be further recognized that the bounding box score prediction error component 2014 may be used to evaluate a proficiency of a target machine learning model (e.g., YOLOv2 object detection machine learning model) in predicting whether a subject object is present in a subject grid cell and an accuracy of a corresponding confidence score associated with the subject object during a training of the target machine learning model. Specifically, the confidence score represents the intersection over union (IoU) between a subject predicted bounding box and a corresponding ground-truth bounding box. For instance, when a subject grid cell is not responsible for predicting a subject object, the bounding box score prediction error component 2014 may penalize the target machine learning model. It shall be recognized that Cij relates to the predicted confidence score for the i-th cell and the corresponding j-th bounding box, λnoobj relates to a hyperparameter that balances the confidence score loss associated with empty grid cells relative to the confidence score loss associated with grid cells containing objects, Lijnoobj is an indicator function that is equal to one (1) when the j-th bounding box in the i-th cell is not responsible for any object and zero (0) otherwise, and λobj relates to a hyperparameter that that controls a contribution of the loss associated with the bounding box score prediction error component 2014 during a training of the target machine learning model.
It shall be further recognized that the object classification error component 2016 may be used to evaluate a proficiency of a target machine learning model (e.g., YOLOv2 object detection machine learning model) in predicting object class predictions of objects within a subject image during a training of the target machine learning model. It shall be recognized that pij(c) relates to the predicted probability of the c-th object class for the i-th grid cell, relates to the ground-truth object class of the object associated with the i-th grid cell, c∈classes relates to the total number of object classes, and λclass relates to a hyperparameter that that controls a contribution of the loss associated with object classification error component 2016 during a training of the target machine learning model.
Additionally, in one or more embodiments, generating the machine learning-based object localization model 1508 may include adapting the multi-criteria loss function 2010 of the object detection machine learning model to remove one or more loss function components associated with object classification. For instance, in a non-limiting example, the multi-criteria loss function 2010 of the YOLOv2 object detection machine learning model may be adapted to a target multi-criteria loss function 2020 based on eliminating one or more loss function components of the multi-criteria loss function 2010 associated with object classification. Stated another way, the multi-criteria loss function 2010 of the YOLOv2 object detection machine learning model may include the object classification error component 2016 and the target multi-criteria loss function 2020 may exclude the object classification error component 2016, as shown generally by way of example in
Additionally, in one or more embodiments, generating the machine learning-based object localization model 1508 may include transforming the object detection machine learning model to the machine learning-based object localization model 1508 based on implementing (e.g., using or the like) the target multi-criteria loss function 2020 (instead of the multi-criteria loss function 2010) during a training of the object detection machine learning model. That is, in one or more embodiments, transforming the object detection machine learning model to the machine learning-based object localization model 1508 may include a transformation of a model structure of the object detection machine learning model based on or in response to a training of the object detection machine learning model. For instance, in a non-limiting example, the YOLOv2 object detection machine learning model may be trained on a plurality of training data samples that correspond to a target object class (e.g., the electrical insulator class) using, in part, the target multi-criteria loss function 2020. Accordingly, based on the training, the machine learning-based object localization model 1508 may function to identify and locate target objects within a subject scene that likely correspond to the target object class (e.g., the electrical insulator class). In a variant to such non-limiting example, the YOLOv2 object detection machine learning model may be trained on a corpus of training data samples that may include a first set of training data samples that correspond to a first object class (e.g., the electrical insulator class), a second set of training data samples that correspond to a second object class (e.g., the electrical transformer class), and/or a third set of training data samples that correspond to the first object class (e.g., the electrical insulator class) and the second object class (e.g., the electrical transformer class) using, in part, the target multi-criteria loss function 2020. Accordingly, based on the training, the machine learning-based object localization model 1508 may function to identify and locate target objects within a subject scene that likely correspond to at least one of the first object class (e.g., the electrical insulator class) and the second object class (e.g., the electrical transformer class).
It shall be recognized that the object detection machine learning model may be trained on training data samples that correspond to additional object classes, fewer object classes, and/or different object classes without departing from the scope of the disclosure.
It shall be further recognized that the system or service implementing the method 1400 may function to replace the multi-criteria loss function 2010 with the target multi-criteria loss function 2020 within a model training structure of the YOLOv2 object detection machine learning model prior to a training of the YOLOv2 object detection machine learning model.
Generating the Machine Learning-Based Object Classification Model
In one or more embodiments, the system or service implementing the method 1400 may function to generate the machine learning-based object classification model 1524 using any suitable machine learning model training and testing platform.
In one or more embodiments, the machine learning-based object classification model 1524 may be generated based on a training of a target machine learning-based image classification model using an object classification training data corpus.
In one or more embodiments, the object classification training data corpus may include a plurality of training data samples in which a first subset of the plurality of training data samples correspond to an in-scope object class (e.g., electrical insulator class) and a second subset of the plurality of training data samples correspond to an out-of-scope object class (e.g., not applicable class). Accordingly, based on the training of the target machine learning-based image classification model with the object classification training data corpus, the machine learning-based object classification model 1524 may be configured to classify a subject sub-image containing a subject object to the in-scope object class (e.g., electrical insulator class) or the out-of-scope object class (e.g., not applicable class) based on the machine learning-based object classification model 1524 receiving the subject sub-image. As described in more detail herein, a sub-image may be a target portion or target segment of a subject original digital image, as shown generally by way of example in
Additionally, or alternatively, in one or more embodiments, the object classification training data corpus may include a plurality of training data samples in which a first subset of the plurality of training data samples correspond to a first in-scope object class (e.g., electrical insulator class), a second subset of the plurality of training data samples correspond to a second in-scope object class (e.g., electrical transformer class), and a third subset of the plurality of training data samples correspond to an out-of-scope object class (e.g., not applicable class). Accordingly, based on the training of the target machine learning-based image classification model using the object classification training data corpus, the machine learning-based object classification model 1524 may be configured to classify a subject sub-image containing a subject object to the first in-scope object class (e.g., electrical insulator class), the second in-scope object class (e.g., electrical transformer class), or the out-of-scope object class (e.g., not applicable class) based on the machine learning-based object classification model 1524 receiving the subject sub-image.
Generating one or more Object-Condition Machine Learning Classification Models
In one or more embodiments, the system or service implementing the method 1400 may function to generate one or more object-condition machine learning classification models using any suitable machine learning model training and testing platform.
An object-condition machine learning classification model, as generally referred to herein, may be a sub-classifier that is trained to identify specific conditions or characteristics of a target object class (e.g., an in-scope object class or the like) of the machine learning-based object classification model 1524. Stated another way, an object-condition machine learning classification model may be trained to classify a sub-image associated with a subject object to one or more sub-classes of the target object class to which the object-condition machine learning classification model corresponds.
For instance, in a non-limiting example, an insulator object-condition model 1920 may be trained to identify specific conditions or characteristics (e.g., sub-classes) of the electrical insulator class such as whether an electrical insulator (e.g., object) contained within a subject sub-image is defective or not. In such non-limiting example, the system or service implementing the method 1400 may function to generate the insulator object-condition model 1920 based on a training of a machine learning-based image classification model using a training data corpus that may include a first set of training data samples that correspond to a first type of electrical insulator defect class (e.g., electrical insulators having one or more broken shells), a second set of training data samples that correspond to a second type of electrical insulator defect class (e.g., electrical insulators having shock damage), and/or a third set of training data samples that correspond to a not defective electrical insulator class (i.e., electrical insulators that are not visibly defective).
Accordingly, based on the training, the insulator object-condition model 1920 may be configured to classify a subject sub-image of a subject object to the first type of electrical insulator defect class, the second type of electrical insulator defect class, or the not defective electrical insulator class based on the insulator object-condition model 1920 receiving the subject sub-image.
In another non-limiting example, the transformer object-condition model 1918 may be trained to identify specific conditions or characteristics (e.g., sub-classes) of the electrical transformer class in analogous ways.
It shall be recognized that, in some embodiments, one or more of the object-condition machine learning models may be trained using a regression estimation model (e.g., linear regression model, etc.) without departing from the scope of the disclosure.
It shall be further recognized that the system or service implementing the method 1400 may use the multi-stage object classification and condition pipeline 1501 in a variety of modes. For instance, in a first implementation, based on receiving n-number of original digital images, the system or service implementing the method 1400 may function to implement n-number of multi-stage object classification and condition pipelines to concurrently process each of the n-number of original digital images.
Additionally, or alternatively, in a second implementation, based on receiving n-number of original digital images, the system or service implementing the method 1400 may function to implement a single multi-stage object classification and condition pipeline that is configured to sequentially process each of the n-number of original digital images.
First Stage of the Multi-Stage Object Classification and Condition Pipeline
In one or more embodiments, the method 1400 may include process 1410. Process 1410 may be used within the first stage 1532 of the multi-stage object classification and condition pipeline 1501. The first stage 1532, in one or more embodiments, may receive an original digital image 1502 of a subject scene and output a distinct sub-image of the original digital image 1502 for each target object detected within the subject scene, as described in more detail herein. It shall be recognized that the “first stage” may be interchangeably referred to herein as a “first modeling stage”, a “localization stage”, or the like.
In one or more embodiments, the original digital image 1502 may be associated with or may correspond to a digital frame of a digital video. For instance, in a non-limiting example, a digital video capturing device (e.g., a digital video capturing device coupled to a drone or the like) may be used to capture a digital video of a physical environment and, subsequently, the system or service implementing the method 1400 may function to receive the digital video. In such non-limiting example, the digital video capturing device may function to capture a digital video of one or more components associated with an electrical grid, such as one or more electrical transformers, one or more transmission towers, one or more substations, one or more wires, one or more conductors, one or more electrical insulators, and/or the like. It shall be recognized that in such non-limiting example, the digital video may capture the one or more electrical transformers, the one or more transmission towers, the one or more substations, the one or more wires, the one or more conductors, the one or more electrical insulators, and/or the like at a variety of positions, distances, and/or angles, which traditionally causes problems with accurately assessing such objects. However, as described in more detail herein, a system or service using the multi-stage object classification and condition pipeline may function to accurately predict a probable object class and/or a probable object-condition class of such objects.
Accordingly, based on receiving the digital video, the system or service implementing the method 1400 may function to convert the digital video to a sequence of original digital images in which each original digital image of the sequence of original digital images may correspond to a distinct digital frame of the digital video. In such non-limiting example, the original digital image 1502 illustrated in
In one or more embodiments, the original digital image 1502 may be routed to a digital image downsampling algorithm 1504 that may function to decrease (e.g., reduce) an image resolution of the original digital image 1502 to a target image resolution. In such embodiments, based on the digital image downsampling algorithm 1504 receiving the original digital image 1502, the digital image downsampling algorithm 1504 may function to output a downsampled digital image 1506 of the original digital image 1502. Stated another way, in one or more embodiments, the digital image downsampling algorithm 1504 may function to receive, as input, digital image data of the original digital image 1502 and output downsampled image data that corresponds to the downsampled digital image 1506.
For instance, in a non-limiting example, the original digital image 1502 that may be provided, as input, to the digital image downsampling algorithm 1504 may include digital image data associated with a target scene, as shown generally by way of example in
In one or more embodiments, based on or in response to the digital image downsampling algorithm 1504 outputting the downsampled digital image 1506, the downsampled digital image 1506 may be provided, as input, to the machine learning-based object localization model 1508. Stated another way, the digital image data of the original digital image 1502 may have a first image resolution and the digital image data of the downsampled digital image 1506 may have a second image resolution lower than the first image resolution. It shall be recognized that the digital image downsampling algorithm 1504 may be configured to output the downsampled digital image 1506 with an image resolution that satisfies an input image resolution criterion (e.g., a target image resolution parameter or the like) of the machine learning-based object localization model 1508.
Accordingly, based on the machine learning-based object localization model 1508 receiving the downsampled digital image 1506, process 1410 may be commenced. In some embodiments, process 1410 may include detecting, via the machine learning-based object localization model 1508, one or more target objects within a subject scene based on digital image data of the downsampled digital image 1506. In such embodiments, the machine learning-based object localization model 1508 may be trained to identify each object within the subject scene of the downsampled digital image 1506 that likely corresponds to a target object class that the machine learning-based object localization model 1508 was trained to identify and, accordingly, compute object position data (e.g., bounding box data, object location data, etc.) that includes such object, as shown generally by way of example in
For instance, in the non-limiting example of
Stated another way, the machine learning-based object localization model 1508 may be trained to detect each object within the scene of the downsampled digital image 1506 that likely corresponds to a target object class (e.g., an electrical insulator class) and, in turn, compute object position data for each detected object within the scene. For instance, in the non-limiting example of
In a variant to such non-limiting example, the machine learning-based object localization model 1508 may be trained to detect each object with the scene of the downsampled digital image 1506 that likely corresponds to any one of a plurality of object classes (e.g., electrical insulator class, electrical transformer class, etc.) and, in turn, define object position data for each detected object. In such non-limiting example, based on the machine learning-based object localization model 1508 receiving the downsampled digital image 1506, the machine learning-based object localization model 1508 may detect n-number of objects (e.g., one or more objects, two or more objects, three or more objects, etc.) that likely correspond to a first object class (e.g., the electrical insulator class) of the plurality of object classes and n-number of objects (e.g., one or more objects, two or more objects, three or more objects, etc.) that likely correspond to a second object class (e.g., the electrical transformer class) of the plurality of object classes. Accordingly, the machine learning-based object localization model 1508 may function to define a distinct spatial area (e.g., bounding box) for each object detected by the machine learning-based object localization model 1508 in analogous ways described above.
In one or more embodiments, the object position data computed by the machine learning-based object localization model 1508 may be provided, as input, to a digital image-to-object position mapping model 1512. In such embodiments, based on the digital image-to-object position mapping model 1512 receiving the object position data, process 1420 may be commenced. Process 1420, in one or more embodiments, may include identifying a likely position of each target object detected by the machine learning-based object localization model 1508 within digital image data of the original digital image 1502. Stated another way, the digital image-to-object position mapping model 1512 may function to map the object position data outputted (e.g., computed, predicted, etc.) by the machine learning-based object localization model 1508 to the original digital image 1502. It shall be noted that the object position data predicted by the machine learning-based object localization model 1508 may be mapped to the original digital image 1502 using any suitable technique, such as coordinate normalization or the like.
In one or more embodiments, based on the digital image-to-object position mapping model 1512 receiving the object position data computed by the machine learning-based object localization model 1508 and/or the original digital image 1502, the digital image-to-object position mapping model 1512 may function to output an original digital image-to-object position data mapping 1514, as shown generally by way of example in
For instance, in the non-limiting example of
Additionally, or alternatively, in such non-limiting example, bounding box 1712B may include object B 1710B within digital image data of the downsampled digital image 1506. Accordingly, bounding box 1712B may correspond to bounding box 1812B, which may include object B 1710B within digital image data of the original digital image 1502.
Additionally, or alternatively, in such non-limiting example, bounding box 1712C may include object C 1710C within digital image data of the downsampled digital image 1506. Accordingly, bounding box 1712C may correspond to bounding box 1812C, which may include object C 1710C within digital image data of the original digital image 1502.
Additionally, or alternatively, in such non-limiting example, bounding box 1712D may include object D 1710D within digital image data of the downsampled digital image 1506. Accordingly, bounding box 1712D may correspond to bounding box 1812D, which may include object D 1710D within digital image data of the original digital image 1502.
Additionally, or alternatively, in such non-limiting example, bounding box 1712E may include object E 1710E within digital image data of the downsampled digital image 1506. Accordingly, bounding box 1712E may correspond to bounding box 1812E, which may include object E 1710E within digital image data of the original digital image 1502.
Additionally, or alternatively, in such non-limiting example, bounding box 1712F may include object F 1710F within digital image data of the downsampled digital image 1506. Accordingly, bounding box 1712F may correspond to bounding box 1812F, which may include object F 1710F within digital image data of the original digital image 1502.
Additionally, or alternatively, in such non-limiting example, bounding box 1712G may include object G 1710G within digital image data of the downsampled digital image 1506. Accordingly, bounding box 1712G may correspond to bounding box 1812G, which may include object G 1710G within digital image data of the original digital image 1502.
Additionally, or alternatively, in such non-limiting example, bounding box 1712H may include object H 1710H within digital image data of the downsampled digital image 1506. Accordingly, bounding box 1712H may correspond to bounding box 1812H, which may include object H 1710H within digital image data of the original digital image 1502.
Additionally, or alternatively, in such non-limiting example, bounding box 1712I may include object I 1710I within digital image data of the downsampled digital image 1506. Accordingly, bounding box 1712I may correspond to bounding box 1812I, which may include object I 1710I within digital image data of the original digital image 1502.
Additionally, or alternatively, in such non-limiting example, bounding box 1712N may include object N 1710N within digital image data of the downsampled digital image 1506. Accordingly, bounding box 1712N may correspond to bounding box 1812N, which may include object N 1710N within digital image data of the original digital image 1502.
In one or more embodiments, the original digital image-to-object position data mapping 1514 may be provided, as input, to an object extraction model 1516. In such embodiments, based on the object extraction model 1516 receiving the original digital image-to-object position data mapping 1514, process 1430 may be commenced. Process 1430, in one or more embodiments, may include extracting, from digital image data of the original digital image 1502, a distinct sub-image for each target object detected by the machine learning-based object localization model 1508 based on the likely position of a subject object within the digital image data of the original digital image 1502.
Stated another way, in one or more embodiments, process 1420 may function to identify a likely position of a subject object detected by the machine learning-based object localization model 1508 within digital image data of the original digital image 1502, and process 1430 may function to extract, from digital image data of the original digital image 1502, a sub-image containing the subject object based on the likely position.
For instance, in the non-limiting example of
Additionally, or alternatively, in the non-limiting example of
Additionally, or alternatively, in the non-limiting example of
Stated another way, in one or more embodiments, the object extraction model 1516 may function to output the sub-image of object A 1518A (e.g., a sub-image containing object A) based on extracting, from the original digital image 1502, the original image data contained in bounding box 1812A, as shown generally by way of example in
Second Stage of the Multi-Stage Object Classification and Condition Pipeline
In one or more embodiments, the method 1400 may include process 1440. Process 1440 may be used within the second stage 1534 of the multi-stage object classification and condition pipeline 1501. The second stage 1534, in one or more embodiments, may receive one or more sub-images of the original digital image 1502 and classify each of the one or more sub-images to a probable object class, as described in more detail herein. It shall be recognized that the “second stage” may be interchangeably referred to herein as a “second modeling stage”, an “object classification stage”, or the like.
In one or more embodiments, each of the one or more sub-images outputted by the object extraction model 1516 may be provided to a sub-image resizing model 1520. The sub-image resizing model, in one or more embodiments, may be configured to transform each of the one or more sub-images to an image resolution that satisfies an input image resolution criterion (e.g., a target image resolution parameter or the like) of the machine learning-based object classification model 1524 and/or the object-condition machine learning classification model 1528, as shown generally by way of example in
For instance, in the non-limiting example of
In one or more embodiments, each of the transformed sub-images may be provided, as input, to the machine learning-based object classification model 1524. In such embodiments, based on the machine learning-based object classification model 1524 receiving a transformed sub-image, process 1440 may be commenced. Process 1440 may include classifying, via the machine learning-based object classification model 1524, each transformed sub-image to a probable object class of a plurality of distinct object classes. Stated differently, process 1440 may classify, via the machine learning-based object classification model 1524, an object contained within digital image data of a subject transformed sub-image to a probable object class of a plurality of distinct object classes.
In one or more embodiments, the machine learning-based object classification model 1524 may be configured to classify a subject transformed sub-image to an in-scope object class of one or more in-scope object classes or an out-of-scope object class (e.g., a not applicable object class or the like) based on a set of features extracted from the subject transformed sub-image. That is, in some embodiments, the machine learning-based object classification model 1524 may classify the subject transformed sub-image to one of the one or more in-scope object classes. Alternatively, in some embodiments, the machine learning-based object classification model 1524 may classify the subject transformed sub-image to the out-of-scope object class.
It shall be recognized that, in some embodiments, the subject transformed sub-image may be germane to a target classification objective of a downstream object-condition machine learning classification model (e.g., the object-condition machine learning classification model 1528) when the machine learning-based object classification model 1524 classifies the subject sub-image to one of the one or more in-scope object classes. It shall be further recognized that, in some embodiments, the transformed subject sub-image may be immaterial to a target classification objective of a downstream object-condition machine learning classification model (e.g., the object-condition machine learning classification model 1528) when the machine learning-based object classification model 1524 classifies the subject transformed sub-image to the out-of-scope object class.
For instance, in a non-limiting example, the machine learning-based object classification model 1524 may function to classify the transformed sub-image of object A 1522A to a probable object class (e.g., probable object class of object A 1526A). In such embodiments, the probable object class of object A 1526A may relate to an in-scope object class (e.g., electrical insulator class). Thus, the machine learning-based object localization model 1508 may have correctly localized object A within the digital image data of the downsampled digital image 1506 as the object (e.g., object A, electrical insulator A, etc.) contained within the transformed sub-image of object A 1522A likely corresponds to a target object class (e.g., electrical insulator class) that the machine learning-based object localization model 1508 was trained to identify.
Additionally, or alternatively, in such non-limiting example, the machine learning-based object classification model 1524 may function to classify the transformed sub-image of object B 1522B to a probable object class (e.g., probable object class of object B 1526B). In such embodiments, the probable object class of object B 1526B may relate to an in-scope object class (e.g., electrical insulator class). Thus, the machine learning-based object localization model 1508 may have correctly localized object B within the digital image data of the downsampled digital image 1506 as the object (e.g., object B, electrical insulator B) contained within the transformed sub-image of object B 1522B likely corresponds to a target object class (e.g., electrical insulator class) that the machine learning-based object localization model 1508 was trained to identify.
Additionally, or alternatively, in such non-limiting example, the machine learning-based object classification model 1524 may function to classify the transformed sub-image of object N 1522N to a probable object class (e.g., probable object class of object N 1526N). In such embodiments, the probable object class of object N 1526N may relate to an in-scope object class (e.g., electrical insulator class). Thus, the machine learning-based object localization model 1508 may have correctly localized object N within the digital image data of the downsampled digital image 1506 as the object (e.g., object N, electrical insulator N) contained within the transformed sub-image of object N 1522N likely corresponds to a target object class (e.g., electrical insulator class) that the machine learning-based object localization model 1508 was trained to identify.
It shall be recognized that, in some embodiments, the machine learning-based object localization model 1508 may have incorrectly localized an object within digital image data of the downsampled digital image 1506. For instance, in the non-limiting example of
At least one technical benefit of using the machine learning-based object classification model 1524 to classify each of the transformed sub-images may enable a rectification of localization error (e.g., correct inaccuracies) caused by the machine learning-based object localization model 1508 of the first stage 1532 of the multi-stage object classification and condition pipeline 1501. Furthermore, another technical advantage of using the machine learning-based object classification model 1524 may result in a higher (e.g., increased) classification accuracy when compared to a classification accuracy of a combined localization and classification machine learning model as the combined localization and classification machine learning model is attempting to balance accuracy across a series of predictions (e.g., classification and localization) rather than specialize to a single machine learning task type (e.g., object classification).
Third Stage of the Multi-Stage Object Classification and Condition Pipeline
In one or more embodiments, the method 1400 may include process 1450 and/or process 1460. Process 1450 and process 1460 may be used within the third stage 1536 of the multi-stage object classification and condition pipeline 1501. It shall be recognized that the “third stage” may be interchangeably referred to herein as a “third modeling stage”, an “object-condition classification stage”, or the like.
In one or more embodiments, based on the machine learning-based object classification model 1524 classifying a subject transformed sub-image to an in-scope object class, process 1450 may be commenced. Process 1450, in one or more embodiments, may include routing, via one or more processors, at least a subset of transformed sub-images to one or more target object-condition machine learning classification models in which each transformed sub-image of the subset satisfies routing criteria of the multi-stage object classification and condition pipeline 1501.
In one or more embodiments, a subject transformed sub-image may satisfy routing criteria when the machine learning-based object classification model 1524 classifies the subject transformed sub-image to one of the one or more in-scope object classes. It shall be recognized, in one or more embodiments, a subject transformed sub-image may not satisfy routing criteria when the machine learning-based object classification model 1524 classifies the subject transformed sub-image to the out-of-scope object class (e.g., not applicable object class).
In one or more embodiments, based on a subject transformed sub-image satisfying routing criteria of the multi-stage object classification and condition pipeline 1501, the subject transformed sub-image may be routed to a target object-condition machine learning model of one or more target object-condition machine learning models based on the in-scope object class associated with the subject transformed sub-image. Accordingly, in some embodiments, process 1450 may function to assess a mapping that includes one or more distinct routing nexuses in which each distinct routing nexus associates a distinct object class (e.g., distinct in-scope object class) to a distinct object-condition machine learning model. Stated another way, in one or more embodiments, each distinct routing nexus defines a routing relationship between a distinct object class and a distinct object-condition machine learning model, thereby defining a path for routing a subject transformed sub-image to the appropriate (e.g., specialized) object-condition machine learning classification model based on the classification of the subject transformed sub-image by the machine learning-based object classification model 1524. It shall be recognized that the mapping including the one or more distinct routing nexuses may provide a technical benefit of enabling the system or service implementing the method 1400 to route transformed sub-images to one or more appropriate object-condition machine learning classification models.
For instance, in one or more embodiments, the mapping may include a first routing nexus that associates a first object class (e.g., an electrical insulator object class) to an insulator object-condition machine learning model 1920. Additionally, or alternatively, the mapping may include a second routing nexus that associates a second object class (e.g., electrical transformer object class) to a transformer object-condition machine learning model 1918. It shall be noted that the mapping may include additional routing nexuses, fewer routing nexuses, and/or different routing nexuses without departing from the scope of the disclosure.
In a non-limiting example, the transformed sub-image of object A 1522A may be provided to the machine learning-based object classification model 1524 which, in turn, may classify the transformed sub-image of object A 1522A to an electrical insulator class (e.g., in-scope object class). Further, in such non-limiting example, process 1450 may function to identify a routing nexus of the mapping that correspond to the electrical insulator class. Accordingly, based on identifying the routing nexus that corresponds to the electrical insulator class, process 1450 may function to route the transformed sub-image of object A 1522A to the insulator object-condition model 1920 as the routing nexus defines routing a subject transformed sub-image to the insulator object-condition model 1920 when the machine learning-based object classification model 1524 classifies the subject transformed sub-image to the electrical insulator class.
Additionally, or alternatively, in a non-limiting example, the transformed sub-image of object B 1522B may be provided to the machine learning-based object classification model 1524 which, in turn, may classify the transformed sub-image of object B 1522B to an electrical insulator class (e.g., in-scope object class). Further, in such non-limiting example, process 1450 may function to identify a routing nexus of the mapping that correspond to the electrical insulator class. Accordingly, based on identifying the routing nexus that corresponds to the electrical insulator class, process 1450 may function to route the transformed sub-image of object B 1522B to the insulator object-condition model 1920 as the routing nexus defines routing a subject transformed sub-image to the insulator object-condition model 1920 when the machine learning-based object classification model 1524 classifies the subject transformed sub-image to the electrical insulator class.
Additionally, or alternatively, in a non-limiting example, the transformed sub-image of object C 1522C may be provided to the machine learning-based object classification model 1524 which, in turn, may classify the transformed sub-image of object C 1522C to an out-of-scope object class (e.g., not applicable class, probable object class of object C 1526C). In such non-limiting example, process 1450 may function to bypass an object-condition classification of the transformed sub-image of object C 1522C when the machine learning-based object classification model 1524 classifies a subject transformed sub-image to the out-of-scope object class (e.g., not applicable object class). Stated another way, process 1450 may forego a routing of the transformed sub-image of object C 1522C to an object-condition classification model based on the machine learning-based object classification model 1524 classifying the transformed sub-image of object C 1522C to the out-of-scope object class.
Additionally, or alternatively, in a non-limiting example, the transformed sub-image of object N 1522N may be provided to the machine learning-based object classification model 1524 which, in turn, may classify the transformed sub-image of object N 1522N to an electrical insulator class (e.g., in-scope object class). Further, in such non-limiting example, process 1450 may function to identify a routing nexus of the mapping that correspond to the electrical insulator class. Accordingly, based on identifying the routing nexus that corresponds to the electrical insulator class, process 1450 may function to route the transformed sub-image of object N 1522N to the insulator object-condition model 1920 as the routing nexus defines routing a subject transformed sub-image to the insulator object-condition model 1920 when the machine learning-based object classification model 1524 classifies the subject transformed sub-image to the electrical insulator class.
In one or more embodiments, based on routing a subject transformed sub-image to a target object-condition machine learning classification model, process 1460 may be commenced. Process 1460, in one or more embodiments, may function to classify, via a target object-condition machine learning classification model, a subject transformed sub-image to a probable object-condition class of a plurality of distinct object-condition classes based on a routing of the subject transformed sub-image to the target object-condition machine learning classification model.
For instance, in a non-limiting example, based on routing the transformed sub-image of object A 1522A to the insulator object-condition model 1920 (e.g., insulator object-condition machine learning model), the insulator object-condition model 1920 may classify the transformed sub-image of object A 1522A to a probable object-condition class (e.g., not defective object class). Stated another way, the object (e.g., object A) contained within the transformed sub-image of object A 1522A is not defective (e.g., the electrical insulator does not have a broken shell, the electrical insulator does not have shock damage, etc.).
Additionally, or alternatively, in a non-limiting example, based on routing the transformed sub-image of object B 1522B to the insulator object-condition model 1920 (e.g., insulator object-condition machine learning model), the insulator object-condition model 1920 may classify the transformed sub-image of object B 1522B to a probable object-condition class (e.g., not defective object class). Stated another way, the object (e.g., object B) contained within the transformed sub-image of object B 1522B is not defective (e.g., the electrical insulator does not have a broken shell, the electrical insulator does not have shock damage, etc.).
Additionally, or alternatively, in a non-limiting example, based on routing the transformed sub-image of object N 1522N to the insulator object-condition model 1920 (e.g., insulator object-condition machine learning model), the insulator object-condition model 1920 may classify the transformed sub-image of object N 1522N to a probable object-condition class (e.g., defective object class). Stated another way, the object (e.g., object N) contained within the transformed sub-image of object N 1522N is defective (e.g., the electrical insulator has one or more broken shells, the electrical insulator has shock damage, and/or the like.).
It shall be recognized that, in embodiments in which a transformed sub-image contains an object associated with an electrical transformer, process 1450 may function to route the transformed sub-image to the transformer object-condition machine learning model 1918 in analogous ways. In such embodiments, process 1460 may classify, via the transformer object-condition machine learning model 1918, the transformed sub-image to an object condition-class of a plurality of distinct object-condition classes associated with electrical transformers.
In another non-limiting example, the machine learning-based object classification model 1524 may function to classify the transformed sub-image of object I 1602A, the transformed sub-image of object II 1602B, and the transformed sub-image of object III 1604C to a first in-scope object class (e.g., probable object class of object I), an out-of-scope object class (e.g., probable object class of object II), and a second in-scope object class (e.g., probable object class of object III), respectively.
In such non-limiting example, process 1450 may function to route the transformed sub-image of object I 1602A to an object-condition machine learning model (e.g., object-condition machine learning classification model A 16106A) of the plurality of object-condition machine learning classification models 1606 that specializes in detecting object conditions of objects of the first in-scope object class, as shown generally by way of example in
Additionally, or alternatively, in such non-limiting example, based on the machine learning-based object classification model classifying the transformed sub-image of object II 1602B to the out-of-scope class, process 1450 may function to forego routing the transformed sub-image of object II 1602B to one of the plurality of object-condition machine learning classification models 1606 based on routing criteria of the multi-stage object classification and condition pipeline 1501 not being satisfied, as described above.
Additionally, or alternatively, in such non-limiting example, process 1450 may function to route the transformed sub-image of object III 1602C to an object-condition machine learning model (e.g., object-condition machine learning classification model A 16106B) of the plurality of object-condition machine learning classification models 1606 that specializes in detecting object conditions of objects of the second in-scope object class, as shown generally by way of example in
In one or more embodiments, based on one or more object-condition machine learning classification models classifying a set of transformed sub-images to a probable object-condition class, process 1470 may be commenced. Process 1470, in one or more embodiments, may include displaying, via a graphical user interface, a representation of the target object in association with the probable object-condition class of the target object.
In one or more embodiments, the graphical user interface may display a representation of a subject object in association with the probable object condition-class for each transformed sub-image classified by one or more object-condition machine learning classification models. In such embodiments, the graphical user interface may display a first set of sub-images (sub-image of object A 1518A, sub-image of object B 1518B) in associated with the probable object-condition class that corresponds to the not defective object-condition class. Additionally, in such embodiments, the graphical user interface may display a set second of sub-images (e.g., sub-image of object N 1518N) in associated with the probable object-condition class that corresponds to the defective object-condition class.
In a variant to such embodiments, the graphical user interface may display one or more representations of one or more objects that correspond to a target object-condition class (e.g., defective object condition-class). In such embodiments, the graphical user interface may display the set of sub-images (e.g., sub-image of object N 1518N that correspond to the defective object condition-class. The graphical user interface, in some embodiments, may allow users to visually understand the classification results and/or condition of subject objects classified using the multi-stage object classification and condition pipeline 1501.
It shall also be noted that the system and methods of the embodiment and variations described herein can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with the system and one or more portions of the processors and/or the controllers. The computer-readable medium can be stored on any suitable computer-readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, memory sticks (e.g., SD cards, USB flash drives), cloud-based services (e.g., cloud storage), magnetic storage devices, Solid-State Drives (SSDs), or any suitable device. The computer-executable component is preferably a general or application-specific processor, but any suitable dedicated hardware or hardware/firmware combination device can alternatively or additionally execute the instructions.
The systems and methods of the preferred embodiments may additionally, or alternatively, be implemented on an integrated data analytics software application and/or software architecture such as that are offered by SAS Institute Inc. of Cary, N.C., USA. Merely for illustration, the systems and methods of the preferred embodiments may be implemented using or integrated with one or more SAS software tools such as SAS® Viya™ which is developed and provided by SAS Institute Inc. of Cary, N.C., USA.
Although omitted for conciseness, the preferred embodiments include every combination and permutation of the implementations of the systems and methods described herein.
As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the embodiments of the disclosure without departing from the scope of the various described embodiments.
This application claims the benefit of U.S. Provisional Application No. 63/431,277, filed on 8 Dec. 2022, which is incorporated in its entirety by this reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 20200410245 | Israel | Dec 2020 | A1 |
| 20230237671 | Khinvasara | Jul 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 109711437 | May 2019 | CN |
| 110033453 | Jul 2019 | CN |
| 111784685 | Oct 2020 | CN |
| 112184692 | Jan 2021 | CN |
| 113379699 | Sep 2021 | CN |
| 115220479 | Oct 2022 | CN |
| Number | Date | Country | |
|---|---|---|---|
| 63431277 | Dec 2022 | US |
