Search Results

The process of developing, parameterizing, validating, and maintaining models occurs within a wide variety of tools, and requires significant time and resources. To maximize model utilization, models are often shared between various toolsets and experts. Model integration is typically divided into two categories: model exchange and model co-simulation. Of these two categories, model co-simulation is typically regarded as the more complex and difficult to implement. Co-Simulation provides the ability to integrate models between different toolsets or incompatible versions of the same software. Additionally, it provides the capabilities for real-time simulations and hardware-in-the-loop test scenarios. This paper reviews some of the common co-simulation data communication methods including pipes and file input/output. The differences between serial and parallel, aka synchronous and asynchronous, communication patterns are also discussed.

The process of developing, parameterizing, validating, and maintaining models occurs within a wide variety of tools, and requires significant time and resources. To maximize model utilization, models are often shared between various toolsets and experts. One common example is sharing aircraft engine models with airframers. The functionality of a given model may be utilized and shared with a secondary model, or multiple models may run collaboratively through co-simulation. There are many technical challenges associated with model sharing and co-simulation. For example, data communication between models and tools must be accurate and reliable, and the model usage must be well-documented and perspicuous for a user. This requires clear communication and understanding between computer scientists and engineers. Most often, models are developed by engineers, whereas the tools used to share the models are developed by computer scientists.