How to run two simulink models in parallel?

Hello everyone,

I am working with a 3DOF model of a commercial airplane in MatLab/Simulink. This model contains the state propagator and the autopilot. I would like to train an RL agent using the outputs of this model. The problem is that the environment for the RL application contains an exact copy of the state propagator of the 3DOF model. How can I use two of these systems without conflicting with the goto/from blocks and the signal name?

Thank you

Answer 1

[Ashutosh Thakur]

Hi Leonardo,

When working with multiple instances of the same subsystem, you may encounter conflicts with signal naming and block usage. Here are some strategies to address these issues:

• Model References: Model references allow you to include the same model multiple times within a parent model without any conflicts. You can convert the conflicting subsystems to model references to have them operate independently. For more information, refer to the following documentation: https://www.mathworks.com/help/simulink/model-reference.html.
• Data Store Memory block: Instead of using Goto/From blocks, consider using Data Store Memory, Data Store Read, and Data Store Write blocks to handle shared data. This approach prevents conflicts with shared data. For more details, refer to the following link: https://www.mathworks.com/help/simulink/slref/datastorememory.html.
• Parallel Simulations: Different models can be simulated in parallel using the parsim function. You can execute parsim in Normal mode as well as Rapid Acceleration mode. Examples and further details can be found here: https://www.mathworks.com/help/simulink/slref/parsim.html.
• Bus Signals: You can group different signals into a single bus signal to reduce the number of individual signals, which can help avoid conflicts with signal naming. More information can be found here: https://www.mathworks.com/help/simulink/slref/simulink-bus-signals.html.

I hope that the above-mentioned strategies helps you!

[Leonardo Molino]

Hi @Ashutosh Thakur, thanks for answering! So far I was working with "Goto visibility tag"; basically, I am changing the tag visibility from "global" to "scoped", leaving unchanged the "local" ones. In your opinion, could this strategy also work?