Project

General

Profile

rec-assembler-1.xml

Daniel Crawl, 12/01/2014 04:00 PM

 
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="rec-assembler-1" class="ptolemy.actor.TypedCompositeActor">
5
    <property name="_createdBy" class="ptolemy.kernel.attributes.VersionAttribute" value="11.0.devel">
6
    </property>
7
    <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org/ns/:62508:1495:67">
8
    </property>
9
    <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.TypedCompositeActor">
10
        <property name="id" class="ptolemy.kernel.util.StringAttribute" value="null">
11
        </property>
12
    </property>
13
    <property name="derivedFrom" class="org.kepler.moml.NamedObjIdReferralList">
14
    </property>
15
    <property name="SDF Director" class="ptolemy.domains.sdf.kernel.SDFDirector">
16
        <property name="localClock" class="ptolemy.actor.LocalClock">
17
            <property name="globalTimeResolution" class="ptolemy.actor.parameters.SharedParameter" value="1.0E-10">
18
            </property>
19
            <property name="clockRate" class="ptolemy.data.expr.Parameter" value="1.0">
20
            </property>
21
        </property>
22
        <property name="iterations" class="ptolemy.data.expr.Parameter" value="AUTO">
23
        </property>
24
        <property name="vectorizationFactor" class="ptolemy.data.expr.Parameter" value="1">
25
        </property>
26
        <property name="allowDisconnectedGraphs" class="ptolemy.data.expr.Parameter" value="false">
27
        </property>
28
        <property name="allowRateChanges" class="ptolemy.data.expr.Parameter" value="false">
29
        </property>
30
        <property name="constrainBufferSizes" class="ptolemy.data.expr.Parameter" value="true">
31
        </property>
32
        <property name="period" class="ptolemy.data.expr.Parameter" value="0.0">
33
        </property>
34
        <property name="synchronizeToRealTime" class="ptolemy.data.expr.Parameter" value="false">
35
        </property>
36
        <property name="Scheduler" class="ptolemy.domains.sdf.kernel.SDFScheduler">
37
            <property name="constrainBufferSizes" class="ptolemy.data.expr.Parameter" value="constrainBufferSizes">
38
            </property>
39
        </property>
40
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
41
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
42
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Steve Neuendorffer</configure></property>
43
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
44
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>&#10;&lt;p&gt;The SDF Director is often used to oversee fairly simple, sequential workflows in which the director can determine the order of actor invocation from the workflow. Types of workflows that would run well under an SDF Director include processing and reformatting tabular data, converting one data type to another, and reading and plotting a series of data points. A workflow in which an image is read, processed (rotated, scaled, clipped, filtered, etc.), and then displayed, is also an example of a sequential workflow that requires a director simply to ensure that each actor fires in the proper order (i.e., that each actor executes only after it receives its required inputs).&lt;/p&gt;&#10;&#10;&lt;p&gt;The SDF Director is very efficient and will not tax system resources with overhead. However, this efficiency requires that certain conditions be met, namely that the data consumption and production rate of each actor in an SDF workflow be constant and declared. If an actor reads one piece of data and calculates and outputs a single result, it must always read and output a single token of data. This data rate cannot change during workflow execution and, in general, workflows that require dynamic scheduling and/or flow control cannot use this director. Additionally, the SDF Director has no understanding of passing time (at least by default), and actors that depend on a notion of time may not work as expected. For example, a TimedPlotter actor will plot all values at time zero when used in SDF. &lt;/p&gt;&#10;&#10;&lt;p&gt;By default, the SDF Director requires that all actors in its workflow be connected. Otherwise, the director cannot account for concurrency between disconnected workflow parts. Usually, a PN Director should be used for workflows that contain disconnected actors; however, the SDF Director's allowDisconnectedGraphs parameter may also be set to true. The SDF Director will then schedule each disconnected &quot;island&quot; independently. The director cannot infer the sequential relationship between disconnected actors (i.e., nothing forces the director to finish executing all actors on one island before firing actors on another). However, the order of execution within each island should be correct. Usually, disconnected graphs in an SDF model indicate an error.&lt;/p&gt;&#10; &#10;&lt;p&gt;Because SDF Directors schedule actors to fire only after they receive their inputs, workflows that require loops (feeding an actor's output back into its input port for further processing) can cause &quot;deadlock&quot; errors. The deadlock errors occur because the actor depends on its own output value as an initial input. To fix this problem, use a SampleDelay actor to generate and inject an initial input value into the workflow.&lt;/p&gt;&#10;&#10;&lt;p&gt;The SDF Director determines the order in which actors execute and how many times each actor needs to be fired to complete a single iteration of the workflow. This schedule is calculated BEFORE the director begins to iterate the workflow. Because the SDF Director calculates a schedule in advance, it is quite efficient. However, SDF workflows must be static. In other words, the same number of tokens must be consumed/produced at every iteration of the workflow. Workflows that require dynamic control structures, such as a BooleanSwitch actor that sends output on one of two ports depending on the value of a 'control', cannot be used with an SDF Director because the number of tokens on each output can change for each execution.&lt;/p&gt;&#10;&#10;&lt;p&gt;Unless otherwise specified, the SDF Director assumes that each actor consumes and produces exactly one token per channel on each firing. Actors that do not follow the one-token-per-channel firing convention (e.g., Repeat or Ramp) must declare the number of tokens they produce or consume via the appropriate parameters. &lt;/p&gt;&#10;&#10;&lt;p&gt;The number of times a workflow is iterated is controlled by the director's iterations parameter. Since Kepler 2.4, this parameter is set to &quot;AUTO&quot; by default. The director will run the workflow once when it is placed in the top level workflow. When it is placed in a composite actor, the director will keep running the sub-workflow inside of the composite actor until the top level director tells it to stop. In other words, &quot;AUTO&quot; means its value will be &quot;1&quot; when it is placed in the top level workflow, and will be &quot;UNBOUNDED&quot; when it is placed in a composite actor. This default value works for most cases. You can also select &quot;UNBOUNDED&quot; or specify &quot;0&quot; for this parameter, which means the workflow will iterate forever. Concrete numbers can be specified here too for the actual number of times the director should execute the workflow. &lt;/p&gt;&#10;&#10;&lt;p&gt;The amount of data processed by an SDF workflow is a function of both the number of times the workflow iterates and the value of the director's vectorizationFactor parameter. The vectorizationFactor is used to increase the efficiency of a workflow by increasing the number of times actors fire each time the workflow iterates. If the parameter is set to a positive integer (other than 1), the director will fire each actor the specified number of times more than normal. The default is 1, indicating that no vectorization should be performed. Keep in mind that changing the vectorizationFactor parameter changes the meaning of a nested SDF workflow and may cause deadlock in a workflow that uses it. &lt;/p&gt;&#10;&#10;&lt;p&gt;The SDF Director has several advanced parameters that are generally only relevant when an SDF workflow contains composite components. In most cases the period, timeResolution, synchronizeToRealTime, allowRateChanges, timeResolution, and constrainBufferSizes parameters can be left at their default values.&lt;/p&gt;&#10;&#10;&lt;p&gt;For more information about the SDF Director, see the Ptolemy documentation (http://ptolemy.eecs.berkeley.edu/papers/05/ptIIdesign3-domains/ptIIdesign3-domains.pdf).&lt;/p&gt;&#10;&#10;</configure></property>
45
<property name="prop:allowDisconnectedGraphs" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Specify whether to allow disconnected actors in the workflow (by default, all actors are required to be connected). If disconnected actors are permitted, the SDF Director will schedule each disconnected 'island' independently. Nothing &quot;forces&quot; the director to finish executing all actors on one island before firing actors on another. However, the order of execution within each island should be correct. Usually, disconnected graphs in an SDF workflow indicate an error.</configure></property>
46
<property name="prop:allowRateChanges" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Specify whether dynamic rate changes are permitted or not. By default, rate changes are not permitted, and the director will perform a check to disallow such workflows. If the parameter is selected, then workflows that require rate parameters to be modified during execution are valid, and the SDF Director will dynamically compute a new schedule at runtime. This is an advanced parameter that can usually be left at its default value.</configure></property>
47
<property name="prop:constrainBufferSizes" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Specify whether buffer sizes are fixed. By default, buffers are fixed, and attempts to write to the buffer that cause the buffer to exceed its scheduled size result in an error. This is an advanced parameter that can usually be left at its default value.</configure></property>
48
<property name="prop:timeResolution" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The time precision used by this director. All time values are rounded to the nearest multiple of this number. The value is a double that defaults to &quot;1E-10&quot; (which is 10-10). This is an advanced parameter that can usually be left at its default value.</configure></property>
49
<property name="prop:iterations" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Specify the number of times a workflow is iterated. Since Kepler 2.4, this parameter is set to &quot;AUTO&quot; by default. The director will run the workflow once when it is placed in the top level workflow. When it is placed in a composite actor, the director will keep running the sub-workflow inside of the composite actor until the top level director tells it to stop. In other words, &quot;AUTO&quot; means its value will be &quot;1&quot; when it is placed in the top level workflow, and will be &quot;UNBOUNDED&quot; when it is placed in a composite actor. This default value works for most cases. You can also select &quot;UNBOUNDED&quot; or specify &quot;0&quot; for this parameter, which means the workflow will iterate forever. Concrete numbers can be specified here too for the actual number of times the director should execute the workflow. </configure></property>
50
<property name="prop:vectorizationFactor" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The vectorizationFactor is used to increase the efficiency of a workflow by increasing the number of times actors fire each time the workflow iterates. If the parameter is set to a positive integer (other than 1), the director will fire each actor the specified number of times more than normal. The default is 1, indicating that no vectorization should be performed. Keep in mind that changing the vectorizationFactor parameter changes the meaning of a nested SDF workflow and may cause deadlock in a workflow that uses it. </configure></property>
51
<property name="prop:synchronizeToRealTime" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Specify whether the execution should synchronize to real time or not. By default, the director does not synchronize to real time. If synchronize is selected, the director will only process the workflow when elapsed real time matches the product of the period parameter and the iteration count. Note: if the period parameter has a value of 0.0 (the default), then selecting this parameter has no effect. This is an advanced parameter that can usually be left at its default value.</configure></property>
52
<property name="prop:period" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The time period of each iteration. The value is a double that defaults to 0.0, which means that the director does not increment workflow time. If the value greater than 0.0, the actor will increment workflow time each time it fires. This is an advanced parameter that can usually be left at its default value. </configure></property>
53
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:director:1:2">
54
        </property>
55
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.domains.sdf.kernel.SDFDirector">
56
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:directorclass:1:2">
57
            </property>
58
        </property>
59
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#Director">
60
        </property>
61
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Director">
62
        </property>
63
        <property name="_location" class="ptolemy.kernel.util.Location" value="{65, 80}">
64
        </property>
65
    </property>
66
    <property name="_windowProperties" class="ptolemy.actor.gui.WindowPropertiesAttribute" value="{bounds={377, 129, 1038, 790}, maximized=false}">
67
    </property>
68
    <property name="_vergilSize" class="ptolemy.actor.gui.SizeAttribute" value="[728, 632]">
69
    </property>
70
    <property name="_vergilZoomFactor" class="ptolemy.data.expr.ExpertParameter" value="1.0">
71
    </property>
72
    <property name="_vergilCenter" class="ptolemy.data.expr.ExpertParameter" value="{354.0, 306.0}">
73
    </property>
74
    <entity name="Record Assembler" class="ptolemy.actor.lib.RecordAssembler">
75
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
76
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
77
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Yuhong Xiong</configure></property>
78
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
79
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>&#10;&lt;p&gt;The RecordAssembler actor receives tokens of various types on user-defined input ports and assembles those tokens into a record, which it outputs. The actor reads and converts one token from each port every time it fires.&lt;/p&gt;&#10;&#10;&lt;p&gt;A record is a composite data type consisting of one or more elements. Each element is named and can have a distinct type. For example, {number=1, name=&quot;dog&quot;} is a record containing two elements. The first element, named &quot;number&quot;, contains an integer value. The second element, named &quot;name&quot;, contains a string value. &lt;/p&gt;&#10;&#10;&lt;p&gt;The name of each record element generated by the actor is the name of the input port from which the value was received. An actor customized to use three input ports named &quot;day&quot;, &quot;week&quot;, &quot;month&quot; could output the following record {day=&quot;Monday&quot;, week=5, month=12}.&lt;/p&gt;&#10;&#10;</configure></property>
80
<property name="port:output" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An output port that broadcasts the generated records. </configure></property>
81
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org/ns/:62508:1501:1">
82
        </property>
83
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.RecordAssembler">
84
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:923:1">
85
            </property>
86
        </property>
87
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#RecordActor">
88
        </property>
89
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#DataStructureOperation">
90
        </property>
91
        <property name="_location" class="ptolemy.kernel.util.Location" value="[230.72933197021484, 216.80281829833984]">
92
        </property>
93
        <property name="derivedFrom" class="org.kepler.moml.NamedObjIdReferralList" value="urn:lsid:kepler-project.org:actor:47:1">
94
        </property>
95
        <port name="a" class="ptolemy.actor.TypedIOPort">
96
            <property name="input"/>
97
            <property name="_showName" class="ptolemy.data.expr.SingletonParameter" value="true">
98
            </property>
99
        </port>
100
        <port name="b" class="ptolemy.actor.TypedIOPort">
101
            <property name="input"/>
102
            <property name="_showName" class="ptolemy.data.expr.SingletonParameter" value="true">
103
            </property>
104
        </port>
105
    </entity>
106
    <entity name="Record Assembler2" class="ptolemy.actor.lib.RecordAssembler">
107
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
108
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
109
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Yuhong Xiong</configure></property>
110
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
111
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>&#10;&lt;p&gt;The RecordAssembler actor receives tokens of various types on user-defined input ports and assembles those tokens into a record, which it outputs. The actor reads and converts one token from each port every time it fires.&lt;/p&gt;&#10;&#10;&lt;p&gt;A record is a composite data type consisting of one or more elements. Each element is named and can have a distinct type. For example, {number=1, name=&quot;dog&quot;} is a record containing two elements. The first element, named &quot;number&quot;, contains an integer value. The second element, named &quot;name&quot;, contains a string value. &lt;/p&gt;&#10;&#10;&lt;p&gt;The name of each record element generated by the actor is the name of the input port from which the value was received. An actor customized to use three input ports named &quot;day&quot;, &quot;week&quot;, &quot;month&quot; could output the following record {day=&quot;Monday&quot;, week=5, month=12}.&lt;/p&gt;&#10;&#10;</configure></property>
112
<property name="port:output" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An output port that broadcasts the generated records. </configure></property>
113
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org/ns/:62508:1502:1">
114
        </property>
115
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.RecordAssembler">
116
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:923:1">
117
            </property>
118
        </property>
119
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#RecordActor">
120
        </property>
121
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#DataStructureOperation">
122
        </property>
123
        <property name="_location" class="ptolemy.kernel.util.Location" value="[325.0, 305.0]">
124
        </property>
125
        <property name="derivedFrom" class="org.kepler.moml.NamedObjIdReferralList" value="urn:lsid:kepler-project.org:actor:47:1">
126
        </property>
127
        <port name="z" class="ptolemy.actor.TypedIOPort">
128
            <property name="input"/>
129
            <property name="_showName" class="ptolemy.data.expr.SingletonParameter" value="true">
130
            </property>
131
        </port>
132
        <port name="c" class="ptolemy.actor.TypedIOPort">
133
            <property name="input"/>
134
            <property name="_showName" class="ptolemy.data.expr.SingletonParameter" value="true">
135
            </property>
136
        </port>
137
    </entity>
138
    <entity name="String Constant" class="ptolemy.actor.lib.StringConst">
139
        <property name="value" class="ptolemy.data.expr.Parameter" value="a">
140
        </property>
141
        <property name="firingCountLimit" class="ptolemy.data.expr.Parameter" value="NONE">
142
        </property>
143
        <property name="NONE" class="ptolemy.data.expr.Parameter" value="0">
144
        </property>
145
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
146
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
147
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Edward Lee</configure></property>
148
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
149
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>&lt;p&gt;The StringConstant actor outputs a string specified via the actor's value parameter.&lt;/p&gt;&#10;&#10;&lt;p&gt;Specifying strings with the StringConstant actor is convenient, as the actor does not require that strings be surrounded by quotes. The actor is often used to specify file paths, which can be selected using the Browse button available in the actor's parameters.&lt;/p&gt;&#10;&#10;&lt;p&gt;Specified string values can include references to parameters within scope (i.e., parameters defined at the same level of the hierarchy or higher). &lt;/p&gt;&#10;&#10;&lt;p&gt;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. &lt;/p&gt;&#10;&#10;</configure></property>
150
<property name="port:output" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An output port that broadcasts a string constant specified by the value parameter.  </configure></property>
151
<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>
152
<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>
153
<property name="prop:value" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The value produced by the actor. Specified strings do not require enclosing quotes. (To include a '$' sign in the string, enter '$$'.)</configure></property>
154
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org/ns/:62508:1498:1">
155
        </property>
156
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.StringConst">
157
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:1052:1">
158
            </property>
159
        </property>
160
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#StringFunctionActor">
161
        </property>
162
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Constant">
163
        </property>
164
        <property name="_icon" class="ptolemy.vergil.icon.BoxedValueIcon">
165
            <property name="attributeName" class="ptolemy.kernel.util.StringAttribute" value="value">
166
            </property>
167
            <property name="displayWidth" class="ptolemy.data.expr.Parameter" value="60">
168
            </property>
169
        </property>
170
        <property name="_location" class="ptolemy.kernel.util.Location" value="[65.0, 210.0]">
171
        </property>
172
        <property name="derivedFrom" class="org.kepler.moml.NamedObjIdReferralList" value="urn:lsid:kepler-project.org:actor:204:1">
173
        </property>
174
        <port name="trigger" class="ptolemy.actor.TypedIOPort">
175
            <property name="input"/>
176
            <property name="multiport"/>
177
            <property name="_showName" class="ptolemy.data.expr.SingletonParameter" value="true">
178
            </property>
179
        </port>
180
    </entity>
181
    <entity name="String Constant2" class="ptolemy.actor.lib.StringConst">
182
        <property name="value" class="ptolemy.data.expr.Parameter" value="c">
183
        </property>
184
        <property name="firingCountLimit" class="ptolemy.data.expr.Parameter" value="NONE">
185
        </property>
186
        <property name="NONE" class="ptolemy.data.expr.Parameter" value="0">
187
        </property>
188
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
189
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
190
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Edward Lee</configure></property>
191
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
192
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>&lt;p&gt;The StringConstant actor outputs a string specified via the actor's value parameter.&lt;/p&gt;&#10;&#10;&lt;p&gt;Specifying strings with the StringConstant actor is convenient, as the actor does not require that strings be surrounded by quotes. The actor is often used to specify file paths, which can be selected using the Browse button available in the actor's parameters.&lt;/p&gt;&#10;&#10;&lt;p&gt;Specified string values can include references to parameters within scope (i.e., parameters defined at the same level of the hierarchy or higher). &lt;/p&gt;&#10;&#10;&lt;p&gt;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. &lt;/p&gt;&#10;&#10;</configure></property>
193
<property name="port:output" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An output port that broadcasts a string constant specified by the value parameter.  </configure></property>
194
<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>
195
<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>
196
<property name="prop:value" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The value produced by the actor. Specified strings do not require enclosing quotes. (To include a '$' sign in the string, enter '$$'.)</configure></property>
197
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org/ns/:62508:1500:1">
198
        </property>
199
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.StringConst">
200
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:1052:1">
201
            </property>
202
        </property>
203
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#StringFunctionActor">
204
        </property>
205
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Constant">
206
        </property>
207
        <property name="_icon" class="ptolemy.vergil.icon.BoxedValueIcon">
208
            <property name="attributeName" class="ptolemy.kernel.util.StringAttribute" value="value">
209
            </property>
210
            <property name="displayWidth" class="ptolemy.data.expr.Parameter" value="60">
211
            </property>
212
        </property>
213
        <property name="_location" class="ptolemy.kernel.util.Location" value="[65.0, 335.0]">
214
        </property>
215
        <property name="derivedFrom" class="org.kepler.moml.NamedObjIdReferralList" value="urn:lsid:kepler-project.org:actor:204:1">
216
        </property>
217
        <port name="trigger" class="ptolemy.actor.TypedIOPort">
218
            <property name="input"/>
219
            <property name="multiport"/>
220
            <property name="_showName" class="ptolemy.data.expr.SingletonParameter" value="true">
221
            </property>
222
        </port>
223
    </entity>
224
    <entity name="String Constant3" class="ptolemy.actor.lib.StringConst">
225
        <property name="value" class="ptolemy.data.expr.Parameter" value="b">
226
        </property>
227
        <property name="firingCountLimit" class="ptolemy.data.expr.Parameter" value="NONE">
228
        </property>
229
        <property name="NONE" class="ptolemy.data.expr.Parameter" value="0">
230
        </property>
231
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
232
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
233
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Edward Lee</configure></property>
234
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
235
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>&lt;p&gt;The StringConstant actor outputs a string specified via the actor's value parameter.&lt;/p&gt;&#10;&#10;&lt;p&gt;Specifying strings with the StringConstant actor is convenient, as the actor does not require that strings be surrounded by quotes. The actor is often used to specify file paths, which can be selected using the Browse button available in the actor's parameters.&lt;/p&gt;&#10;&#10;&lt;p&gt;Specified string values can include references to parameters within scope (i.e., parameters defined at the same level of the hierarchy or higher). &lt;/p&gt;&#10;&#10;&lt;p&gt;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. &lt;/p&gt;&#10;&#10;</configure></property>
236
<property name="port:output" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An output port that broadcasts a string constant specified by the value parameter.  </configure></property>
237
<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>
238
<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>
239
<property name="prop:value" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The value produced by the actor. Specified strings do not require enclosing quotes. (To include a '$' sign in the string, enter '$$'.)</configure></property>
240
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org/ns/:62508:1499:1">
241
        </property>
242
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.StringConst">
243
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:1052:1">
244
            </property>
245
        </property>
246
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#StringFunctionActor">
247
        </property>
248
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Constant">
249
        </property>
250
        <property name="_icon" class="ptolemy.vergil.icon.BoxedValueIcon">
251
            <property name="attributeName" class="ptolemy.kernel.util.StringAttribute" value="value">
252
            </property>
253
            <property name="displayWidth" class="ptolemy.data.expr.Parameter" value="60">
254
            </property>
255
        </property>
256
        <property name="_location" class="ptolemy.kernel.util.Location" value="[65.0, 285.0]">
257
        </property>
258
        <property name="derivedFrom" class="org.kepler.moml.NamedObjIdReferralList" value="urn:lsid:kepler-project.org:actor:204:1">
259
        </property>
260
        <port name="trigger" class="ptolemy.actor.TypedIOPort">
261
            <property name="input"/>
262
            <property name="multiport"/>
263
            <property name="_showName" class="ptolemy.data.expr.SingletonParameter" value="true">
264
            </property>
265
        </port>
266
    </entity>
267
    <entity name="Expression2" class="ptolemy.actor.lib.Expression">
268
        <property name="expression" class="ptolemy.kernel.util.StringAttribute" value="in.z.a">
269
            <property name="_hide" class="ptolemy.data.expr.Parameter" value="true">
270
            </property>
271
        </property>
272
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
273
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
274
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Xiaojun Liu, Edward A. Lee, Steve Neuendorffer</configure></property>
275
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
276
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>&lt;p&gt;The Expression actor evaluates a specified expression (e.g., an addition or multiplication operation), which may reference the values of user-specified input ports, the current time, or the actor's iteration count. The actor outputs the value of the evaluated expression. &lt;/p&gt;&#10;&#10;&lt;p&gt;Expressions are specified in the Ptolemy expression language via the expression parameter. For more information about the expression language, see http://ptolemy.eecs.berkeley.edu/papers/05/ptIIdesign1-intro/ptIIdesign1-intro.pdf. &lt;/p&gt;&#10;&#10;&lt;p&gt;By default, the expression parameter is empty, and attempting to execute the actor without first specifying an expression generates an error. Expressions can refer to the values of inputs by the port name; to the current time by the identifier &quot;time&quot;; and to the current iteration count by the identifier &quot;iteration.&quot; &lt;/p&gt;&#10;&#10;&lt;p&gt;Input ports are created by the user and correspond to variables used in the specified expression. Currently, the Expression actor does not support input multiports. The actor requires all of its inputs to be present. If inputs are not all present, then the actor will generate an error. &lt;/p&gt;&#10;&#10;&lt;p&gt;Note: the Expression actor can be used instead of many of the arithmetic actors, such as AddSubtract, MultiplyDivide, and TrigFunction. However, those actors will be usually be more efficient, and sometimes more convenient to use.&lt;/p&gt;</configure></property>
277
<property name="port:output" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An output port that broadcasts the value of the evaluated expression. The actor automatically determines the type based on the type of the input.</configure></property>
278
<property name="prop:expression" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An expression to evaluate. Expressions are specified in the Ptolemy expression language. For more information about the expression language, see http://ptolemy.eecs.berkeley.edu/papers/05/ptIIdesign1-intro/ptIIdesign1-intro.pdf. By default, the parameter is empty, and attempting to execute the actor without first specifying an expression generates an error. Expressions can refer to the values of inputs by the port name; to the current time by the identifier &quot;time&quot;; and to the current iteration count by the identifier &quot;iteration.&quot;</configure></property>
279
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org/ns/:62508:1504:6">
280
        </property>
281
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.Expression">
282
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:950:1">
283
            </property>
284
        </property>
285
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#MathOperationActor">
286
        </property>
287
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#GeneralPurpose">
288
        </property>
289
        <property name="_icon" class="ptolemy.vergil.icon.BoxedValueIcon">
290
            <property name="attributeName" class="ptolemy.kernel.util.StringAttribute" value="expression">
291
            </property>
292
            <property name="displayWidth" class="ptolemy.data.expr.Parameter" value="60">
293
            </property>
294
        </property>
295
        <property name="_location" class="ptolemy.kernel.util.Location" value="[500.0, 325.0]">
296
        </property>
297
        <property name="derivedFrom" class="org.kepler.moml.NamedObjIdReferralList" value="urn:lsid:kepler-project.org:actor:75:1">
298
        </property>
299
        <port name="in" class="ptolemy.actor.TypedIOPort">
300
            <property name="input"/>
301
        </port>
302
    </entity>
303
    <relation name="relation" class="ptolemy.actor.TypedIORelation">
304
    </relation>
305
    <relation name="relation2" class="ptolemy.actor.TypedIORelation">
306
    </relation>
307
    <relation name="relation3" class="ptolemy.actor.TypedIORelation">
308
    </relation>
309
    <relation name="relation4" class="ptolemy.actor.TypedIORelation">
310
    </relation>
311
    <relation name="relation5" class="ptolemy.actor.TypedIORelation">
312
    </relation>
313
    <link port="Record Assembler.output" relation="relation4"/>
314
    <link port="Record Assembler.a" relation="relation"/>
315
    <link port="Record Assembler.b" relation="relation2"/>
316
    <link port="Record Assembler2.output" relation="relation5"/>
317
    <link port="Record Assembler2.z" relation="relation4"/>
318
    <link port="Record Assembler2.c" relation="relation3"/>
319
    <link port="String Constant.output" relation="relation"/>
320
    <link port="String Constant2.output" relation="relation3"/>
321
    <link port="String Constant3.output" relation="relation2"/>
322
    <link port="Expression2.in" relation="relation5"/>
323
</entity>