getPropertyValue - Get value of architecture property - MATLAB (original) (raw)

Main Content

Get value of architecture property

Syntax

Description

[value](#mw%5Fe840050f-e912-4281-a5d6-e1f17e06d70c) = getPropertyValue([element](#mw%5F70098cab-df92-4112-9fb8-8cf6c00f5857%5Fsep%5Fmw%5F6d55457b-71a8-4e02-8988-eb9cdd468568),[property](#mw%5Fb5117393-df34-409b-b2cb-4b87937b7d81)) gets the non-evaluated property value for the provided architectural element.

example

Examples

collapse all

Create a profile, add a component stereotype, and add a property with a default value.

profile = systemcomposer.profile.Profile.createProfile("LatencyProfile"); stereotype = addStereotype(profile,"electricalComponent",AppliesTo="Component"); stereotype.addProperty("latency",Type="double",DefaultValue="10");

Create a model with a component called Component.

model = systemcomposer.createModel("archModel"); systemcomposer.openModel("archModel"); arch = get(model,"Architecture"); comp = addComponent(arch,"Component");

Apply the profile to the model and apply the stereotype to the component. Open theProfile Editor.

model.applyProfile("LatencyProfile") comp.applyStereotype("LatencyProfile.electricalComponent") systemcomposer.profile.editor(profile)

Get the property value.

value = getPropertyValue(comp,"LatencyProfile.electricalComponent.latency")

Input Arguments

collapse all

Property name, specified as a character vector or string in the form"<profile>.<stereotype>.<property>".

Data Types: char | string

Output Arguments

collapse all

Property value, returned as a character vector.

Data Types: char

More About

collapse all

Term Definition Application More Information
Architecture A System Composer™ architecture represents a system of components and how they interface with each other structurally and behaviorally. Different types of architectures describe different aspects of systems. You can use views to visualize a subset of components in an architecture. You can define parameters on the architecture level using the Parameter Editor. Compose Architectures VisuallyAuthor Parameters in System Composer Using Parameter Editor
Root A root is at the top of an architecture hierarchy. A root architecture has a boundary defined by its architecture ports that surround the system of interest. The root architecture has a system boundary surrounding your architecture model. You can add architecture ports that define interfaces across the boundary. Compose Architectures Visually
Model A System Composer model is the file that contains architectural information, such as components, ports, connectors, interfaces, and behaviors. Perform operations on a model including extracting root-level architecture, applying profiles, linking interface data dictionaries, or generating instances from model architecture. A System Composer model is stored as an SLX file. Create Architecture Model with Interfaces and Requirement Links
Component A component is a replaceable part of a system that fulfills a clear function in the context of an architecture. A component defines an architectural element, such as a function, another system, hardware, software, or other conceptual entity. A component can also be a subsystem or subfunction. Represented as a block, a component is a part of an architecture model that can be separated into reusable artifacts. Transfer information between components with port interfaces using the Interface Editor, and parameters using the Parameter Editor. Compose Architectures Visually
Port A port is a node on a component or architecture that represents a point of interaction with its environment. A port permits the flow of information to and from other components or systems. Component ports are interaction points on the component to other components. Architecture ports are ports on the boundary of the system, whether the boundary is within a component or the overall architecture model. The root architecture has a boundary defined by its ports. Compose Architectures Visually
Connector Connectors are lines that provide connections between ports. Connectors describe how information flows between components or architectures. A connector allows two components to interact without defining the nature of the interaction. Set an interface on a port to define how the components interact. Compose Architectures Visually
Term Definition Application More Information
Physical subsystem A physical subsystem is a Simulink® subsystem with Simscape™ connections. A physical subsystem with Simscape connections uses a physical network approach suited for simulating systems with real physical components and represents a mathematical model. Implement Component Behavior Using Simscape
Physical port A physical port represents a Simscape physical modeling connector port called a Connection Port (Simscape). Use physical ports to connect components in an architecture model or to enable physical systems in a Simulink subsystem. Define Physical Ports on Component
Physical connector A physical connector can represent a nondirectional conserving connection of a specific physical domain. Connectors can also represent physical signals. Use physical connectors to connect physical components that represent features of a system to simulate mathematically. Architecture Model with Simscape Behavior for a DC Motor
Physical interface A physical interface defines the kind of information that flows through a physical port. The same interface can be assigned to multiple ports. A physical interface is a composite interface equivalent to a Simulink.ConnectionBus object that specifies a number of Simulink.ConnectionElement objects. Use a physical interface to bundle physical elements to describe a physical model using at least one physical domain. Specify Physical Interfaces on Ports
Physical element A physical element describes the decomposition of a physical interface. A physical element is equivalent to a Simulink.ConnectionElement object. Define the Type of a physical element as a physical domain to enable use of that domain in a physical model. Describe Component Behavior Using Simscape

Version History

Introduced in R2019a

See Also

Tools

Blocks

Objects

Functions

Topics