FLITES

POSTED: May 11, 2023

The Fast Line-of-sight Imagery for Targets and Exhaust-plume Signatures (FLITES) software provides high fidelity scene generation capabilities for a multitude of applications, e.g., sensor algorithm development or Hardware-in-the-loop (HWIL) analysis and testing. FLITES simulates the physical world in the IR, UV, and Visual spectrum by calculating signature phenomenological effects (self-emission, sky-shine, earthshine, solar illumination, etc.) and creating time-sequenced radiance images from the sensor’s perspective. All signature processing algorithms are performed using Graphics Processing Units (GPUs).

FLITES generates radiance images for data analysis, closed-loop digital simulations, real-time HWIL testing, and visualization studies. Images can be saved to a hard drive for playback or projected/injected to test a sensor. All of this is potentially done in “real-time,” which refers to the speed FLITES can achieve relative to the fidelity of the phenomena contained in the scenario. Simple polygon scenes can reach over 10,000 fps while more complex scenes can be limited to 10-30 fps.

As previously mentioned, FLITES works by leveraging the computational capability of a GPU through both OpenGL and the Compute Unified Device Architecture (CUDA) NVIDIA libraries. Due to the CUDA capability, an NVIDIA GPU is required to fully realize FLITES capabilities. There are future-plans to enable FLITES to work not only on non-NVIDIA GPUs but on CPUs as well.

FLITES is designed to provide large levels of flexibility for the end-user while allowing a diverse set of use-cases to be modeled. As such, FLITES is primarily designed as an Application Programming Interface (API) that can easily be integrated into large scale simulations or connected to separate specialized software to perform tasks like physics-based motion controls. FLITES is designed with a plugin architecture so that the end-user can develop plugins to solve custom problems or implement unique features. These plugins can also be used to integrate other software packages into FLITES.

Input Output Details Distribution

Input

FLITES required inputs consist of definitions for the various object types to be rendered into a scenes (hardbody meshes, plumes, and backgrounds). Other definitions include sensor bandpass, object/viewer kinematics, optical properties (hardbody and plume) in the EO/IR bandwidth of choice, and any other custom data leveraged by the required plugins. An input deck is utilized for each simulation to control the scenario through capabilities like object placement, object motion, sensor bands, backgrounds, viewing frustum, and image size. The API can be leveraged as well to override the input deck in order to provide more flexibility for scenario construction. The 3D models of any mesh objects to be rendered into the scene are stored in a custom format called an fpgn file. Documentation exists within FLITES to convert common 3D object formats like Wavefront (obj) into this format as well as other tools to convert CFD plume flowfields into FLITES applicable models.

Output

FLITES outputs its images to either a display through a monitor (or projector) or send its GPU-generated images back to the CPU to support closed-loop digital simulations or image archival operations. The API can also be leveraged to send the images to algorithms for interpretation through shared memory. Images can be output in multiple formats and custom formats can be created through the plugin mechanism if required. The second major output from FLITES is log files. The contents of these log files can vary depending on the type of object or module (mesh, plume, dynamics, etc.) being logged. This can be used throughout the simulation process to help set up scenarios and record various internal data calculated during a simulation. Finally, the spatially resolved signature FLITES generates can be down sampled into equivalent point source signatures using an energy-conservative algorithm.

Details

Distribution

Software Deliverable contains three installers, Windows, Linux-x86, Linux-Arm

Installers provide documentation, binaries, API, sample testcases for binaries and API, core plugins, and dependencies

Software: DISTRIBUTION STATEMENT F. Further dissemination only as directed by AFRL/RWWG, 101 West Eglin Blvd., Suite 233, Eglin Air Force Base, FL 32542-6810, April 2011, or higher DoD authority.

Documentation: DISTRIBUTION STATEMENT D. Distribution authorized to Department of Defense and US DoD contractors only: Critical Technology; April 2011. Other requests shall be referred to AFRL/RWWG, 101 West Eglin Blvd., Suite 233, Eglin Air Force Base, FL 32542-6810.

All documentation and software are ITAR, Export Controlled per warning below.

WARNING− This media contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.