Main Content

hasStereotype

Find if element has stereotype applied

Since R2021a

collapse all in page

    Syntax

    result = hasStereotype(element,stereotype)

    Description

    result = hasStereotype(element,stereotype) returns true if the stereotype stereotype has been applied on the model element element.

    example

    Examples

    collapse all

    Create a model with a component.

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

    Create a profile with a stereotype and properties, open the Profile Editor, then apply the profile to the model.

    profile = systemcomposer.profile.Profile.createProfile("LatencyProfile");
latencybase = profile.addStereotype("LatencyBase");
latencybase.addProperty("latency",Type="double");
latencybase.addProperty("dataRate",Type="double",DefaultValue="10");
systemcomposer.profile.editor(profile)
model.applyProfile("LatencyProfile");

    Apply the stereotype to the component. Find if the stereotypes are applied on the component.

    comp.applyStereotype("LatencyProfile.LatencyBase");
result = hasStereotype(comp,"LatencyProfile.LatencyBase")
    result =

  logical

   1

    Input Arguments

    collapse all

    Architectural element, specified as one these objects:

    Stereotype, specified as a character vector or string in the form "<profile>.<stereotype>" or a systemcomposer.profile.Stereotype object.

    Data Types: char | string

    Output Arguments

    collapse all

    Query result, returned as 1 (true) or 0 (false).

    Data Types: logical

    More About

    collapse all

    Definitions

    TermDefinitionApplicationMore 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.
    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:

    • Extract root-level architecture.

    • Apply profiles.

    • Link interface data dictionaries.

    • Generate 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:

    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

    TermDefinitionApplicationMore Information
    stereotype

    Stereotypes provide a mechanism to extend the core language elements and add domain-specific metadata.

    Apply stereotypes to core element types. An element can have multiple stereotypes. Stereotypes allow you to style different elements. Stereotypes provide elements with a common set of properties, such as mass, cost, and power.
    property

    A property is a field in a stereotype. You can specify property values for each element to which the stereotype is applied.

    Use properties to store quantitative characteristics, such as weight or speed, that are associated with a model element. Properties can also be descriptive or represent a status. You can view and edit the properties of each element in the architecture model using the Property Inspector. For more information, see Use Property Inspector in System Composer.
    profile

    A profile is a package of stereotypes.

    You can use profiles to create a domain of specialized element types. Author profiles and apply profiles to a model using the Profile Editor. You can store stereotypes for a project in one or several profiles. When you save profiles, they are stored in XML files.

    TermDefinitionApplicationMore Information
    interface data dictionary

    An interface data dictionary is a consolidated list of interfaces and value types in an architecture and where you use them in the architecture.

    You can save local interfaces on a System Composer model in an interface data dictionary using the Interface Editor. You can reuse data dictionaries between models that need to use a given set of interfaces, elements, and value types. Data dictionaries that you link to models are stored in separate SLDD files.
    data interface

    A data interface defines the kind of information that flows through a port. The same interface can be assigned to multiple ports. A data interface can be composite, meaning that it can include data elements that describe the properties of an interface signal.

    Data interfaces represent the information that is shared through a connector and enters or exits a component through a port. Use the Interface Editor to create and manage data interfaces and data elements and store them in an interface data dictionary for reuse between models.
    data element

    A data element describes a portion of an interface, such as a communication message, a calculated or measured parameter, or other decomposition of that interface.

    Data interfaces are decomposed into data elements:

    • Pins or wires in a connector or harness.

    • Messages transmitted across a bus.

    • Data structures shared between components.
    value type

    A value type can be used as a port interface to define the atomic piece of data that flows through that port and has a top-level type, dimension, unit, complexity, minimum, maximum, and description.

    You can also assign the type of data elements in data interfaces to value types. Add value types to data dictionaries using the Interface Editor so that you can reuse the value types as interfaces or data elements.

    		Create Value Types as Interfaces
    owned interface

    An owned interface is an interface that is local to a specific port and not shared in a data dictionary or the model dictionary.

    Create an owned interface to represent a value type or data interface that is local to a port.

    		Define Owned Interfaces Local to Ports
    adapter

    An adapter connects two components with incompatible port interfaces by mapping between the two interfaces. An adapter can act as a unit delay, rate transition, or merge. You can also use an adapter for bus creation. Use the Adapter block to implement an adapter.

    With an adapter, you can perform functions on the Interface Adapter dialog box:

    • Create and edit mappings between input and output interfaces.

    • Apply an interface conversion UnitDelay to break an algebraic loop.

    • Apply an interface conversion RateTransition to reconcile different sample time rates for reference models.

    • Apply an interface conversion Merge to merge two or more message or signal lines.

    • When output interfaces are undefined, you can use input interfaces in bus creation mode to author owned output interfaces.

    TermDefinitionApplicationMore 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 R2021a

    See Also

    Tools

    Blocks

    Objects

    Functions

    Topics