Скачать с ютуб Simulation Basics with Cameo Simulation Toolkit / Magic Model Analyst в хорошем качестве

Simulation Basics with Cameo Simulation Toolkit / Magic Model Analyst

www.STC.Arcfield.com ChatGPT Video Summary: In the "Simulation Basics with Cameo Simulation Toolkit / Magic Model Analyst" YouTube video, Brian Moberly from Strategic Technology Consulting provides an introduction to simulating models using Cameo Systems Modeler and the Cameo Simulation Toolkit. He covers the necessity of having the toolkit installed and licensed, setting up options for successful simulations, and the importance of simulation context. Brian also explains how to run simulations within a system block context, adding time events, dealing with parts of a system, and the significance of classifier behavior. Additionally, he discusses using accept event actions and opaque actions to capture data, managing levels of abstraction, and designing communication between parts of a system using proxy ports and connectors. Simulations bring models to life, allowing for the exploration of various SysML diagram types, including state machines and interaction behaviors. 00:00:00: Brian introduces the basics of simulations using Cameo Systems Modeler and the Cameo Simulation Toolkit, emphasizing its necessity for those new to simulation. He explains the importance of having the Cameo Simulation Toolkit installed and licensed and advises setting up certain options, such as initializing empty values to zero and checking the model before execution, to ensure successful simulations. He explains the concept of simulation context and its importance in providing access to value properties for the simulation to use. 00:05:00: Brian explains how to run simulations within a system block context. To do this, the system block must have a type and an instantiated value property. He also discusses the importance of object ids and how to instantiate reference properties. Brian introduces the concept of opaque actions and their usefulness in simulations for executing software scripts and accessing value properties. He demonstrates how to output engine rpm values to a signal for further use in the system. 00:10:00: Brian explains how to run a simulation using the Cameo Simulation Toolkit. Some value properties may not be instantiated because they have not been run with context. He demonstrates how to add a time event to the control flow and make it relative, allowing the simulation to wait for a certain amount of time before continuing. He discusses the concept of dealing with parts of a system, using an engine and a computer as examples. Brian explains that each part of the system is defined by a specific block, and running the simulation from that block will only instantiate and make visible that part. To instantiate and view all parts of the system, the simulation must be run from the system block itself. He mentions the importance of the classifier behavior, which is the main behavior associated with a system block. 00:15:00: Brian explains the concept of classifier behavior and its significance in the simulation process. Classifier behavior starts automatically when an activity or part property is instantiated. By default, the first behavior of an activity is set as the classifier behavior. Brian demonstrates how to change the classifier behavior to another behavior and move behaviors between parts in the containment tree. The simulation will start up the classifier behaviors of all part properties below the highest level context when run from that context. He introduces the concept of capturing data using an accept event action and setting the default property of the accept event action to "is un-marshal true" to parse out any properties of the signal. 00:20:00: Brian explains how to use an "accept event action" and "opaque action" in the simulation toolkit to capture data. He discusses what happens when multiple accept event actions exist in the same activity and how to use a "fork node" and "merge node" to handle this situation. Brian emphasizes the importance of managing levels of abstraction in the model and avoiding behaviors running at multiple levels of abstraction. The video demonstrates how to create a line of communication between parts of a system using an internal block diagram. 00:25:00: Brian explains how to designate communication between parts of a system using proxy ports and connectors. Proxy ports are recommended over full ports for simulation purposes, and they can be named for easy identification. To send a signal from one part of the system to another, Brian suggests right-clicking on the "send signal action" and designating the on port. The signal will then traverse the connector to its destination. Brian emphasizes the importance of simulations in bringing models to life and the ability to simulate various SysML diagram types simultaneously. State machines are useful for inhibiting certain behaviors, while interaction behaviors, represented in sequence diagrams, are valuable simulation subjects.