|
1
|
<?xml version="1.0" standalone="no"?>
|
|
2
|
<!DOCTYPE entity PUBLIC "-//UC Berkeley//DTD MoML 1//EN"
|
|
3
|
"http://ptolemy.eecs.berkeley.edu/xml/dtd/MoML_1.dtd">
|
|
4
|
<entity name="test-portparameter" class="ptolemy.actor.TypedCompositeActor">
|
|
5
|
<property name="_createdBy" class="ptolemy.kernel.attributes.VersionAttribute" value="7.1.devel">
|
|
6
|
</property>
|
|
7
|
<property name="_windowProperties" class="ptolemy.actor.gui.WindowPropertiesAttribute" value="{bounds={261, 125, 877, 800}, maximized=false}">
|
|
8
|
</property>
|
|
9
|
<property name="_vergilSize" class="ptolemy.actor.gui.SizeAttribute" value="[600, 659]">
|
|
10
|
</property>
|
|
11
|
<property name="_vergilZoomFactor" class="ptolemy.data.expr.ExpertParameter" value="1.0">
|
|
12
|
</property>
|
|
13
|
<property name="_vergilCenter" class="ptolemy.data.expr.ExpertParameter" value="{300.0, 329.5}">
|
|
14
|
</property>
|
|
15
|
<property name="DDF Director" class="ptolemy.domains.ddf.kernel.DDFDirector">
|
|
16
|
<property name="timeResolution" class="ptolemy.actor.parameters.SharedParameter" value="1E-10">
|
|
17
|
</property>
|
|
18
|
<property name="iterations" class="ptolemy.data.expr.Parameter" value="0">
|
|
19
|
</property>
|
|
20
|
<property name="maximumReceiverCapacity" class="ptolemy.data.expr.Parameter" value="0">
|
|
21
|
</property>
|
|
22
|
<property name="runUntilDeadlockInOneIteration" class="ptolemy.data.expr.Parameter" value="false">
|
|
23
|
</property>
|
|
24
|
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
|
|
25
|
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
26
|
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Gang Zhou</configure></property>
|
|
27
|
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
28
|
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure> <p> The dynamic dataflow (DDF) domain is a superset of the synchronous dataflow(SDF) and Boolean dataflow(BDF) domains. In the SDF domain, an actor consumes and produces a fixed number of tokens per firing. This static information makes possible compile-time scheduling. In the DDF domain, there are few constraints on the production and consumption behavior of actors, and the schedulers make no attempt to construct a compile-time schedule. Instead, each actor has a set of firing rules (patterns) and can be fired if one of them is satisfied, i.e., one particular firing pattern forms a prefix of sequences of unconsumed tokens at input ports. The canonical actors in the DDF domain include Select and Switch, which consume or produce tokens on different channels based on the token received from the control port. (In practice, use DDFSelect and DDFBooleanSelect in the DDF-specific library instead of Select and BooleanSelect in the regular FlowControl library; however, Switch and BooleanSwitch in the regular FlowControl library can be used in DDF domain.)</p> <p> The dynamic scheduler implemented in this director fires all enabled and non-deferrable actors once in a basic iteration. A deferrable actor is one that will not help one of the downstream actors become enabled because that downstream actor either already has enough tokens on the channel connecting those two actors or is waiting for tokens on another channel. If no actor fires so far, which means there is no enabled and non-deferrable actor, then among all enabled and deferrable actors, this director fires those which have the smallest maximum number of tokens on their output channels which satisfy the demand of destination actors. If still no actor fires, then there is no enabled actor. A user can treat several such basic iterations as a single iteration by adding a parameter with name <i>requiredFiringsPerIteration</i> to an actor (which is often a sink actor or an actor directly connected to output port of the composite actor) and specifying the number of times this actor must be fired in a single iteration. If the value of the parameter <i>runUntilDeadlockInOneIteration</i> is a BooleanToken with value true, one single iteration consists of repeating the basic iteration until deadlock is reached (thus overriding the previous definition of one iteration), which is the status of the model where all active actors under the control of this director are unable to fire because their firing rules are not satisfied. However, they may be able to fire again during next iteration when tokens are transferred in from an outside domain. Note <i>runUntilDeadlockInOneIteration</i> can be set to true only when this director is not on the top level.</p> <p> The algorithm implementing one basic iteration goes like this: <pre> E = set of enabled actors D = set of deferrable enabled actors </pre> One basic(default) iteration consists of: <pre> if (E\D != empty set) { fire (E\D) } else if (D != empty set) { fire minimax(D) } else { declare deadlock } </pre> The function "minimax(D)" returns a subset of D with the smallest maximum number of tokens on their output channels which satisfy the demand of destination actors.</p> <p> Note that any SDF model can be run with a DDF Director. However, the notion of iteration is different. One could try to imitate the SDF iteration in the DDF domain by controlling the number of firings in one iteration for some actors, such as requiring a plotter to plot a fixed number of points in each iteration.</p> <p> In the DDF domain, the firing rule of any actor is specified by the token consumption rates of its input ports. A general DDF actor could change the consumption rates of its input ports after each firing of this actor. For multiports, an array token could be used to specify different rates for different channels connected to the same multiport. Note that in SDF, all channels connected to the same multiport have the same rate.</p> <p> Based on DDFSimpleSched in Ptolemy Classic, by Edward Lee. See E. A. Lee et al., "The Almagest," documentation for Ptolemy Classic, Vol. 1, Chapter 7, 1997.</p> </configure></property>
|
|
29
|
<property name="prop:iterations" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Specify the number of times a workflow is iterated. By default, this parameter is set to "0". Note that "0" does not mean "no iterations." Rather, "0" means that the workflow will iterate forever. Values greater than zero specify the actual number of times the director should execute the entire workflow. </configure></property>
|
|
30
|
<property name="prop:maximumReceiverCapacity" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>A Parameter representing the maximum capacity of each receiver controlled by this director. This is an integer that defaults to 0, which means the queue in each receiver is unbounded. To specify bounded queues, set this to a positive integer. </configure></property>
|
|
31
|
<property name="prop:runUntilDeadlockInOneIteration" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>A parameter indicating whether one iteration consists of repeated basic iterations until deadlock. If this parameter is true, the model will be executed until deadlock in one iteration. The default value is a BooleanToken with the value false. It cannot be set to true if this director is at the top level.</configure></property>
|
|
32
|
</property> <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:director:5:1">
|
|
33
|
</property>
|
|
34
|
<property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.domains.ddf.kernel.DDFDirector">
|
|
35
|
<property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:directorclass:5:1">
|
|
36
|
</property>
|
|
37
|
</property>
|
|
38
|
<property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#Director">
|
|
39
|
</property>
|
|
40
|
<property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Director">
|
|
41
|
</property>
|
|
42
|
<property name="_location" class="ptolemy.kernel.util.Location" value="{125, 190}">
|
|
43
|
</property>
|
|
44
|
</property>
|
|
45
|
<entity name="CompositeActor" class="ptolemy.actor.TypedCompositeActor">
|
|
46
|
<property name="_createdBy" class="ptolemy.kernel.attributes.VersionAttribute" value="7.1.devel">
|
|
47
|
</property>
|
|
48
|
<property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:actor:449:1">
|
|
49
|
</property>
|
|
50
|
<property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.TypedCompositeActor">
|
|
51
|
<property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:449:1">
|
|
52
|
</property>
|
|
53
|
</property>
|
|
54
|
<property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#Actor">
|
|
55
|
</property>
|
|
56
|
<property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#GeneralPurpose">
|
|
57
|
</property>
|
|
58
|
<property name="semanticType22" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Workflow">
|
|
59
|
</property>
|
|
60
|
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
|
|
61
|
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
62
|
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Yuhong Xiong</configure></property>
|
|
63
|
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
64
|
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure><p>A Composite actor is an aggregation of actors. It may have a local director that is responsible for executing the contained actors. A Composite actor with a local director is called an opaque actor. Composite actors do not require a local director. Composite actors with no local director "inherit" the director from the containing workflow and are called non-opaque.</p> <p>To create a composite actor, drag and drop the Composite actor onto the Workflow canvas. Right-click the actor and select Open Actor from the drop-down menu. A new Kepler application window will open for designing the composite.</p></configure></property>
|
|
65
|
</property> <property name="_location" class="ptolemy.kernel.util.Location" value="{325.0, 280.0}">
|
|
66
|
</property>
|
|
67
|
<property name="PortParameter" class="ptolemy.actor.parameters.PortParameter" value="-1">
|
|
68
|
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
|
|
69
|
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
70
|
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
71
|
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
72
|
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure> <p>The PortParameter component specifies a persistent value, but can also accept an updated/current value via an associated port. The current value and the persistent value may differ.</p> <p>There are a few situations where PortParameter might not behave as expected:</p> <ol> <li>If PortParameter is used in a transparent composite actor, then a token provided to a PortParameter will never be read. A transparent composite actor is one without a director. Workaround: Put a director in the composite actor. </li> <li>Certain actors (such as the Integrator in CT) read parameter values only during initialization. During initialization, a PortParameter can only have a value set via the parameter (it can't have yet received a token). So if the initial value of the Integrator is set to the value of the PortParameter, then it will see only the parameter value, never the value provided via the port. Workaround: Use a RunCompositeActor to contain the model with the Integrator. </li> </ol> </configure></property>
|
|
73
|
<property name="prop:portParameter" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The specified persistent value. </configure></property>
|
|
74
|
</property> <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:actor:425:1">
|
|
75
|
</property>
|
|
76
|
<property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.parameters.PortParameter">
|
|
77
|
<property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:1189:1">
|
|
78
|
</property>
|
|
79
|
</property>
|
|
80
|
<property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#Parameter">
|
|
81
|
</property>
|
|
82
|
<property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Parameter">
|
|
83
|
</property>
|
|
84
|
<property name="_hideName" class="ptolemy.kernel.util.SingletonAttribute">
|
|
85
|
</property>
|
|
86
|
<property name="_icon" class="ptolemy.vergil.icon.ValueIcon">
|
|
87
|
</property>
|
|
88
|
<property name="_smallIconDescription" class="ptolemy.kernel.util.SingletonConfigurableAttribute">
|
|
89
|
<configure>
|
|
90
|
<svg>
|
|
91
|
<text x="20" style="font-size:14; font-family:SansSerif; fill:black" y="20">-P-</text>
|
|
92
|
</svg>
|
|
93
|
</configure>
|
|
94
|
</property>
|
|
95
|
<property name="_editorFactory" class="ptolemy.vergil.toolbox.VisibleParameterEditorFactory">
|
|
96
|
</property>
|
|
97
|
<property name="_location" class="ptolemy.kernel.util.Location" value="{90, 265}">
|
|
98
|
</property>
|
|
99
|
</property>
|
|
100
|
<property name="DDF Director" class="ptolemy.domains.ddf.kernel.DDFDirector">
|
|
101
|
<property name="timeResolution" class="ptolemy.actor.parameters.SharedParameter" value="1E-10">
|
|
102
|
</property>
|
|
103
|
<property name="iterations" class="ptolemy.data.expr.Parameter" value="0">
|
|
104
|
</property>
|
|
105
|
<property name="maximumReceiverCapacity" class="ptolemy.data.expr.Parameter" value="0">
|
|
106
|
</property>
|
|
107
|
<property name="runUntilDeadlockInOneIteration" class="ptolemy.data.expr.Parameter" value="false">
|
|
108
|
</property>
|
|
109
|
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
|
|
110
|
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
111
|
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Gang Zhou</configure></property>
|
|
112
|
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
113
|
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure> <p> The dynamic dataflow (DDF) domain is a superset of the synchronous dataflow(SDF) and Boolean dataflow(BDF) domains. In the SDF domain, an actor consumes and produces a fixed number of tokens per firing. This static information makes possible compile-time scheduling. In the DDF domain, there are few constraints on the production and consumption behavior of actors, and the schedulers make no attempt to construct a compile-time schedule. Instead, each actor has a set of firing rules (patterns) and can be fired if one of them is satisfied, i.e., one particular firing pattern forms a prefix of sequences of unconsumed tokens at input ports. The canonical actors in the DDF domain include Select and Switch, which consume or produce tokens on different channels based on the token received from the control port. (In practice, use DDFSelect and DDFBooleanSelect in the DDF-specific library instead of Select and BooleanSelect in the regular FlowControl library; however, Switch and BooleanSwitch in the regular FlowControl library can be used in DDF domain.)</p> <p> The dynamic scheduler implemented in this director fires all enabled and non-deferrable actors once in a basic iteration. A deferrable actor is one that will not help one of the downstream actors become enabled because that downstream actor either already has enough tokens on the channel connecting those two actors or is waiting for tokens on another channel. If no actor fires so far, which means there is no enabled and non-deferrable actor, then among all enabled and deferrable actors, this director fires those which have the smallest maximum number of tokens on their output channels which satisfy the demand of destination actors. If still no actor fires, then there is no enabled actor. A user can treat several such basic iterations as a single iteration by adding a parameter with name <i>requiredFiringsPerIteration</i> to an actor (which is often a sink actor or an actor directly connected to output port of the composite actor) and specifying the number of times this actor must be fired in a single iteration. If the value of the parameter <i>runUntilDeadlockInOneIteration</i> is a BooleanToken with value true, one single iteration consists of repeating the basic iteration until deadlock is reached (thus overriding the previous definition of one iteration), which is the status of the model where all active actors under the control of this director are unable to fire because their firing rules are not satisfied. However, they may be able to fire again during next iteration when tokens are transferred in from an outside domain. Note <i>runUntilDeadlockInOneIteration</i> can be set to true only when this director is not on the top level.</p> <p> The algorithm implementing one basic iteration goes like this: <pre> E = set of enabled actors D = set of deferrable enabled actors </pre> One basic(default) iteration consists of: <pre> if (E\D != empty set) { fire (E\D) } else if (D != empty set) { fire minimax(D) } else { declare deadlock } </pre> The function "minimax(D)" returns a subset of D with the smallest maximum number of tokens on their output channels which satisfy the demand of destination actors.</p> <p> Note that any SDF model can be run with a DDF Director. However, the notion of iteration is different. One could try to imitate the SDF iteration in the DDF domain by controlling the number of firings in one iteration for some actors, such as requiring a plotter to plot a fixed number of points in each iteration.</p> <p> In the DDF domain, the firing rule of any actor is specified by the token consumption rates of its input ports. A general DDF actor could change the consumption rates of its input ports after each firing of this actor. For multiports, an array token could be used to specify different rates for different channels connected to the same multiport. Note that in SDF, all channels connected to the same multiport have the same rate.</p> <p> Based on DDFSimpleSched in Ptolemy Classic, by Edward Lee. See E. A. Lee et al., "The Almagest," documentation for Ptolemy Classic, Vol. 1, Chapter 7, 1997.</p> </configure></property>
|
|
114
|
<property name="prop:maximumReceiverCapacity" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>A Parameter representing the maximum capacity of each receiver controlled by this director. This is an integer that defaults to 0, which means the queue in each receiver is unbounded. To specify bounded queues, set this to a positive integer. </configure></property>
|
|
115
|
<property name="prop:iterations" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Specify the number of times a workflow is iterated. By default, this parameter is set to "0". Note that "0" does not mean "no iterations." Rather, "0" means that the workflow will iterate forever. Values greater than zero specify the actual number of times the director should execute the entire workflow. </configure></property>
|
|
116
|
<property name="prop:runUntilDeadlockInOneIteration" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>A parameter indicating whether one iteration consists of repeated basic iterations until deadlock. If this parameter is true, the model will be executed until deadlock in one iteration. The default value is a BooleanToken with the value false. It cannot be set to true if this director is at the top level.</configure></property>
|
|
117
|
</property> <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:director:5:1">
|
|
118
|
</property>
|
|
119
|
<property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.domains.ddf.kernel.DDFDirector">
|
|
120
|
<property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:directorclass:5:1">
|
|
121
|
</property>
|
|
122
|
</property>
|
|
123
|
<property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#Director">
|
|
124
|
</property>
|
|
125
|
<property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Director">
|
|
126
|
</property>
|
|
127
|
<property name="_location" class="ptolemy.kernel.util.Location" value="{125, 150}">
|
|
128
|
</property>
|
|
129
|
</property>
|
|
130
|
<port name="PortParameter" class="ptolemy.actor.parameters.ParameterPort">
|
|
131
|
<property name="input"/>
|
|
132
|
<property name="_location" class="ptolemy.kernel.util.Location" value="{70.0, 260.0}">
|
|
133
|
</property>
|
|
134
|
</port>
|
|
135
|
<entity name="Constant" class="ptolemy.actor.lib.Const">
|
|
136
|
<property name="firingCountLimit" class="ptolemy.data.expr.Parameter" value="3">
|
|
137
|
</property>
|
|
138
|
<property name="NONE" class="ptolemy.data.expr.Parameter" value="0">
|
|
139
|
</property>
|
|
140
|
<property name="value" class="ptolemy.data.expr.Parameter" value="PortParameter">
|
|
141
|
</property>
|
|
142
|
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
|
|
143
|
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
144
|
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
145
|
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
146
|
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure><p>The Constant actor outputs a constant, which is specified by the value parameter. By default, the actor outputs the integer 1.</p> <p>The actor can be used to output other types of values, e.g., a string (such as "Hello") or a double (such as 1.2). The actor' s output type matches the type of the specified value.</p> <p>NOTE: If using a PN Director, the 'firingCountLimit' parameter is often set to a finite integer (e.g. '1') so that the workflow will terminate. </p> </configure></property>
|
|
147
|
<property name="port:output" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An output port that broadcasts the specified constant. By default, the output is 1.</configure></property>
|
|
148
|
<property name="port:trigger" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>A multiport that has no declared type (in other words, the port can accept any data type: double, int, array, etc.) If the port is connected, the actor will not fire until the trigger port receives an input token. Connecting the port is optional, but useful when scheduling the actor to perform at a certain time.</configure></property>
|
|
149
|
<property name="prop:firingCountLimit" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The limit on the number of times the actor will fire. The default value is 'NONE', meaning there is no limit on the number of time the constant will be provided to the output port. Any integer can be provided as a value for this parameter.</configure></property>
|
|
150
|
<property name="prop:value" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The value produced by the Constant actor. By default, the value is the integer token 1. The value can be set to another type, e.g., a string (such as "Hello") or a double (such as 1.2). The output type matches the type of the value specified here.</configure></property>
|
|
151
|
</property> <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:actor:1:1">
|
|
152
|
</property>
|
|
153
|
<property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.Const">
|
|
154
|
<property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:877:1">
|
|
155
|
</property>
|
|
156
|
</property>
|
|
157
|
<property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#ConstantActor">
|
|
158
|
</property>
|
|
159
|
<property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Constant">
|
|
160
|
</property>
|
|
161
|
<property name="kar" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:kar:57:1">
|
|
162
|
</property>
|
|
163
|
<property name="_icon" class="ptolemy.vergil.icon.BoxedValueIcon">
|
|
164
|
<property name="attributeName" class="ptolemy.kernel.util.StringAttribute" value="value">
|
|
165
|
</property>
|
|
166
|
<property name="displayWidth" class="ptolemy.data.expr.Parameter" value="40">
|
|
167
|
</property>
|
|
168
|
</property>
|
|
169
|
<property name="_location" class="ptolemy.kernel.util.Location" value="[185.0, 315.0]">
|
|
170
|
</property>
|
|
171
|
</entity>
|
|
172
|
<entity name="Display" class="ptolemy.actor.lib.gui.Display">
|
|
173
|
<property name="_windowProperties" class="ptolemy.actor.gui.WindowPropertiesAttribute" value="{bounds={644, 402, 330, 243}, maximized=false}">
|
|
174
|
</property>
|
|
175
|
<property name="_paneSize" class="ptolemy.actor.gui.SizeAttribute" value="[322, 182]">
|
|
176
|
</property>
|
|
177
|
<property name="rowsDisplayed" class="ptolemy.data.expr.Parameter" value="10">
|
|
178
|
</property>
|
|
179
|
<property name="columnsDisplayed" class="ptolemy.data.expr.Parameter" value="40">
|
|
180
|
</property>
|
|
181
|
<property name="suppressBlankLines" class="ptolemy.data.expr.Parameter" value="false">
|
|
182
|
</property>
|
|
183
|
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
|
|
184
|
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
185
|
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Yuhong Xiong, Edward A. Lee</configure></property>
|
|
186
|
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
187
|
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure><p>The Display actor reads tokens of any type via its input multiport, and displays each token on a separate line in a text display window.</p> <p>Specify the size of the text display window with the rowsDisplayed and columnsDisplayed parameters. Simply resizing the window onscreen does not persistently change the size when the workflow is saved, closed, and then re-opened. </p> <p>If the input is a string token, then the actor strips the surrounding quotation marks before displaying the value.</p> <p>Select the suppressBlankLines parameter to specify that the actor not add blank lines to the display. By default, the actor will add blank lines.</p> <p>Note: this actor can consume large amounts of memory. It is not advisable to use it to display large output streams.</p></configure></property>
|
|
188
|
<property name="port:input" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>A multiport that accepts tokens of any type.</configure></property>
|
|
189
|
<property name="prop:suppressBlankLines" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Specify whether the actor should display blank lines (the default) or suppress them.</configure></property>
|
|
190
|
<property name="prop:rowsDisplayed" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The vertical size of the display, in rows. The value is an integer that defaults to 10.</configure></property>
|
|
191
|
<property name="prop:columnsDisplayed" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The horizontal size of the display, in columns. The value is an integer that defaults to 40.</configure></property>
|
|
192
|
<property name="prop:title" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The title of the text display window. If specified, the value will appear in the title bar of the text display window.</configure></property>
|
|
193
|
</property> <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:actor:7:1">
|
|
194
|
</property>
|
|
195
|
<property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.gui.Display">
|
|
196
|
<property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:883:1">
|
|
197
|
</property>
|
|
198
|
</property>
|
|
199
|
<property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#TextualOutputActor">
|
|
200
|
</property>
|
|
201
|
<property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#TextualOutput">
|
|
202
|
</property>
|
|
203
|
<property name="_location" class="ptolemy.kernel.util.Location" value="[375.0, 295.0]">
|
|
204
|
</property>
|
|
205
|
</entity>
|
|
206
|
<relation name="relation" class="ptolemy.actor.TypedIORelation">
|
|
207
|
<property name="width" class="ptolemy.data.expr.Parameter" value="1">
|
|
208
|
</property>
|
|
209
|
</relation>
|
|
210
|
<link port="Constant.output" relation="relation"/>
|
|
211
|
<link port="Display.input" relation="relation"/>
|
|
212
|
</entity>
|
|
213
|
<entity name="Display" class="ptolemy.actor.lib.gui.Display">
|
|
214
|
<property name="_windowProperties" class="ptolemy.actor.gui.WindowPropertiesAttribute" value="{bounds={481, 643, 330, 243}, maximized=false}">
|
|
215
|
</property>
|
|
216
|
<property name="_paneSize" class="ptolemy.actor.gui.SizeAttribute" value="[322, 182]">
|
|
217
|
</property>
|
|
218
|
<property name="rowsDisplayed" class="ptolemy.data.expr.Parameter" value="10">
|
|
219
|
</property>
|
|
220
|
<property name="columnsDisplayed" class="ptolemy.data.expr.Parameter" value="40">
|
|
221
|
</property>
|
|
222
|
<property name="suppressBlankLines" class="ptolemy.data.expr.Parameter" value="false">
|
|
223
|
</property>
|
|
224
|
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
|
|
225
|
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
226
|
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Yuhong Xiong, Edward A. Lee</configure></property>
|
|
227
|
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
228
|
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure><p>The Display actor reads tokens of any type via its input multiport, and displays each token on a separate line in a text display window.</p> <p>Specify the size of the text display window with the rowsDisplayed and columnsDisplayed parameters. Simply resizing the window onscreen does not persistently change the size when the workflow is saved, closed, and then re-opened. </p> <p>If the input is a string token, then the actor strips the surrounding quotation marks before displaying the value.</p> <p>Select the suppressBlankLines parameter to specify that the actor not add blank lines to the display. By default, the actor will add blank lines.</p> <p>Note: this actor can consume large amounts of memory. It is not advisable to use it to display large output streams.</p></configure></property>
|
|
229
|
<property name="port:input" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>A multiport that accepts tokens of any type.</configure></property>
|
|
230
|
<property name="prop:suppressBlankLines" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Specify whether the actor should display blank lines (the default) or suppress them.</configure></property>
|
|
231
|
<property name="prop:rowsDisplayed" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The vertical size of the display, in rows. The value is an integer that defaults to 10.</configure></property>
|
|
232
|
<property name="prop:columnsDisplayed" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The horizontal size of the display, in columns. The value is an integer that defaults to 40.</configure></property>
|
|
233
|
<property name="prop:title" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The title of the text display window. If specified, the value will appear in the title bar of the text display window.</configure></property>
|
|
234
|
</property> <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:actor:7:1">
|
|
235
|
</property>
|
|
236
|
<property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.gui.Display">
|
|
237
|
<property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:883:1">
|
|
238
|
</property>
|
|
239
|
</property>
|
|
240
|
<property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#TextualOutputActor">
|
|
241
|
</property>
|
|
242
|
<property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#TextualOutput">
|
|
243
|
</property>
|
|
244
|
<property name="_location" class="ptolemy.kernel.util.Location" value="[295.0, 400.0]">
|
|
245
|
</property>
|
|
246
|
</entity>
|
|
247
|
<entity name="Ramp" class="ptolemy.actor.lib.Ramp">
|
|
248
|
<property name="firingCountLimit" class="ptolemy.data.expr.Parameter" value="2">
|
|
249
|
</property>
|
|
250
|
<property name="NONE" class="ptolemy.data.expr.Parameter" value="0">
|
|
251
|
</property>
|
|
252
|
<property name="init" class="ptolemy.data.expr.Parameter" value="2">
|
|
253
|
</property>
|
|
254
|
<property name="step" class="ptolemy.actor.parameters.PortParameter" value="1">
|
|
255
|
</property>
|
|
256
|
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
|
|
257
|
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
258
|
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Yuhong Xiong, Edward A. Lee</configure></property>
|
|
259
|
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
|
|
260
|
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure><p>The Ramp actor is the equivalent of the "for loop" in many traditional computer languages. Its parameters include an intial value, the amount the value is incremented each time the actor fires (the 'step'), and the upper limit of the value (the firingCountLimit). The actor outputs an integer each time it is fired. </p> <p>The actor's output can be used as a counter (increasing or decreasing), or as a parameter used in an incremented workflow. For example, the output of a Ramp actor can be input to an Expression actor to create file names that are unique for each iteration (e.g., 'file1', 'file2', etc.) The Ramp actor is also particularly useful with PN directed workflows where there is no way to set the number of iterations as a Director parameter. </p> <p>The first time the actor fires, it outputs the value of its init parameter. The increment value, specified with either the step port or parameter, will only be added on the following iteration. To add an increment to the first iteration, use the Accumulator actor.</p> <p>The actor accepts values of any type that support addition.</p></configure></property>
|
|
261
|
<property name="port:output" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An output port that broadcasts the incremented value.</configure></property>
|
|
262
|
<property name="port:trigger" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An input port that has no declared type (in other words, the port can accept any data type: double, int, array, etc.) If the port is connected, the actor will not fire until the trigger port receives an input token. Connecting the port is optional, but useful when scheduling the actor to perform at a certain time.</configure></property>
|
|
263
|
<property name="port:step" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An input port that accepts the amount by which the output is incremented on each iteration. The port accepts a value of any type that supports addition. The value is an integer and defaults to 1.</configure></property>
|
|
264
|
<property name="prop:firingCountLimit" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The number of iterations that transpire before the actor indicates that it is finished. If firingCountLimit is set to zero, the actor has no limit imposed.</configure></property>
|
|
265
|
<property name="prop:step" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The amount by which the output is incremented on each iteration. The port accepts a value of any type that supports addition. The default is the integer 1.</configure></property>
|
|
266
|
<property name="prop:init" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The value produced by the Ramp on its first iteration. The default value is the integer 0.</configure></property>
|
|
267
|
</property> <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:actor:5:1">
|
|
268
|
</property>
|
|
269
|
<property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.Ramp">
|
|
270
|
<property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:881:1">
|
|
271
|
</property>
|
|
272
|
</property>
|
|
273
|
<property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#IterativeMathOperationActor">
|
|
274
|
</property>
|
|
275
|
<property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#IterativeOperation">
|
|
276
|
</property>
|
|
277
|
<property name="semanticType22" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#WorkflowInput">
|
|
278
|
</property>
|
|
279
|
<property name="_location" class="ptolemy.kernel.util.Location" value="{135, 340}">
|
|
280
|
</property>
|
|
281
|
</entity>
|
|
282
|
<relation name="relation2" class="ptolemy.actor.TypedIORelation">
|
|
283
|
<property name="width" class="ptolemy.data.expr.Parameter" value="1">
|
|
284
|
</property>
|
|
285
|
<vertex name="vertex1" value="[260.0, 305.0]">
|
|
286
|
</vertex>
|
|
287
|
</relation>
|
|
288
|
<link port="CompositeActor.PortParameter" relation="relation2"/>
|
|
289
|
<link port="Display.input" relation="relation2"/>
|
|
290
|
<link port="Ramp.output" relation="relation2"/>
|
|
291
|
</entity>
|