Hybrid Coupled Model with Coordinator Functionalities

stored in DEVS_PATH/00-simulator/hybridcoupled.p

Is provided as p-code.

Contents

Based on modified parallel DEVS algorithms (Zeigler, Schwatinski) and wrapper extension (Deatcu).
User defined coupled models can be created as instances of this class directly or can be derived from it alternatively. For initialization, the modeler has to define input and output portnames. Components and coupling information are defined after instantiation via the methods *addcomponents(obj,comps)*, *set_Zid(obj,Zid)* and *set_CZid(obj,CZid)*.
C. Deatcu 2016

Description

Class definition file for a hybrid coupled DEVS model and it's associated coordinator. Extends the discrete associated coordinator and model.

constructor call: obj = hybridcoupled(name,xportnames,yportnames), where xportnames and yportnames are optional

Superclass

coupled

Inherited properties

eventlist = [a,b,c;...]
a - time for next transition
b - {1,2} | 1 if atomic DEVS, 2 if coupled DEVS
c - index for eventlist (position in Da or Dc)

Properties

Class methods

Methods to Define Components and Couplings

Set Methods for Flags

Z_MSG

function [obj,aSimObj,gstatvec,gevveclen,outoffs]=z_msg(obj,gt,soff,eoff)

WHAT HAPPENS IN Z_MSG?

Z2_MSG

function obj=z2_msg(obj,gt,ioffs)
WHAT HAPPENS IN Z2_MSG?

SE_MSG

function [obj,event_flag]=se_msg(obj,te,ye,ie)

WHAT HAPPENS IN SE_MSG?

Functions for displaying the coupled objects

These functions can be called to get some information during or after simulation.





DEVS Tbx Home      Examples      Modelbase           << Back