Hidayet T Simsek

20110078652, Mar 31, 2011

Sep 30, 2010

12/895209

Ramamurthy MANI - Wayland MA, US
Katalin Maria POPOVICI - Natick MA, US
Hidayet Tunc SIMSEK - Newton MA, US
Benjamin Charles MARTIN - Natick MA, US
John Edward CIOLFI - Wellesley MA, US

THE MATHWORKS, INC. - Natick MA

G06F 9/44

717105

Exemplary embodiments allow executable graphical models, such as block diagram models, to be graphically partitioned for execution on concurrent computing resources. Embodiments allow model components to be grouped into subtasks that are affiliated with tasks associated with concurrent computing resources. Tasks and sub graphs can be mapped to concurrent computing resources according to characteristics, such as sample time, solver type, etc. Embodiments further allow mappings to be visually indicated to a user via various display techniques including color, text, icons, shading, grouping of identifiers, etc. Concurrently executing portions of a model allows model results to be obtained faster than can be obtained when models are executed on a single computing resource, such as a single processor.

20110296435, Dec 1, 2011

May 27, 2011

13/117531

Hidayet Tunc Simsek - Newton MA, US
Vijay Raghavan - Brookline MA, US
Ramamurthy Mani - Wayland MA, US

THE MATHWORKS, INC. - Natick MA

G06F 3/00
G06F 9/44

719313

A system and method may generate executable block diagrams in which at least some of the blocks run in accordance with message-based execution semantics. A message may include an input data payload that does not change over time, and the message may persist for only a determined time interval during execution of block diagram. A message-based execution engine may control execution of message-based blocks in which a source block may generate a message at a particular point in time, the message may be sent to one or more destination blocks triggering execution of those blocks, and the message may be destroyed on or after a determined time interval. Other execution domains, such as a time-based or state-based execution domain, may be provided, and the system may implement a hybrid execution model. A verification engine may provide one or more tools for evaluating and verifying operation of message-based blocks. The verification engine may support one or more verification blocks that may be added to the block diagram and associated with the diagram's message-based blocks. The verification blocks may capture and present messages exchanged among the message-based blocks. The verification blocks may also specify an expected interaction of messages, and determine whether the actual messages are equivalent to the expected interaction. If not, the verification block may perform one or more predefined actions, such as suspending further execution of the block diagram.

8359304, Jan 22, 2013

Jul 18, 2011

13/185243

Pieter J. Mosterman - Framingham MA, US
Farid Antoine Abi-Zeid - Natick MA, US
Hidayet Tunc Simsek - Newton MA, US
Claudia Gaudagnini Wey - Wayland MA, US
Mojdeh Shakeri - Southborough MA, US
Jay Ryan Torgerson - Hopkinton MA, US

The MathWorks, Inc. - Natick MA

G06F 7/00
G06F 17/30

707706, 707713, 707723, 707731, 707749, 707769

A system may receive a model, extract information from the model, form a group of tags using the extracted information, and associate the group of tags with the model. The system may further receive a search query including one or more sequences of characters and determine whether to provide the model in a list of models created for the search query, based on the one or more sequences of characters and the group of tags.

20190370028, Dec 5, 2019

Jun 1, 2018

15/995495

- Natick MA, US
Sankalp S. MODI - Acton MA, US
Peter S. SZPAK - Newton MA, US
Hidayet T. Simsek - Newton MA, US

G06F 9/451

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

20150331978, Nov 19, 2015

May 15, 2015

14/713508

- Natick MA, US
Srinath AVADHANULA - Sudbury MA, US
Aravind PILLARISETTI - Hopkinton MA, US
Nirmal K. GUNASEELAN - Wayland MA, US
Peter S. SZPAK - Newton MA, US
Hidayet T. SIMSEK - Newton MA, US

G06F 17/50
G06F 17/15

A device may generate code for a caller element of a first graphical model and a called element of a second graphical model by generating a first function and a second function. The first function may represent an interface between the caller element and the called element. The first function may include a first input argument corresponding to an input variable and a first output argument corresponding to an output variable. The second function may represent an underlying function of the called element. The underlying function may include the input variable passed from the caller element and the output variable. The underlying function may further include an internal input variable and an internal output variable. The second function may include second input arguments corresponding to the input variable and the internal input variable, and may include second output arguments corresponding to the output variable and the internal output variables.

20150331979, Nov 19, 2015

May 15, 2015

14/713527

- Natick MA, US
Srinath AVADHANULA - Sudbury MA, US
Aravind PILLARISETTI - Hopkinton MA, US
Nirmal K. GUNASEELAN - Wayland MA, US
Peter S. SZPAK - Newton MA, US
Hidayet T. SIMSEK - Newton MA, US

G06F 17/50
G06F 17/15

A device may receive function information that describes a caller element that calls a called element that is separate from the caller element. The function information may identify a name or reference of the called element, a passed input, and a passed output. The passed input may be provided by the caller element to the called element, and the passed output may be received by the caller element from the called element. The caller element may be associated with a caller model, and the called element may be associated with a called model. The device may identify the called element, and may execute the caller element in a simulation environment. Execution of the caller element may cause execution of the called element without causing execution of an entirety of the called model. The device may receive the passed output from the called element based on executing the called element.