Patent Application
20230056472
Embodiments described herein generally relate to the generation of firing cut out maps in a missile launching system, and in an embodiment, but not by way of limitation, firing cutout rapid generation aided by machine learning.
Generation of firing cutout maps for missile launching systems that fire at low elevations usually involves time consuming surveying of surrounding areas. Shore and land-based environments change rapidly, and there is normally not enough time to re-survey the area. Additionally, launching systems are often not located close enough to the system sensors to develop firing cutout maps that reflect the exact relationship of close-in objects to the launching system. Also, current systems in general do not support fire on the run capabilities. Firing cut-out maps need to be produced rapidly and safely to reflect the changing scene that launching systems face.
In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. Some embodiments are illustrated by way of example, and not limitation, in the figures of the accompanying drawings.
An embodiment is a method for using machine learning to aid an operator in quickly constructing a firing cutout map that meets safety requirements. While current efforts with machine learning are used to identify targets (e.g., Automatic Target Recognition (ATR)), the current embodiment identifies all structures and objects that should not be targeted.
An embodiment uses a standalone piece of equipment (which can be referred to as the scene machine (SM)) that is co-located with a missile launching system. The embodiment includes two or more image sensing devices such as two high quality mid-wave infra-red (IR) cameras, a touchscreen operator interface, a processor housing the necessary algorithms, and multi-media writing capability. When the scene machine is first deployed in a unique operating environment, for example the Persian Gulf off-shore oil fields, an image collection campaign is conducted to “teach” the scene machine's image classification software which types of objects are to be protected (i.e., included in a no-fire zone). For example, in the oil field environment, the scene machine would be taught that oil platforms, venting stacks, and large docked ships are objects to be included in the no fire zone. After the learning is completed, the image classification software is loaded in each scene machine that is associated with the launching system.
An operator then initializes a scan of the scene in front of the launching system using the IR cameras. The scene machine uses the machine-learned image classification to identify and display all the objects it considers to be non-targets. Having two or more IR cameras or other image sensing devices permits the scene machine to provide range estimates. Using the range estimates, an observed object is not included in the map if it is beyond the range where it is in danger of missile contact. Using the touchscreen, the operator can deselect any object that the operator does not want to include in the cut-out map.
The use of machine learning increases the safety of firing cut out map generation as the operator alone may miss an object by human error or failure to recognize it. However, allowing the operator to de-select an object keeps all possible objects to be protected in the map unless the operator makes a conscious decision to remove it.
The scene machine then generates a firing cut out map that meets all the requirements of the launching system. Such requirements could be additional space around the object for safety margins or system specific rules (e.g., the random access memory (RAM) of the launching system requires minimum zone widths, and dimensions must be quantized).
Once the firing cut out map is finalized, it can either be sent directly to the launching system via an Ethernet connection or written to whatever media the launching system uses (for example, a RAM of the launching system can store maps in an EEPROM that resides on a main processor board and is removable for re-programming).
The above-described process of generating firing cut out maps is illustrated in graphic form in
Referring now to
At 120, the system receives from the scan an image of the environment. In an embodiment, the image is an infra-red (IR) image (122). At 130, the system identifies any non-targets in the image using the trained machine learning algorithm. As indicated at 132, these non-targets were identified based on distances, azimuth angles, and elevation angles of the non-targets relative to the system.
At 140, the system generates a firing cut out map for overlaying on the image of the environment based on the identified non-targets in the image of the environment. At 142, the firing cut out map is transmitted to a missile launching system or a computer storage medium associated with the missile launching system. An example of such a firing cut out map is illustrated in
At 150, the system uses the firing cut out map to refrain from initiating a missile launch directed at the non-targets. In a missile launch system, there are many sub-systems that contribute to fire and/or no-fire decisions, and the firing cut out map is just one of those sub-systems.
Example computing platform 300 includes at least one processor 302 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both, processor cores, compute nodes, etc.), a main memory 304 and a static memory 306, which communicate with each other via a link 308 (e.g., bus). The computing platform 300 may further include a video display unit 310, input devices 312 (e.g., a keyboard, camera, microphone), and a user interface (UI) navigation device 314 (e.g., mouse, touchscreen). The computing platform 300 may additionally include a storage device 316 (e.g., a drive unit), a signal generation device 318 (e.g., a speaker), and a RF-environment interface device (RFEID) 320.
The storage device 316 includes a non-transitory machine-readable medium 322 on which is stored one or more sets of data structures and instructions 324 (e.g., software) embodying or utilized by any one or more of the methodologies or functions described herein. The instructions 324 may also reside, completely or at least partially, within the main memory 304, static memory 306, and/or within the processor 302 during execution thereof by the computing platform 300, with the main memory 304, static memory 306, and the processor 302 also constituting machine-readable media.
While the machine-readable medium 322 is illustrated in an example embodiment to be a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more instructions 324. The term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media. Specific examples of machine-readable media include non-volatile memory, including but not limited to, by way of example, semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
RFEID 320 includes radio receiver circuitry, along with analog-to-digital conversion circuitry, and interface circuitry to communicate via link 308 according to various embodiments. Various form factors are contemplated for RFEID 320. For instance, RFEID may be in the form of a wideband radio receiver, or scanning radio receiver, that interfaces with processor 302 via link 308. In one example, link 308 includes a PCI Express (PCIe) bus, including a slot into which the NIC form-factor may removably engage. In another embodiment, RFEID 320 includes circuitry laid out on a motherboard together with local link circuitry, processor interface circuitry, other input/output circuitry, memory circuitry, storage device and peripheral controller circuitry, and the like. In another embodiment, RFEID 320 is a peripheral that interfaces with link 308 via a peripheral input/output port such as a universal serial bus (USB) port. RFEID 320 receives RF emissions over wireless transmission medium 326. RFEID 320 may be constructed to receive RADAR signaling, radio communications signaling, unintentional emissions, or some combination of such emissions.
The above detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments that may be practiced. These embodiments are also referred to herein as “examples.” Such examples may include elements in addition to those shown or described. However, also contemplated are examples that include the elements shown or described. Moreover, also contemplated are examples using any combination or permutation of those elements shown or described (or one or more aspects thereof), either with respect to a particular example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.
Publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated reference(s) are supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.
In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to suggest a numerical order for their objects.
The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with others. Other embodiments may be used, such as by one of ordinary skill in the art upon reviewing the above description. The Abstract is to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the above Detailed Description, various features may be grouped together to streamline the disclosure. However, the claims may not set forth every feature disclosed herein as embodiments may feature a subset of said features. Further, embodiments may include fewer features than those disclosed in a particular example. Thus, the following claims are hereby incorporated into the Detailed Description, with a claim standing on its own as a separate embodiment. The scope of the embodiments disclosed herein is to be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
