Shared Memory Interface for Gas Turbine Engine Performance Programs
This is a recommended practice for an interface to supplier simulations that utilize traditional interprocess communication (IPC) methods of shared memory and semaphore communications. These IPC methods are fairly standard practice in the computer science world, that allow for communication by separate processes running on a computer without any common runtime requirements of each process being run. So 32bit applications can talk with 64 bit applications as well as any other compiler or runtime dependency being needed by the calling program to interface with the called system. This also allows the calling program and the called program to be run on separate CPUs to allow parallel execution of the called program as well as multiple instances of the called program to execute all on separate processors. Also other 3rd party applications would be able to interact with this common IPC interface allowing an interface where no compilation or integration of either parties libraries or code is required. This ARP provides definition of the shared memory space and interactive IPC functions to enable the interaction between these separate applications.
Rationale: Shared Memory is a common methodology in computer science to interface between two separate executables. This ARP Proposes a general approach for creating a standard interface and interactions to allow this type of interface to be easily utilized for real time model execution, standardized 3rd party interfaces or multiple model executions in the same computing space.