-
Notifications
You must be signed in to change notification settings - Fork 6
Home
Note: The wiki is currently under development. Please come back later for the completed support wiki
The Generic Software Architecture for Prognostics (GSAP) is a framework for applying prognostics. It makes applying prognostics more efficient by implementing many of the common elements across prognostic applications. The standard interface of the GSAP framework enables adaptability of prognostic algorithms and models to systems of interest.
The GSAP framework is used through the creation of communicators, prognosers, or models (the deployment layer). The elements of the deployment layer plug into the framework and use the tools of the support layer. These elements are described further below:
-
Models: Models are a method of representing the behavior of a component. A common way of performing prognostics is using a model that describes both the healthy and damaged behavior of the components. The ModelBasedPrognoser class uses the models to perform prognostics.
-
Prognosers: These are the core of the GSAP system. The prognosers contain the fundamental logic for performing prognostics. A new prognoser is created to support a new method for performing prognostics. Many prognostics systems follow a common model-based structure. Those systems do not require the creation of a new prognoser, only the creation of a new model that will be used by the ModelBasedPrognoser class. For more information on this see the section Extending.
-
Communicators: Communicators are used to communicate data with the outside world. These function as interfaces with various data sources and sinks. Some examples could be a playback agent that reads from a file, a GUI for displaying prognostic results, an automated report generator, or a client that connects into a network messaging system. These systems can receive data which will be used by prognosers or communicate the results with operators.
Each of these components is configured through the use of configuration files. This allows for a GSAP deployment to be configured to a new configuration or system without any software changes.
GSAP was created by the NASA Ames Research Center Diagnostics and Prognostics Group
This wiki aims to provide complete documentation and examples of how to use GSAP. This wiki is still very much a work in progress. If there is a section that you feel needs work, please open an issue describing what you would like to see.