The Mathworks, Inc.

Peter S Szpak

Matthew J Englehart

Xiaocang Lin

Biao Yu

Mirko Conrad

Aravind Pillarisetti

Pieter Johannes Mosterman

Hidayet Tunc Simsek

Yuan Cao

Ebrahim Mehran Mestchian

Robert Olson Aberg

James E Carrick

Alongkrit Chutinan

Jesung Kim

Thomas Joseph Erkkinen

Paulo J Pacheco

Christian Robl

Martin Orehek

Jun Yan

Appa Rao Nirakh

Murali K Yeddanapudi

Vijay Raghavan

Srinath Avadhanula

Andrew C Bartlett

Arwen M Warlock

Yang Feng

Joel Thornton

Hongbo Yang

Nirmal K Gunaseelan

Jaya Shankar

Jan Sjodin

Jay Ryan Torgerson

David A Foti

Vijaya Raghavan

Michael David Tocci

Andrew C Grace

Darel Allen Linebarger

Paul Jackson

Sankalp Sandeep Modi

Yao Ren

Paul F Kinnucan

Daniel Forrest Higgins

Shailesh Shashikant Nirgudkar

Jayaprabha Shankar

Fazil Peermohammed

Peter Mott

Alexander C Feinman

Qingmin Shi

David William Hoadley

Stefan David

Roy Mathew

Patrick Munier

Alexandre De Barros

Suman Kumar Kondreddy

Emmanuel Roy

Bernd J Kanamueller

Dekun Pei

Jianhao Du

Vivek Bhownani

Antoine Requet

Alexander Feinman

Nirmal Gunaseelan

Hidayet T Simsek

Systems and methods may generate code, for a model, with one or more service access points generated and at locations in the code based on an analysis of model constraints and deployment specifications (e.g., RTE specifications or OS specifications). The systems and methods may analyze the model and identify a functionality that needs an RTE service. The system and methods may receive deployment specifications. The systems and methods may generate code for the model, where an analysis of model constraints and the deployment specifications determine which service access points are generated and where in the code the service access points are located. In an embodiment, the code may be executed by different RTEs. In an embodiment, the systems and methods may determine, based on the analysis of the model constraints and the deployment specification, one or more admissible implementations for an RTE service that may be implemented in different ways.

Systems and methods for generating service access points for RTE services in code or other RTE service information for use with the code

Systems and methods may aggregate and organize implicit and explicit initialization, reset, and termination operations defined throughout the hierarchy of an executable. The systems and methods may analyze the model and identify implicit and explicit initialization, reset, and termination operations defined at various hierarchical levels. The systems and methods may aggregate the implicit and explicit initialization, reset, and termination operations into an initialize callable unit, a reset callable unit, and a termination callable unit. The systems and methods may apply optimizations to the callable units, and resolve conflicts. The systems and methods may define a single entry point for each of the initialize, reset, and termination callable units.

Systems and methods for aggregating implicit and explicit event code of executable models

Systems and methods decouple model components from a model execution style for which the model components are created, and the model components may be utilized in parent models having different execution styles. A model component may be partitioned into executable entities, and the entry points of the executable entities and their call styles may be identified. An adaptation layer that includes access points for the entry points may be constructed. The model component, including the adaptation layer, may be included in the model, and connection elements of the parent model may be connected to the access points of the adaptation layer. The execution call styles associated with the connection elements of the parent model may be bound to the execution call styles of the entry points as originally designed. The adaptation layer may manage translation of call styles and may coordinate scheduling of data communication with the model component.

Systems and methods for extracting adjustable attributes of model components

Processing external code includes: parsing the external code to identify a first semantic entity, mapping the first semantic entity to a second semantic entity, the first semantic entity comprising a first set of one or more specified attributes and the second semantic entity comprising a second set of one or more attributes that are capable of being specified, determining that a first attribute of the second set of one or more attributes does not have a corresponding specified attribute within the first set of one or more specified attributes, determining available information for specifying the first attribute of the second set of one or more attributes, and storing the second semantic entity in association with the first attribute of the second set of one or more attributes specified based on user selection or specifying the first attribute in response to available information provided to a user interface system.

External code integrations within a computing environment

A first request is received for one or more service interface specifications. The first request includes information about one or more model element interface specifications usable for identifying the service interface specifications. The model element interface specifications are part of or extracted from one or more executable model elements of an executable graphical model. The service interface specifications correspond to respective services that include features complying with the model element interface specifications and are associated with information necessary for implementing semantics of the model elements. The information about the model element interface specifications is analyzed, comprising evaluating semantics of the executable model elements within the executable graphical model. The service interface specifications are identified based on the analyzing. Information is provided representing the identified service interface specifications for display and selection. A selection of at least one of the identified service interface specifications is stored after the selection is made.

Managing discovery and selection of service interface specifications

Systems and methods automatically detect violations of coding rules of a coding standard in computer programming code. The systems and methods may mark the locations in the code where the violations are found. The coding rules may be mapped to code verification checks that check for undesired runtime behavior in the code. The systems and methods may identify the code verification check mapped to a given violation detected in the code. The systems and methods may apply that check to the code. If the check proves that the undesired runtime behavior will not occur, the violation may be marked as justified. If the check proves that the undesired runtime behavior will occur, the violation may be marked as not justified.

Systems and methods for analyzing violations of coding rules

In an embodiment, a modeling component generated in a first modeling environment can be implemented in a second modeling environment. The modeling component is executed in the first modeling environment. A first behavior of the modeling component in the first modeling environment is obtained based on the executing. The modeling component is then executed in the second modeling environment. A second behavior of the modeling component in the second modeling environment is obtained based on the executing the modeling component in the second modeling environment. The first behavior is compared to the second behavior. Based on the comparing, it is verified that the second behavior of the modeling component complies with one or more modeling requirements of the second modeling environment. The second behavior of the modeling component may be implemented in the second modeling environment.

Reusable component in a modeling environment

A system and method automatically ensures consistency among a design model and one or more test models that test the design model. The system may include a broker adapted to construct an interface specification. The interface specification identifies the interface of the design model, e.g., its external inputs, external outputs, and initialization states. It may also identify the outputs, inputs, and initialization setting objects of the test models. Proposed changes to the design model's interface may be captured by the broker, and applied to the design model and to the test models atomically. Proposed changes to a given test model that implicate the design model's interface also may be captured, and applied to the given test model, the other test models, and the design model atomically. Default behaviors may be defined for applying the proposed changes to the other test models and the design model.

Self-testing graphical component algorithm specification

A method of specifying and configuring a causal relationship between the dynamics of a graphical model and the execution of components of the model is disclosed. Model component execution is tied to the occurrence of model events. Model events are first defined in the modeling environment. The occurrence of conditions in the model specified in the definition of the event causes the event to be 'posted'. Model components that have been associated with the occurrence of the event 'receive' the notice of the posting of the event and then execute. Random components within a subsystem may be designated to execute upon the occurrence of an event, as may non-contiguous components within a model. The association between model events and component execution may be specified without drawing graphical indicators connecting components in the view of the model.

System and method for scheduling the execution of model components using model events

A computer readable medium including executable instructions that when executed perform a method for validating an optimization in generated code using an executable constraints document is provided. The medium can include instructions for relating an assumption to the optimization during code generation. The medium can include instructions for generating the executable constraints document during the code generation, the executable constraints document including information about the relating; and the medium can include instructions for executing the constraints document when the validating is performed, the validating including performing an operation based on a validation result produced by the validating, where the operation includes displaying the validation result to a user, storing the validation result, sending the validation result to a destination, or modifying the generated code.

Optimization identification

A device may receive a model for code generation. The device may determine to preserve continuity with a first generated code associated with the model. The device may receive, based on determining to preserve continuity, a first generation record associated with the first generated code. The first generation record may include information associated with generation of the first code. The device may generate second code based on the model and the first generation record. The device may create a second generation record based on the second generated code. The second generation record may include information associated with generation of the second code. The device may provide the second generated code.

Code continuity preservation during automatic code generation

A computing device may receive a request to create a link between a control mechanism of a human machine interface and an attribute of a model. The model, when executed, may simulate behavior of a system. The human machine interface may correspond to a physical object. The request may include information identifying the attribute and information identifying the control mechanism. The computing device may create a link between the control mechanism and the attribute based on receiving the request. The computing device may further observe the control mechanism in a spatial environment and detect that the control mechanism has changed based on observing the control mechanism. The computing device may modify a value, associated with the attribute, based on detecting that the control mechanism has changed and based on the link.

Generic human machine interface for a graphical model

Graphical programming or modeling environments in which a coding standard can be applied to graphical programs or models are disclosed. The present invention provides mechanisms for applying the coding standard to graphical programs/models in the graphical programming/modeling environments. The mechanisms may detect violations of the coding standard in the graphical model and report such violations to the users. The mechanisms may automatically correct the graphical model to remove the violations from the graphical model. The mechanisms may also automatically avoid the violations in the simulation and/or code generation of the graphical model.

Applying coding standards in graphical programming environments

Growing community of inventors

Newton, MA, United States of America

Peter S Szpak