[kepler-dev] Kepler actor icons

Bertram Ludaescher ludaesch at ucdavis.edu
Wed Jul 13 16:54:49 PDT 2005


We talk about different user groups for sure (as is now acknowledge
generally ;-)

But we also talk about very different kinds of uses cases! (not just
different user groups) 

Some "workflow" use cases might very well have some components that
correspond to numerically solving differential equations. Other
workflow use cases might be just darn complicated by their nature,
i.e., inherently. No usability engineering (or software engineering
for that matter) can simplify the inherent complexity of those complex
problems.

But this seems obvious. Simple linear pipelines can capture certain
linear workflows. But when your problem requires complex data and
control flow, nesting, complex iteration and/or recursion etc. then
one has to bite the bullet, no matter what. Obviously icons don't do
much to help this problem. Higher order functions (map, foldl,
foldr,...) or other workflow patterns as recently adopted by Triana
(from the van der Aalst type of pattern) do. 

We should focus more on these things too. Icons (and the discussion
about them) should focus on those used in toolbars, menus etc. 

For actors they are overrated (IMHO)

Bertram

Laura L. Downey writes:
 > Thanks for the clarification on the actor being fired versus iteration  - I
 > wasn't positive I had understood your meaning correctly the first time. ;-)
 > 
 >  
 > 
 > Yes I agree with your concern Dan.  It is going to take a certain level of
 > expertise and knowledge to create workflows from scratch than it is to use
 > them or modify them.  We are definitely talking about different user groups
 > as Bertram and others have mentioned before.  I don't know if it is possible
 > to abstract to a level in all cases where someone won't have to have some
 > computer science or programming knowledge.  I've been envisioning that in
 > some cases with really complex models a domain scientist will conceptually
 > know what they want to do but will have to work with an IT person to get
 > things implemented unless they are that "rare" hybrid user of both domain
 > scientist and competent programmer.  We definitely have some challenges
 > ahead.  But hey it would be boring otherwise.. ;-)
 > 
 >  
 > 
 > Laura L. Downey
 > Senior Usability Engineer
 > LTER Network Office
 > Department of Biology, MSC03 2020
 > 1 University of New Mexico
 > Albuquerque, NM  87131-0001
 > 505.277.3157 phone
 > 
 > 505.277-2541 fax
 > ldowney at lternet.edu
 > 
 >  
 > 
 >   _____  
 > 
 > From: Dan Higgins [mailto:higgins at nceas.ucsb.edu] 
 > Sent: Wednesday, July 13, 2005 11:56 AM
 > To: Laura L. Downey
 > Cc: 'Kepler-Dev'; Mark Schildhauer
 > Subject: Re: Kepler actor icons
 > 
 >  
 > 
 > Laura (and other Kepler developers/users),
 > 
 >     One slight clarification - the numbers in the icons in the examples are
 > the number of times an actor is to be fired, not the iteration number, but
 > including both some parameters of this sort and the iteration number while
 > running would be good as you mentioned.
 > 
 >     As far as 'for some users the notion of "adding tokens" will have no
 > meaning' - Good point; I was the mistake of using a technical term that most
 > user wouldn;t initially recognize. [A 'token' is just a block of data passed
 > between actors.] But this does bring up a point that has been bothering me
 > for awhile. It looks to me like an understanding of some computer science
 > concepts are essential to creating new workflows in Kepler and deciding
 > which Computational models (Directors) to use. ['Token' is an example,
 > although we don't have to call it a 'token'.]  This notion has been enhanced
 > by recent work in trying to create loops and iterations and some discussions
 > on kepler-dev. I guess I am just expressing a concern that we have a LOT of
 > work to do in trying to make Kepler useful to someone wtihout requiring a
 > considerable start up effort.
 > 
 > Dan
 > 
 > -----
 > 
 > Laura L. Downey wrote: 
 > 
 > Thanks Dan.  Interesting comments.  I hadn't seen these icons before and
 > they have some of the same characteristics I've been proposing - simple
 > representatations (e.g., sequence to array and array to sequence).  I
 > support the idea of adding the number somewhere if we are talking about a
 > repeating process within an actor.  That would be good feedback to the user
 > when executing the workflow.  Right now the plan is to highlight an actor as
 > it is executing and we could add the number somewhere on the actor if we
 > have a repeating process happening within that actor and the user could see
 > the "counting up or down" happening etc.
 > 
 >  
 > 
 > Just a comment though, for some users the notion of "adding tokens" will
 > have no meaning.  That is a computer science perspective not necessarily an
 > ecologist or biologist perspective.  However, the simple act of just having
 > numbers iterate over a repeating process will let a user know that things
 > are happening and that is good feedback as I mentioned before.
 > 
 >  
 > 
 > As to a parameter being embedded within an actor, my comment there is that
 > we would somehow need to communicate that it is a parameter (and not an
 > iteration of a repeating process).  We could maybe do this by parameters
 > always being in the bottom left hand corner and iterations being in the
 > bottom right hand corner etc.  Of course this only deals with the notion of
 > one parameter - if an actor has more than one parameter, say 5 or so then
 > that would be a problem displaying all the parameters on an actor because we
 > would run out of room.
 > 
 >  
 > 
 > p.s. I'll be publishing the final proposed visual re-design most likely
 > within the next month or so incorporating feedback from our last meeting.
 > Basically I'm going to go with the set we have (about 25 of so) with the
 > option that people can add their own icons using the proposed color (teal
 > and white) of the actors.
 > 
 >  
 > 
 > Laura L. Downey
 > Senior Usability Engineer
 > LTER Network Office
 > Department of Biology, MSC03 2020
 > 1 University of New Mexico
 > Albuquerque, NM  87131-0001
 > 505.277.3157 phone
 > 
 > 505.277-2541 fax
 > ldowney at lternet.edu
 > 
 >  
 > 
 >   _____  
 > 
 > From: Dan Higgins [mailto:higgins at nceas.ucsb.edu] 
 > Sent: Wednesday, July 13, 2005 11:05 AM
 > To: Laura L. Downey; Kepler-Dev
 > Subject: Kepler actor icons
 > 
 >  
 > 
 > Laura,
 > 
 >     In out continuing discussion of Kepler actor icons, take a look at the
 > workflow below (from an example from Edward Lee about how to handle nested
 > loops). This is an example of some more interesing icons that are already in
 > PTII and Keper (rather than the default blue triangle). In particular, the
 > SequenceToArray actually shows the process of putting tokens into an array
 > and the ArrayToSequence the inverse. More interestingly, the number '5' on
 > the icons is a parameter of the actor and it is 'dynamic', i.e. it changes
 > as the parameter is changed, avoiding the need to open the actor! (This also
 > occurs for the Repeat actor, which has an icon that depicts its function and
 > shows a dynamic parameter.)
 > 
 > Dan
 > 
 > 
 > 
 > 
 > 
 > 
 > 
 > -- 
 > *******************************************************************
 > Dan Higgins                                  higgins at nceas.ucsb.edu
 > http://www.nceas.ucsb.edu/    Ph: 805-893-5127
 > National Center for Ecological Analysis and Synthesis (NCEAS) 
 > Marine Science Building - Room 3405
 > Santa Barbara, CA 93195
 > *******************************************************************
 > 
 > 
 > 
 > 
 > 
 > 
 > -- 
 > *******************************************************************
 > Dan Higgins                                  higgins at nceas.ucsb.edu
 > http://www.nceas.ucsb.edu/    Ph: 805-893-5127
 > National Center for Ecological Analysis and Synthesis (NCEAS) 
 > Marine Science Building - Room 3405
 > Santa Barbara, CA 93195
 > *******************************************************************
 > <html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"
 > xmlns:ns0="urn:schemas-microsoft-com:office:smarttags">
 > 
 > <head>
 > <meta http-equiv=Content-Type content="text/html; charset=us-ascii">
 > <meta name=Generator content="Microsoft Word 11 (filtered medium)">
 > <!--[if !mso]>
 > <style>
 > v\:* {behavior:url(#default#VML);}
 > o\:* {behavior:url(#default#VML);}
 > w\:* {behavior:url(#default#VML);}
 > .shape {behavior:url(#default#VML);}
 > </style>
 > <![endif]--><o:SmartTagType
 >  namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"/>
 > <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 >  name="PlaceType"/>
 > <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 >  name="PostalCode"/>
 > <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 >  name="City"/>
 > <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 >  name="State"/>
 > <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 >  name="place"/>
 > <!--[if !mso]>
 > <style>
 > st1\:*{behavior:url(#default#ieooui) }
 > </style>
 > <![endif]-->
 > <style>
 > <!--
 >  /* Font Definitions */
 >  @font-face
 > 	{font-family:Tahoma;
 > 	panose-1:2 11 6 4 3 5 4 4 2 4;}
 >  /* Style Definitions */
 >  p.MsoNormal, li.MsoNormal, div.MsoNormal
 > 	{margin:0in;
 > 	margin-bottom:.0001pt;
 > 	font-size:12.0pt;
 > 	font-family:"Times New Roman";
 > 	color:black;}
 > a:link, span.MsoHyperlink
 > 	{color:blue;
 > 	text-decoration:underline;}
 > a:visited, span.MsoHyperlinkFollowed
 > 	{color:blue;
 > 	text-decoration:underline;}
 > pre
 > 	{margin:0in;
 > 	margin-bottom:.0001pt;
 > 	font-size:10.0pt;
 > 	font-family:"Courier New";
 > 	color:black;}
 > tt
 > 	{font-family:"Courier New";}
 > span.EmailStyle19
 > 	{mso-style-type:personal;
 > 	font-family:Arial;
 > 	color:navy;}
 > span.EmailStyle20
 > 	{mso-style-type:personal-reply;
 > 	font-family:Arial;
 > 	color:navy;}
 > @page Section1
 > 	{size:8.5in 11.0in;
 > 	margin:1.0in 1.25in 1.0in 1.25in;}
 > div.Section1
 > 	{page:Section1;}
 > -->
 > </style>
 > <!--[if gte mso 9]><xml>
 >  <o:shapedefaults v:ext="edit" spidmax="1026" />
 > </xml><![endif]--><!--[if gte mso 9]><xml>
 >  <o:shapelayout v:ext="edit">
 >   <o:idmap v:ext="edit" data="1" />
 >  </o:shapelayout></xml><![endif]-->
 > </head>
 > 
 > <body bgcolor=white lang=EN-US link=blue vlink=blue>
 > 
 > <div class=Section1>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'>Thanks for the clarification on the actor
 > being fired versus iteration &nbsp;&#8211; I wasn&#8217;t positive I had
 > understood your meaning correctly the first time. ;-)<o:p></o:p></span></font></p>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'>Yes I agree with your concern Dan.&nbsp; It
 > is going to take a certain level of expertise and knowledge to create workflows
 > from scratch than it is to use them or modify them.&nbsp; We are definitely
 > talking about different user groups as Bertram and others have mentioned
 > before.&nbsp; I don&#8217;t know if it is possible to abstract to a level in
 > all cases where someone won&#8217;t have to have some computer science or
 > programming knowledge.&nbsp; I&#8217;ve been envisioning that in some cases
 > with really complex models a domain scientist will conceptually know what they
 > want to do but will have to work with an IT person to get things implemented
 > unless they are that &#8220;rare&#8221; hybrid user of both domain scientist
 > and competent programmer.&nbsp; We definitely have some challenges ahead.&nbsp;
 > But hey it would be boring otherwise&#8230;. ;-)<o:p></o:p></span></font></p>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>
 > 
 > <div>
 > 
 > <p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
 > style='font-size:12.0pt'>Laura L. Downey<br>
 > Senior Usability Engineer<br>
 > LTER Network Office<br>
 > Department of Biology, MSC03 2020<br>
 > 1 University of </span></font><font color=black><span style='color:windowtext'><ns0:State
 >  w:insAuthor="Laura L. Downey" w:insDate="2005-07-13T12:07:00Z"
 >  w:endInsAuthor="Laura L. Downey" w:endInsDate="2005-07-13T12:07:00Z"><ns0:place
 >   w:insAuthor="Laura L. Downey" w:insDate="2005-07-13T12:07:00Z"
 >   w:endInsAuthor="Laura L. Downey" w:endInsDate="2005-07-13T12:07:00Z"><st1:State
 >   w:st="on"><st1:place w:st="on"><font color=black><span style='color:black'>New
 >     Mexico</span></font></st1:place></st1:State></ns0:place></ns0:State></span></font><br>
 > <font color=black><span style='color:windowtext'><ns0:place
 >  w:insAuthor="Laura L. Downey" w:insDate="2005-07-13T12:07:00Z"
 >  w:endInsAuthor="Laura L. Downey" w:endInsDate="2005-07-13T12:07:00Z"><ns0:City
 >   w:insAuthor="Laura L. Downey" w:insDate="2005-07-13T12:07:00Z"
 >   w:endInsAuthor="Laura L. Downey" w:endInsDate="2005-07-13T12:07:00Z"><st1:place
 >   w:st="on"><st1:City w:st="on"><font color=black><span style='color:black'>Albuquerque</span></font></st1:City></ns0:City></st1:place><font
 >  color=black><span style='color:black'>, </span></font><ns0:State
 >   w:insAuthor="Laura L. Downey" w:insDate="2005-07-13T12:07:00Z"
 >   w:endInsAuthor="Laura L. Downey" w:endInsDate="2005-07-13T12:07:00Z"><st1:State
 >   w:st="on"><font color=black><span style='color:black'>NM</span></font></st1:State></ns0:State><font
 >  color=black><span style='color:black'>&nbsp; </span></font><ns0:PostalCode
 >   w:insAuthor="Laura L. Downey" w:insDate="2005-07-13T12:07:00Z"
 >   w:endInsAuthor="Laura L. Downey" w:endInsDate="2005-07-13T12:07:00Z"><st1:PostalCode
 >   w:st="on"><font color=black><span style='color:black'>87131-0001</span></font></st1:PostalCode></ns0:PostalCode></ns0:place></span></font><br>
 > 505.277.3157 phone<o:p></o:p></p>
 > 
 > <p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
 > style='font-size:12.0pt'>505.277-2541 fax<br>
 > <a href="mailto:ldowney at lternet.edu">ldowney at lternet.edu</a><o:p></o:p></span></font></p>
 > 
 > <p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
 > style='font-size:12.0pt'>&nbsp;</span><o:p></o:p></font></p>
 > 
 > </div>
 > 
 > <div>
 > 
 > <div class=MsoNormal align=center style='text-align:center'><font size=3
 > color=black face="Times New Roman"><span style='font-size:12.0pt;color:windowtext'>
 > 
 > <hr size=2 width="100%" align=center tabindex=-1>
 > 
 > </span></font></div>
 > 
 > <p class=MsoNormal><b><font size=2 color=black face=Tahoma><span
 > style='font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight:bold'>From:</span></font></b><font
 > size=2 color=black face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;
 > color:windowtext'> Dan Higgins [mailto:higgins at nceas.ucsb.edu] <br>
 > <b><span style='font-weight:bold'>Sent:</span></b> Wednesday, July 13, 2005
 > 11:56 AM<br>
 > <b><span style='font-weight:bold'>To:</span></b> Laura L. Downey<br>
 > <b><span style='font-weight:bold'>Cc:</span></b> 'Kepler-Dev'; Mark Schildhauer<br>
 > <b><span style='font-weight:bold'>Subject:</span></b> Re: Kepler actor icons</span></font><font
 > color=black><span style='color:windowtext'><o:p></o:p></span></font></p>
 > 
 > </div>
 > 
 > <p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
 > style='font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>
 > 
 > <p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
 > style='font-size:12.0pt'>Laura (and other Kepler developers/users),<br>
 > <br>
 > &nbsp;&nbsp;&nbsp; One slight clarification - the numbers in the icons in the
 > examples are the number of times an actor is to be fired, not the iteration
 > number, but including both some parameters of this sort and the iteration
 > number while running would be good as you mentioned.<br>
 > <br>
 > &nbsp;&nbsp;&nbsp; As far as '</span></font><font size=2 color=navy face=Arial><span
 > style='font-size:10.0pt;font-family:Arial;color:navy'>for some users the notion
 > of &#8220;adding tokens&#8221; will have no meaning' - Good point; I was the
 > mistake of using a technical term that most user wouldn;t initially recognize.
 > [A 'token' is just a block of data passed between actors.] But this does bring
 > up a point that has been bothering me for awhile. It looks to me like an
 > understanding of some computer science concepts are essential to creating new
 > workflows in Kepler and deciding which Computational models (Directors) to use.
 > ['Token' is an example, although we don't have to call it a 'token'.]&nbsp;
 > This notion has been enhanced by recent work in trying to create loops and
 > iterations and some discussions on kepler-dev. I guess I am just expressing a
 > concern that we have a LOT of work to do in trying to make Kepler useful to
 > someone wtihout requiring a considerable start up effort.<br>
 > <br>
 > Dan<br>
 > <br>
 > -----<br>
 > </span></font><br>
 > Laura L. Downey wrote: <o:p></o:p></p>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'><u1:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"><u1:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"><u1:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u1:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u1:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u1:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><!--[if gte mso 9]><xml>
 >        <u1:shapedefaults u2:ext="edit" spidmax="1026"/>
 > </xml><![endif]--><!--[if gte mso 9]><xml>
 >        <u1:shapelayout u3:ext="edit">
 >         <u1:idmap u3:ext="edit" data="1"/>
 >        </u1:shapelayout>
 > </xml><![endif]--></u1:SmartTagType></u1:SmartTagType></u1:SmartTagType></u1:SmartTagType></u1:SmartTagType></u1:SmartTagType>Thanks
 > Dan.&nbsp; Interesting comments.&nbsp; I hadn&#8217;t seen these icons before
 > and they have some of the same characteristics I&#8217;ve been proposing
 > &#8211; simple representatations (e.g., sequence to array and array to
 > sequence).&nbsp; I support the idea of adding the number somewhere if we are
 > talking about a repeating process within an actor.&nbsp; That would be good
 > feedback to the user when executing the workflow.&nbsp; Right now the plan is
 > to highlight an actor as it is executing and we could add the number somewhere
 > on the actor if we have a repeating process happening within that actor and the
 > user could see the &#8220;counting up or down&#8221; happening etc.<u1:p></u1:p></span></font><o:p></o:p></p>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'><u1:p>&nbsp;</u1:p></span></font><o:p></o:p></p>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'>Just a comment though, for some users the
 > notion of &#8220;adding tokens&#8221; will have no meaning.&nbsp; That is a
 > computer science perspective not necessarily an ecologist or biologist
 > perspective.&nbsp; However, the simple act of just having numbers iterate over
 > a repeating process will let a user know that things are happening and that is
 > good feedback as I mentioned before.<u1:p></u1:p></span></font><o:p></o:p></p>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'><u1:p>&nbsp;</u1:p></span></font><o:p></o:p></p>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'>As to a parameter being embedded within an
 > actor, my comment there is that we would somehow need to communicate that it is
 > a parameter (and not an iteration of a repeating process).&nbsp; We could maybe
 > do this by parameters always being in the bottom left hand corner and
 > iterations being in the bottom right hand corner etc.&nbsp; Of course this only
 > deals with the notion of one parameter &#8211; if an actor has more than one
 > parameter, say 5 or so then that would be a problem displaying all the
 > parameters on an actor because we would run out of room.<u1:p></u1:p></span></font><o:p></o:p></p>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'><u1:p>&nbsp;</u1:p></span></font><o:p></o:p></p>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'>p.s. I&#8217;ll be publishing the final
 > proposed visual re-design most likely within the next month or so incorporating
 > feedback from our last meeting.&nbsp; Basically I&#8217;m going to go with the
 > set we have (about 25 of so) with the option that people can add their own
 > icons using the proposed color (teal and white) of the actors.<u1:p></u1:p></span></font><o:p></o:p></p>
 > 
 > <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
 > 10.0pt;font-family:Arial;color:navy'><u1:p>&nbsp;</u1:p></span></font><o:p></o:p></p>
 > 
 > <div>
 > 
 > <p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
 > style='font-size:12.0pt'>Laura L. Downey<br>
 > Senior Usability Engineer<br>
 > LTER Network Office<br>
 > Department of Biology, MSC03 2020<br>
 > 1 University of <ns0:State u4:insauthor="Laura L. Downey" u4:insdate="2005-07-13T11:10:00Z" u4:endinsauthor="Laura L. Downey" u4:endinsdate="2005-07-13T11:10:00Z"><ns0:place u4:insauthor="Laura L. Downey" u4:insdate="2005-07-13T11:10:00Z" u4:endinsauthor="Laura L. Downey" u4:endinsdate="2005-07-13T11:10:00Z"><st1:State u4:st="on"><st1:place u4:st="on">New
 > Mexico</st1:place></st1:State></ns0:place></ns0:State><br>
 > <ns0:place u4:insauthor="Laura L. Downey" u4:insdate="2005-07-13T11:10:00Z" u4:endinsauthor="Laura L. Downey" u4:endinsdate="2005-07-13T11:10:00Z"><ns0:City u4:insauthor="Laura L. Downey" u4:insdate="2005-07-13T11:10:00Z" u4:endinsauthor="Laura L. Downey" u4:endinsdate="2005-07-13T11:10:00Z"><st1:place u4:st="on"><st1:City u4:st="on">Albuquerque</st1:City></st1:place></ns0:City>,
 > <ns0:State u4:insauthor="Laura L. Downey" u4:insdate="2005-07-13T11:10:00Z" u4:endinsauthor="Laura L. Downey" u4:endinsdate="2005-07-13T11:10:00Z"><st1:State u4:st="on">NM</st1:State></ns0:State>&nbsp;
 > <ns0:PostalCode u4:insauthor="Laura L. Downey" u4:insdate="2005-07-13T11:10:00Z" u4:endinsauthor="Laura L. Downey" u4:endinsdate="2005-07-13T11:10:00Z"><st1:PostalCode u4:st="on">87131-0001</st1:PostalCode></ns0:PostalCode></ns0:place><br>
 > 505.277.3157 phone<o:p></o:p></span></font><u1:p></u1:p></p>
 > 
 > <p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
 > style='font-size:12.0pt'>505.277-2541 fax<br>
 > <a href="mailto:ldowney at lternet.edu">ldowney at lternet.edu</a><u1:p></u1:p><o:p></o:p></span></font></p>
 > 
 > <p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
 > style='font-size:12.0pt'>&nbsp;<o:p></o:p></span><u1:p></u1:p></font></p>
 > 
 > </div>
 > 
 > <div>
 > 
 > <div class=MsoNormal align=center style='text-align:center'><font size=3
 > color=black face="Times New Roman"><span style='font-size:12.0pt;color:windowtext'>
 > 
 > <hr size=2 width="100%" align=center tabindex=-1>
 > 
 > </span></font></div>
 > 
 > <p class=MsoNormal><b><font size=2 color=black face=Tahoma><span
 > style='font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight:bold'>From:</span></font></b><font
 > size=2 color=black face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;
 > color:windowtext'> Dan Higgins [<a href="mailto:higgins at nceas.ucsb.edu">mailto:higgins at nceas.ucsb.edu</a>]
 > <br>
 > <b><span style='font-weight:bold'>Sent:</span></b> Wednesday, July 13, 2005
 > 11:05 AM<br>
 > <b><span style='font-weight:bold'>To:</span></b> Laura L. Downey; Kepler-Dev<br>
 > <b><span style='font-weight:bold'>Subject:</span></b> Kepler actor icons</span></font><o:p></o:p></p>
 > 
 > </div>
 > 
 > <u1:p></u1:p>
 > 
 > <p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
 > style='font-size:12.0pt'><u1:p>&nbsp;</u1:p><o:p></o:p></span></font></p>
 > 
 > <p class=MsoNormal><tt><font size=2 color=black face="Courier New"><span
 > style='font-size:10.0pt'>Laura,</span></font></tt><font size=2
 > face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><br>
 > <br>
 > <tt><font face="Courier New">&nbsp;&nbsp;&nbsp; In out continuing discussion of
 > Kepler actor icons, take a look at the workflow below (from an example from
 > Edward Lee about how to handle nested loops). This is an example of some more
 > interesing icons that are already in PTII and Keper (rather than the default
 > blue triangle). In particular, the SequenceToArray actually shows the process
 > of putting tokens into an array and the ArrayToSequence the inverse. More
 > interestingly, the number '5' on the icons is a parameter of the actor and it
 > is 'dynamic', i.e. it changes as the parameter is changed, avoiding the need to
 > open the actor! (This also occurs for the Repeat actor, which has an icon that
 > depicts its function and shows a dynamic parameter.)</font></tt><br>
 > <br>
 > <tt><font face="Courier New">Dan</font></tt><br>
 > <br>
 > <br>
 > </span></font><img border=0 width=575 height=294 id="_x0000_i1025"
 > src="cid:image001.jpg at 01C587A4.43BD1A60"><br>
 > <br>
 > <br>
 > <o:p></o:p></p>
 > 
 > <u1:p></u1:p><pre><font size=2 color=black face="Courier New"><span
 > style='font-size:10.0pt'>-- <u1:p></u1:p><o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>*******************************************************************<u1:p></u1:p><o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>Dan Higgins &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a
 > href="mailto:higgins at nceas.ucsb.edu">higgins at nceas.ucsb.edu</a><u1:p></u1:p><o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'><a
 > href="http://www.nceas.ucsb.edu/">http://www.nceas.ucsb.edu/</a>&nbsp;&nbsp;&nbsp; Ph: 805-893-5127<u1:p></u1:p><o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>National Center for Ecological Analysis and Synthesis (NCEAS) <u1:p></u1:p><o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>Marine Science Building - Room 3405<u1:p></u1:p><o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>Santa Barbara, CA 93195<u1:p></u1:p><o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>*******************************************************************<u1:p></u1:p><o:p></o:p></span></font></pre>
 > 
 > <p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
 > style='font-size:12.0pt'><br>
 > <br>
 > <br>
 > <o:p></o:p></span></font></p>
 > 
 > <pre><font size=2 color=black face="Courier New"><span style='font-size:10.0pt'>-- <o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>*******************************************************************<o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>Dan Higgins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;<a
 > href="mailto:higgins at nceas.ucsb.edu">higgins at nceas.ucsb.edu</a><o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'><a
 > href="http://www.nceas.ucsb.edu/">http://www.nceas.ucsb.edu/</a>&nbsp;&nbsp;&nbsp; Ph: 805-893-5127<o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>National Center for Ecological Analysis and Synthesis (NCEAS) <o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>Marine Science Building - Room 3405<o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>Santa Barbara, CA 93195<o:p></o:p></span></font></pre><pre><font
 > size=2 color=black face="Courier New"><span style='font-size:10.0pt'>*******************************************************************<o:p></o:p></span></font></pre></div>
 > 
 > </body>
 > 
 > </html>
 > _______________________________________________
 > Kepler-dev mailing list
 > Kepler-dev at ecoinformatics.org
 > http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev



More information about the Kepler-dev mailing list