Project

General

Profile

dhCommandLineExec.xml

Dan Homerick, 09/06/2007 10:49 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="dhCommandLineExec" class="ptolemy.actor.TypedCompositeActor">
5
    <property name="_createdBy" class="ptolemy.kernel.attributes.VersionAttribute" value="6.1.devel">
6
    </property>
7
    <property name="SDF Director" class="ptolemy.domains.sdf.kernel.SDFDirector">
8
        <property name="iterations" class="ptolemy.data.expr.Parameter" value="1">
9
        </property>
10
        <property name="vectorizationFactor" class="ptolemy.data.expr.Parameter" value="1">
11
        </property>
12
        <property name="allowDisconnectedGraphs" class="ptolemy.data.expr.Parameter" value="false">
13
        </property>
14
        <property name="allowRateChanges" class="ptolemy.data.expr.Parameter" value="false">
15
        </property>
16
        <property name="constrainBufferSizes" class="ptolemy.data.expr.Parameter" value="true">
17
        </property>
18
        <property name="period" class="ptolemy.data.expr.Parameter" value="0.0">
19
        </property>
20
        <property name="synchronizeToRealTime" class="ptolemy.data.expr.Parameter" value="false">
21
        </property>
22
        <property name="timeResolution" class="ptolemy.moml.SharedParameter" value="1E-10">
23
        </property>
24
        <property name="Scheduler" class="ptolemy.domains.sdf.kernel.SDFScheduler">
25
            <property name="constrainBufferSizes" class="ptolemy.data.expr.Parameter" value="constrainBufferSizes">
26
            </property>
27
        </property>
28
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
29
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
30
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Steve Neuendorffer</configure></property>
31
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
32
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>
33
<p>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).</p>
34

    
35
<p>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. </p>
36

    
37
<p>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 "island" 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.</p>
38
 
39
<p>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 "deadlock" 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.</p>
40

    
41
<p>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.</p>
42

    
43
<p>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. </p>
44

    
45
<p>The number of times a workflow is iterated is controlled by the director's iterations parameter. 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. A value of 1, meaning that the director will run the workflow once, is often the best setting when building an SDF workflow. </p>
46

    
47
<p>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. </p>
48

    
49
<p>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.</p>
50

    
51
<p>For more information about the SDF Director, see the Ptolemy documentation (http://ptolemy.eecs.berkeley.edu/papers/05/ptIIdesign3-domains/ptIIdesign3-domains.pdf).</p>
52

    
53
</configure></property>
54
<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 "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 workflow indicate an error.</configure></property>
55
<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>
56
<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>
57
<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 "1E-10" (which is 10-10). This is an advanced parameter that can usually be left at its default value.</configure></property>
58
<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. A value of 1, meaning that the director will run the workflow once, is often the best setting when building an SDF workflow. </configure></property>
59
<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>
60
<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>
61
<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>
62
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:director:1:1">
63
        </property>
64
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.domains.sdf.kernel.SDFDirector">
65
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:directorclass:1:1">
66
            </property>
67
        </property>
68
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#Director">
69
        </property>
70
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Director">
71
        </property>
72
        <property name="_location" class="ptolemy.kernel.util.Location" value="{345, 50}">
73
        </property>
74
        <property name="keplerFormattedPTIIDocumentation" class="ptolemy.vergil.basic.DocAttribute">
75
            <property name="description" class="ptolemy.data.expr.StringParameter" value="&#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. By default, this parameter is set to &quot;0&quot;. Note that &quot;0&quot; does not mean &quot;no iterations.&quot; Rather, &quot;0&quot; means that the workflow will iterate forever. Values greater than zero specify the actual number of times the director should execute the entire workflow. A value of 1, meaning that the director will run the workflow once, is often the best setting when building an SDF 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;">
76
            </property>
77
            <property name="author" class="ptolemy.kernel.util.StringAttribute" value="Steve Neuendorffer">
78
            </property>
79
            <property name="version" class="ptolemy.kernel.util.StringAttribute" value="null">
80
            </property>
81
            <property name="iterations (parameter)" class="ptolemy.data.expr.StringParameter" value="Specify the number of times a workflow is iterated. By default, this parameter is set to &quot;0&quot;. Note that &quot;0&quot; does not mean &quot;no iterations.&quot; Rather, &quot;0&quot; means that the workflow will iterate forever. Values greater than zero specify the actual number of times the director should execute the entire workflow. A value of 1, meaning that the director will run the workflow once, is often the best setting when building an SDF workflow. ">
82
            </property>
83
            <property name="vectorizationFactor (parameter)" class="ptolemy.data.expr.StringParameter" value="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. ">
84
            </property>
85
            <property name="allowDisconnectedGraphs (parameter)" class="ptolemy.data.expr.StringParameter" value="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.">
86
            </property>
87
            <property name="allowRateChanges (parameter)" class="ptolemy.data.expr.StringParameter" value="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.">
88
            </property>
89
            <property name="constrainBufferSizes (parameter)" class="ptolemy.data.expr.StringParameter" value="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.">
90
            </property>
91
            <property name="period (parameter)" class="ptolemy.data.expr.StringParameter" value="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. ">
92
            </property>
93
            <property name="synchronizeToRealTime (parameter)" class="ptolemy.data.expr.StringParameter" value="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.">
94
            </property>
95
            <property name="timeResolution (parameter)" class="ptolemy.data.expr.StringParameter" value="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.">
96
            </property>
97
        </property>
98
    </property>
99
    <property name="_windowProperties" class="ptolemy.actor.gui.WindowPropertiesAttribute" value="{bounds={34, 25, 813, 718}, maximized=false}">
100
    </property>
101
    <property name="_vergilSize" class="ptolemy.actor.gui.SizeAttribute" value="[470, 585]">
102
    </property>
103
    <property name="_vergilZoomFactor" class="ptolemy.data.expr.ExpertParameter" value="1.0">
104
    </property>
105
    <property name="_vergilCenter" class="ptolemy.data.expr.ExpertParameter" value="{287.0, 269.5}">
106
    </property>
107
    <entity name="Display" class="ptolemy.actor.lib.gui.Display">
108
        <property name="_windowProperties" class="ptolemy.actor.gui.WindowPropertiesAttribute" value="{bounds={298, 277, 428, 214}, maximized=false}">
109
        </property>
110
        <property name="_paneSize" class="ptolemy.actor.gui.SizeAttribute" value="[418, 158]">
111
        </property>
112
        <property name="rowsDisplayed" class="ptolemy.data.expr.Parameter" value="10">
113
        </property>
114
        <property name="columnsDisplayed" class="ptolemy.data.expr.Parameter" value="40">
115
        </property>
116
        <property name="suppressBlankLines" class="ptolemy.data.expr.Parameter" value="false">
117
        </property>
118
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
119
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
120
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Yuhong Xiong, Edward A. Lee</configure></property>
121
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
122
<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>
123

    
124
<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>
125

    
126
<p>If the input is a string token, then the actor strips the surrounding quotation marks before displaying the value.</p> 
127

    
128
<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>
129

    
130
<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>
131
<property name="port:input" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>A multiport that accepts tokens of any type.</configure></property>
132
<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>
133
<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>
134
<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>
135
<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>
136
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:actor:7:1">
137
        </property>
138
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.gui.Display">
139
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:883:1">
140
            </property>
141
        </property>
142
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#TextualOutputActor">
143
        </property>
144
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#TextualOutput">
145
        </property>
146
        <property name="_location" class="ptolemy.kernel.util.Location" value="[475.0, 335.0]">
147
        </property>
148
    </entity>
149
    <entity name="String Constant" class="ptolemy.actor.lib.StringConst">
150
        <property name="firingCountLimit" class="ptolemy.data.expr.Parameter" value="NONE">
151
        </property>
152
        <property name="NONE" class="ptolemy.data.expr.Parameter" value="0">
153
        </property>
154
        <property name="value" class="ptolemy.data.expr.Parameter" value="ls">
155
        </property>
156
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
157
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
158
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Edward Lee</configure></property>
159
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
160
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure><p>The StringConstant actor outputs a string specified via the actor's value parameter.</p>
161

    
162
<p>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.</p>
163

    
164
<p>Specified string values can include references to parameters within scope (i.e., parameters defined at the same level of the hierarchy or higher). </p>
165

    
166
<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>
167

    
168
</configure></property>
169
<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>
170
<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>
171
<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>
172
<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>
173
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:actor:204:1">
174
        </property>
175
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.StringConst">
176
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:1052:1">
177
            </property>
178
        </property>
179
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#StringFunctionActor">
180
        </property>
181
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Constant">
182
        </property>
183
        <property name="_icon" class="ptolemy.vergil.icon.BoxedValueIcon">
184
            <property name="attributeName" class="ptolemy.kernel.util.StringAttribute" value="value">
185
            </property>
186
            <property name="displayWidth" class="ptolemy.data.expr.Parameter" value="60">
187
            </property>
188
        </property>
189
        <property name="_location" class="ptolemy.kernel.util.Location" value="{100, 220}">
190
        </property>
191
    </entity>
192
    <entity name="Command Line Exec" class="org.sdm.spa.CommandLineExec">
193
        <property name="outputFile" class="ptolemy.actor.parameters.FilePortParameter" value="">
194
        </property>
195
        <property name="environment" class="ptolemy.data.expr.Parameter" value="{{name = &quot;&quot;, value = &quot;&quot;}}">
196
        </property>
197
        <property name="directory" class="ptolemy.data.expr.FileParameter" value="/home">
198
        </property>
199
        <property name="outputLineByLine" class="ptolemy.data.expr.Parameter" value="false">
200
        </property>
201
        <property name="waitForProcess" class="ptolemy.data.expr.Parameter" value="false">
202
        </property>
203
        <property name="hasTrigger" class="ptolemy.data.expr.Parameter" value="false">
204
        </property>
205
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
206
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
207
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>
208
Edward A. Lee</configure></property>
209
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
210
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure><p>The CommandLineExec actor generates and executes a Unix command. The actor is given a command string (e.g., ls or C:/Program Files/Internet Explorer/IEXPLORE.EXE) and, optionally, one or more arguments, strings, and input and output files.</p> 
211

    
212
<p>Once the execution is complete, the actor will output the results as well as any execution errors. </p>
213

    
214
<p>The CommandLineExec actor depends on system-specific executables and is operating-system specific.</p>
215

    
216

    
217
</configure></property>
218
<property name="port:inputStream" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An input port that accepts strings to pass to the command (e.g., a file name)</configure></property>
219
<property name="port:arguments" class="ptolemy.kernel.util.ConfigurableAttribute"><configure> An input port that accepts an argument or arguments (e.g., -r or –al), which will be passed to the command. If the infileHandle parameter is used, this port can be empty.</configure></property>
220
<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.
221
</configure></property>
222
<property name="port:output" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An output port that broadcasts the result stream of the command. The port broadcasts only if no outputFile is specified.
223
</configure></property>
224
<property name="port:command" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An input port accepting the command to execute.</configure></property>
225
<property name="port:infileHandle" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An optional input port that accepts the path to an input file. Used an input file if the command accepts one instead of a list of arguments.
226
</configure></property>
227
<property name="port:outputFile" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An input port accepting the path to the output file. To output command results to a file, specify an output file name.</configure></property>
228
<property name="port:exitCode" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An output port that indicates whether or not the command executed successfully. The exit code will be 1 if the command is success. 
229
</configure></property>
230
<property name="port:outfileHandle" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An output port that broadcasts the path to the output file, if specified. An output file replaces the standard output. 
231
</configure></property>
232
<property name="prop:environment" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>An array of records that name an environmental variable and a value:
233
 
234
  {{name = "NAME1", value = "value1"}...}
235
  
236
Where NAME1 is the name of the environmental variable, and value1 is the value. 
237
For example {{name = "PTII", value = "c:/ptII"}} would set the value of PTII to c:/ptII. If the parameter is set to {{name="", value = ""}}, then the environment from the parent process is used. If environmental variables are set with the parameter, the parent values may not be passed to the process. To view the current environment, use the "env" command.
238
 </configure></property>
239
<property name="prop:directory" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The directory in which to execute the command. The default value of this parameter $CWD, which represents the user's current working or home directory. </configure></property>
240
<property name="prop:outputLineByLine" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Select to broadcast the output of the command line by line. The parameter is used to format the output if no outputFile is specified.</configure></property>
241
<property name="prop:waitForProcess" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Select to    indicate that the command should finish executing before the actor outputs results. By default, the actor will stream command results as they are generated. </configure></property>
242
<property name="prop:outputFile" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The path to the output file. Specify an output file to output command results to a file.</configure></property>
243
<property name="prop:command" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>The command to execute.</configure></property>
244
<property name="prop:hasTrigger" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Select to activate a trigger input port.</configure></property>
245
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:actor:185:1">
246
        </property>
247
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="org.sdm.spa.CommandLineExec">
248
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:1040:1">
249
            </property>
250
        </property>
251
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#ExternalExecutionEnvironmentActor">
252
        </property>
253
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#UnixCommand">
254
        </property>
255
        <property name="_location" class="ptolemy.kernel.util.Location" value="[300.0, 280.0]">
256
        </property>
257
        <property name="" class="ptolemy.vergil.basic.DocAttribute">
258
            <property name="description" class="ptolemy.data.expr.StringParameter" value="&lt;p&gt;The CommandLineExec actor generates and executes a Unix command. The actor is given a command string (e.g., ls or C:/Program Files/Internet Explorer/IEXPLORE.EXE) and, optionally, one or more arguments, strings, and input and output files.&lt;/p&gt; &#10;&#10;&lt;p&gt;Once the execution is complete, the actor will output the results as well as any execution errors. &lt;/p&gt;&#10;&#10;&lt;p&gt;The CommandLineExec actor depends on system-specific executables and is operating-system specific.&lt;/p&gt;&#10;&#10;&#10;">
259
            </property>
260
            <property name="author" class="ptolemy.kernel.util.StringAttribute" value="&#10;Edward A. Lee">
261
            </property>
262
            <property name="version" class="ptolemy.kernel.util.StringAttribute" value="null">
263
            </property>
264
            <property name="environment (parameter)" class="ptolemy.data.expr.StringParameter" value="An array of records that name an environmental variable and a value:&#10; &#10;  {{name = &quot;NAME1&quot;, value = &quot;value1&quot;}...}&#10;  &#10;Where NAME1 is the name of the environmental variable, and value1 is the value. &#10;For example {{name = &quot;PTII&quot;, value = &quot;c:/ptII&quot;}} would set the value of PTII to c:/ptII. If the parameter is set to {{name=&quot;&quot;, value = &quot;&quot;}}, then the environment from the parent process is used. If environmental variables are set with the parameter, the parent values may not be passed to the process. To view the current environment, use the &quot;env&quot; command.&#10; ">
265
            </property>
266
            <property name="directory (parameter)" class="ptolemy.data.expr.StringParameter" value="The directory in which to execute the command. The default value of this parameter $CWD, which represents the user's current working or home directory. ">
267
            </property>
268
            <property name="outputLineByLine (parameter)" class="ptolemy.data.expr.StringParameter" value="Select to broadcast the output of the command line by line. The parameter is used to format the output if no outputFile is specified.">
269
            </property>
270
            <property name="waitForProcess (parameter)" class="ptolemy.data.expr.StringParameter" value="Select to    indicate that the command should finish executing before the actor outputs results. By default, the actor will stream command results as they are generated. ">
271
            </property>
272
            <property name="hasTrigger (parameter)" class="ptolemy.data.expr.StringParameter" value="Select to activate a trigger input port.">
273
            </property>
274
            <property name="arguments (port)" class="ptolemy.kernel.util.StringAttribute" value=" An input port that accepts an argument or arguments (e.g., -r or –al), which will be passed to the command. If the infileHandle parameter is used, this port can be empty.">
275
            </property>
276
            <property name="inputStream (port)" class="ptolemy.kernel.util.StringAttribute" value="An input port that accepts strings to pass to the command (e.g., a file name)">
277
            </property>
278
            <property name="infileHandle (port)" class="ptolemy.kernel.util.StringAttribute" value="An optional input port that accepts the path to an input file. Used an input file if the command accepts one instead of a list of arguments.&#10;">
279
            </property>
280
            <property name="trigger (port)" class="ptolemy.kernel.util.StringAttribute" value="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.&#10;">
281
            </property>
282
            <property name="outfileHandle (port)" class="ptolemy.kernel.util.StringAttribute" value="An output port that broadcasts the path to the output file, if specified. An output file replaces the standard output. &#10;">
283
            </property>
284
            <property name="exitCode (port)" class="ptolemy.kernel.util.StringAttribute" value="An output port that indicates whether or not the command executed successfully. The exit code will be 1 if the command is success. &#10;">
285
            </property>
286
            <property name="output (port)" class="ptolemy.kernel.util.StringAttribute" value="An output port that broadcasts the result stream of the command. The port broadcasts only if no outputFile is specified.&#10;">
287
            </property>
288
            <property name="command (port)" class="ptolemy.kernel.util.StringAttribute" value="An input port accepting the command to execute.">
289
            </property>
290
            <property name="outputFile (port)" class="ptolemy.kernel.util.StringAttribute" value="An input port accepting the path to the output file. To output command results to a file, specify an output file name.">
291
            </property>
292
            <property name="outputFile (parameter)" class="ptolemy.data.expr.StringParameter" value="The path to the output file. Specify an output file to output command results to a file.">
293
            </property>
294
            <property name="command (parameter)" class="ptolemy.data.expr.StringParameter" value="The command to execute.">
295
            </property>
296
        </property>
297
        <port name="trigger" class="ptolemy.actor.TypedIOPort">
298
            <property name="input"/>
299
            <property name="_hide" class="ptolemy.data.expr.SingletonParameter" value="true">
300
            </property>
301
        </port>
302
    </entity>
303
    <entity name="String Constant2" class="ptolemy.actor.lib.StringConst">
304
        <property name="firingCountLimit" class="ptolemy.data.expr.Parameter" value="NONE">
305
        </property>
306
        <property name="NONE" class="ptolemy.data.expr.Parameter" value="0">
307
        </property>
308
        <property name="value" class="ptolemy.data.expr.Parameter" value="-l">
309
        </property>
310
<property name="KeplerDocumentation" class="ptolemy.vergil.basic.KeplerDocumentationAttribute">
311
<property name="description" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
312
<property name="author" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>Edward Lee</configure></property>
313
<property name="version" class="ptolemy.kernel.util.ConfigurableAttribute"><configure>null</configure></property>
314
<property name="userLevelDocumentation" class="ptolemy.kernel.util.ConfigurableAttribute"><configure><p>The StringConstant actor outputs a string specified via the actor's value parameter.</p>
315

    
316
<p>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.</p>
317

    
318
<p>Specified string values can include references to parameters within scope (i.e., parameters defined at the same level of the hierarchy or higher). </p>
319

    
320
<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>
321

    
322
</configure></property>
323
<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>
324
<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>
325
<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>
326
<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>
327
</property>        <property name="entityId" class="org.kepler.moml.NamedObjId" value="urn:lsid:kepler-project.org:actor:204:1">
328
        </property>
329
        <property name="class" class="ptolemy.kernel.util.StringAttribute" value="ptolemy.actor.lib.StringConst">
330
            <property name="id" class="ptolemy.kernel.util.StringAttribute" value="urn:lsid:kepler-project.org:class:1052:1">
331
            </property>
332
        </property>
333
        <property name="semanticType00" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:1:1#StringFunctionActor">
334
        </property>
335
        <property name="semanticType11" class="org.kepler.sms.SemanticType" value="urn:lsid:localhost:onto:2:1#Constant">
336
        </property>
337
        <property name="_icon" class="ptolemy.vergil.icon.BoxedValueIcon">
338
            <property name="attributeName" class="ptolemy.kernel.util.StringAttribute" value="value">
339
            </property>
340
            <property name="displayWidth" class="ptolemy.data.expr.Parameter" value="60">
341
            </property>
342
        </property>
343
        <property name="_location" class="ptolemy.kernel.util.Location" value="{100, 310}">
344
        </property>
345
    </entity>
346
    <relation name="relation" class="ptolemy.actor.TypedIORelation">
347
        <property name="width" class="ptolemy.data.expr.Parameter" value="1">
348
        </property>
349
    </relation>
350
    <relation name="relation2" class="ptolemy.actor.TypedIORelation">
351
        <property name="width" class="ptolemy.data.expr.Parameter" value="1">
352
        </property>
353
    </relation>
354
    <relation name="relation3" class="ptolemy.actor.TypedIORelation">
355
        <property name="width" class="ptolemy.data.expr.Parameter" value="1">
356
        </property>
357
    </relation>
358
    <relation name="relation4" class="ptolemy.actor.TypedIORelation">
359
        <property name="width" class="ptolemy.data.expr.Parameter" value="1">
360
        </property>
361
    </relation>
362
    <relation name="relation5" class="ptolemy.actor.TypedIORelation">
363
        <property name="width" class="ptolemy.data.expr.Parameter" value="1">
364
        </property>
365
    </relation>
366
    <link port="Display.input" relation="relation2"/>
367
    <link port="Display.input" relation="relation3"/>
368
    <link port="Display.input" relation="relation4"/>
369
    <link port="String Constant.output" relation="relation"/>
370
    <link port="Command Line Exec.command" relation="relation"/>
371
    <link port="Command Line Exec.arguments" relation="relation5"/>
372
    <link port="Command Line Exec.outfileHandle" relation="relation4"/>
373
    <link port="Command Line Exec.exitCode" relation="relation3"/>
374
    <link port="Command Line Exec.output" relation="relation2"/>
375
    <link port="String Constant2.output" relation="relation5"/>
376
</entity>